Vcd 5.1 VM (DHCP configuration) domain join fails

[mbalasre]

I am unable join Windows 7 VM to domain using the vapp Join domain option. This is failing with the following error

02/15/2013 17:09:35      RunCustomization 'runLater': 1

02/15/2013 17:09:35      About to run post-customization...

02/15/2013 17:09:35      Extracting customization script ...

02/15/2013 17:09:35      Key CUSTOMIZATIONINFO was not found in the config map

02/15/2013 17:09:35      Extracting customization script has successfully finished.

02/15/2013 17:09:35      Customization script step is complete.

02/15/2013 17:09:35      Guest operating system customization completed successfully

Everything including SID change works. I have been using the SetpComplete.cmd trick to get this working.

Thanks

[JayhawkEric]

If you logon to the VM after it's done can you reslolve the domain by DNS properly?

[guitzer]

Dear Sender:

Thank you for your email.

I will be out of office by next week returning back by Monday January 25th.

For any follow up, plesae contact Robert Matos 809-979-7052, for any URGENT matter please contact Elvin Urbaez 829-540-3574.

I will get back to you when return to the office.

Regards

GR

[mbalasre]

Yes i am able to resolve dns and join the machine to domain manually

[aneverov]

Hi,

> Key CUSTOMIZATIONINFO was not found in the config map

Is not an error, it's a warning which indicates that you run without pre-/post-customization script.

> I have been using the SetpComplete.cmd trick to get this working.

In VCD 5.1 (and previous ones) there is a number of unpleasant limitations with regards to joining domain. In 5.1 GA (and previous ones) networking configuration is always performed after sysprep tries to join the domain. The implication is that template NICs must be configured in such way that it's possible to join the domain without running VCD networking customization. This means:

1) for DHCP suggested DNS servers must be able to resolve domain name

2) for static provided manually DNS servers must be able to resolve domain name and static addresses must be valid for the connected VCD/VC network (network is already connected at the time VM is powered on)

To complicate things even more sysprep is known to reset NICs to DHCP automatically in some cases. This means that the only recommended approach for VCD 5.1 and before is 1), although 2) may randomly work for some templates.

Also I believe in VCD 5.1.1 there was a patch which additionally configures networking before running sysprep on Vista+ in order to allow for KMS activation to workaround "rearms" issue. That might help in some cases, but again approach 2) may not work.

I'm working on lifting these limitations, but I wouldn't expect that to be fixed in in 5.1.xxx releases since required changes are way too intrusive and require rewrites of some big parts of the current code.

/Andrii

[mbalasre]

> 1) for DHCP suggested DNS servers must be able to resolve domain name

I have configured DHCP for the VLAN used by external network and the vm is able to obtain ip from DHCP server. The domain name resolves as well. Once the customisation is over. Everything seems to work fine except for domain membership. Any other logs other than customization logs where i could get additional info?

[aneverov]

>> Any other logs other than customization logs where i could get additional info?

Sysprep logs are in %WINDIR%\Panther\Unattendgc (especially setupact.log and setuperr.log), there should be an error related to domain join. Could you please post those?

There are also logs in %WINDIR%\Debug, but those usually aren't that useful.

> I have configured DHCP for the VLAN used by external network and the vm  is able to obtain ip from DHCP server. The domain name resolves as well.

I would suggest to try to simplify setup even more, e.g. not use VLAN.

Also make sure not to include domain name into user's name:

domain: mydom.com

user: Administrator

pass: <somepass>

OU: <leave empty for testing pursposes, otherwise it should be something like OU=Unit1,DC=mydom,DC=com>

/Andrii

[mbalasre]

