kgsivan's Accepted Solutions

You are right that KMS activation starts when the 26th Machine request activation. But this will ot impact in your case. The parent VM need not to get activated, but has to configure the KMS server in it You can do this by: cscript c:\windows\system32\slmgr.vbs -skms <KMS Server hostname> Now the parent VM is KMS server pointed, and all the clones created out of it will get activated through the specified KMS.  You may have to create a pool of 25 VMs to reach the threshold. Thanks Siva

Absolutely no issue. You can always use the same golden image. And if you choose the same datastore that you have used for deploying the first pool then the pool provisioning will be pretty fast as it will use the same replica-vm. In such cases you can consider the replica-to-clone ratio also for better perfomance

AFAIK, it is not possible, and here if you are using View to provision the linked clones there is no way that you can avoid domain membership. First of all, if you do not add the quick prep domain you will not able to complete the pool creation wizard. If you need to simply provision linked clones without View feature-support then in the master snapshot change to DNS entry to a fake one so that the domain is unreachable. Complete the pool provisioning. Now all the linked clones will be deployed. The pool may go to a timeout state but clones will not be part of any domain

This depends on what you use your system for. According to Microsoft If you’ve got the latest hardware and drivers are available, then it  would be worth while taking the step up to a 64 bit OS. If you regularly  work with resource hungry applications that are 64 bit optimised then it would be especially  beneficial to be able to work with over 4GB of RAM amongst the other  improvements. We may expect in future that the 64 bit computing to become a common  standard. Nowadays most of the hardwares have been  designed with this in mind. Until a complete upgrade cycle has passed  for the majority of users, there is still a strong case for some users  to stick with 32 bit Windows for the time being. Once more 64 bit  applications start to appear, it would be a good time to make the switch  to the new architecture. You can overcome the 4GB limit, and the 64bit-applications will have defenitely better performace. But be aware about below concerns 16 bit applications will not support (but it is rare case to run 16 bit applications nowadays) Running some (not all ) 32 bit applications on a 64 bit OS could actually be slower. The additional overheads in running 32 bit software in 64 bit mode could cause a slight degradation in performance. It will take some time for 64 bit software to become the norm From VMware perspective, View supports recompose desktops (or entire Pool) to an image from same OS category but different architecture. That means you may recompose your 32 Windows 7 dekstop/pool to a 64 bit Windows7. So this will help you to safely choose 32 bit version for the time being and change the archticture version when need arises. Best Regards Siva *** EDITED *** FYI:  http://windows.microsoft.com/en-US/windows-vista/32-bit-and-64-bit-Windows-frequently-asked-questions

Thinapps those are assigned to a pool will be pushed(or streamed) whenever a VM from the pool is launched by user using View Client. You cannot expect Thinapp getting installed to all VMs immediately after assignment. Also during thinapp assignment if the VM is already launched by the user, then it has to be logged off and login again for the thinapp to install.

If you are using full virtual machines you need to follow below proceedure.-- It is not a perfect workaround and would tedious job in case of large pool with and user ownership. From view manager, delete the the pool -- it will ask delete from view manager <or> delete from disk - proceed with delete from view manager only. Now pool configuration will be removed leaving all the VMs in vCenter server. Now connect any ESX server from new vCenter server to this vCenter server. Migrate all the VMs to new esx and new datastore.. (If the same datastre is visble in new vCenter server you may probably unregister those VMs from source vcenter server and register in destination vcenter server) New create a Manual pool using existing VMs from new vCenter server If the old pool was a dedicated pool, make note of those VM-to-User assignments and apply those user ownership manually. There are UI options to do this manually inside the pool inventory. Pease be aware that  your automated full clone pool in old VC become a Manual Pool in the new VC Hope this helps. Best Regards Siva

No Special configuration is required specific to Windows 7 64 bit. Where are you facing this issue ? In VC or View. If iit is in VC then check the network settings of teh custom sepc for proper DNS configuration to reach the domain. The issue will be mostle the domain is unreachble from the deployed VMs If the issue is in View Desktop deployments then refer blog Common errors with SVI Pools and View Composer

At very first just query nslookup and check whether the clones hostname is resolving or not. Also select al the Vms from view administrator page and perform a reset and see <--  If both these actions resolve your issue then it was due to a minor network outage happened during the provisioning process. If not then, 1. Whether the DNS server is an active directory integrated one or not ? If not check for the permission to get registered in that DNS server. 2. Whether the DNS entry received from the DHCP Server to clone is pointing to the right DNS Server ? and same DNS / Domain name is resolvable from vCenter server ? 3. Have you used Sysprep customization ? If yes please be aware that the domain setting will not be picked from the custom spec but DNS settings will be picked from custom spec. In such case the DNS setting given in custom spec should able to resolve the domain whic added in vcenter configuration page of View administrator

Please ensure that you have the VMware Tools installed on your agent machine. If Vmware tools is not present in the agent VM, install will not provide view composer and related components. To install VMware tools, right click on the VM -> Guest -> Install/Upgrade VMware Tools. Reboor the VM and proceed with the View Agent installation.

Hi, Welcome to the Community If you want to use your existing Roaming Profile setup, then the better option is not to use the 'Persistent Disk' configuration. Redirection to the persistent disk in static, and it bring additional storage utilization. While provisioning a Desktop pool with persistent disk, View composert modifies the user profile path in HKLM\Software\Microsoft\Windows NT\CurrentVersion\Profile List to the D Drive.  This may conflict with your roaming profile setup. To confirm that, in the physical machine modify 'Default',  'Profile Directory' and 'Public' string values in Profile List registry which refers to a new path. >> if I should scrap the persistent drive in a way that the data will all  remain and sync to roaming profile consistently even if I refresh or  update my VDI golden image? Yes, this sould be the feasible option for you. Deploy dedicated pools without User Data redirection

Get the machine out from domain Remove the Ethernet card from VM settings generate new SID for the machine Add new Network card Join to domain - Should be successfull Install Broker - Should be successfull Access View Administrator with right permissions - Should be successfull If the above does not work for you, there should be something serious about your setup. In that case try deploying new Machine Custom spec and SID creation.

If the clock skewed stays for longs time, then there is some issue. Please ensure that all agent machines and brokers follows time with domain controller, rather than time syncronization with vmware tools (with ESX) or internet time syncronization

Welcome to the Community >> First, should this change stick since this is a persistent linked  clone? No, Persistent linked clones get driver letter configured during pool creation wizard. Hence recompose or any such operation will override manual changes >> Second, is there a way to reassign the drive letter  automatically? In View 4.5 there is an option for changing the drive letter for Persistent Disks

From the Pool inventory manually remove the VM with (missing) text. If provisioning is disabled for the pool, then select the pool and click on enable provisioning. If these thiongs doesnot work for you then the entry cna be removed from ADAM OU=Server

This is a very much known issue. A view4.5 patch build (353760) is available to resolve this issue. http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1034262

Such issues are mostly becasue View composer is unable to contact database/dsn From the vCenter server , if View composer is running, restart the service and ensure Composer service comes back to the running state withut any error. If error occures, you are welcome to send the logs

Please perform following steps. ----------------------------------------- Create a fresh Virtual machine with  custom SCSI controller. (Keep Floppy drive configuration) Extract the downloaded driver symmpi_wXP_1201800.zip (version 1.28.03) The driver floppy image can be pointed by editing VM, floppy. Initiate Windows XP installation, press F6 when asks and and point to the driver in the floppy Continue and complete the installaton. Now use this VM as a parent VM, and it should solve your problem