7.0
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
The network label cmdlet obtains the network labels configured in vCenter Server for all the ESXi hosts in
the specified cluster, sets the maximum number of virtual machines that can be provisioned with IP
addresses from each network label, and exports the list of NICs and network labels to the network label
configuration file.
Example: Obtaining NIC and Network Label Information
In this example, the Export-NetworkLabelSpecForLinkedClone cmdlet obtains NICs from the Win7-Parent
virtual machine and Snapshot1, and network label information from Cluster1. A maximum of 244 virtual
machines can be provisioned with IP addresses from each network label. The information is exported to a
network label configuration file named C:/label.txt.
Export-NetworkLabelSpecForLinkedClone -vc_id 1a2b3c4d-5e6f
-clusterPath "/myresourcepool/host/Cluster1/"
-parentVMPath "/myresourcepool/vm/Win7-Parent" -parentSnapshotPath "/snapshot1"
-maxVMsPerNetworkLabel 244 -networkLabelConfigFile "C:/label.txt"
What to do next
Verify and edit the network label configuration file. See “Verify and Edit a Network Label Configuration
File,” on page 55.
Verify and Edit a Network Label Configuration File
After you generate a network label configuration file, you must verify its contents and edit it to specify the
NIC and network label pairings to assign to the pool.
Prerequisites
n
Generate a network label configuration file. See “Obtain and Export NIC and Network Label
Information,” on page 54.
n
Become familiar with the network label configuration file format. See “Network Label Configuration
File Format,” on page 52.
Procedure
1 In a text editor, open the network label configuration file.
2 For each NIC and network label pairing that you want to assign to the pool, remove the comments (###
marks).
3 Verify that each network label is assigned to only one NIC.
4 Verify that only one type of network label is used for the pool.
A NIC can be configured with a standard network switch or distributed virtual network switch.
5 Save your changes.
Example: Edited Network Label Configuration File
In this example, network06 and network07 are assigned to nic1 (Network adapter 1) and network08 and
network09 are assigned to nic2 (Network adapter 2). network01 through network05 remain commented and
are not used. This configuration can support a pool of up to 488 virtual machines.
#Network Label Configuration Spec
...
#Network Label Attribute Definition
#Expected format:
#<nic_param>.<network_param>.maxvm=<max vm for network label>
Chapter 3 Using View PowerCLI
VMware, Inc. 55