Sysprep issues with WinXP SP2 (that I did not have with WinXP SP1)

[Lyman Green]

Under SP1 I had an "master image" drive that had everything configured
exactly how I wanted it. When I needed to change the image, I would
logon with the administrator account and make the change to the system,
and then run sysprep and "use mini-setup" and then "reseal."
Everything worked great!

If I apply WinXPSP2 to the master image drive, the scenario changes,
and I haven't been able to figure out why for the life of me.

Under SP2 I am seeing the following behavior: I fire up a newly cloned
SP1 system. I have the system joining the network automatically via
the sysprep.inf file. All this works fine. I run WinXPSP2 and make a
few other post SP2 tweaks to the registry. Once I've confirmed XPSP2
is applied successfully to the system, I run sysprep, and choose the
same choices as I did under SP1 (use mini-setup and then reseal). All
still looks well - it appears as though everything is working. I take
the cloned copy and join it to the network and run through the
mini-setup wizard. I logon as administrator and add a new user (all as
I did exactly, no changes). When I then logoff and log on with the new
user, I see the weirdness.

For some reason, the new user has a number of the settings (both
registry and otherwise) that the administrator profile had! Like for
instance, I had a specific bitmap for the desktop background for the
admin profile only (splashed across the bitmap in capital letters
"Admin Logon"). Somehow, the sysprep process has copied that default
background bitmap into the default user settings!!! I completely do not
understand why or how this is happening, and I have confirmed that this
ONLY happens after the sysprep.

If I just apply WinXPSP2 and do not sysprep the system, and then add a
new user and logon with that user, I will not see these issues.

Another example: for the administrative profile I have "Display
Administrative Tools" selected in the Customize Classic Start Menu
options. I had that option OFF for the default user profile. Sysprep
has now copied that option to the default user profile.

Has anyone seen similar behavior and if so, do you have a solution?

I'd appreciate any assistance, I've been beating my head against a wall
trying to figure out why this is happening.

Lyman Green

 

[Darrell Gorter[MSFT]]

Hello Lyman,
This was a change that was requested and included with SP2
Here is a QFE article link to revert the behavior.
887816 Changes in behavior of the SysPrep and RIPREP tools after you
install Windows XP Service Pack 2
http://support.microsoft.com/default.aspx?scid=kb;EN-US;887816

Thanks,
Darrell Gorter[MSFT]

