In this article, I will share alternative methods of deploying replicated Platform Services Controller Node (PSCs) using the VCSA 6.0 appliance. Take a look at the various deployment methods below and their respective instructions for more details. If you are deploying using one of the scripts below, you will need to extract the contents of the VCSA ISO. If you are deploying to Workstation/Fusion, you will need to extract the VCSA ISO and add the .ova extension to the following file VMware-VCSA-all-6.0.0-2562643->vcsa->vmware-vcsa before deploying.
Disclaimer: Though these alternative deployment options work, they are however not officially supported by VMware. Please use at your own risk.

Deploying to an existing vCenter Server using ovftool (shell script)

I have created a shell script called which requires using ovftool 4.1 (included in the VCSA ISO) to specify the appropriate OVF "guestinfo" properties for a replicated PSC deployment. You will need to edit the script and modify several variables based on your environment.

Here is an example of executing the script:


Deploying to an ESXi host using ovftool (shell script)

I have created a shell script called which requires using ovftool 4.0 or greater to specify the appropriate OVF "guestinfo" properties for a replicated PSC deployment. You will need to edit the script and modify several variables based on your environment. The behavior of this script is similar to the one above, except you are deploying directly to an ESXi host.

Deploying to an existing vCenter Server using ovftool (PowerCLI)

I have created a PowerCLI script called Deployment-PSC-Replication.ps1 which uses ovftool and specifies the appropriate OVF "guestinfo" properties for a replicated PSC deployment. You will need to edit the script and modify several variables based on your environment.

Deploying to VMware Fusion & Workstation

To properly deploy the new VCSA 6.0, the proper OVF properties MUST be set prior to the booting of the VM. Since VMware Fusion and Workstation do not support OVF properties, you will need to manually deploy the VCSA, but not power it on. Once the deployment has finished, you will need to add the following entries to the VCSA's VMX file and replace it with your environment settings. Once you have saved your changes, you can then power on the VM and the configurations will then be read into the VM for initial setup.

guestinfo.cis.deployment.node.type = "infrastructure"
guestinfo.cis.vmdir.domain-name = "vghetto.local" = "vghetto"
guestinfo.cis.vmdir.password = "VMware1!"
guestinfo.cis.vmdir.first-instance = "false"
guestinfo.cis.vmdir.replication-partner-hostname = "" = "ipv4" = "" = "" = "24" = "static" = "192.1681.1" = ""
guestinfo.cis.appliance.root.passwd = "VMware1!"
guestinfo.cis.appliance.ssh.enabled = "true"

For more information, you can take a look at this article here.

Deploying using new supported scripted install (bonus)

As mentioned earlier, there is also a new scripted installer included inside of the VMware-VCSA ISO under /vcsa-cli-installer which supports Windows, Mac OS X and Linux, but must be connected directly to an ESXi host. There are several templates that are also included within the /vcsa-cli-installer/templates. I thought as a bonus I would also share the template I have been using to deploy replicated PSC instances using a static IP Address which some of you may find useful.

The use the scripted installer, you just need to change into the appropriate OS platform directory (win32,mac or lin64) and there should be a binary called vcsa-deploy. To use this template, you just need to save the JSON to a file and then specify that as the first argument to vcsa-deploy utility.

Here is an example of deploying a PSC using the vcsa-deploy scripted installer.


