View 4.5 XP Base VM AD issue

[alwynstrydom]

Hallo

I recently upgraded from View 4.0.1 to View 4.5 Upgraded all ESX hosts to 4.1 as well as the VC to 4.1 Installed the latest version of the composer as well.

Upgraded the View agent on the Windows XP base images to 4.5 and also upgraded VMware tools to the latest version.

Re-deployed new pools, but now I get the following error:

2010/09/30 12:39:08 PM: View Composer agent initialization state error (18): Failed to join the domain (waited 915 seconds)

Have already tried the below without any resolution:

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=102441... \

Any suggestions would be great.

[mikebarnett]

This is almost certainly caused by the VM failing to get an IP before the domain join occurs. Can you confirm that you haven't run out of DHCP addresses or that the VMs have an IP when you log in to check out this error after it is seen?

Regards,

Mike

[alwynstrydom]

Hallo Mike

That is what I thought as well. Funny thing is that if you open a console session to one of the VM’s, it obtains an IP from the DHCP without any issues. But the VM itself, takes extremely long just to log onto.

I checked DNS and all seems ok.

Regards

Alwyn

[mikebarnett]

Interesting. Maybe it's getting that IP when you are trying to log in. If you check in VC do you see an IP listed on the Summary page of the VM itself?

Have you tried doing an 'ipconfig /release' on the parent VM just before you shut it down?

-Mike

[alwynstrydom]

Hallo

Jip, that is the funny part IP is showing in Sumary tab on VC. Every thing worked. Only changes, was updating to vSphere 4.1 and View 4.5 It previously worked without any glitches on 4.0.1

Funny thing is, it communicated with the View agent on the VM, because it indicates in the View inventory exactly what version of the client is installed, but keeps on giving the error.

2010/09/30 3:37:40 PM: View Composer agent initialization state error (18): Failed to join the domain (waited 960 seconds)

Regards

Alwyn

[alwynstrydom]

Oo, and yes, I have tried the ipconfig /release option and then re-provisioned the pool, but no go.

[porpoise77]

Is time synchonization configured properly in your snapshot?

[mikebarnett]

Good point about the time sync.

You can also take a look at the customization logs stored in C:\Windows\Temp to see what error is being thrown when it tries to join the domain.

Regards,

Mike Barnett, VCP

Technical Support Engineer

Business Critical Support

VMware Global Support Services

Tel: 905.315.6059

Email: mbarnett@vmware.com

[LarryBlanco2 · Accepted solution]

I had the same exact issue with XP and having it join the domain.

Download the following and it'll fix your issue. It has to do with a bug in SP3 and how view has it joining the domain.

http://support.microsoft.com/kb/944043

Download the XP package and try again. I'm certain it'll resolve your issue.

Larry

Remember to give points to helpful answers.

[alwynstrydom]

Hallo

Thanks Larry! This patch resolved the AD issue.

Have a new type of issue thou and this is that the VM's goes into a "Configuration error" status. If I check the events DB I get the following error:

Provisioning error occurred for Machine "VM Name": View Composer agent initialization failed

Any ideas on this one?

Regards

Alwyn

[alwynstrydom]

Hallo

Please find the composer log from one of the VM's attached.

Regards

[LarryBlanco2]

On this one I don't know off the top of my head.

Just as a start.. try to uninstall the agent and make sure if can successfully uninstall the agent completely. If not remove the reg entries left behind and reinstall the agent.

I have not come accross this error as of yet.

You may want to post a new thread to get others to assist as well.

Larry

[rbrink]

Hi,

Check you firewall settings.

Regards,

R. van den Brink