kgsivan's Posts

How is the parent VM prepared ? -- Cloned from another. Whether  it has been  switched between snapshot of different activate staged May be client machine ID duplication.. Please run slmgr/rearm and try reactivate again. If no luck, I would advise to prepare a new parent VM and try activation freshly, so that you can safely change the default image to the newly activated parent VM

It is better to activate the Parent VM, (though we can handle any technical situation if not) Go to "c:\windows\system32\" Run "cscript slmgr.vbs -skms <kms server Ipaddress or hostname>" -- This step might be already done , that's why the clones are getting activated Run "cscript slmgr.vbs -ato"  -- This must be a pending step in the parent VM Notes: You should have elevated privilege You also need to ensure proper time zone and time on the parent VM, prior to activation

This will ensure a unified computing experience for both physical and virtual desktops. One drawback would be power management options cannot be applied (like for virtual desktops, we can keep the VM in powered off state if not in use) will will not be available in physical machine. Secondly, you should have your own third-party solution to manage the desktop, where as in virtual desktop (linked cloning) you can use refresh the change the desktop state to the default.

Leave the current Standalone host as it is. Create a new cluster, and the new host to that cluster. Now your VC will have one stand alone host and one cluster with single host. Now edit that pool and change the resource settings from standalone host to the new cluster Perform rebalance (All the clones will migrate to the cluster) Once the standalone host is empty, move that host to the cluster.

Login to SQL Studio using any full permission account. Select the user that created for configuring DSN from composer server to connect the database, go to properties and in one of the TAB you will see "Grand Permission to Connect" Enable/Disable Also as explained by Gaurav, check weather mixed mode authentication is enabled. I presume all necessary permissions are given to the user on the composer DB

If there was a Persistent Disk configured, yes there is a way. Go to left panel inventory, Persistent disk and locate the archived Persistent disk of the removed VM. Right click and select "Recreate" . A new linked clone will be created with all user data and settings and user assignment will be intact The above steps are applicable if you have Removed a VM of Linked clone pool with User data redirection Archived its persistent disk (default) while accidental deletion.

Since it is being connected from other clients, I guess some connectivity issue from the laptop If PCoIP secure gateway is incorrectly configured, you still be able to connect through RDP. So getting these clarified can help in isolating the issue.

Ensure script is working by using some other simple commands  (Calling vbscripts through batch file) Also make sure that you elevate privilege while releasing IP (You can try this way: "runas /user:administrator C:\data\mybatchfile.bat" )

Very much expected to work, but not officially listed as a supported one as of now. As per, page 11 of https://pubs.vmware.com/horizon-view-60/topic/com.vmware.ICbase/PDF/horizon-view-60-installation.pdf latest supported Oracle DB version is 11.2.0.3 You can get in touch with VMware official contact to get a formal confirmation about the supporting the next version

Define and register a new name with Load balance IP address. Let us say view-ab.company.com. When DNS resolve this address it should resolve the external IP of the load balancer. Now, login to view administrator console either viewa or viewb go to view configuration, servers, select connection servers tab, both viewa and viewb will be listed out there. select viewa, and click edit, select http(s) secure tunnel, and at the external URL filed give https://view-ab.company.com:443/ Save the settings. Now repeat same steps for all remaining connection server, and give same external URL Now when users connection via https://view-ab.company.com:443/ it will be load balanced across all connection servers. (in certificates you can use subject alternative name)

Could you please tell me the pool size Min / Mix / Spare. and number of Connected VMs at the time of recompose? Minimum during recompose is set to 5 at pool level.. What was the max number of concurrent composer maint. operations at the vCenter settings?

This looks strange. Request to help me with below questions. Have you also upgraded vSphere and/or View Composer along with this? I hope you must be followed View Upgrades - VMware Horizon 6.0 guide to complete the upgrade. Does any VM hardware or tool upgrade happened between these snapshot states ?

I guess, you must be using Sysprep, which will reconfigure entire network configuration with default configuration for unspecified items... such as IPv6 Could you please try with Quickprep and check for the same issue ?

Is the connection server on Domain B is installed as a replica server ? If answer is Yes: Ensure Two way transitive trust is is configured. Domain Names are resolvable across the member machines (also from View Composer) If answer is No: Use user principal names for VC and View composer, Try to add VC alone, then check if the error is only for composer (Try to add using IP address and verify) Note: Composer account should have administrative privilege on the local machine where the composer is running.

True. You can disable provisioning for a short period of time (during the time of deletion up-to host removal.) However as you pointed out you can let the provisioning happens to other datastores in parallel, and prevent to the particular host by deselecting the datastore. Agree with you that both are tedious in large scale...  Thanks for the detailed response.