This posting is provided "AS IS" with no warranties, and confers no rights
--------------------
<From: "Lyman Green" <[email protected]>
<Newsgroups: microsoft.public.windowsxp.setup_deployment
<Subject: Sysprep issues with WinXP SP2 (that I did not have with WinXP SP1)
<Date: 12 Jan 2006 07:30:54 -0800
<Organization: http://groups.google.com
<Lines: 45
<Message-ID: <[email protected]>
<NNTP-Posting-Host: 192.58.204.226
<Mime-Version: 1.0
<Content-Type: text/plain; charset="iso-8859-1"
<X-Trace: posting.google.com 1137079859 26671 127.0.0.1 (12 Jan 2006
15:30:59 GMT)
<X-Complaints-To: (e-mail address removed)
<NNTP-Posting-Date: Thu, 12 Jan 2006 15:30:59 +0000 (UTC)
<User-Agent: G2/0.2
<X-HTTP-UserAgent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1;
.NET CLR 1.0.3705; .NET CLR 1.1.4322),gzip(gfe),gzip(gfe)
<Complaints-To: (e-mail address removed)
<Injection-Info: g43g2000cwa.googlegroups.com; posting-host=192.58.204.226;
< posting-account=EDSCdAwAAABnllg95lrEbqIVbKod9Z7P
<Path:
TK2MSFTNGXA02.phx.gbl!TK2MSFTNGP08.phx.gbl!newsfeed00.sul.t-online.de!t-onli
ne.de!border2.nntp.dca.giganews.com!border1.nntp.dca.giganews.com!nntp.gigan
ews.com!postnews.google.com!g43g2000cwa.googlegroups.com!not-for-mail
<Xref: TK2MSFTNGXA02.phx.gbl
microsoft.public.windowsxp.setup_deployment:146127
<X-Tomcat-NG: microsoft.public.windowsxp.setup_deployment
<
<Under SP1 I had an "master image" drive that had everything configured
<exactly how I wanted it. When I needed to change the image, I would
<logon with the administrator account and make the change to the system,
<and then run sysprep and "use mini-setup" and then "reseal."
<Everything worked great!
<
<If I apply WinXPSP2 to the master image drive, the scenario changes,
<and I haven't been able to figure out why for the life of me.
<
<Under SP2 I am seeing the following behavior: I fire up a newly cloned
<SP1 system. I have the system joining the network automatically via
<the sysprep.inf file. All this works fine. I run WinXPSP2 and make a
<few other post SP2 tweaks to the registry. Once I've confirmed XPSP2
<is applied successfully to the system, I run sysprep, and choose the
<same choices as I did under SP1 (use mini-setup and then reseal). All
<still looks well - it appears as though everything is working. I take
<the cloned copy and join it to the network and run through the
<mini-setup wizard. I logon as administrator and add a new user (all as
<I did exactly, no changes). When I then logoff and log on with the new
<user, I see the weirdness.
<
<For some reason, the new user has a number of the settings (both
<registry and otherwise) that the administrator profile had! Like for
<instance, I had a specific bitmap for the desktop background for the
<admin profile only (splashed across the bitmap in capital letters
<"Admin Logon"). Somehow, the sysprep process has copied that default
<background bitmap into the default user settings!!! I completely do not
<understand why or how this is happening, and I have confirmed that this
<ONLY happens after the sysprep.
<
<If I just apply WinXPSP2 and do not sysprep the system, and then add a
<new user and logon with that user, I will not see these issues.
<
<Another example: for the administrative profile I have "Display
<Administrative Tools" selected in the Customize Classic Start Menu
<options. I had that option OFF for the default user profile. Sysprep
<has now copied that option to the default user profile.
<
<Has anyone seen similar behavior and if so, do you have a solution?
<
<I'd appreciate any assistance, I've been beating my head against a wall
<trying to figure out why this is happening.
<
<Lyman Green
<
<

 

[Adam Leinss]

(e-mail address removed) ("Darrell Gorter[MSFT]") wrote in

Hello Lyman,
This was a change that was requested and included with SP2
Here is a QFE article link to revert the behavior.
887816 Changes in behavior of the SysPrep and RIPREP tools
after you install Windows XP Service Pack 2
http://support.microsoft.com/default.aspx?scid=kb;EN-US;887816

Makes sense. Most people use the administrator profile to create the
look they want and then copy to default user.


Adam

 

[Lyman Green]

I would agree completely that this "made sense" IF they (they being
Microsoft) had made WinXP SP1 work this way, but I've spent 3 years
customizing our default user profile via OTHER methods, and to have it
SUDDENLY be erased by my administrator profile is completely
ridiculous! In addition, I did not see any documentation of that
behavior! I mean really, that's insane to change something like that
without making it clear. I will not deny - if they had made this
behavior the default from the release of XP, then I would have had a
really easy time of the customization process. They didn't though!

Since I'm not an idiot I kept backups of old images pre-SP2 so I am now
able to use this "patch" and revert the behavior back to what it was
all along (the hotfix DID work, BTW) so I'm OK, but I think this is
just .... infuriating. I spent many, many hours trying to figure out
why the sysprep process was now "broken" and was intentionally copying
the admin profile customizations over my finely tuned and customized
default user profile.

And since I'm doing a bit of rant, let me say I think it is
reprehensible on the part of Microsoft to make this change, and then
NOT PROVIDE THE HOTFIX FOR DOWNLOAD. I mean really!! Thankfully we
have a premier support account in my company and I happen to know the
individual who has access to the downloads so she could get it for me
without me having to jump through hoops by calling Microsoft and
waiting on the phone or paying for it, or whatever.

