> [!CAUTION]
> **Note:** Cloud Deployment Manager reaches end of support on March 31, 2026. For more information, see [Cloud Deployment Manager deprecation](https://docs.cloud.google.com/deployment-manager/docs/deprecations.md.txt).
>
> To automate the deployment of a single-node SAP MaxDB system on Windows Server
> on Google Cloud, contact
> [Cloud Customer Care](https://cloud.google.com/support).

This deployment guide shows you how to deploy and connect to a Compute Engine
virtual machine (VM) that is ready for the installation of SAP MaxDB on a
Windows Server operating system.

The instructions in this guide use
[Cloud Deployment Manager](https://docs.cloud.google.com/deployment-manager/docs/fundamentals.md.txt)
to deploy and configure the VM, the Windows Server operating system, and the
required disk volumes for SAP MaxDB.

For details on planning your deployment, see the
[SAP MaxDB planning guide](https://docs.cloud.google.com/sap/docs/sap-maxdb-planning-guide.md.txt).

## Prerequisites


If you require your SAP workload to run in compliance with data residency, access control, support
personnel, or regulatory requirements, then you must create the required
Assured Workloads folder. For more information,
see [Compliance and sovereign controls
for SAP on Google Cloud](https://docs.cloud.google.com/sap/docs/compliance-and-sovereign-controls).

If you do not already have a Google Cloud project with billing enabled, you must
create one before you can deploy a VM for your SAP MaxDB installation.

To create a project:

## Configuring the `gcloud` command environment

These instructions use
[Cloud Shell](https://docs.cloud.google.com/shell/docs.md.txt) to enter `gcloud` commands that deploy or configure
your Google Cloud resources. Cloud Shell is accessed through the
Google 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
[Google Cloud CLI](https://docs.cloud.google.com/sdk/docs.md.txt).
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 gcloud CLI.

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

Whether you use Cloud Shell or gcloud CLI, you
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:

  ```
  gcloud init
  ```
- Check the settings of your current gcloud configuration:

  ```
  gcloud config list
  ```
- Switch to the required Google Cloud project. Replace
  `PROJECT_ID` with your Google Cloud project ID.

  ```
  gcloud config set project PROJECT_ID
  ```
- Set a default region. Replace `REGION` with a
  Google Cloud region.

  ```
  gcloud config set compute/region REGION
  ```
- Set a default zone. Replace `ZONE` with a
  Google Cloud zone.

  ```
  gcloud config set compute/zone ZONE
  ```
- Create a new configuration. Replace `NAME` with the name
  for the configuration.

  ```
  gcloud config configurations create NAME
  ```

For more information about working with configurations, see
[Managing gcloud CLI configurations](https://docs.cloud.google.com/sdk/docs/configurations.md.txt).

## 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, then 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, Compute Engine instances typically require access to the internet to
download Google Cloud's Agent for SAP. If you are using one of the SAP-certified Linux
images that are available from Google Cloud, then the compute 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 compute instances don't have external IPs.

To set up networking:

### Console

1. In the Google Cloud console, go to the **VPC networks** page.

   [Go to VPC networks](https://console.cloud.google.com/networking/networks/list)
2. Click **Create VPC network**.
3. Enter a **Name** for the network.

   The name must adhere to the
   [naming convention](https://docs.cloud.google.com/compute/docs/naming-resources.md.txt#resource-name-format).
   VPC networks use the Compute Engine naming convention.
4. For **Subnet creation mode** , choose **Custom**.
5. In the **New subnet** section, specify the following configuration parameters for a subnet:
   1. Enter a **Name** for the subnet.
   2. For **Region** , select the [Compute Engine region](https://docs.cloud.google.com/compute/docs/regions-zones.md.txt) where you want to create the subnet.
   3. For **IP stack type** , select **IPv4 (single-stack)** and then enter an IP address range in the [CIDR format](https://wikipedia.org/wiki/Classless_Inter-Domain_Routing), such as `10.1.0.0/24`.

      This is the [primary
      IPv4 range](https://docs.cloud.google.com/vpc/docs/vpc#manually_created_subnet_ip_ranges) for the subnet. If you plan to add more than one subnet, then
      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. Click **Done**.
6. To add more subnets, click **Add subnet** and repeat the preceding steps. You can add more subnets to the network after you have created the network.
7. Click **Create**.

### gcloud

1. Go to Cloud Shell. [Go to Cloud Shell](https://console.cloud.google.com/?cloudshell=true)

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

   ```
   gcloud compute networks create NETWORK_NAME --subnet-mode custom
   ```

   Replace `NETWORK_NAME` with the name of the new network. The
   name must adhere to the
   [naming convention](https://docs.cloud.google.com/compute/docs/naming-resources.md.txt#resource-name-format).
   VPC networks use the Compute Engine naming convention.

   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](https://docs.cloud.google.com/vpc/docs/vpc.md.txt#subnet-ranges).
3. Create a subnetwork, and specify the region and IP range:

   ```
   gcloud compute networks subnets create SUBNETWORK_NAME \
       --network NETWORK_NAME --region REGION --range RANGE
   ```

   Replace the following:
   - `SUBNETWORK_NAME`: the name of the new subnetwork
   - `NETWORK_NAME`: the name of the network you created in the previous step
   - `REGION`: the [region](https://docs.cloud.google.com/compute/docs/regions-zones.md.txt) where you want the subnetwork
   - `RANGE`: the IP address range, [specified in CIDR format](https://wikipedia.org/wiki/Classless_Inter-Domain_Routing), such as `10.1.0.0/24`

     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 compute instances without public IP addresses, then you need to use network
address translation (NAT) to enable the instances to access the internet. Use Cloud NAT, a
Google Cloud distributed, software-defined managed service that lets the compute instances send outbound
packets to the internet and receive any corresponding established inbound response packets.
Alternatively, you can set up a separate compute instance as a NAT gateway.

> [!IMPORTANT]
> **Key Point:** When you configure Cloud NAT, specify at least 160 as the minimum number of ports per compute instance. Certain operating system updates run concurrent processes that might exceed the Cloud NAT default for the number of ports, which can result in activation or download errors.
>
> When you create a Cloud NAT instance, specify the number of ports in the **Minimum
> ports per VM** field under **Advanced configurations** on the Create a NAT gateway page in the
> Google Cloud console.

To create a Cloud NAT instance for your project, see
[Using Cloud NAT](https://docs.cloud.google.com/nat/docs/set-up-network-address-translation).

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

## Deploying a Windows VM for SAP MaxDB with Deployment Manager

The following instructions use Deployment Manager to deploy a
VM instance with Windows and all of the persistent disks that SAP
MaxDB 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](https://console.cloud.google.com/dm/deployments)
page in the Google 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](https://docs.cloud.google.com/deployment-manager/docs/deployments.md.txt#create-policy).

### Deployment procedure

1. Open the Cloud Shell.

   [Go to the Cloud Shell](https://console.cloud.google.com/?cloudshell=true)
2. Download the template.yaml configuration file template to your working
   directory by entering the following command in the Cloud Shell:

   ```
   wget https://storage.googleapis.com/cloudsapdeploy/deploymentmanager/latest/dm-templates/sap_maxdb-win/template.yaml
   ```
3. Optionally, rename the template.yaml file to identify the configuration it
   defines. For example, maxdb-win-2016.yaml.

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

   To open the Cloud Shell code editor, click the pencil icon in the
   upper right corner of the 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 MaxDB will be installed. The name must be 13 characters or less and be specified in lowercase letters, numbers, or hyphens. |
   | instanceType | String | The type of Compute Engine [virtual machine](https://docs.cloud.google.com/compute/docs/machine-types) on which SAP MaxDB will be installed. Specify a machine type with two or more vCPUs. For example, \`n1-standard-4\`. If you are running SAP MaxDB on the same VM as SAP NetWeaver, select a machine type that includes enough CPUs and memory to support both systems. See the [SAP NetWeaver Planning Guide](https://docs.cloud.google.com/sap/docs/netweaver-planning-guide.md.txt#machine_types). |
   | zone | String | The zone in which you are deploying your SAP MaxDB. 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 MaxDB. To specify an image family, add the prefix `family/` to the family name. For example, `family/windows-2016`. To specify a specific image, specify only the image name. For the list of available image families, see the [Images](https://console.cloud.google.com/compute/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](https://docs.cloud.google.com/compute/docs/images.md.txt) page in the Compute Engine documentation. |
   | maxdbRootSize | Integer | The size in GB of **MaxDB (D:)**, which is the root directory of the database instance. The minimum and default values for maxdbRootSize are both 8 GB. |
   | maxdbDataSize | Integer | The size of **MaxDB Data (E:)**, which holds the database data files. The minimum and default values for maxdbDataSize are both 30 GB. |
   | maxdbLogSize | Integer | The size of **MaxDB Log (L:)**, which holds the database transaction logs. The minimum and default values for maxdbLogSize are both 8 GB. |
   | maxdbBackupSize | Integer | The size of the **Backup (X:)** volume. This property is optional. If set to 0 or omitted, no disk is created. |
   | maxdbDataSSD | boolean | Specifies whether the data drive uses an SSD persistent disk (\`Yes\`) or an HDD persistent disk (\`No\`). \`Yes\` is the default. |
   | maxdbLogSSD | boolean | Specifies whether the log drive uses an SSD persistent disk (\`Yes\`) or an HDD persistent disk (\`No\`). \`Yes\` is the default. SSD is recommended for the log drive. |
   | usrsapSize | Integer | Required only if you are installing SAP MaxDB to run with SAP NetWeaver on the same VM instance. In the deployed VM, this volume is labeled **SAP (S:)**. |
   | swapSize | Integer | Required only if you are installing SAP MaxDB to run with SAP NetWeaver on the same VM instance. In the deployed VM, this volume is labeled **Pagefile (P:)**. |

   The following configuration file creates a VM that is
   configured to run both the SAP MaxDB database server and SAP NetWeaver. The
   configuration file directs Deployment Manager to deploy
   an n1-standard-16 virtual that is running a Windows Server 2016 operating
   system. The VM includes all of the directories that are required to run SAP
   MaxDB with NetWeaver.

   ```
   resources:
   - name: sap_maxdb-win
     type: https://storage.googleapis.com/cloudsapdeploy/deploymentmanager/latest/dm-templates/sap_maxdb-win/sap_maxdb-win.py
     #
     # 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: https://storage.googleapis.com/cloudsapdeploy/deploymentmanager/202103310846/dm-templates/sap_maxdb-win/sap_maxdb-win.py
     #
     properties:
       instanceName: ex-vm-maxdb-win
       instanceType: n1-standard-16
       zone: us-central1-f
       subnetwork: example-sub-network
       windowsImage: family/windows-2016
       windowsImageProject: windows-cloud
       maxdbRootSize: 10
       maxdbDataSize: 50
       maxdbLogSize: 30
       maxdbBackupSize: 100
       maxdbDataSSD: Yes
       maxdbLogSSD: Yes
       usrsapSize: 15
       swapSize: 24
   ```
6. Deploy the VM:

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

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

### Verifying deployment

To verify deployment, you check the deployment logs in Cloud Logging.

#### Check the logs

1. In the Google Cloud console, open Cloud Logging to monitor installation
   progress and check for errors.

   > [!NOTE]
   > **Note:** You might incur costs when completing this step in Cloud Logging. For more information, see [Cloud Logging pricing](https://cloud.google.com/stackdriver/pricing).

   [Go to Cloud Logging](https://console.cloud.google.com/logs/query)
2. Filter the logs:

   1. In the **Logs Explorer** page, go to the **Query** pane.

   2. From the **Resource** drop-down menu, select **Global** , and then click
      **Add**.

      If you don't see the **Global** option, then in the query editor, enter
      the following query:

          resource.type="global"
          "Deployment"

   3. Click **Run query**.

3. Analyze the filtered logs:

   - If `"--- Finished"` is displayed, then the deployment processing is complete and you can proceed to the next step.
   - If you see a quota error:

     1. On the IAM \& Admin
        [Quotas](https://console.cloud.google.com/iam-admin/quotas)
        page, increase any of your quotas that do not meet the
        SAP MaxDB requirements that are listed in the

        [SAP MaxDB planning guide](https://docs.cloud.google.com/sap/docs/sap-maxdb-planning-guide.md.txt#pricing-and-quotas).


     2. On the Deployment Manager
        [Deployments](https://console.cloud.google.com/dm/deployments)
        page, delete the deployment to clean up the VMs and persistent
        disks from the failed installation.

     3. Rerun your deployment.

After the SAP MaxDB system deploys, connect to your VM as described in the next
section, [Connecting to your VM](https://docs.cloud.google.com/sap/docs/sap-maxdb-deployment-windows.md.txt#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 MaxDB.](https://docs.cloud.google.com/static/sap/docs/images/maxdb-disk-drives-win.png)

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

1. Correct the error.
2. On the [Deployments](https://console.cloud.google.com/dm/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

After you create a Windows VM, you must generate a password for the VM before
you can connect to it.

1. Go to the **VM instances** page.

   [Go to VM instances](https://console.cloud.google.com/compute/instances)
2. Open the VM instance details page by clicking the name of the VM that you
   just created.

   ![VM name on the VM instances page.](https://docs.cloud.google.com/static/sap/docs/images/maxdb-select-win-vm.png)
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.

   ![Set Windows password by clicking button on VM instance details page.](https://docs.cloud.google.com/static/sap/docs/images/maxdb-set-win-password.png)

### Using RDP

If your [firewall rule](https://docs.cloud.google.com/sap/docs/sap-maxdb-deployment-windows.md.txt#adding_firewall_rules) 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](https://docs.cloud.google.com/sap/docs/sap-maxdb-deployment-windows.md.txt#using_powershell).

Connect to the remote desktop on Windows instances by manually connecting
through the Windows Remote Desktop Connection client or a third-party client:

1. If you don't already have an RDP client, install one now. For information from Microsoft about available RDP clients, see [Remote Desktop clients](https://docs.microsoft.com/en-us/windows-server/remote/remote-desktop-services/clients/remote-desktop-clients).
2. Get your Windows VM's external IP address. To find the VM IP address, you can use either of the following methods:
   - In the Google Cloud console, go to the [VM Instances page](https://console.cloud.google.com/compute/instances).
   - Use the gcloud CLI to run `gcloud compute
     instances list` to list your VM instances with their external IP addresses.
3. In your RDP client, provide your VM's external IP address as the IP address to connect to.
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](https://docs.cloud.google.com/sap/docs/netweaver-deployment-windows-dm.md.txt#connecting_to_your_vm).

### Using PowerShell

1. If you have not created a username and password on the Windows VM yet, [create your Windows password](https://docs.cloud.google.com/sap/docs/sap-maxdb-deployment-windows.md.txt#generating_passwords).
2. Add a firewall rule or edit your existing firewall rule to open port 5986 on the [Google Cloud network](https://docs.cloud.google.com/compute/docs/networking) where your Windows Server VM is located.
3. On your local workstation, open the PowerShell terminal.
4. Optionally, you can 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](https://msdn.microsoft.com/en-us/powershell/reference/5.1/microsoft.powershell.core/enter-pssession)
   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

## Installing the database

Now that your operating system is configured, you can install your SAP MaxDB
database. MaxDB is typically installed with the SAP product with which it will
be used.

To install SAP MaxDB on your VM:

1. Use RDP or Windows PowerShell to connect to your Windows-based VM.
2. Download the SAP Software Provisioning Manager (SWPM), the SAP product installation media, and MaxDB installation Media according to SAP installation guides.
3. Install your SAP product and SAP MaxDB database according to the SAP installation guides for your SAP product. For additional guidance, see the [SAP MaxDB documentation](https://help.sap.com/viewer/9d62a6d2a95149718db6b65b7ffa2052/113/en-US).

SAP provides additional installation information in [SAP Note 1020175 - FAQ: SAP MaxDB installation, upgrade or applying a patch](https://launchpad.support.sap.com/#/notes/0001020175).

## Validate your installation of Google Cloud's Agent for SAP

After you have deployed a VM and installed your SAP system, validate that
Google Cloud's Agent for SAP is functioning properly.

### Verify that Google Cloud's Agent for SAP is running

To verify that the agent is running, follow these steps:


1. Use RDP to connect to the Compute Engine instance.

2. As an administrator, run the following command from PowerShell:

   ```
   $(Get-Service -Name 'google-cloud-sap-agent' -ErrorAction Ignore).Status
   ```
   If the agent is running, then the status shows `Running`.

   <br />

<br />


<br />

If the agent isn't running, then [restart the agent](https://docs.cloud.google.com/sap/docs/agent-for-sap/latest/operations.md.txt#agent4sap-restart).

<br />

### Verify that SAP Host Agent is receiving metrics


To verify that the infrastructure metrics are collected by
Google Cloud's Agent for SAP and sent correctly to the SAP Host Agent,
follow these steps:

1. In your SAP system, enter transaction `ST06`.
2. 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`

<br />

## Performing post-deployment tasks

Before using your SAP MaxDB instance, we recommend that you perform the
following post-deployment steps:

1. Update your SAP MaxDB software with the latest patches, if available.
2. Install any additional components.
3. Configure and back up your new SAP MaxDB database.

For more information, see [SAP MaxDB Database Administration](https://help.sap.com/viewer/2c2effc99b6746019aeb1af52ad59f5d/113/en-US/1a32c42a0fcf40b5b95ff7040a60aa41.html).