View/quickprep breaking Windows XP SP3 domain membership?

[KFM]

So I have a problem with View or quickprep in my VDI installation.

I am currently using the latest build of View (3.0.1) and my desktop is a vanilla Windows XP SP3 image.

If I deploy a pool and use quickprep to add the desktops to the domain, I find that after the desktops have been deployed and created, that they are not in fact on the domain. i.e. at the Windows logon screen, I get no option to choose a domain to logon to, in fact, the desktop has not been added to the domain and is just a part of a workgroup.

BUT, if I check Active Directory, I can see the computer accounts created by View! What gives!?

It seems to be only the quickprep (or something to do with the pool provisioning) that breaks the image/domain membership. If I manually deploy a Windows XP SP3 VM using either a customization specification or the customisation wizard then it works fine.

Anyone else experiencing this problem? For the record, the same deployment works for Windows XP SP2 machines so it seems isolated to just SP3.

[jimjimk]

Do you mean sysprep? and are you using the correct version of Sysprep for SP3 - remember all service packs have their own sysprep...

[admin]

HI there,

I've that running with SP3 on my environment. Please check DHCP (does the desktop have an IP address) and also check the FQDN name resolution.... The View Composer does use the given domain admin account to add the desktops to the domain, is this account valid?

Is there somethin in the logs files?

Please check the things above, after that:

What's in the event tab?

Can you see something in the composer logfile? (C:\program files\vmware\view composer\....*.log)

If you cant find the issue .... create a debug log! Check the start menu / vmware folder for that! (on the server, agent, client, composer)

Thanks,

Christoph

[Rodos]

Kam, you get this resolved yet?

Rodos

Consider the use of the helpful or correct buttons to award points. Blog: http://rodos.haywood.org/

[KFM]

No I don't mean sysprep - I already alluded to the fact that using the customisation specification to sysprep the VM worked fine and that uses the sysprep files in the c:\documents and settings\all users\blahblah\sysprep folder.

[KFM]

Hi Christoph,

Thanks for your suggestions. I'll check the log files and the event tab and check out the debug log.

For the record, the domain admin account used by View Composer works fine - I can successfully quickprep Win XP SP2 machines so Win XP SP3 should be no different (you would think). Ditto with the DHCP settings as it has always worked with SP2 machines but I'll double check tomorrow when I'm back in the office.

[KFM]

Nah not yet mate, if I can't work it out, Robin suggested I contact VMware support. Funny enough he also said that he's having the same problem (I think) so good to hear it's not just me!

[mpryor]

For linked clone pools that use quickprep, you need to use a master snapshot that is already in the domain (the opposite to the recommendation for a normal sysprep). Could you confirm that is the case?

Thanks,

Mike

[ako]

Hi

Have jou checked, that the Netbios Name of tze Master Image does not contain any unsupported characters. I had exaclty the same Problem

[admin]

Just curious, did you ever find a solution to your problem? I am experiencing the same issue and wanted to know if a soution had been found.

[KFM]

I never found a proper solution per se. All I did was remove my WinXP SP3 VM from the domain then rejoined it. All subsequent linked clone deployments were successful, ie joined the domain fine.

I have some theories on why the original deployment didn't work but I don't have time right now to test those out so I used the above method to get over that hurdle. It may be the only fix and in reality, how hard/quick is it to do a remove/add to domain? Not very!

[dongtranuc]

I had an issue similar to this. My VM template was joined to the domain, and I would always logon as the local administrator to update it. Unknowingly, the AD computer account had disabled/changed/SID was updated at some other point. Solution was to disjoin domain, and rejoin, all subsequent linked-clone functions worked, correctly.

[Scott_T]

I had this exact same issue ..

local firewall was turned on the eth adapter ..

[Scott_T]

and system restore ON