Automated VM deployment for SAP NetWeaver on Windows Server

This guide uses Deployment Manager to deploy all of the required Google Cloud resources to run SAP NetWeaver on Windows Server, including the Compute Engine virtual machine (VM), the Windows Server operating system, and the persistent disks. You define the values for the installation, such as machine type, resource names, disk sizes, and so forth, in a Deployment Manager configuration file template.

If your SAP NetWeaver installation requires more control over the deployment process than the Deployment Manager template provides, see Manual VM deployment for SAP NetWeaver on Windows.

To deploy a VM that is running Linux, see the Linux Deployment Guide.

VM configuration deployed by these instructions

The VM that is deployed by these instructions is for use in a 3-tier configuration, where SAP NetWeaver runs on one VM and the database server runs on another.

To set up a 2-tier configuration, where SAP NetWeaver runs on the same VM as the database server, you deploy the database server first and create the VM and the required disk drives for both the database server and for SAP NetWeaver at that time. You then install SAP NetWeaver on the same VM as the database server.

For instructions about deploying the VM for a database server, see the database deployment guide for your database server.

Google Cloud resources deployed by these instructions

The Google Cloud resources that are deployed by Deployment Manager include:

  • A VM that uses an SAP-certified version of Windows Server.
  • A persistent disk for SAP binaries.
  • A persistent disk for the pagefile.
  • The recommended APIs.

The following instructions use Cloud Shell, but if you prefer, you can use the Cloud SDK in your local terminal instead.

For more details on planning your implementation, see the Planning Guide. For an overview of IT ops for your system, see the Operations Guide.

Creating a project

To create a project:

  1. Sign in to your Google Cloud account. If you're new to Google Cloud, create an account to evaluate how our products perform in real-world scenarios. New customers also get $300 in free credits to run, test, and deploy workloads.
  2. In the Google Cloud Console, on the project selector page, select or create a Google Cloud project.

    Go to project selector

  3. Make sure that billing is enabled for your Cloud project. Learn how to confirm that billing is enabled for your project.

Configuring the gcloud command environment

These instructions use Cloud Shell to enter gcloud commands that deploy or configure your Google Cloud resources. Cloud Shell is accessed through the Cloud Console in your browser.

Cloud Shell runs on a VM that Google Cloud provisions each time you start Cloud Shell. The first time you use Cloud Shell, Google Cloud also creates a persistent $HOME directory for you, which is restored each time you open Cloud Shell.

The provisioned VM includes the latest Cloud SDK, which provides the gcloud command-line interface. Therefore, the gcloud commands that you use in Cloud Shell are the same as those you would use in a locally installed instance of the Cloud SDK.

If you have the Cloud SDK installed, you can issue the gcloud commands that are used in these instructions from your local machine. However, with a locally installed Cloud SDK you must always make sure that you are using the latest version of the Cloud SDK.

Whether you use Cloud Shell or Cloud SDK, you can can set and change the properties of your gcloud command environment and save them as a configuration. Configurations are collections of key-value pairs that influence the behavior of the gcloud commands.

Some basic actions you can take with a configuration in Cloud Shell include:

  • Initialize a configuration with gcloud init.

  • Check the settings of your current gcloud configuration with gcloud config list.

  • Change the Google Cloud project you are working in with gcloud config set project [PROJECT_ID] where [PROJECT_ID] represents your Google Cloud project.

  • Set a default region with gcloud config set compute/region [REGION] where [REGION] represents a Google Cloud region.

  • Set a default zone with gcloud config set compute/zone [ZONE] where [ZONE] represents a Google Cloud zone.

  • Create a new configuration with gcloud config configurations create [NAME] where [NAME] represents the name for the configuration.

For more information about working with configurations, see Managing Cloud SDK configurations.

Creating a network

For security purposes, create a new network. You can control who has access by adding firewall rules or by using another access control method.

If your project has a default VPC network, don't use it. Instead, create your own VPC network so that the only firewall rules in effect are those that you create explicitly.