2013-03-05 15:31:29, Info                         [DJOIN.EXE] Unattended Join: Checking that auto start services have started.
2013-03-05 15:31:29, Info                         [DJOIN.EXE] Unattended Join: Joining domain [XXXXXXXXX]...
2013-03-05 15:31:29, Info                         [DJOIN.EXE] Unattended Join: Calling DsGetDcName for XXXXX...
2013-03-05 15:31:32, Warning                      [DJOIN.EXE] Unattended Join: DsGetDcName failed: 0x54b, last error is 0x0, will retry in 5 seconds...
2013-03-05 15:31:39, Warning                      [DJOIN.EXE] Unattended Join: DsGetDcName failed: 0x54b, last error is 0x0, will retry in 5 seconds...
2013-03-05 15:31:46, Warning                      [DJOIN.EXE] Unattended Join: DsGetDcName failed: 0x54b, last error is 0x0, will retry in 5 seconds...
2013-03-05 15:31:53, Warning                      [DJOIN.EXE] Unattended Join: DsGetDcName failed: 0x54b, last error is 0x0, will retry in 5 seconds...
2013-03-05 15:32:01, Warning                      [DJOIN.EXE] Unattended Join: DsGetDcName failed: 0x54b, last error is 0x0, will retry in 5 seconds...
2013-03-05 15:32:08, Warning                      [DJOIN.EXE] Unattended Join: DsGetDcName failed: 0x54b, last error is 0x0, will retry in 5 seconds...
2013-03-05 15:32:15, Warning                      [DJOIN.EXE] Unattended Join: DsGetDcName failed: 0x54b, last error is 0x0, will retry in 5 seconds...
2013-03-05 15:32:22, Warning                      [DJOIN.EXE] Unattended Join: DsGetDcName failed: 0x54b, last error is 0x0, will retry in 5 seconds...
2013-03-05 15:32:30, Warning                      [DJOIN.EXE] Unattended Join: DsGetDcName failed: 0x54b, last error is 0x0, will retry in 5 seconds...
2013-03-05 15:32:37, Warning                      [DJOIN.EXE] Unattended Join: DsGetDcName failed: 0x54b, last error is 0x0, will retry in 5 seconds...
2013-03-05 15:32:44, Warning                      [DJOIN.EXE] Unattended Join: DsGetDcName failed: 0x54b, last error is 0x0, will retry in 5 seconds...
2013-03-05 15:32:52, Warning                      [DJOIN.EXE] Unattended Join: DsGetDcName failed: 0x54b, last error is 0x0, will retry in 5 seconds...
2013-03-05 15:38:12, Warning                      [DJOIN.EXE] Unattended Join: DsGetDcName failed: 0x54b, last error is 0x0, will retry in 5 seconds...
2013-03-05 15:38:20, Warning                      [DJOIN.EXE] Unattended Join: DsGetDcName failed: 0x54b, last error is 0x0, will retry in 5 seconds...
2013-03-05 15:38:27, Warning                      [DJOIN.EXE] Unattended Join: DsGetDcName failed: 0x54b, last error is 0x0, will retry in 5 seconds...
2013-03-05 15:38:32, Error                        [DJOIN.EXE] Unattended Join: NetJoinDomain failed error code is [1355]
2013-03-05 15:38:32, Error                        [DJOIN.EXE] Unattended Join: Unable to join; gdwError = 0x54b
2013-03-05 15:38:32, Info                         [DJOIN.EXE] Unattended Join: Exit, returning 0x0

Errors from setupact. Looks like network is not up resulting in Error 1355: The specified domain either does not exist or could not be contacted

[aneverov]

Yes, it seems like.

http://technet.microsoft.com/en-us/library/cc961817.aspx suggests:

"To investigate further, run nltest /dsgetdc:< domain-name > and examine the output. If you still receive errors, either the domain really does not exist or there is a transient net error that is preventing domain controller discovery. By running Netdiag.exe and examining the output, you usually can determine the cause. A "Failure to connect to a domain controller" message usually means that transient net errors or insufficient credentials are the cause."

Could you try to put something like that into pre-customization script? Also any other troubleshooting things like ping or even "netdom join" just to see if that works.

prost-customization script is executed after network is fully reconfigured, so that's why "netdom join" in there has higher chances to succeed.

/Andrii