Hi.

I've been using sysprep to manage my Windows XP image since conception.
Every few months I update our "Template" image and create a new Post-Sysprep
image with new applications and product updates just to lessen the load once
machines are imaged. We also have very specific things we want set up in
the users' profiles, so we set that up under Default User beforehand.

The way that I've always created the Default User profile is to:

A) Create a Local User called "COMPANYNAME", login as that and make my Start
Menu/Explorer/IE Settings changes.
B) Login as Local Admin
C) Remove customization from the COMPANYNAME user's profile folder, such as
Desktop.INI files' OWNER=COMPANYNAME lines. This makes them be recreated
for new users logging into the system.
D) Using the System control panel, copy that user's profile to the Default
User profile, marked usable for Everyone.
E) Disable that local user account, Delete that user's profile, then
Sysprep-Reseal and ghost to the network.

This was working great. New users logging into the system post-sysprep
would get a perfectly configured user profile.

This morning I decided to update the Post-Sysprep image to SP2 to get our QA
group going on testing the final code. Suddenly, the Default User's profile
is being filled with items from the Local Administrator's user profile for
some reason. The OWNER=USERNAME lines are back into the DESKTOP.INI files
that I specifically cleared out of the Default User folder before imaging.
In fact, I can open the Ghost Image in Ghost Explorer and see for myself
that those lines are NOT THERE. Between mini-setup and userlogin something
is copying Administrator's profile to Default User. This behavior is new in
SP2. Anyone have any ideas why this is happening?

Hello Derrick,
It's a change in SP2 that was supposed to be in SP1. The Local
Administrator account is used to overwrite the default user account.
Thanks,
Darrell Gorter[MSFT]

This posting is provided "AS IS" with no warranties, and confers no rights
--------------------
>From: "Derick Schuetz"
<(E-Mail Removed)>
>Subject: Sysprep on SP2 - Default User profile
>Date: Wed, 11 Aug 2004 13:46:48 -0500
>Lines: 35
>X-Priority: 3
>X-MSMail-Priority: Normal
>X-Newsreader: Microsoft Outlook Express 6.00.2900.2180
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
>X-RFC2646: Format=Flowed; Original
>Message-ID: <#$(E-Mail Removed)>
>Newsgroups: microsoft.public.windowsxp.setup_deployment
>NNTP-Posting-Host: 198.184.20.126
>Path:
cpmsftngxa06.phx.gbl!TK2MSFTNGXA01.phx.gbl!TK2MSFTFEED01.phx.gbl!TK2MSFTNGP0
8.phx.gbl!TK2MSFTNGP10.phx.gbl
>Xref: cpmsftngxa06.phx.gbl
microsoft.public.windowsxp.setup_deployment:118829
>X-Tomcat-NG: microsoft.public.windowsxp.setup_deployment
>
>Hi.
>
>I've been using sysprep to manage my Windows XP image since conception.
>Every few months I update our "Template" image and create a new
Post-Sysprep
>image with new applications and product updates just to lessen the load
once
>machines are imaged. We also have very specific things we want set up in
>the users' profiles, so we set that up under Default User beforehand.
>
>The way that I've always created the Default User profile is to:
>
>A) Create a Local User called "COMPANYNAME", login as that and make my
Start
>Menu/Explorer/IE Settings changes.
>B) Login as Local Admin
>C) Remove customization from the COMPANYNAME user's profile folder, such
as
>Desktop.INI files' OWNER=COMPANYNAME lines. This makes them be recreated
>for new users logging into the system.
>D) Using the System control panel, copy that user's profile to the Default
>User profile, marked usable for Everyone.
>E) Disable that local user account, Delete that user's profile, then
>Sysprep-Reseal and ghost to the network.
>
>This was working great. New users logging into the system post-sysprep
>would get a perfectly configured user profile.
>
>This morning I decided to update the Post-Sysprep image to SP2 to get our
QA
>group going on testing the final code. Suddenly, the Default User's
profile
>is being filled with items from the Local Administrator's user profile for
>some reason. The OWNER=USERNAME lines are back into the DESKTOP.INI files
>that I specifically cleared out of the Default User folder before imaging.
>In fact, I can open the Ghost Image in Ghost Explorer and see for myself
>that those lines are NOT THERE. Between mini-setup and userlogin
something
>is copying Administrator's profile to Default User. This behavior is new
in
>SP2. Anyone have any ideas why this is happening?
>
>
>

