Installing and Configuring PAS for Windows

This topic describes how to install and configure the Pivotal Application Service (PAS) for Windows tile. The PAS for Windows tile installs Windows cells on your PCF deployment.

Step 1: Confirm Shared PAS Tile Settings

There are two settings in the Pivotal Application Service tile that affect the Windows cells installed by the PAS for Windows tile. Configure these settings as desired:

  • In the Networking section, if you select the Disable SSL certificate verification for this environment checkbox, SSL certificate verification is disabled for Windows cells.
  • In the System Logging section, if you configure an external syslog aggregator, logs are drained from Windows cells as well as non-Windows cells.

Step 2: Install the Tile

  1. Download the Pivotal Application Service for Windows product file from the product page of Pivotal Network.

  2. From the same Pivotal Network page, download the PAS for Windows File System Injector tool for your workstation OS, Windows, Linux, or Mac. The Injector tool is an executable binary winfs-injector that adds the Windows Server container base image into the product file. This step requires internet access and can take up to 20 minutes. Note that you will need the git and tar (BSD) executables on your %PATH% in order in order to run the winfs-injector. Note, to use the injector on a Windows machine, winfs-injector.exe, the included utility, tar.exe, must be copied to a folder in your %PATH%. For example, C:\Windows.

  3. Run winfs-injector with the following options, replacing PAS-WINDOWS-DOWNLOADED.pivotal with the path to the downloaded PAS for Windows product file and PAS-WINDOWS-INJECTED.pivotal with a desired output path for the importable product file:

    $ winfs-injector --input-tile PAS-WINDOWS-DOWNLOADED.pivotal \
    --output-tile PAS-WINDOWS-INJECTED.pivotal
    For troubleshooting the winfs-injector, see PAS for Windows File System Injector Troubleshooting.

  4. Navigate to the Ops Manager Installation Dashboard and click Import a Product.

  5. Select the importable PAS-WINDOWS-INJECTED.pivotal file on your workstation. PAS for Windows appears in the product list under Import a Product.

  6. Click + under the PAS for Windows product listing to add it to your staging area.

Step 3: Configure the Tile

  1. Click the newly added PAS for Windows tile.

    Pcf windows tile orange

  2. Click Assign AZs and Networks or Assign Networks. The name of the section varies depending on your IaaS.

  3. Assign your AZs and networks and click Save.

  4. Click VM Options.

    Vm options

  5. Specify how you would like to manage the password for the user called “Administrator” for your Windows VMs.

    • The default option is to Use the Windows default password, which randomizes the password for this user and the password is not retrievable by an operator.
    • Set the password will set the same password for the user called “Administrator” for every Windows cell; this can be used to access any Windows cell (e.g. RDP sessions).
  6. (Optional) Select the BETA: Enable BOSH-native SSH support on all VMs checkbox to start the Microsoft beta port of the OpenSSH daemon on port 22 on all VMs. Users will be able to SSH onto Windows VMs with the bosh ssh command, and enter a CMD terminal as an administrator user. They can then run powershell.exe to start a PowerShell session.

    Note: This feature is beta and not considered production-ready.

  7. (Optional) If you want all VMs to support connection through Remote Desktop Protocol (RDP), click Enable Remote Desktop Protocol.

  8. (Optional) If you want to configure a Key Management Service (KMS) that your volume-licensed Windows cell can register with, perform the following steps:

    1. Click Enable
    2. For the Host field, enter the KMS hostname.
    3. For the Port field, enter the port number. The default port number is 1688.

    The enable KMS text fields: host and port

  9. (Optional) To deploy your PAS for Windows application workloads to an isolation segment, click Application Containers and perform the steps in the Assign a Tile to an Isolation Segment section below.

  10. (Optional) To configure Windows cells to send Windows Event logs to an external syslog server, click System Logging and perform the steps in the Send Cell Logs to a Syslog Server section.

  11. Click Errands. Pivotal recommends that you set the Install HWC Buildpack Errand to On. This ensures that you receive the most up-to-date HWC Buildpack.

    Errands hwc

  12. Click Save.

Step 4: Configure Tile Resources

To configure your tile resources, perform the following steps:

  1. Navigate to the Resource Config pane of the PAS for Windows tile.
  2. Use the drop-down menus to configure Windows Diego Cell. For more information, see Disk Size of Windows Diego Cells.
  3. Click Save.

Note: Provision your Master Compilation Job with the minumum disk space for your IaaS as follows:
• AWS: 128 GB
• Azure: 100 GB
• GCP: 100 GB
• vSphere: 128 GB

Disk Size of Windows Diego Cells

Before configuring the disk size of your Windows Diego cells, review the information below:

  • Windows stemcells v1709.13 and later in the 1709 line support ephemeral disks. If your PAS for Windows deployment is based on one of these stemcells, the recommended disk size for your Windows Diego cells is as follows:

    IaaS Disk size of Windows Diego cell
    AWS 100 GB
    Azure 150 GB
    GCP 150 GB
    vSphere 100 GB

    Note: If you use vSphere, you must create your own stemcell. The default root disk size of Windows stemcell v1709.13 and later in the 1709 line is 30 GB. Pivotal recommends setting the root disk size of your Windows stemcell for vSphere to 30 GB. For more information, see Creating a vSphere Windows Stemcell.

  • Windows stemcells v1709.5 through v1709.12 do not support ephemeral disks. The size of the root disk of your stemcell determines the minimum root disk size of any Windows VM that the BOSH Director can create from that stemcell. If your PAS for Windows deployment is based on one of these stemcells, ensure that Windows Diego Cell has a minimum disk size according to the table below.

    IaaS Disk size of Windows stemcell v1709.5-v1709.12
    AWS 128 GB
    Azure 30 GB
    GCP 100 GB
    vSphere Recommended 128 GB+

    Note: Because you create your own stemcell on vSphere, you can control its root disk size.

Step 5: Upload the Stemcell

  1. On the Ops Manager Installation Dashboard, in Pivotal Application Service for Windows, click on Missing Stemcell. You will be taken to the Stemcell Library.

  2. Retrieve the stemcell that you downloaded or created in Downloading or Creating a Windows Stemcell.

  3. Follow the steps in Importing and Managing Stemcells to upload the Windows stemcell to Pivotal Application Service for Windows.

Step 6: Deploy the Tile

  1. Return to the Ops Manager Installation Dashboard and click Apply Changes to install the PAS for Windows tile.

Step 7: (Optional) Create More Tiles

If you want to run Windows cells in multiple isolation segments, you must create and configure additional PAS for Windows tiles. See Windows Cells in Isolation Segments for how to do this.

Create a pull request or raise an issue on the source for this page in GitHub