Veeam Home | Support | Downloads
Veeam FastSCP 1.0 for Microsoft Azure

Veeam Help Center  > User Guide >  Requirements > System Requirements

System Requirements

Previous page Next page Print this Topic

Table of contents

Make sure that your environment meets the necessary system requirements.

Veeam FastSCP Console

The machine where you want to install Veeam FastSCP for Microsoft Azure must meet the following requirements:

Specification

Requirement

Hardware

CPU: modern x86-64 processor (2 cores or vCPUs recommended).

Memory: 2 GB RAM.

Disk Space: 50 MB for product installation.

Network: 1 Mbps or faster. High latency and reasonably unstable links are supported. Internet connection is required*.

OS

64-bit versions of the following operating systems are supported:

Microsoft Windows Server 2012 R2

Microsoft Windows Server 2012

Microsoft Windows Server 2008 R2 SP1

Microsoft Windows Server 2008 SP2

Microsoft Windows 10

Microsoft Windows 8.x

Microsoft Windows 7 SP1

Software

The following software must be installed:

Microsoft .NET Framework 4.0

Microsoft PowerShell 2.0 or later  (included in supported Windows versions). Latest PowerShell 5.0 support is experimental.

*If you connect to the Internet through a proxy server, make sure that winhttp proxy settings are properly configured on the machine. For details on configuring a proxy, see https://technet.microsoft.com/nl-nl/library/cc731131%28v=ws.10%29.aspx.

Azure VM

Azure VM that you plan to connect to Veeam FastSCP for Microsoft Azure must meet the following requirements:

Specification

Requirement

OS

Both 64-bit and 32-bit (where applicable) versions of the following operating systems are supported:

Microsoft Windows Server 2012 R2

Microsoft Windows Server 2012

Microsoft Windows Server 2008 R2 SP1

Microsoft Windows Server 2008 SP2

Microsoft Windows 10

Microsoft Windows 8.x

Microsoft Windows 7 SP1

Software

The following software must be installed and configured:

Microsoft PowerShell 2.0 or later (included in supported Windows versions). Latest PowerShell 5.0 support is experimental.

Windows Remote Management (WinRM) and PowerShell Remoting must be enabled and configured. You can use HTTP or HTTPS connection for WinRM.
 
For details on setting up Azure VM endpoints for PowerShell remoting, see How to Set Up Endpoints to a Virtual Machine. For details on configuring WinRM for HTTPS, see https://support.microsoft.com/en-us/kb/2019527.

Note: Starting from April 26, 2013 Azure Update, PowerShell remoting can be enabled for Windows VMs during the provisioning process in the Windows Azure Management Portal. This option is available when you create a VM from the gallery.

Table of contents