12 thoughts on “Ultimate automation guide to deploying VCSA 6.0 Part 3: Replicated Platform Service Controller Node

  1. Hi William,

    I have a question about the default timeout settings policy for the vcsa bash shell login.

    I have noticed that after some time if the putty session is inactive the vcsa shell session displays the message and it’s as mentioned in the below screenshot.

    vmware-vcsa:/ #timed out waiting for input: auto-logout

    Wanted to know if this timout can be altered within the linux appliance without going into the VAMI page or not.

    Thanks in advance,

    • Yes, you’ll want to use shell.set command and specify a timeout:

      Command> shell.set –help

      shell.set [–help/-h] –enabled BOOL –timeout INT
      Set enabled state of BASH, that is, access to BASH from
      within the controlled CLI.
      Input Arguments:
      –enabled BOOL
      Enabled can be set to true or false
      –timeout INT
      The timeout (in seconds) specifies how long you enable the
      Shell access.

      BTW – There’s no VAMI in the VCSA 6.0

  2. Hi William,

    I have another question that needs to be addressed by VMware as this is critical . I’m currently testing the VCSA for security hardening for within our organization and i’m having a major concern over the way the appliance is storing the password in plain text.


    “source-components”: {
    [{“url” : “//localhost:443”,
    “username” : “root”,
    “password” : “vmware”,
    “platform” : “linux”,
    “version” : “5.1”}]
    “destination-components”: {
    [{“url”: “//localhost”,
    “username” : “root”,
    “password” : “vmware”,
    “platform” : “linux”}]
    “targets”: [
    “host”: “localhost”,
    “username” : “root”,
    “password” : “vmware”,
    “platform” : “linux”
    “upgrade-settings” : {
    “power-off-source” : “True”,
    “infrastructure” : {
    “host”: “localhost”,
    “httpPort”: “80”,
    “httpsPort”: “443”,
    “username”: “root”,
    “password”: “vmware”
    “export-folder” : “/tmp/vmware/cis-export-folder”

    Please review this at the earliest and let your product team know if this case be hashed in anyway so that we donot save password’s in plain text.


  3. Hi Srinivas,

    Thanks for your comment. The file you’re referencing is actually just a default “template” file and the VCSA is not storing the actual passwords. You can confirm by setting the password of choice during deployment and checking this file again. I can see how this could be miss-interpreted, especially by security tools. I’ve also shared this feedback with Engineering.

  4. Either I’m missing something, or there seems to be an issue with the dns.servers key when trying to enter more than one DNS server. The following doesn’t work:

    “dns.servers”: “,”,

    This works fine:


    This also works fine:

    “ntp.servers”: “ntp1.test.local,ntp2.test.local”,

    I get “The value,,, of the key ‘vcsa->networking->dns.servers’ is invalid!” when running the script.

      • Our TAM pointed me to the release notes…it’s a bug. Hopefully it will be fixed soon!

        The vCenter Server Appliance scripted installer fails if more DNS servers are provided simultaneously
        The scripted installation of vCenter Server Appliance fails if you provide more than one DNS server during the installation process.
        Workaround: You should use only one DNS server at a time, and after the installation has finished, you can add more DNS servers.

        • I managed to resolve this by changing the dns.server entry under the network section to this:
          “dns.servers”: “,”,

          The default templates have another notation and will throw an error:
          “dns.servers”: [

          The same (serialized string) notation is being used for the ntp.servers variable, and documented in “Command-Line Deployment and Upgrade of VMware vCenter Server Appliance 6.0 Update 2”

  5. William, You VCSA posts have been amazing as I work to get our vSphere design updated for 6! I’m working on a script to automated the changing/repointing of the vcsa to different PSCs but am getting stuck on having plink establish the session & enable shell before it executes the ‘/usr/lib/vmware-vmafd/bin/vmafd-cli set-dc-name –server-name localhost –dc-name PSCFQDN’ command.
    I was thinking of a PowerShell script to read the root creds securely and select which VC to change and which PSC to change the VC to… then pass all that in a plink script to execute.
    If I manually establish a putty session, then exit and run my script it works. but if the VC reboots, then the script wont work.
    Any advice? Other approaches?

    • I’ve not really done much with plink, so won’t be able to help much there. I would recommend that you build up a shell script and just have plink run that, that way you don’t have to worry about the execution of the script over SSH and just have it run it locally. Good Luck

  6. I am having trouble trying to find out how to verify that replication is setup and occuring as expected between 2 PSC setup behind a load balancer. I am pretty confident I have deployed this correctly but am looking for some type of validation.

Thanks for the comment!

This site uses Akismet to reduce spam. Learn how your comment data is processed.