12.2 Configuring the vSphereUpdate Client

Create a proxy user:
1. In the Orchestration Console, click Actions > Create User to open the Create a New User dialog.
2. In the Source Groups list, select administrators, then click Add to move the administrators user group to the Target Group list.
3. In the New User Name field, specify a user name, click Create, then click Close.
  
  This is the proxy user. The user name must contain the word “proxy,” for example, my_proxy, or proxy1.
Modify the vSphereUpdate.policy (or modify the job arguments in the Orchestration Server Job Scheduler) so that zos.proxy.user contains the name of the user created in Step 1.c:
1. In the Explorer Tree, select the Policies group to expand the list of policies included on this grid.
2. Select the vSphereUpdate policy to open the Policy Editor view.
3. Find the zos.proxy.user fact in the policy, then specify the name of the proxy user you created in Step 1.c as the value for this fact.
4. (Optional) configure other policy settings for the vSphereUpdate Scheduled Job.
  
  See Table 12-1, Cluster-Related Facts in the vSphereUpdate Policy.
Run the vSphereUpdate schedule and job:
1. In the toolbar of the Orchestration Console, select Scheduler to open the Orchestration Server Job Scheduler.
2. Select the vSphereUpdate schedule, click Enable, then click Run Now.
(Optional) Verify that the update job has run.
1. In the Orchestration Console main menu, select Jobs to open the Jobs admin view.
2. In the admin view, locate the VsphereUpdate job that ran last, then select its Job Log tab.
  
  You should see something similar to the following in the log:
```
       [vrack-vc] checking pid: 5276
       [vrack-vc] pid '5276' is still alive
```
  The “pid” reference in the log refers to the javaw.exe process running on the resource that accesses the vCenter software. You can verify that this process is running in the Windows Task Manager on the VCenter host machine.