Integration
Table Of Contents
- 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 RDS Hosts
- Obtaining Information About Users and Groups from Active Directory
- Managing Desktop Entitlements
- 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. 63
Chapter 4 Customizing LDAP Data
Table 4-1 lists the attributes that are important when you modify a desktop pool definition.
In a similar manner to desktop pools, you can create customized LDIF files for other objects that are defined
in the LDAP repository, for example:
Global configuration settings.
Configuration settings for a specific View Connection Server instance or security server.
Configuration settings for a specific user.
Import LDAP Configuration Data
You can import configuration data from an LDIF file into a standard or replica View Connection Server by
running the vdmimport command.
The vdmimport command is available in View 4.5 and later releases. In releases prior to View 4.5, you must
use the LDIFDE command. See “Import LDAP Configuration Data Using the LDIFDE Command” on page 64.
By default, the vdmimport command-line utility is installed in the C:\Program Files\VMware\VMware
View\Server\tools\bin directory.
The vdmimport command does not update, create, or delete any LDAP records that are not defined in the LDIF
file. This allows you to customize an LDIF file so that only selected records are affected when you import the
file.
You must be logged into a View Connection Server instance as a user in the Administrators role to import
configuration data successfully into the View configuration repository.
To import configuration data into a View Connection Server instance
1 Select Start > Command Prompt.
2 At the command prompt, type the vdmimport command and specify an existing LDIF file as an argument
to the -f option.
vdmimport -f myexport.LDF
The configuration of your View Connection Server instance is updated with the data from the file, and the
number of records that have been successfully updated is displayed. Errors are displayed if some records
could not be updated because your role has insufficient privileges.
Table 4-1. Important Attributes for Defining a Desktop Pool
Entry Attribute Description
Virtual Desktop VM
VM Pool
Desktop Application
cn Specifies the common name of an entry. If you require names to be
generated automatically, specify globally unique identifier (GUID)
strings. You can use any reliable GUID generator, such as the
mechanism provided by .NET (for example, by calling
System.Guid.NewGuid().ToString() in Visual Basic).
Desktop Application member Specifies a list of Active Directory (AD) users and groups who are
entitled to access the desktop pool. The attribute is specified in the
form of a Windows Security Identifier (SID) reference. A member
value of <SID=S-1-2-3-4> represents an AD user or group with the
SID value S-1-2-3-4. In LDIF format, the left angle (<) character is
reserved, so you must place two colons (::) after the attribute name
and specify the SID value in base 64 format (for example,
PFNJRD1TLTEtMi0zLTQ+IA==). Because this attribute is
multivalued, you can use it on multiple lines to represent each entry
in a list of SIDs.