I have used the same methodology in the past and I experience the same
behaviour with SP2 now. Another difference: before, an image built for
an HP Evo d530 would work for a d510. With the SP2 sysprep, it does
not ...

I need to do further tests but I think I am not even able to copy my
"template user" to the default user profile. There is a DEFUSER hive
loaded (I had a look at a SP1 and it is not there...) and I get the
message "Failed to copy [...]Default user\ntuser.dat [...] because the
file is being used by another process"

So,

Do you mean the default user account is pretty much useless now ?

Should we just configure the local "Administrator" account instead ?

What do you exactly mean by "overwrite", is it kind of a merge or the
"Administrator" acount is used instead of the "Default user" ?

Thanks a lot in advance for any help,


(E-Mail Removed) ("Darrell Gorter[MSFT]") wrote in message news:<0iu6HM$(E-Mail Removed)>...
> Hello Derrick,
> It's a change in SP2 that was supposed to be in SP1. The Local
> Administrator account is used to overwrite the default user account.
> Thanks,
> Darrell Gorter[MSFT]
>

well that's bad news! is there any way around this new feature?

(E-Mail Removed) ("Darrell Gorter[MSFT]") wrote in message news:<0iu6HM$(E-Mail Removed)>...
> Hello Derrick,
> It's a change in SP2 that was supposed to be in SP1. The Local
> Administrator account is used to overwrite the default user account.
> Thanks,
> Darrell Gorter[MSFT]
>
> This posting is provided "AS IS" with no warranties, and confers no rights
> --------------------
> >From: "Derick Schuetz"
> <(E-Mail Removed)>
> >Subject: Sysprep on SP2 - Default User profile
> >Date: Wed, 11 Aug 2004 13:46:48 -0500
> >Lines: 35
> >X-Priority: 3
> >X-MSMail-Priority: Normal
> >X-Newsreader: Microsoft Outlook Express 6.00.2900.2180
> >X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
> >X-RFC2646: Format=Flowed; Original
> >Message-ID: <#$(E-Mail Removed)>
> >Newsgroups: microsoft.public.windowsxp.setup_deployment
> >NNTP-Posting-Host: 198.184.20.126
> >Path:
> cpmsftngxa06.phx.gbl!TK2MSFTNGXA01.phx.gbl!TK2MSFTFEED01.phx.gbl!TK2MSFTNGP0
> 8.phx.gbl!TK2MSFTNGP10.phx.gbl
> >Xref: cpmsftngxa06.phx.gbl
> microsoft.public.windowsxp.setup_deployment:118829
> >X-Tomcat-NG: microsoft.public.windowsxp.setup_deployment
> >
> >Hi.
> >
> >I've been using sysprep to manage my Windows XP image since conception.
> >Every few months I update our "Template" image and create a new
> Post-Sysprep
> >image with new applications and product updates just to lessen the load
> once
> >machines are imaged. We also have very specific things we want set up in
> >the users' profiles, so we set that up under Default User beforehand.
> >
> >The way that I've always created the Default User profile is to:
> >
> >A) Create a Local User called "COMPANYNAME", login as that and make my
> Start
> >Menu/Explorer/IE Settings changes.
> >B) Login as Local Admin
> >C) Remove customization from the COMPANYNAME user's profile folder, such
> as
> >Desktop.INI files' OWNER=COMPANYNAME lines. This makes them be recreated
> >for new users logging into the system.
> >D) Using the System control panel, copy that user's profile to the Default
> >User profile, marked usable for Everyone.
> >E) Disable that local user account, Delete that user's profile, then
> >Sysprep-Reseal and ghost to the network.
> >
> >This was working great. New users logging into the system post-sysprep
> >would get a perfectly configured user profile.
> >
> >This morning I decided to update the Post-Sysprep image to SP2 to get our
> QA
> >group going on testing the final code. Suddenly, the Default User's
> profile
> >is being filled with items from the Local Administrator's user profile for
> >some reason. The OWNER=USERNAME lines are back into the DESKTOP.INI files
> >that I specifically cleared out of the Default User folder before imaging.
> >In fact, I can open the Ghost Image in Ghost Explorer and see for myself
> >that those lines are NOT THERE. Between mini-setup and userlogin
> something
> >is copying Administrator's profile to Default User. This behavior is new
> in
> >SP2. Anyone have any ideas why this is happening?
> >
> >
> >