During deployment, VM instances typically require access to the internet to download Google's monitoring agent. If you are using one of the SAP-certified Linux images that are available from Google Cloud, the VM instance also requires access to the internet in order to register the license and to access OS vendor repositories. A configuration with a NAT gateway and with VM network tags supports this access, even if the target VMs do not have external IPs.

To set up networking:

  1. Go to Cloud Shell.

    Go to Cloud Shell

  2. To create a new network in the custom subnetworks mode, run:

    gcloud compute networks create [YOUR_NETWORK_NAME] --subnet-mode custom

    where [YOUR_NETWORK_NAME] is the name of the new network. The network name can contain only lowercase characters, digits, and the dash character (-).

    Specify --subnet-mode custom to avoid using the default auto mode, which automatically creates a subnet in each Compute Engine region. For more information, see Subnet creation mode.

  3. Create a subnetwork, and specify the region and IP range:

    gcloud compute networks subnets create [YOUR_SUBNETWORK_NAME] \
            --network [YOUR_NETWORK_NAME] --region [YOUR_REGION] --range [YOUR_RANGE]


    • [YOUR_SUBNETWORK_NAME] is the new subnetwork.
    • [YOUR_NETWORK_NAME] is the name of the network you created in the previous step.
    • [REGION] is the region where you want the subnetwork.
    • [YOUR_RANGE] is the IP address range, specified in CIDR format, such as If you plan to add more than one subnetwork, assign non-overlapping CIDR IP ranges for each subnetwork in the network. Note that each subnetwork and its internal IP ranges are mapped to a single region.
  4. Optionally, repeat the previous step and add additional subnetworks.

Setting up a NAT gateway

If you need to create one or more VMs without public IP addresses, you need to use network address translation (NAT) to enable the VMs to access the internet. Use Cloud NAT, a Google Cloud distributed, software-defined managed service that lets VMs send outbound packets to the internet and receive any corresponding established inbound response packets. Alternatively, you can set up a separate VM as a NAT gateway.

To create a Cloud NAT instance for your project, see Using Cloud NAT.

After you configure Cloud NAT for your project, your VM instances can securely access the internet without a public IP address.

Adding firewall rules

By default, incoming connections from outside your Google Cloud network are blocked. To allow incoming connections, set up a firewall rule for your VM. Firewall rules regulate only new incoming connections to a VM. After a connection is established with a VM, traffic is permitted in both directions over that connection.

You can create a firewall rule to allow access to specified ports, or to allow access between VMs on the same subnetwork.

Create firewall rules to allow access for such things as:

  • The default ports used by SAP NetWeaver, as documented in TCP/IP Ports of All SAP Products.
  • Connections from your computer or your corporate network environment to your Compute Engine VM instance. If you are unsure of what IP address to use, talk to your company's network admin.
  • Communication between VMs in a 3-tier, scaleout, or high-availability configuration. For example, if you are deploying a 3-tier system, you will have at least 2 VMs in your subnetwork: the VM for SAP NetWeaver, and another VM for the database server. To enable communication between the two VMs, you must create a firewall rule to allow traffic that originates from the subnetwork.
  • RDP connections to your VM instance through port 3389.
  • PowerShell connections to your VM instance through port 5986.

To create a firewall rule:

  1. In the Cloud Console, go to the Firewall Rules page.

    Open Firewall Rules page

  2. At the top of the page, click Create firewall rule.

    • In the Network field, select the network where your VM is located.
    • In the Targets field, select All instances in the network.
    • In the Source filter field, select one of the following:
      • IP ranges to allow incoming traffic from specific IP addresses. Specify the range of IP addresses in the Source IP ranges field.
      • Subnets to allow incoming traffic from a particular subnetwork. Specify the subnetwork name in the following subnets field. You can use this option to allow access between the VMs in a 3-tier or scaleout configuration.
    • In the Protocols and ports section, select Specified protocols and ports and specify tcp:[PORT_NUMBER];.
  3. Click Create to create your firewall rule.

