Sysprep Version 2 not keeping customized settings- I applied the h

[Guest]

We're about to do a rollout of new computer systems and I'm running into
problems trying to sysprep the machines. I've configured each system with XP
PRO SP2 and configured a customized profile. I than copy the Customized
profile to the Default User Profile in the User Profiles dialog box. There is
a hot fix and known problem with sysprep and mini-setup where it strips the
settings in the default profile and uses the administrator profile settings
instead. I called MS and installed the hotfix however it doesn't seem to be
working. After going through mini-setup and joining a domain the customized
settings are mostly gone. If I log in as a user with limited rights some
desktop icons do not work and the corporate wallpaper is not displayed. If I
log in as an admin on the domain everything works properly. So it looks like
the hot fix isn't working. Am I doing something wrong here? Or is there a
work around?

Thanks,
Pete

 

[Adam Leinss]

We're about to do a rollout of new computer systems and I'm
running into problems trying to sysprep the machines. I've
configured each system with XP PRO SP2 and configured a customized
profile. I than copy the Customized profile to the Default User
Profile in the User Profiles dialog box. There is a hot fix and
known problem with sysprep and mini-setup where it strips the
settings in the default profile and uses the administrator profile
settings instead. I called MS and installed the hotfix however it
doesn't seem to be working. After going through mini-setup and
joining a domain the customized settings are mostly gone. If I log
in as a user with limited rights some desktop icons do not work
and the corporate wallpaper is not displayed. If I log in as an
admin on the domain everything works properly. So it looks like
the hot fix isn't working. Am I doing something wrong here? Or is
there a work around?

Check the registry permissions on the user's hive using regedit and
make sure whatever account you are logging into the computer has access
to that hive. If you did a profile copy using the profile copy
utility, it gives you an option "Permission to use". If you didn't
change this to the Everyone group, then the default user profile may be
set to be only used by the administrator.

Adam

 

[Guest]

Check the registry permissions on the user's hive using regedit and
make sure whatever account you are logging into the computer has access
to that hive. If you did a profile copy using the profile copy
utility, it gives you an option "Permission to use". If you didn't
change this to the Everyone group, then the default user profile may be
set to be only used by the administrator.

Adam

Adam,
Thanks for responding. I did set the permissions to everyone when copying to
the default profile.

Pete

 

[Michael Niehaus [MS]]

Did you install the hotfix (http://support.microsoft.com/kb/887816) and also
set the Unattend parameter:

[UNATTENDED]
UpdateServerProfileDirectory=1

Without this, mini-setup will still copy the Administrator profile over the
Default User profile.

Wallpaper settings can also be interesting if they point to a location
within the user profile (specific location instead of a relative one). What
location have you set?

-Michael Niehaus
Systems Design Engineer
(e-mail address removed)
This posting is provided "AS IS" with no warranties, and confers no rights.

 

[Guest]

I installed the hotfix but left out the Unattend parameter. I wasn't sure
whether to add it or not. The article said if you want the admin profile as
your default user profile use the Unattend parameter. Though I think at this
point I'll just customize the admin profile and let mini use it as the
default profile. As I'm running out of time and this seems to work ok. My
biggest concern was allowing admin profile rights to users group. I've tested
installing software and looks like regular users group doesn't have access to
this. My guess is mini-setup only uses certain settings but doesn't use the
full admin profile structure for new users? I hope I'm right...

Thank you!
Pete

Pete

Did you install the hotfix (http://support.microsoft.com/kb/887816) and also
set the Unattend parameter:

[UNATTENDED]
UpdateServerProfileDirectory=1

Without this, mini-setup will still copy the Administrator profile over the
Default User profile.

Wallpaper settings can also be interesting if they point to a location
within the user profile (specific location instead of a relative one). What
location have you set?

-Michael Niehaus
Systems Design Engineer
(e-mail address removed)
This posting is provided "AS IS" with no warranties, and confers no rights.

We're about to do a rollout of new computer systems and I'm running into
problems trying to sysprep the machines. I've configured each system with
XP
PRO SP2 and configured a customized profile. I than copy the Customized
profile to the Default User Profile in the User Profiles dialog box. There
is
a hot fix and known problem with sysprep and mini-setup where it strips
the
settings in the default profile and uses the administrator profile
settings
instead. I called MS and installed the hotfix however it doesn't seem to
be
working. After going through mini-setup and joining a domain the
customized
settings are mostly gone. If I log in as a user with limited rights some
desktop icons do not work and the corporate wallpaper is not displayed. If
I
log in as an admin on the domain everything works properly. So it looks
like
the hot fix isn't working. Am I doing something wrong here? Or is there a
work around?

Thanks,
Pete

 

[Lyman Green]

Wow.
Good thing I decided to look back a bit and search. I just made a big
post but it is DIRECTLY addressed by this supposed hotfix. Which of
course is not available for direct download.
I hope to get this hotfix ASAP and try it as I am definitely
experiencing this issue. I do NOT want the administrator
customizations copied to my default user profile which I've spent
several years customizing to be exactly what I want for our users.
Thankfully I've kept backups as I keep searching for a way to make this
work.

Thanks to everyone who posted to this thread as it has led me to at
least an admission of a problem on Microsoft's part and hopefully a
possible FIX for the issue. Now.. about that hotfix!!!

Lyman Green