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"
<derick.schuetz@additional.hosts.confuse.bots.us.benfieldgroup.com>
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: <#
[email protected]>
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?