Deploying a VM for SAP NetWeaver on Windows with Deployment Manager

The following instructions use Google Cloud Console, Cloud Shell, and Deployment Manager to deploy a VM instance with Windows Server and all of the persistent disks that SAP NetWeaver requires.

About Deployment Manager

In these instructions, you define the resource options for your installation in a Deployment Manager configuration file template.

Deployment Manager treats all of the resources that are created for your SAP system as a single entity called a deployment. You can view and work with all of the deployments for your project on the Deployments page in the Cloud Console.

Be aware of the following behaviors when using Deployment Manager:

  • Deleting a deployment deletes all of the resources associated with the deployment, including the VMs, the persistent disks, and any SAP systems that are installed on the VM.
  • By default, Deployment Manager uses the ACQUIRE resource creation policy. If you specify a VM name that is already in use by another VM in your project, Deployment Manager doesn't create a new VM, but instead adds the existing VM to your new deployment. If your original VM was created by a previous run of Deployment Manager, the VM is associated with two deployments.

    If you then delete the new deployment, the acquired VM is deleted from the deployment that originally created it. To avoid such a scenario, either set the Deployment Manager resource policy to CREATE, or make sure that you use unique resource names in your new deployment.

    For information about the policies you can use while creating resources with Deployment Manager and how to specify them, see the Deployment Manager documentation.

Deployment procedure

  1. Open Cloud Shell.

    Go to Cloud Shell

  2. Download the template.yaml configuration file template to your working directory:

  3. Optionally, rename the template.yaml file to identify the configuration it defines. For example, nw-windows-2016.yaml.

  4. Open the template.yaml file in Cloud Shell code editor.

    To open Cloud Shell code editor, click the pencil () icon in the upper right corner of Cloud Shell terminal window.

  5. In the template.yaml file, update the following property values by replacing the brackets and their contents with the values for your installation.

    Property Data type Description
    type String

    Specifies the location, type, and version of the Deployment Manager template to use during deployment.

    The YAML file includes two type specifications, one of which is commented out. The type specification that is active by default specifies the template version as latest. The type specification that is commented out specifies a specific template version with a timestamp.

    If you need all of your deployments to use the same template version, use the type specification that includes the timestamp.

    instanceName String The name of the VM instance on which SAP NetWeaver is installed. The name must be 13 characters or less and be specified in lowercase letters, numbers, or hyphens. Use a name that is unique within your project.
    instanceType String The type of Compute Engine virtual machine that you need. If you need a custom VM type, specify a small predefined VM type and, after deployment is complete, customize the VM as needed.
    zone String The zone in which you are deploying SAP NetWeaver. It must be in the same region that you selected for your subnetwork.
    subnetwork String The name of the subnetwork that you created in a previous step. If you are deploying to a shared VPC, specify this value as [SHAREDVPC_PROJECT]/[SUBNETWORK]. For example, myproject/network1.
    windowsImage String The name of the Windows operating-system image or image family that you are using with SAP NetWeaver. To specify an image family, add the prefix family/ to the family name. For example, family/windows-2012-r2. For the list of available image families, see the Images page in the Cloud console.
    windowsImageProject String The Google Cloud project that contains the image you are going to use. This project might be your own project or a Google Cloud image project, such as windows-cloud. For a list of Google Cloud image projects, see the Images page in the Compute Engine documentation.
    usrsapSize Integer The size of the SAP binaries disk. The minimum size is 8 GB. In the deployed VM, this volume is labeled SAP (S:).
    swapSize Integer The size of the pagefile volume. The minimum size is 1 GB. In the deployed VM, this volume is labeled Pagefile (P:).
    networkTag String Optional. A network tag that represents your VM instance for firewall or routing purposes. If you specify publicIP: No and do not specify a network tag, be sure to provide another means of access to the internet.
    publicIP Boolean Optional. Determines whether a public IP address is added to your VM instance. The default is Yes.

    The following configuration file creates a VM that is configured to run SAP NetWeaver. The configuration file directs Deployment Manager to deploy the n1-standard-16 VM that is running a Windows Server 2016 operating system. The VM includes all of the directories that are required in order to run SAP NetWeaver.

    - name: sap-nw-win
      # By default, this configuration file uses the latest release of the deployment
      # scripts for SAP on Google Cloud.  To fix your deployments to a specific release
      # of the scripts, comment out the type property above and uncomment the type property below.
      # type:
        instanceName: ex-vm-nw-win
        instanceType: n1-standard-16
        zone: us-central1-f
        subnetwork: example-sub-network-sap
        windowsImage: family/windows-2016
        windowsImageProject: windows-cloud
        usrsapSize: 15
        swapSize: 24
  6. Deploy the VM:

    gcloud deployment-manager deployments create [DEPLOYMENT-NAME] --config [TEMPLATE-NAME].yaml

    The above command invokes Deployment Manager, which deploys the VM, all according to the specifications in your template.yaml file. The process may take a few minutes. To check the progress of your deployment, follow the steps in the next section.

  7. After the VM instance deploys, if you need Compute Engine to save the boot disk in the event the VM instance is deleted:

    1. Go to VM instances in the Cloud Console.
    2. Open VM instance details for your VM instance by clicking the name of the VM instance.
    3. Under Boot disk and local disks, clear Delete boot disk when instance is deleted.

