Highlighted
3 Silver

Domain join tip when provisioning desktops through vCenter with vWorkspace

Here's a handy piece of advice when using vWorkspace to provision virtual desktops through vCenter, and using the sysprep options to do a domain join.

Sometimes it seems that vCenter is ready the sysprep settings, but the domain join does not complete. One common cause is using the NetBIOS domain name, rather than the FQDN domain name.

For example, if you type the domain name as TEST then it might now work. If you type TEST.DEMO (the FQDN) then suddenly desktop happily join the domain.

Jon

0 Kudos
1 Reply
Highlighted
2 Bronze

RE: Domain join tip when provisioning desktops through vCenter with vWorkspace

That is a good tip Jon, but in my experience almost all my sysprep deployments fail to join the desktop into an AD domain. I have found that when I do a desktop provisioning through vCenter and the VM template used in deploying is already memeber of the desired AD domain the sysprep can do the domain join sucessfully. Which means: keep your templates joined to the desired domain. This is only goog if you going to use this template only for one domain.

Baeta

0 Kudos