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.
View Management Packs View management packs enable you to use SCOM to monitor and manage the state of View components.
Import the View Management Packs on the SCOM Server You must import the View management packs on the SCOM server to use SCOM to monitor and manage the state of View components.
Enable a Proxy Agent on a View Connection Server Host or Security Server You must use the Operations Manager console to enable a proxy agent on each View Connection Server host or security server that you want to monitor with SCOM. The discovery script can discover a Windows server only if you enable the proxy agent for the server.
Run the Discovery Script in the Operations Manager Console The discovery script finds systems on which a View server is installed. It probes the registries of Windows servers for entries that indicate the version of the View software, the type of server, and the name and ID of the View Connection Server group.
View Connection Server and Security Server Managed Objects The discovery script discovers managed objects for View Connection Server instances and security servers.
View Object Classes and Relationships The VMware.View.Library management pack contains class and relationship definitions for the View management packs. A class can have properties, such as a name or ID. The relationships between classes describe their hierarchy. For example, the relationship contains exists between VMware.View.Clusters and VMware.View.Cluster, and between VMware.View.Cluster and VMware.View.Cluster.Node.