Section 2 – Configure and Administer View Components
Objective 2.1 – Configure and Manage View Global Policies and Settings
- Enable and disable global policies – p175 (Administration guide)
- Configure and modify global settings – p26-29 (Administration guide)
Objective 2.2 – Configure Administrator Roles and Permissions
- Create, modify and delete administrator roles – p39 (Administration guide)
- Add and remove user permissions – p43 (Administration guide)
- Assign and Manage permissions on View folders – p45 (Administration guide)
Objective 2.3 – Configure Syslog and View Events Database
- Configure Events database – p119-122 (Installtion guide)
- Configure Syslog using vdmadmin
Connection Server, vdmadmin located in C:\Program Files\VMware\Vmware View\Server\tools\bin
- vdmadmin -I -eventSyslog -enable -localOnly
- vdmadmin -I -eventSyslog -enable -path path
- vdmadmin -I -eventSyslog -enable -path \\logserver\share\ViewEvents -user mydomain\myuser -password mypassword
Objective 2.4 – Backup and Restore View Environment
- Backup the View Composer database
- Use SQL Server Studio Manager to backup SQL database(s)
- Backup LDIF or SVI using View Administrator
- View Admin>Servers>Connection Servers>Select Server>Backup Now
- Backup LDIF using vdmexport
- Locate vdmexport.exe command on View Connection Server – C:\Program Files\VMware\VMware View\Server\tools\bin
- vdmexport > c:\Myexport.LDF
- Restore a View environment from a backup
For example, as part of a business continuity and disaster recovery (BC/DR) plan, you might want to have a procedure ready to implement in case a datacenter stops functioning. The first step in such a plan is to ensure that the View LDAP configuration is backed up in another location. A second step is to install View Connection Server in the new location and import the backup configuration, as described in this procedure. You might also use this procedure when you set up a second datacenter with the existing View configuration. Or you might use it if your View deployment contains only a single View Connection Server instance, and a problem occurs with that server.
You do not have to follow this procedure if you have multiple View Connection Server instances in a replicated group, and a single instance goes down. You can simply reinstall View Connection Server as a replicated instance and View restores the View LDAP configuration from the other instance.
- Install a new instance of View Connection Server
- Locate the vdmimport tool – C:\Program Files\VMware\VMware View\Server\tools\bin
- Decrypt the encrypted LDIF file
- vdmimport -d -p mypassword -f MyEncryptedexport.LDF > MyDecryptedexport.LDF
- Import the decrypted LDIF file to restore the View LDAP configuration
- vdmimport -f MyDecryptedexport.LDF
Objective 2.5 – Configure Location Based Printing
- Configure location-based printing using a Group Policy Object
Create a GPO for the location-based group policy setting and link it to the OU that contains your View desktops
Because print jobs are sent directly from the View desktop to the printer, verify that the required printer drivers are installed on your desktops.
- Computer Configuration>Software Settings and select AutoConnect Map Additional Printers for VMware View.
- In the Policy pane, double-click Configure AutoConnect Map Additional Printers.
- Select Enabled to enable the group policy setting.
- Clicking Disabled deletes all table entries.
- Add the printers that you want to map to View desktops and define their associated translation rules
- Deploy and configure Thinprint modules
TPVMGPoACmap.dll located on Connection Server at \VMware View\Server\extras\GroupPolicyFiles\ThinPrint
- Copy TPVMGPoACmap.dll to AD\DC server
- Run command regsvr32 “C:\TPVMGPoACmap.dll”
- Configure Group Policy (see above)
- Configure clients for virtual printing
Configure printing rules via translation table in GPO>AutoConnect Map Additional Printers
- Add IP of printer as IP_xxx.xxx.xxx.xxx
- Ensure print driver(s) installed in virtual desktop (parent image)
- Ensure Virtual Printing option selected when installing View Agent on parent image