I have been creating images using PowerQuest the same way you are
using Ghost. Yesterday I updated an image with Windows SP2 and ran
sysprep with the mini install. I thought I had messed up copying the
default profile and redid the image again this morning. I got the
same results you got. I have not found out how to correct the problem
or get a work around. I found nothing on Microsoft's website.
Talking to them I was told it would be a charged call for $200 and
some dollars. The only thing I see is to copy the default profile
after the mini install is finished. That is going to be a lot more
work for each deployed image.
Please let me know if you find out anything more.

Hello,
There is no workaround currently.
Thanks,
Darrell Gorter[MSFT]

This posting is provided "AS IS" with no warranties, and confers no rights
--------------------
>From: (E-Mail Removed) (gdock99)
>Newsgroups: microsoft.public.windowsxp.setup_deployment
>Subject: Re: Sysprep on SP2 - Default User profile
>Date: 13 Aug 2004 09:56:52 -0700
>Organization: http://groups.google.com
>Lines: 11
>Message-ID: <(E-Mail Removed)>
>References: <#$(E-Mail Removed)>
>NNTP-Posting-Host: 66.28.32.148
>Content-Type: text/plain; charset=ISO-8859-1
>Content-Transfer-Encoding: 8bit
>X-Trace: posting.google.com 1092416213 12750 127.0.0.1 (13 Aug 2004
16:56:53 GMT)
>X-Complaints-To: groups-(E-Mail Removed)
>NNTP-Posting-Date: Fri, 13 Aug 2004 16:56:53 +0000 (UTC)
>Path:
cpmsftngxa06.phx.gbl!TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!newsfeed00.s
ul.t-online.de!t-online.de!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!p
ostnews2.google.com!not-for-mail
>Xref: cpmsftngxa06.phx.gbl
microsoft.public.windowsxp.setup_deployment:119078
>X-Tomcat-NG: microsoft.public.windowsxp.setup_deployment
>
>I have been creating images using PowerQuest the same way you are
>using Ghost. Yesterday I updated an image with Windows SP2 and ran
>sysprep with the mini install. I thought I had messed up copying the
>default profile and redid the image again this morning. I got the
>same results you got. I have not found out how to correct the problem
>or get a work around. I found nothing on Microsoft's website.
>Talking to them I was told it would be a charged call for $200 and
>some dollars. The only thing I see is to copy the default profile
>after the mini install is finished. That is going to be a lot more
>work for each deployed image.
>Please let me know if you find out anything more.
>

Hello Juan,
The change I am talking about is that the Local Administrator Profile is
copied over the Default User profile when you run Sysprep on a machine. So
yes you should configure the Local Administrator account now before you run
sysprep.
This does not affect the hardware issue listed below that is something else.
It should also not affect the copying of the profile. How are you copying
the profile? Are you using System Control Panel applet?
Thanks,
Darrell Gorter[MSFT]

