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
Assigning Multiple Network Labels to a Desktop Pool
In View 5.2 and later releases, you can congure automated full-clone and linked-clone desktop pools to use
multiple network labels. This feature expands the number of IP addresses you can assign to the virtual
machines in a pool, making it easier to create pools that have a large number of desktops. You can use View
PowerCLI cmdlets to assign network labels that are available in the vCenter Server resource pool where the
automated full-clone or linked-clone desktop pool is deployed.
By default, the virtual machines in a desktop pool inherit the network interface card (NIC) and its associated
network label from the parent virtual machine or template. Some parent virtual machines or templates
might have multiple NICs and associated network labels. Typically, the subnet mask of a VLAN dened by
a network label has a limited range of available IP addresses. For example, a subnet mask might have a
maximum of 254 IP addresses that can be assigned to the desktop virtual machines.
View distributes network labels among the virtual machines in the entire desktop pool. When View
provisions desktops, it assigns network labels in alphabetical order. When the maximum number of virtual
machines are provisioned with IP addresses that use the rst network label, View starts to assign the second
label, and so on.
To congure a desktop pool to use multiple network labels, you select network labels from the labels
dened for the ESXi cluster in vCenter Server, associate the labels with the NICs that are inherited from a
parent virtual machine or template, specify the maximum number of IP addresses that can be assigned to
virtual machines from each network label, and save the information in a network label conguration le.
You specify the network label conguration le in the View PowerCLI cmdlet that you use to create the
desktop pool.
Network Label Configuration File Format
You use a network label conguration le to congure automated full-clone and linked-clone desktop pools
to use multiple network labels. The network label conguration le contains a ag that controls whether
network labels are assigned and sections that dene NICs, network labels, and network label aributes.
Enabled Flag
This ag is set to enabled=true by default. Keep the ag set to true to allow View to assign network labels to
the pool.
Parameter Definition for NIC Section
This section lists the NICs dened in vCenter Server on the template or snapshot of the parent virtual
machine. Do not edit this section.
Parameter Definition for Network Section
This section lists the network labels dened in vCenter Server instance for the ESXi hosts in the cluster.
Network labels are listed in alphabetical order. If a cluster uses standard network labels and distributed
virtual switch network labels, use only one type of label for a pool. Do not edit this section.
Network Label Attribute Definition Section
This section lists the network labels associated with each NIC. The network labels are commented out and
the assignments are not functional. You must remove the comments (### marks) from the appropriate
network labels to allow them to be assigned to a desktop pool.
The maxvm parameter denes the maximum number of IP assignments that can be made to virtual machines
from the network label. The value of the maxvm parameter is generated by the -maxVMsPerNetworkLabel
parameter in the Export-NetworkLabelSpecForLinkedClone or Export-NetworkLabelSpecForFullClone
cmdlet. You can manually edit this value in the conguration le.
View Integration
52 VMware, Inc.