RE: SteadyState and Sysprep - do not lock profile ever!

2009-09-02T19:47:50Z

Hello. I didn't get any responses on here when I asked this question, so I ventured out and asked a collegue that uses Steadystate and I have found his advice to be very useful.

First, off I did not use sysprep at all. Before I installed Windows SteadyState on the computer, I added the public profiles as regular users and the administrator profiles to the computer . I then went in and set up the software in each profile - Office, Media Player, I.E. 8 and the children's games that I found will work on Windows XP with no problems. After getting each profile set up and the desktop the way I want it, I then used Norton Ghost 2003 to image all 66 computers. Once an image was created, I logged back into the computer and renamed it to a different name. Remember that I have not loaded Windows SteadyState yet onto these computers. After every computer had been re-imaged, I then installed Windows SteadyState on each indivdual computer separately. Remember all the profiles will show up in WindowsSteady State and then you add the permissions to each profile. Do not lock the profiles until you are sure everything works according to your satisfaction.

This way when you need to reghost a computer, you can uninstall Windows SteadyState and the profiles will remain on the computer because they were not created using Windows SteadyState. Hope this helps someone. Thanks.

SteadyState and Sysprep - do not lock profile ever!

2008-05-13T19:04:17Z

Just in case this saves someone else the frustration and time I have spent... if you are configuring a computer with Windows SteadyState to clone using Sysprep and you've locked the profile even once during testing, you are SOL. The Handbook states that the profile must be unlocked, but that's not actually good enough. The Webjunction manual doesn't mention this either.

http://forums.microsoft.com/WindowsToolsandUtilities/ShowPost.aspx?PostID=1984622&SiteID=69