VMWare View 4.0 + Recursive Domain Enumeration

I was experiencing issues with the View Broker, not being able to enumerate the root domain, and connectivity between itself and the root domain didn't exist.

To solve the issue, I found the following link to the VMWare community forums
http://kb.vmware.com/kb/1005458

Unfortunately, the article provides the incorrect type of value required for this to work. What is required is:

HKLM\Software\VMWare Inc.\VMWare VDM
Name: RecursiveDomainEnum
Type: REG_SZ
Value: False

VMWare View 4.0 + Desktop Composer - Virtual Machine with input specifications already exists

This is related to creating a pool of machines, where one of the machine exists in vCenter, and in the Composer DB, but for some reason, it does not get listed within the pool. At this point, the pool trying to create that VMs conflicts with the actual VM that exists in vCenter, as well as the database entries that exist in the ComposerDB.


Caution: As always, this is risky procedure that involves modifying the database. Ensure that you have a good backup of your SQL database prior to any work.

1.Open the vSphere Client, and find the the VM. Right click and select "Delete from  Disk". Alternatively, you can find the VM's folder in the datastore and delete the contents.

2.Using Active Directory Users and Computer, browse to the OU where you store you View Desktop machine account exist, and delete the computer object.

3.Using SQL Management Studio, open the Composer DB database. You will need to delete some entries    related to problem VM:

- SVI_VM_NAME where NAME is the deployed VM name
- SVI_VM_COMPUTER_NAME where NAME is the deployed VM name
- SVI_SIM_CLONE where VM_NAME is the deployed VM name.

Before you perform this last query, there are 3 other rows to delete, as they have constraints on them:

- SVI_SC_BASE_DISK_KEYS where PARENT_ID is the ID from SVI_SIM_CLONE
- SVI_TASK_STATE where SIM_CLONE_ID is the ID from SVI_SIM_CLONE
- SVI_SC_PDISK_INFO where PARENT_ID is the ID from SVI_SIM_CLONE

After you perform the above steps, check out your provisioning, or re-enable it if it had been disabled due to the error, and things should continue along without a problem.

VMA 4.0 Configuration Setup

VMA 4.0 Configuration 

This is a reference guide to some of the common configuration steps that I performed when 
setting up the VMA on the network. 

Setup Authentification to vCenter/ESX hosts   

 sudo vifp addserver 
vifp listservers
vifpinit
Test it works
vicfg-nics -l --vihost 

Update vMA

$ sudo vi /etc/vmware/esxupdate/vimaupdate.conf
 

If you require a proxy server to connect through: 

Uncomment the line: proxy = http://
Uncomment the line: proxyport = 
 

Press ESC, then type :wq to save the file 

$ sudo vima-update scan
$ sudo vima-update update

Setup SSH Keys

$ mkdir ~/.ssh
$ vi ~/.ssh/authorized_keys2

Save the file by :wq 

$ chmod 700 ~/.ssh/authorized_keys2