That's my two cents on the issue.

Lyman Green

 

[Adam Leinss]

And since I'm doing a bit of rant, let me say I think it is
reprehensible on the part of Microsoft to make this change, and then
NOT PROVIDE THE HOTFIX FOR DOWNLOAD. I mean really!! Thankfully we
have a premier support account in my company and I happen to know the
individual who has access to the downloads so she could get it for me
without me having to jump through hoops by calling Microsoft and
waiting on the phone or paying for it, or whatever.

I agree. I'm not sure why certain hotfixes are only available via PSS.
Probably has something to do with $.

Adam

 

[Guest]

Hey Lyman--this has really infuriated me also, and after reading your post
and applying the fix, it still doesn't work.
I've had this same issue and applied the hotfix-887816--which in Premier is
two or three possible downloads, I'm using file name 219548. But it's still
applying the admin profile to default user.(I've always left the default
admin acct alone and created a "company admin" account to customize--then
copied to def. user-has worked for a long time)
Order of use: I customize the build-run the hotfix, restart and then copy
the profile to def. user. Run Sysprep and bam...the domain users desktop is
STILL the default admin account on XP. Am I doing something in the wrong
order?
Help. Thanks.

 

[Darrell Gorter[MSFT]]

Hello Lyman,
Actually Windows XP Gold was supposed to work this way. XPS2 actually
corrected the way to how it was supposed to work.
This was done per customer's requests as they bugged the problem.
The hotfix was actually a feature request to revert back to the old
behavior.
Thanks,
Darrell Gorter[MSFT]

This posting is provided "AS IS" with no warranties, and confers no rights
--------------------
<From: "Lyman Green" <[email protected]>
<Newsgroups: microsoft.public.windowsxp.setup_deployment
<Subject: Re: Sysprep issues with WinXP SP2 (that I did not have with WinXP
SP1)
<Date: 18 Jan 2006 07:07:34 -0800
<Organization: http://groups.google.com
<Lines: 30
<Message-ID: <[email protected]>
<References: <[email protected]>
< <[email protected]>
< <[email protected]>
<NNTP-Posting-Host: 192.58.204.226
<Mime-Version: 1.0
<Content-Type: text/plain; charset="iso-8859-1"
<X-Trace: posting.google.com 1137596859 21015 127.0.0.1 (18 Jan 2006
15:07:39 GMT)
<X-Complaints-To: (e-mail address removed)
<NNTP-Posting-Date: Wed, 18 Jan 2006 15:07:39 +0000 (UTC)
<In-Reply-To: <[email protected]>
<User-Agent: G2/0.2
<X-HTTP-UserAgent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1;
..NET CLR 1.0.3705; .NET CLR 1.1.4322),gzip(gfe),gzip(gfe)
<Complaints-To: (e-mail address removed)
<Injection-Info: g14g2000cwa.googlegroups.com; posting-host=192.58.204.226;
< posting-account=EDSCdAwAAABnllg95lrEbqIVbKod9Z7P
<Path:
TK2MSFTNGXA02.phx.gbl!TK2MSFTNGP08.phx.gbl!newsfeed00.sul.t-online.de!t-onli
ne.de!news.glorb.com!postnews.google.com!g14g2000cwa.googlegroups.com!not-fo
r-mail
<Xref: TK2MSFTNGXA02.phx.gbl
microsoft.public.windowsxp.setup_deployment:146457
<X-Tomcat-NG: microsoft.public.windowsxp.setup_deployment
<
<I would agree completely that this "made sense" IF they (they being
<Microsoft) had made WinXP SP1 work this way, but I've spent 3 years
<customizing our default user profile via OTHER methods, and to have it
<SUDDENLY be erased by my administrator profile is completely
<ridiculous! In addition, I did not see any documentation of that
<behavior! I mean really, that's insane to change something like that
<without making it clear. I will not deny - if they had made this
<behavior the default from the release of XP, then I would have had a
<really easy time of the customization process. They didn't though!
<
<Since I'm not an idiot I kept backups of old images pre-SP2 so I am now
<able to use this "patch" and revert the behavior back to what it was
<all along (the hotfix DID work, BTW) so I'm OK, but I think this is
<just .... infuriating. I spent many, many hours trying to figure out
<why the sysprep process was now "broken" and was intentionally copying
<the admin profile customizations over my finely tuned and customized
<default user profile.
<
<And since I'm doing a bit of rant, let me say I think it is
<reprehensible on the part of Microsoft to make this change, and then
<NOT PROVIDE THE HOTFIX FOR DOWNLOAD. I mean really!! Thankfully we
<have a premier support account in my company and I happen to know the
<individual who has access to the downloads so she could get it for me
<without me having to jump through hoops by calling Microsoft and
<waiting on the phone or paying for it, or whatever.
<
<That's my two cents on the issue.
<
<Lyman Green
<
<

 

