VMware Cloud Community
phil123
Contributor
Contributor

Trouble joining domain during template deployment

ESX 3.02 and ESX 3.5 with VC 2.5.

Had issue where after deploying a template my new VM doesn't join the domain. Before the upgrade to 2.5 everything was ok. (My template is not in the domain)

I use Customization Specificatin manager with sysprep
when I deploy a new VM. I recreate the customization after the upgrade to 2.5 and is still not working.




No errors appear... and the log history is clear




(The template and customization are for a Windows 2003 standard edition)




any idea ?


thanks


Reply
0 Kudos
6 Replies
rriva
Expert
Expert

what do you mean with "does not join the domain" ?

You can't add the machine to the domain or you can add it but you can't login to the domain after the reboot ?

Riccardo Riva

If you found this or other information useful, please consider awarding points for "Correct" or "Helpful". Thank You!

RRiva | http://about.me/riccardoriva | http://www.riccardoriva.com
Reply
0 Kudos
phil123
Contributor
Contributor

I mean the new windows server 2003 VM is not in the domain. Normally, the vm will join the domain automatically. there's a place where you can choose to join the domain automatically in the "customization specifications" in VI - edit - customization specifications.

Reply
0 Kudos
rriva
Expert
Expert

Yes I know ...

but after deployment, you could manually add the machine to the domain or you couldn't ?

Riccardo Riva

If you found this or other information useful, please consider awarding points for "Correct" or "Helpful". Thank You!

RRiva | http://about.me/riccardoriva | http://www.riccardoriva.com
Reply
0 Kudos
phil123
Contributor
Contributor

Yes I could

Reply
0 Kudos
jkstewie
Contributor
Contributor

I too have the same problem, mine wasnt an upgrade to 2.5, it was really a clean install. The customizations I have (which I have created from new with clear text passwords) fail to join servers to the domain, without any errors shown. I think alot of people are having issues with customizations on VirtualCenter 2.5

Reply
0 Kudos
jkstewie
Contributor
Contributor

Just realised my issue was with a bad password in the customization, since I am using clear text passwords (due to the bug with 2.5 of not decrypting passwords) I had mistakenly left an '=' at the end of the password, both for the local administrator account, and the domain admin account password used to join the domain.

Reply
0 Kudos