Verifying deployment

The following steps use Cloud Logging, which might incur charges. For more information, see Cloud Logging pricing.

  1. Open Cloud Logging to check for errors and monitor the progress of the installation.

    Go to Logging

  2. On the Resources tab, select Global as your logging resource. If INSTANCE DEPLOYMENT COMPLETE is displayed for a VM, Deployment Manager processing is complete for the VM.

    Cloud Logging display.

  3. After the VM instance deploys, connect to your VM as described in Connecting to your VM to confirm that all of the required data volumes exist and that they have the expected capacities. The Pagefile drive should be almost full.

    Disk drives created by Deployment Manager for NetWeaver.

If any of the validation steps show that the installation failed:

  1. Correct the error.
  2. On the Deployments page, delete the deployment to clean up the VMs and persistent disks from the failed installation.
  3. Rerun your deployment.

Connecting to your VM

To connect to a Windows-based VM, you must first generate a password for the VM. You can then connect to the VM using RDP or PowerShell.

Generating passwords

  1. Go to the VM instances page.


  2. Click the name of the VM instance for which you need a new password.

  3. On the instance details page, click the Set Windows Password button. A password is generated for you. Copy the password and store it in a secure place.

Using RDP

If you have defined a firewall rule that allows access on port 3389, you can use RDP to connect to a Windows instance and start a Remote Desktop session. Alternatively, you can connect to Windows instances using the PowerShell terminal.

Connect to the remote desktop on Windows instances using one of the following methods:

  • Use a Chrome browser that has the Chrome RDP for Google Cloud extension installed and establish an RDP connection from the Cloud Console.
  • Download the RDP file and manually connect through the Windows Remote Desktop Connection client or a third-party client.


  1. If the Chrome RDP for Google Cloud extension is not installed already in your Chrome browser, install it now.

    To check for the Chrome RDP for Google Cloud Platform extension, enter chrome://extensions/ in your browser address bar and look for the extension under Chrome Apps on the Extensions page of your Chrome browser.

  2. Go to the VM instances page in the in the Cloud Console.


  3. Click the RDP button next to the instance that you want to connect to. A new browser window opens with the Chrome RDP for Google Cloud extension.

  4. Enter your username and password. If this is your first time connecting to this instance, or if you have forgotten your password, create or reset your Windows password.

  5. Click OK to connect.