This posting is provided "AS IS" with no warranties, and confers no rights
--------------------
>From: (E-Mail Removed) (Juan)
>Newsgroups: microsoft.public.windowsxp.setup_deployment
>Subject: Re: Sysprep on SP2 - Default User profile
>Date: 13 Aug 2004 05:21:01 -0700
>Organization: http://groups.google.com
>Lines: 30
>Message-ID: <(E-Mail Removed)>
>References: <#$(E-Mail Removed)>
<0iu6HM$(E-Mail Removed)>
>NNTP-Posting-Host: 194.7.121.5
>Content-Type: text/plain; charset=ISO-8859-1
>Content-Transfer-Encoding: 8bit
>X-Trace: posting.google.com 1092399661 31313 127.0.0.1 (13 Aug 2004
12:21:01 GMT)
>X-Complaints-To: groups-(E-Mail Removed)
>NNTP-Posting-Date: Fri, 13 Aug 2004 12:21:01 +0000 (UTC)
>Path:
cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!newsfeed00.sul.t-online.de!t-onlin
e.de!news.glorb.com!postnews2.google.com!not-for-mail
>Xref: cpmsftngxa06.phx.gbl
microsoft.public.windowsxp.setup_deployment:119045
>X-Tomcat-NG: microsoft.public.windowsxp.setup_deployment
>
>I have used the same methodology in the past and I experience the same
>behaviour with SP2 now. Another difference: before, an image built for
>an HP Evo d530 would work for a d510. With the SP2 sysprep, it does
>not ...
>
>I need to do further tests but I think I am not even able to copy my
>"template user" to the default user profile. There is a DEFUSER hive
>loaded (I had a look at a SP1 and it is not there...) and I get the
>message "Failed to copy [...]Default user\ntuser.dat [...] because the
>file is being used by another process"
>
>So,
>
>Do you mean the default user account is pretty much useless now ?
>
>Should we just configure the local "Administrator" account instead ?
>
>What do you exactly mean by "overwrite", is it kind of a merge or the
>"Administrator" acount is used instead of the "Default user" ?
>
>Thanks a lot in advance for any help,
>
>
>(E-Mail Removed) ("Darrell Gorter[MSFT]") wrote in message
news:<0iu6HM$(E-Mail Removed)>...
>> Hello Derrick,
>> It's a change in SP2 that was supposed to be in SP1. The Local
>> Administrator account is used to overwrite the default user account.
>> Thanks,
>> Darrell Gorter[MSFT]
>>
>

Hello Marshall,
There is no current workaround to this if you use SP2.
Thanks,
Darrell Gorter[MSFT]

