3.19 vCenter Server Settings

For the following operation components, use VMware vSphere PowerCLI or Windows PowerShell to execute virtual server operations on a vCenter Server. This section describes the required environment settings.

Stop the virtual server on the VM host
Set the maintenance mode of the VM host
Stop the VM host forcibly
Start virtual server
(if not managing virtual server that is subject of operation with ServerView Resource Orchestrator)
Stop virtual server
(if not managing virtual server that is subject of operation with ServerView Resource Orchestrator)

Setting environment variables

To use the targeted operation components, environment variables must be set.
Add the following to the vCenter server system environment variables path. Restart the vCenter Server to enable the added environment variables.

Path to the VMware vSphere Power CLI script
```
<VMware vSphere PowerCLI installation folder>\Scripts
```
Point
If the VMware vSphere PowerCLI installation folder is not changed, see below for the default path to the VMware vSphere PowerCLI script.
32-bit architecture:
```
C:\Program Files\VMware\Infrastructure\vSphere PowerCLI\Scripts
```
64-bit architecture:
```
C:\Program Files (x86)\VMware\Infrastructure\vSphere PowerCLI\Scripts
```

Changes to PowerShell run policy

The Windows PowerShell script run policy must be changed to "RemoteSigned". Refer to the Windows PowerShell manual for information on the run policy.
To change the run policy, start the PowerShell as administrator and then execute the following command:

Set-ExecutionPolicy RemoteSigned

For 64-bit architecture, execute using the PowerShell editions shown below:

vCenter Server environment		PowerShell to be executed
If the Management Server is the same as the vCenter Server		x86 PowerShell
If the Management Server is not the same as the vCenter Server	If 32-bit Systemwalker Runbook Automation Agent is installed on the vCenter Server	x86 PowerShell
	If 64-bit Systemwalker Runbook Automation Agent is installed on the vCenter Server	64-bit PowerShell

VMware vSphere Power CLI port number settings

The targeted operation components use VMware vSphere Power CLI to execute operation requests to the VMware vCenter Server. VMware vSphere Power CLI carries out HTTPS communication with the VMware vCenter Servers. Therefore, open port 443 (HTTPS) on the firewall.

Certificate path verification settings

The targeted operation components use VMware vSphere Power CLI to execute operation requests to the VMware vCenter Server.
If the vCenter server network environment is not connected to the internet, connecting to VMware vCenter Server may take some time. This can be avoided by applying the following settings.

On the Start menu, click Run.
Type "gpedit.msc" to open the Group Policy Editor.
Go to Computer Configuration >> Windows Settings >> Security Settings >> Public Key Policies, then in the right pane, right-click Certificate Path Validation Settings, and select Properties.
Click the Network Retrieval tab, and specify the following:
- Select Define these policy settings.
- Select Automatically update certificates using the Microsoft Root Certificate Program (recommended).
- Set Default path validation cumulative retrieval timeout (in second): Default = 20 to 1.

Note

Products attempting to obtain a digital signature from the Internet may become unable to do so. The above settings should only be used when the vCenter Server network environment is not connected to the Internet.