RDP Client

  1. Install an RDP client. If you don't have a preference, install the Chrome RDP for Google Compute Engine Engine extension.

  2. Get your Windows VM's external IP address. Go to the VM instances page in the Cloud Console or run gcloud compute instances list to see a list of your instances with their external IP values.

  3. In your RDP client, provide your VM's external IP address as the IP address to connect to. For example, in the Chrome RDP extension, you would enter the IP address in the following format:

    Screenshot of the instance creation window with the required options set

  4. Enter your sign-in information and leave the Domain field blank. If this is your first time connecting to this VM, or if you have forgotten your password, create or reset your Windows password.

    Screenshot of the instance creation window with the required options set

Using PowerShell

  1. If you have not created a username and password on the Windows VM yet, create your Windows password.

  2. Add a firewall rule or edit your existing firewall rule to open port 5986 on the VPC network where your Windows Server VM is located.

  3. On your local workstation, open the PowerShell terminal.

  4. Optionally, initialize a variable to hold your user credentials so you do not need to enter them each time you connect to the instance. If you skip this step, you receive a prompt for your username and password later.

    $credentials = Get-Credential
  5. Use the Enter-PSSession command to start a remote PowerShell session and include the flags to use SSL and skip credentials checks.

    Enter-PSSession -ComputerName [IP_ADDRESS] -UseSSL -SessionOption
    (New-PSSessionOption -SkipCACheck -SkipCNCheck) -Credential $credentials

Setting up the database

If you haven't yet deployed your database on Google Cloud, follow the instructions for setting up your database in both the Google Cloud deployment guide for your database, and in the database documentation that is provided by your database vendor.

Google Cloud provides deployment guides for the following SAP-certified databases:

When SAP NetWeaver and the database server are running on different VMs in a 3-tier architecture, make sure that your firewall rules are defined to allow communication between the VMs.

If you used the Google Cloud-provided Windows image that contains SQL Server, you must change the collation to use the SAP collation.

Configuring the Google Cloud Microsoft SQL Server image

If you selected the Google-provided SQL Server Enterprise operating system image when you created your VM, you must configure SQL Server to use the SAP collation (SQL_Latin1_General_CP850_BIN2) so that SQL Server is compatible with SAP systems. The default collation in the Google Cloud-provided SQL Server image is (SQL_Latin1_General_CP1_CI_AS).

To change the collation after the VM is deployed:

  1. Connect to your Windows instance by using either RDP or remote PowerShell.
  2. Sign in to Windows as an admin and stop the MSSQLSERVER service.
  3. Go to the directory that contains the binaries for your SQL Server instance, for example, C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\Binn.
  4. From an elevated command prompt, change the collation by running:

    sqlservr -m -T4022 -T3659 -s"[SQL_SERVER_INSTANCE_NAME]" -q"SQL_Latin1_General_CP850_BIN2"


    • The parameter -m starts the SQL Server instance in single-user mode.
    • The trace flag 4022 forces SQL Server to skip any stored startup procedures.
    • The trace flag 3659 allows all errors to be logged to the SQL Server logs.
    • The parameter -s specifies the name of the SQL Server instance to start. Replace [SQL_SERVER_INSTANCE_NAME] with your SQL Server instance name.
    • The parameter -q rebuilds all databases and objects to the specified SAP collation, without reinstalling the instance or rebuilding system databases.
  5. Restart the SQL Server Service MSSQLSERVER after the collation is changed.

  6. Confirm your change in the most recent SQL Server ERRORLOG or the server's collation properties.

For more information about the configuration of SQL Server for SAP, see:

Installing the Cloud Logging agent

The Cloud Logging agent provides you with a solution for Google Cloud system-activity logging, including operating system events and, if you are using SAP HANA, SAP HANA events. The Cloud Logging agent is an optional but recommended component. See the SAP NetWeaver on Google Cloud operations guide for more information about Google Cloud logging.

To install the Cloud Logging agent in your new VM, see the instructions for Linux and Windows in Installing the agent.

Install the monitoring agent for SAP NetWeaver

