I am trying to redeploy XP. Things are going fine, I have my base image we will be deploying just about everything through Citrix, however I am having one problem that is driving me nuts!

I install the image fine from sysprep and then use a script in the HKLM...Run which calls my routines to rename the PC from its bios, Joins the PC to the domain and changes the auto login to be a domain login, add various domain groups to local groups for local file rights, installs some apps like the Citrix client cleans itself up and so on.

I have had this script working on a previous image, but now when I import my registry file to change the local login to a domain login it does not retain the imported registry file settings.

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon]

"AltDefaultDomainName"="Our Domain"
"DefaultDomainName"="Our Domain"

Any ideas before I pull all my hair out?
0 Comments   [ - ] Hide Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
Answer this question or Comment on this question for clarity


I ran into this the other day. My registry information imported successfully, but the DefaultDomainName key was being changed.

I was able to determine that we had a group policy object that ran a system startup script that included a section that would change the Default Domain Name back to our main AD domain. The problem is that in order for AutoAdminLogon to work properly, you need to reboot the computer, then the Domain GP objects are applied, then the user is allowed to login. Since the Domain GP is applied before the GP settings are applied, autoadminlogon would never work properly.

I worked around this by adding the computer to an OU where this GP didn't apply.

Not sure if this exactly relates to your problem, but it is worth investigating
Answered 07/08/2011 by: jstorino
Senior Yellow Belt

Please log in to comment