Integration
Table Of Contents
- View Integration
- Contents
- View Integration
- Introduction to View Integration
- Integrating View with the Event Database
- Using View PowerCLI
- Getting Started with View PowerCLI
- View Administrator, PowerCLI Cmdlets, and View Command-Line Interfaces Compared
- View PowerCLI cmdlet Reference
- View PowerCLI cmdlet Parameters
- Examples of Using View PowerCLI cmdlets
- Managing View Connection Server Instances
- Managing vCenter Server Instances in View
- Managing Desktop Pools
- Creating and Updating Automatically Provisioned Desktop Pools
- Creating and Updating Linked-Clone Desktop Pools
- Creating and Updating Manually Provisioned Desktop Pools
- Creating and Updating Manual Unmanaged Desktop Pools
- Displaying Information About Users and Groups
- Managing Desktop Entitlements
- Managing Remote Sessions
- Managing Virtual Machines
- Displaying Information About Physical Machines
- Updating Virtual Machine Ownership
- Displaying Event Reports
- Displaying and Updating Global Settings
- Displaying and Adding License Keys
- Examples of Using View PowerCLI to Perform Advanced Tasks
- Assigning Multiple Network Labels to a Desktop Pool
- Network Label Configuration File Format
- Example Network Label Configuration File
- Obtain and Export NIC and Network Label Information
- Verify and Edit a Network Label Configuration File
- Deploy a Desktop Pool That Uses Multiple Network Labels
- Displaying Network Label Assignments for a Pool
- Displaying Network Label Assignments for a Virtual Machine
- Displaying vCenter Server Network Label Assignments for a Virtual Machine
- Disable Automatic Network Label Assignments
- Customizing LDAP Data
- Integrating View with Microsoft SCOM
- Setting Up a SCOM Integration
- Assign a Name to the View Connection Server Group
- View Management Packs
- Import the View Management Packs on the SCOM Server
- Enable a Proxy Agent on a View Connection Server Host or Security Server
- Run the Discovery Script in the Operations Manager Console
- View Connection Server and Security Server Managed Objects
- View Object Classes and Relationships
- Monitoring View in the Operations Manager Console
- Setting Up a SCOM Integration
- Examining PCoIP Session Statistics with WMI
- Setting Desktop Policies with Start Session Scripts
- Index
####nic1.network03.maxvm=244
####nic1.network04.maxvm=244
####nic1.network05.maxvm=244
####nic1.network06.maxvm=244
####nic1.network07.maxvm=244
####nic1.network08.maxvm=244
####nic1.network09.maxvm=244
####nic1.network10.maxvm=244
####nic2.network01.maxvm=244
####nic2.network02.maxvm=244
####nic2.network03.maxvm=244
####nic2.network04.maxvm=244
####nic2.network05.maxvm=244
####nic2.network06.maxvm=244
####nic2.network07.maxvm=244
####nic2.network08.maxvm=244
####nic2.network09.maxvm=244
####nic2.network10.maxvm=244
Obtain and Export NIC and Network Label Information
Before you can assign multiple network labels to a pool, you must obtain NIC and network label
information and export that information to a network label conguration le.
For a full-clone pool, you obtain information about the NICs congured on the template that you use to
create the full-clone pool. For a linked-clone pool, you obtain information about the NICs congured on the
parent virtual machine that you use to create the linked-clone pool. You obtain network label information
from the available network labels congured on the ESXi hosts in the cluster on which the desktop pool is to
be deployed.
When you export the NIC and network label information to a network label conguration le, you set the
maximum number of virtual machines that can be provisioned with IP addresses from each network label.
You should allow a certain number of virtual machines for overhead. For example, if a network label VLAN
allows a maximum of 254 IP addresses to be assigned to virtual machines, you might set the maximum
number to 244.
Prerequisites
Become familiar with using View PowerCLI. See “Geing Started with View PowerCLI,” on page 27.
Procedure
n
To obtain and export NIC and network label information to create a full-clone pool, use the Export-
NetworkLabelSpecForFullClone cmdlet.
For example:
Export-NetworkLabelSpecForFullClone -vc_id id -clusterPath "cluster-path"
-TemplatePath "template-path" -maxVMsPerNetworkLabel nn
-networkLabelConfigFile "config-file-path"
n
To obtain and export NIC and network label information to create a linked-clone pool, use the Export-
NetworkLabelSpecForLinkedClone cmdlet.
For example:
Export-NetworkLabelSpecForLinkedClone -vc_id id -clusterPath "cluster-path"
-parentVMPath "parent-vm-path" -parentSnapshotPath "snapshot-path"
-maxVMsPerNetworkLabel nn -networkLabelConfigFile "config-file-path"
View Integration
54 VMware, Inc.