Hello Rob,
Hmm the hotfix works. Multiple people have reported resolving the issue
after using the hotfix.
Here a couple of things to check. If it's not working it's usually one of
these things
Did you rebuild the image first, the default profile is not regenerated so
if sysprep was run with that image the default user profile was already
overwritten?
Are you using SP2 slipstreamed media? This is actually a change in SP2,
it's not really done by sysprep. ( sysprep just exposes the change)
So the hotfix would need to be deployed after SP2 was installed if you are
installing SP2 and not using slipstreamed media?
the hotfix reverts the behavior to pre-sp2 but there is also an unattended
setting to still copy the profile so if that exists it still will overwrite.
You can also rename the administrator account before running sysprep. If
the administrator account is renamed the copyprofile doesn't happen either.
Thanks,
Darrell Gorter[MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights
--------------------
<Thread-Topic: Sysyprep and default profiles
<thread-index: AcbyD6QU7s2zjR8mToGLVYJMgZF3Lw==
<X-WBNR-Posting-Host: 64.156.190.110
<From: =?Utf-8?B?Um9i?= <
[email protected]>
<Subject: Sysyprep and default profiles
<Date: Tue, 17 Oct 2006 10:14:01 -0700
<Lines: 11
<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: TK2MSFTNGXA01.phx.gbl
<Xref: TK2MSFTNGXA01.phx.gbl
microsoft.public.windowsxp.setup_deployment:154587
<NNTP-Posting-Host: TK2MSFTNGXA01.phx.gbl 10.40.2.250
<X-Tomcat-NG: microsoft.public.windowsxp.setup_deployment
<
<I've read a few things on TechNet about how sysprep strips the default
user
<profile and replaces it with the administrator profile. I've also read
about
<a hotfix that takes care of this issue. I've tried the hotfix but it
doesn't
<work, we still lose the default profile we've set up. I then tried the
<copyprofile tool but I get an error that says "Invalid permitted-to-use
<account name" when I put in Everyone for the permitted to use.
<
<This is driving me crazy. It is creating a lot of extra work for us when
we
<image and deploy new PC's then have to recreate the default profile.
<
<Can anyone steer me in the right direction?
<
