5.2
Table Of Contents
- VMware Horizon View Integration
- Contents
- Introduction
- Integrating with the Event Database
- Using View PowerCLI
- Introduction to View PowerCLI
- View PowerCLI Cmdlets
- View Administrator, View PowerCLI Cmdlet, and vdmadmin Operations
- View PowerCLI Cmdlet Parameters
- Examples of Using View PowerCLI Cmdlets
- Displaying Information About a View Connection Server Instance
- Updating the Configuration of a View Connection Server Instance
- Managing the Configuration of vCenter Servers 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 Manual Unmanaged Desktop Pools
- Creating and Updating Desktops Provisioned by Terminal Servers
- Obtaining Information About Users and Groups from Active Directory
- Managing Desktop Entitlements
- Managing Local Desktops
- Managing Remote Sessions
- Managing Virtual Machines
- Displaying Information About Physical Computers
- Updating the Ownership of Machines
- Displaying Information About Events
- Managing the Global Configuration of View
- Managing View Licenses
- Examples of Using View PowerCLI for Enhanced Functionality
- Assign Multiple Network Labels to a Desktop Pool
- Customizing LDAP Data
- Integrating with SCOM
- View Management Packs
- Name a View Connection Server Group
- Import the View MPs
- View Discovery Script
- Run the Discovery Script
- Display Discovered Objects
- Display Managed Objects
- Views and Monitors
- Enable a Proxy Agent on a Server
- Display Performance Data
- Display Information About an Alert
- Restart a Service
- Exclude a Domain from Connectivity Monitoring
- Close Alerts
- Class and Relationship Definitions
- Examining PCoIP Session Statistics
- Dynamically Setting Desktop Policies with Start Session Scripts
- Index
VMware, Inc. 55
Chapter 3 Using View PowerCLI
NOTE As a best practice, do not assign a network label to more than one desktop pool. Be aware that
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. Otherwise, the IP assignments from the network label might become oversubscribed.
Example of an Edited Network Label Configuration File
In the following example, network01 through network05 remain commented and are not used. network06
and network07 are assigned to nic1 (Network adapter 1). network08 and network09 are assigned to nic2
(Network adapter 2). This configuration can now 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>
...
####nic1.network01.maxvm=244
####nic1.network02.maxvm=244
####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
Deploy a Desktop Pool with Network Label Assignments
To create an automated desktop pool that can use multiple network labels, use the
Add-AutomaticLinkedClonePool cmdlet for linked clone pools or the Add-AutomaticPool cmdlet for full
clone pools.
Use the -NetworkLabelConfigFile parameter with the Add Pool cmdlet to assign the network labels in a
specified configuration file to the pool. Specify the path to the configuration file with the “path”argument:
-NetworkLabelConfigFile “path”.
The -NetworkLabelConfigFile parameter works the same way for linked clone and full clone pools.
The following example creates a linked clone pool, POOL_NAME, and assigns the network labels in the
label.txt file to the pool.
Add-AutomaticLinkedClonePool -Pool_id POOL_NAME -NamePrefix NAME_PREFIX -Vc_id
2162aa44-e99c-4f1a-875d-dd295681d2ca -Persistence Persistent
-VmFolderPath "/resourcepool/vm/Discovered virtual machine"
-ResourcePoolPath "/resourcepool/host/Cluster1/Resources/Cluster1_pool1"
-ParentVmPath "/resourcepool/vm/Win7-Parent" -ParentSnapshotPath
"/780936_agent/noServiceRestart/updatedVPListener" -DatastoreSpecs
"[Conservative,replica]/resourcepool/host/Cluster1/Cluster1_Replica1;[Mod