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, View PowerCLI, and vdmadmin 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
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 defines 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 configuration file.
As a best practice, do not assign a network label to more than one desktop pool. The maximum network
label counts are honored only on a per-NIC, per-pool basis. For example, if you configure NIC1 on pool1 to
use network06 with a maxvm of 244, and you configure NIC1 on pool2 to use the same network label,
network06, with a maxvm of 244, network06 must have an actual assignable IP address space of at least 488
addresses or the IP assignments from the network label might become oversubscribed.
If the parent virtual machine or template has two NICs, each network label discovered by the Export-
NetworkLabelSpecForLinkedClone or Export-NetworkLabelSpecForFullClone cmdlet is associated with both
NICs. Warning messages explain that IP address assignments can become oversubscribed because the
assignment function for one NIC is not aware of the assignments that are made from the same network label
for the second NIC. Each NIC is aware only of its own network label assignments.
Example Network Label Configuration File
The following example shows a typical network label configuration file.
#Network Label Configuration Spec
#WARNING! Setting enabled flag to false will
#turn off the automatic network label assignment
#for newly provisioned desktops.
enabled=true
#Parameter Definition for NIC
nic1=Network adapter 1
nic2=Network adapter 2
#Parameter Definition for Network
network01=dv_2k_2004
network02=dv_2kclient_2164
network03=dv_2kdt1_2084
network04=dv_2kInfra_1924
network05=dv_vMotion
network06=desktop-auto01-230
network07=desktop-auto02-240
network08=desktop-auto03-250
network09=desktop-auto04-260
network10=desktop-auto05-270
#Network Label Attribute Definition
#Expected format:
#<nic_param>.<network_param>.maxvm=<max vm for network label>
#WARNING! Multiple NICs:(nic1,nic2) detected against network01,
#total port count against network01: 488.
#IP address might be over-subscribed.
#WARNING! Multiple NICs:(nic1,nic2) detected against network02,
Chapter 3 Using View PowerCLI
VMware, Inc. 51