This posting is provided "AS IS" with no warranties, and confers no rights
--------------------
>From: (E-Mail Removed) (marshall brunson)
>Newsgroups: microsoft.public.windowsxp.setup_deployment
>Subject: Re: Sysprep on SP2 - Default User profile
>Date: 13 Aug 2004 08:50:24 -0700
>Organization: http://groups.google.com
>Lines: 75
>Message-ID: <(E-Mail Removed)>
>References: <#$(E-Mail Removed)>
<0iu6HM$(E-Mail Removed)>
>NNTP-Posting-Host: 159.178.48.46
>Content-Type: text/plain; charset=ISO-8859-1
>Content-Transfer-Encoding: 8bit
>X-Trace: posting.google.com 1092412225 9587 127.0.0.1 (13 Aug 2004
15:50:25 GMT)
>X-Complaints-To: groups-(E-Mail Removed)
>NNTP-Posting-Date: Fri, 13 Aug 2004 15:50:25 +0000 (UTC)
>Path:
cpmsftngxa06.phx.gbl!TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!newsfeed00.s
ul.t-online.de!t-online.de!border2.nntp.dca.giganews.com!border1.nntp.dca.gi
ganews.com!nntp.giganews.com!news.maxwell.syr.edu!postnews2.google.com!not-f
or-mail
>Xref: cpmsftngxa06.phx.gbl
microsoft.public.windowsxp.setup_deployment:119073
>X-Tomcat-NG: microsoft.public.windowsxp.setup_deployment
>
>well that's bad news! is there any way around this new feature?
>
>(E-Mail Removed) ("Darrell Gorter[MSFT]") wrote in message
news:<0iu6HM$(E-Mail Removed)>...
>> Hello Derrick,
>> It's a change in SP2 that was supposed to be in SP1. The Local
>> Administrator account is used to overwrite the default user account.
>> Thanks,
>> Darrell Gorter[MSFT]
>>
>> This posting is provided "AS IS" with no warranties, and confers no
rights
>> --------------------
>> >From: "Derick Schuetz"
>> <(E-Mail Removed)>
>> >Subject: Sysprep on SP2 - Default User profile
>> >Date: Wed, 11 Aug 2004 13:46:48 -0500
>> >Lines: 35
>> >X-Priority: 3
>> >X-MSMail-Priority: Normal
>> >X-Newsreader: Microsoft Outlook Express 6.00.2900.2180
>> >X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
>> >X-RFC2646: Format=Flowed; Original
>> >Message-ID: <#$(E-Mail Removed)>
>> >Newsgroups: microsoft.public.windowsxp.setup_deployment
>> >NNTP-Posting-Host: 198.184.20.126
>> >Path:
>>
cpmsftngxa06.phx.gbl!TK2MSFTNGXA01.phx.gbl!TK2MSFTFEED01.phx.gbl!TK2MSFTNGP0
>> 8.phx.gbl!TK2MSFTNGP10.phx.gbl
>> >Xref: cpmsftngxa06.phx.gbl
>> microsoft.public.windowsxp.setup_deployment:118829
>> >X-Tomcat-NG: microsoft.public.windowsxp.setup_deployment
>> >
>> >Hi.
>> >
>> >I've been using sysprep to manage my Windows XP image since conception.
>> >Every few months I update our "Template" image and create a new
>> Post-Sysprep
>> >image with new applications and product updates just to lessen the load
>> once
>> >machines are imaged. We also have very specific things we want set up
in
>> >the users' profiles, so we set that up under Default User beforehand.
>> >
>> >The way that I've always created the Default User profile is to:
>> >
>> >A) Create a Local User called "COMPANYNAME", login as that and make my
>> Start
>> >Menu/Explorer/IE Settings changes.
>> >B) Login as Local Admin
>> >C) Remove customization from the COMPANYNAME user's profile folder,
such
>> as
>> >Desktop.INI files' OWNER=COMPANYNAME lines. This makes them be
recreated
>> >for new users logging into the system.
>> >D) Using the System control panel, copy that user's profile to the
Default
>> >User profile, marked usable for Everyone.
>> >E) Disable that local user account, Delete that user's profile, then
>> >Sysprep-Reseal and ghost to the network.
>> >
>> >This was working great. New users logging into the system post-sysprep
>> >would get a perfectly configured user profile.
>> >
>> >This morning I decided to update the Post-Sysprep image to SP2 to get
our
>> QA
>> >group going on testing the final code. Suddenly, the Default User's
>> profile
>> >is being filled with items from the Local Administrator's user profile
for
>> >some reason. The OWNER=USERNAME lines are back into the DESKTOP.INI
files
>> >that I specifically cleared out of the Default User folder before
imaging.
>> >In fact, I can open the Ghost Image in Ghost Explorer and see for
myself
>> >that those lines are NOT THERE. Between mini-setup and userlogin
>> something
>> >is copying Administrator's profile to Default User. This behavior is
new
>> in
>> >SP2. Anyone have any ideas why this is happening?
>> >
>> >
>> >
>

Thank you Darrell,

- it's good to know about this change ! Any piece of documentation or
article where this is mentioned ? Any other relevant changes in
sysprep?

- About the hardware issue, I figured it out: there are updated HDD
drivers in SP2. Before, more generic drivers were there before
ghosting and this fact rendered the image compatible between the two
EVOs.

- I do use ctrl panel to copy the profile. I was able to workaround
the problem by unloading the DEFUSER hive (by the way, why it is there
now...?)

Cheers,

Juan

(E-Mail Removed) ("Darrell Gorter[MSFT]") wrote in message news:<(E-Mail Removed)>...
> Hello Juan,
> The change I am talking about is that the Local Administrator Profile is
> copied over the Default User profile when you run Sysprep on a machine. So
> yes you should configure the Local Administrator account now before you run
> sysprep.
> This does not affect the hardware issue listed below that is something else.
> It should also not affect the copying of the profile. How are you copying
> the profile? Are you using System Control Panel applet?
> Thanks,
> Darrell Gorter[MSFT]
>

ok - just so i have this right - why the heck would you want to overwrite the
default user profile with the Admin profile?!!?!?

frankly this totally screws over our imaging process we use to create our
master images with...

Where is the documentation on this process?!?!!?!?

there should not need to be any need for a workaround.... it should be built
right in the first place!



""Darrell Gorter[MSFT]"" wrote:

> Hello,
> There is no workaround currently.
> Thanks,
> Darrell Gorter[MSFT]
>