The Google Cloud monitoring agent for SAP NetWeaver is required for SAP support of SAP NetWeaver on Google Cloud.

When you install the agent on a Compute Engine VM, the monitoring agent for SAP NetWeaver combines monitoring data from Monitoring and the Compute Engine APIs and provides that data to the SAP Host Agent.

The monitoring agent for SAP NetWeaver is also required when you run SAP NetWeaver on a Bare Metal Solution machine, in which case, the agent does not include data from Monitoring. To install the monitoring agent for SAP NetWeaver on a Bare Metal Solution machine, see Install the monitoring agent for SAP NetWeaver.

Prerequisites for the monitoring agent for SAP NetWeaver

Compute Engine recommends configuring your VM instances to allow full access scopes to all Cloud APIs and using only the IAM permissions of the instance service account to control access to Google Cloud resources. For more information, see Best practices.

If you do limit access to the Cloud APIs, the monitoring agent for SAP NetWeaver requires the following minimum Cloud API access scopes on the host VM instance:

  • Compute Engine: Read Only
  • Stackdriver Monitoring API: Read Only

If you are running SAP NetWeaver on a VM that does not have an external IP address, you must enable Private Google Access on the VM's subnet so that the monitoring agent for SAP NetWeaver can access Google APIs and services.

To enable Private Google Access on a subnet, see Configuring Private Google Access.

Installing the monitoring agent for SAP NetWeaver

To install the monitoring agent for SAP NetWeaver, as an administrator on the host VM, issue the following command:

. { iwr -useb } | iex

After you install SAP NetWeaver and the SAP Host Agent, validate the installation of the monitoring agent for SAP NetWeaver, as described in Validating your installation of the monitoring agent.

For an overview of installation actions, see the Installation overview.

Installing SAP NetWeaver

For instructions on installing SAP NetWeaver on your new VM, see the SAP help portal and the SAP NetWeaver Master Guide.

After you install SAP NetWeaver:

  1. Update the SAP kernel to the minimum supported patch level.

    For details on the supported SAP kernel patch levels, see SAP Note 2456953 - Windows on Google Cloud (IaaS): Adaptation of your SAP License.

  2. Install your permanent SAP NetWeaver license.

    For more information from SAP about managing your SAP NetWeaver licenses, see SAP Licensing Procedure.

Installing the SAP Host Agent

The SAP Host Agent has been enhanced for running on Google Cloud. Ensure that you run at least the minimum SAP Host Agent version required for the Google Cloud environment.

For details, refer to the following SAP Notes:

Validating your installation of the monitoring agent

After you have deployed a VM and installed SAP NetWeaver, validate that Google's monitoring agent is functioning properly with SAP's enhanced monitoring.

Verifying that Google's monitoring agent is running

You can check whether the monitoring agent is running by polling for a health check from the server. Follow these steps:

  1. Use RDP to connect to the VM instance you want to monitor.

  2. In a browser, visit http://localhost:18181/health.

If the monitoring agent is functioning properly, the value for status is UP. For example:


If the monitoring agent isn't running, see the Operations Guide section about restarting Google's monitoring agent.

Verifying that SAP NetWeaver is receiving metrics

To check whether the connection between Google's monitoring agent and SAP NetWeaver works as intended, enter transaction ST06 in your SAP NetWeaver ABAP system. In the overview pane, check the availability and content of the following fields for the correct end-to-end setup of the SAP and Google monitoring infrastructure:

  • Cloud Provider: Google Cloud Platform
  • Enhanced Monitoring Access: TRUE
  • Enhanced Monitoring Details: ACTIVE


This section contains information about how to correct common issues.

Troubleshooting communication problems to the database server

If you are setting up a 3-tier SAP system and having connection issues between your VMs, ensure that you have created a firewall rule to allow traffic between VMs on your subnetwork.

Troubleshooting Google's monitoring agent

To troubleshoot the monitoring agent, see the Operations guide.