[Guest]

Darrell-
Thanks for clarifying. Since XP's release, I've avoided touching the default
admin acct. and just created a corp user acct. to make all my customizations,
copy to default user, run sysprep and all was well. SP2 was released and it
still worked well.
But somewhere something changed in late 2005(an updated version of SP2--or
other updates) and none of my profiles were carrying over. After reading
extensively about this...I applied the 887816 fix which still doesn't work
(for me). The only way I've resolved the problem after much gnashing of teeth
was to use the old version of sysprep..file dated 8/17/2001. On 3/09/06, I
confirmed this and the suffering is over for now. It was just very
frustrating that after a few years of getting a good build process in place
that this suddenly changed.

Hello Lyman,
Actually Windows XP Gold was supposed to work this way. XPS2 actually
corrected the way to how it was supposed to work.
This was done per customer's requests as they bugged the problem.
The hotfix was actually a feature request to revert back to the old
behavior.
Thanks,
Darrell Gorter[MSFT]

This posting is provided "AS IS" with no warranties, and confers no rights
--------------------
<From: "Lyman Green" <[email protected]>
<Newsgroups: microsoft.public.windowsxp.setup_deployment
<Subject: Re: Sysprep issues with WinXP SP2 (that I did not have with WinXP
SP1)
<Date: 18 Jan 2006 07:07:34 -0800
<Organization: http://groups.google.com
<Lines: 30
<Message-ID: <[email protected]>
<References: <[email protected]>
< <[email protected]>
< <[email protected]>
<NNTP-Posting-Host: 192.58.204.226
<Mime-Version: 1.0
<Content-Type: text/plain; charset="iso-8859-1"
<X-Trace: posting.google.com 1137596859 21015 127.0.0.1 (18 Jan 2006
15:07:39 GMT)
<X-Complaints-To: (e-mail address removed)
<NNTP-Posting-Date: Wed, 18 Jan 2006 15:07:39 +0000 (UTC)
<In-Reply-To: <[email protected]>
<User-Agent: G2/0.2
<X-HTTP-UserAgent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1;
.NET CLR 1.0.3705; .NET CLR 1.1.4322),gzip(gfe),gzip(gfe)
<Complaints-To: (e-mail address removed)
<Injection-Info: g14g2000cwa.googlegroups.com; posting-host=192.58.204.226;
< posting-account=EDSCdAwAAABnllg95lrEbqIVbKod9Z7P
<Path:
TK2MSFTNGXA02.phx.gbl!TK2MSFTNGP08.phx.gbl!newsfeed00.sul.t-online.de!t-onli
ne.de!news.glorb.com!postnews.google.com!g14g2000cwa.googlegroups.com!not-fo
r-mail
<Xref: TK2MSFTNGXA02.phx.gbl
microsoft.public.windowsxp.setup_deployment:146457
<X-Tomcat-NG: microsoft.public.windowsxp.setup_deployment
<
<I would agree completely that this "made sense" IF they (they being
<Microsoft) had made WinXP SP1 work this way, but I've spent 3 years
<customizing our default user profile via OTHER methods, and to have it
<SUDDENLY be erased by my administrator profile is completely
<ridiculous! In addition, I did not see any documentation of that
<behavior! I mean really, that's insane to change something like that
<without making it clear. I will not deny - if they had made this
<behavior the default from the release of XP, then I would have had a
<really easy time of the customization process. They didn't though!
<
<Since I'm not an idiot I kept backups of old images pre-SP2 so I am now
<able to use this "patch" and revert the behavior back to what it was
<all along (the hotfix DID work, BTW) so I'm OK, but I think this is
<just .... infuriating. I spent many, many hours trying to figure out
<why the sysprep process was now "broken" and was intentionally copying
<the admin profile customizations over my finely tuned and customized
<default user profile.
<
<And since I'm doing a bit of rant, let me say I think it is
<reprehensible on the part of Microsoft to make this change, and then
<NOT PROVIDE THE HOTFIX FOR DOWNLOAD. I mean really!! Thankfully we
<have a premier support account in my company and I happen to know the
<individual who has access to the downloads so she could get it for me
<without me having to jump through hoops by calling Microsoft and
<waiting on the phone or paying for it, or whatever.
<
<That's my two cents on the issue.
<
<Lyman Green
<
<

 

