Integration

Integrating View with Microsoft
SCOM 5
You can use Microsoft System Center Operations Manager (SCOM) to monitor the state of View
components, including View Connection Server instances, security servers, and the View services that run
on View Connection Server and security server hosts.
This chapter includes the following topics:
n
“Setting Up a SCOM Integration,” on page 65
n
“Monitoring View in the Operations Manager Console,” on page 70
Setting Up a SCOM Integration
Integrating View with SCOM involves assigning a name to the View Connection Server group, importing
the View management packs on the SCOM server, enabling a proxy agent on each View Connection Server
instance and security server, and running the View discovery script in the Operations Manager console.
Assign a Name to the View Connection Server Group
Before you can use SCOM to monitor and manage the state of View components, you must assign a name to
the View Connection Server group in View. The Operations Manager console displays this name to help you
identify the View Connection Server group within SCOM.
NOTE View Administrator does not display the View Connection Server group name.
Prerequisites
Become familiar with the vdmadmin command-line interface. For more information, see the View
Administration document.
Procedure
1 Log in to one of the View Connection Server hosts in the View Connection Server group.
2
At the command prompt, type the vdmadmin command with the -C and -c options.
For example: vdmadmin -C -c group_name
The -c option specifies the name to assign to the View Connection Server group.
Example: Assigning a View Connection Server Group Name
In this example, the vdmadmin command sets the name of a View Connection Server group to VCSG01.
vdmadmin -C -c VCSG01
VMware, Inc.
65