[Darrell Gorter[MSFT]]

Hello,
Hmm, that is strange. The older version of sysprep should not work. The
change was not in Sysprep, Sysprep was just the vehicle.
The change was in syssetup.dll that shipped with SP2. The change occurs
during minisetup when syssetup.dll is run, so it doesn't matter which
version of Sysprep is run, what matters is what version of syssetup.dll is
present.
I seem to recall another workaround is to rename the administrator account.
It looks for an profile named administrator and uses that to overwrite the
default user account. If it doesn't find that profile, it doesn't do the
copy.
Thanks,
Darrell Gorter[MSFT]

This posting is provided "AS IS" with no warranties, and confers no rights
--------------------
<Thread-Topic: Sysprep issues with WinXP SP2 (that I did not have with WinXP
<thread-index: AcZEUUWozfQhe94eSby1vwm/C+Kvpw==
<X-WBNR-Posting-Host: 69.2.124.11
<From: =?Utf-8?B?Y3NobnlueQ==?= <[email protected]>
<References: <[email protected]>
<[email protected]>
<[email protected]>
<[email protected]>
<[email protected]>
<Subject: Re: Sysprep issues with WinXP SP2 (that I did not have with WinXP
<Date: Fri, 10 Mar 2006 06:45:27 -0800
<Lines: 95
<Message-ID: <[email protected]>
<MIME-Version: 1.0
<Content-Type: text/plain;
< charset="Utf-8"
<Content-Transfer-Encoding: 7bit
<X-Newsreader: Microsoft CDO for Windows 2000
<Content-Class: urn:content-classes:message
<Importance: normal
<Priority: normal
<X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830
<Newsgroups: microsoft.public.windowsxp.setup_deployment
<Path: TK2MSFTNGXA03.phx.gbl
<Xref: TK2MSFTNGXA03.phx.gbl
microsoft.public.windowsxp.setup_deployment:148214
<NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
<X-Tomcat-NG: microsoft.public.windowsxp.setup_deployment
<
<Darrell-
<Thanks for clarifying. Since XP's release, I've avoided touching the
default
<admin acct. and just created a corp user acct. to make all my
customizations,
<copy to default user, run sysprep and all was well. SP2 was released and
it
<still worked well.
<But somewhere something changed in late 2005(an updated version of SP2--or
<other updates) and none of my profiles were carrying over. After reading
<extensively about this...I applied the 887816 fix which still doesn't work
<(for me). The only way I've resolved the problem after much gnashing of
teeth
<was to use the old version of sysprep..file dated 8/17/2001. On 3/09/06, I
<confirmed this and the suffering is over for now. It was just very
<frustrating that after a few years of getting a good build process in
place
<that this suddenly changed.
<
<
<
<""Darrell Gorter[MSFT]"" wrote:
<
<> Hello Lyman,
<> Actually Windows XP Gold was supposed to work this way. XPS2 actually
<> corrected the way to how it was supposed to work.
<> This was done per customer's requests as they bugged the problem.
<> The hotfix was actually a feature request to revert back to the old
<> behavior.
<> Thanks,
<> Darrell Gorter[MSFT]
<>
<> This posting is provided "AS IS" with no warranties, and confers no
rights
<> --------------------
<> <From: "Lyman Green" <[email protected]>
<> <Newsgroups: microsoft.public.windowsxp.setup_deployment
<> <Subject: Re: Sysprep issues with WinXP SP2 (that I did not have with
WinXP
<> SP1)
<> <Date: 18 Jan 2006 07:07:34 -0800
<> <Organization: http://groups.google.com
<> <Lines: 30
<> <Message-ID: <[email protected]>
<> <References: <[email protected]>
<> < <[email protected]>
<> < <[email protected]>
<> <NNTP-Posting-Host: 192.58.204.226
<> <Mime-Version: 1.0
<> <Content-Type: text/plain; charset="iso-8859-1"
<> <X-Trace: posting.google.com 1137596859 21015 127.0.0.1 (18 Jan 2006
<> 15:07:39 GMT)
<> <X-Complaints-To: (e-mail address removed)
<> <NNTP-Posting-Date: Wed, 18 Jan 2006 15:07:39 +0000 (UTC)
<> <In-Reply-To: <[email protected]>
<> <User-Agent: G2/0.2
<> <X-HTTP-UserAgent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1;
SV1;
<> .NET CLR 1.0.3705; .NET CLR 1.1.4322),gzip(gfe),gzip(gfe)
<> <Complaints-To: (e-mail address removed)
<> <Injection-Info: g14g2000cwa.googlegroups.com;
posting-host=192.58.204.226;
<> < posting-account=EDSCdAwAAABnllg95lrEbqIVbKod9Z7P
<> <Path:
<>
TK2MSFTNGXA02.phx.gbl!TK2MSFTNGP08.phx.gbl!newsfeed00.sul.t-online.de!t-onli
<>
ne.de!news.glorb.com!postnews.google.com!g14g2000cwa.googlegroups.com!not-fo
<> r-mail
<> <Xref: TK2MSFTNGXA02.phx.gbl
<> microsoft.public.windowsxp.setup_deployment:146457
<> <X-Tomcat-NG: microsoft.public.windowsxp.setup_deployment
<> <
<> <I would agree completely that this "made sense" IF they (they being
<> <Microsoft) had made WinXP SP1 work this way, but I've spent 3 years
<> <customizing our default user profile via OTHER methods, and to have it
<> <SUDDENLY be erased by my administrator profile is completely
<> <ridiculous! In addition, I did not see any documentation of that
<> <behavior! I mean really, that's insane to change something like that
<> <without making it clear. I will not deny - if they had made this
<> <behavior the default from the release of XP, then I would have had a
<> <really easy time of the customization process. They didn't though!
<> <
<> <Since I'm not an idiot I kept backups of old images pre-SP2 so I am now
<> <able to use this "patch" and revert the behavior back to what it was
<> <all along (the hotfix DID work, BTW) so I'm OK, but I think this is
<> <just .... infuriating. I spent many, many hours trying to figure out
<> <why the sysprep process was now "broken" and was intentionally copying
<> <the admin profile customizations over my finely tuned and customized
<> <default user profile.
<> <
<> <And since I'm doing a bit of rant, let me say I think it is
<> <reprehensible on the part of Microsoft to make this change, and then
<> <NOT PROVIDE THE HOTFIX FOR DOWNLOAD. I mean really!! Thankfully we
<> <have a premier support account in my company and I happen to know the
<> <individual who has access to the downloads so she could get it for me
<> <without me having to jump through hoops by calling Microsoft and
<> <waiting on the phone or paying for it, or whatever.
<> <
<> <That's my two cents on the issue.
<> <
<> <Lyman Green
<> <
<> <
<>
<>
<