chairborne1
asked on
Moving to roaming profiles
Scenario. 250 machines of various makes grouped into rooms of 30 approx in our school environment. We have 1500 student users who logon at various machines dependent on their student timetable. We moved from a third party wrap round solution, as it doesn't work with XP..
Students already have user.dat in their areas as a hangoover from the thrd party solution. We have prepped images for all the classrooms ready to ghost so everyone works on a .man profile, and the profile works fine.
Having copied the .man profile back to the default user on the new machines, whan a new user logs on it creates a .man and a .dat in their profile path. How do I stop it creating the .dat? I thought it was from the all users folder, but deleted that and it still happens. the .dat seems to take prescedance over the .man, hence screws up the custom menu and security settings in place! Help!!
Will I have to overight the profile settings in 1500 student user areas? Not easy as they already have documents littered about al over there home drive!
Students already have user.dat in their areas as a hangoover from the thrd party solution. We have prepped images for all the classrooms ready to ghost so everyone works on a .man profile, and the profile works fine.
Having copied the .man profile back to the default user on the new machines, whan a new user logs on it creates a .man and a .dat in their profile path. How do I stop it creating the .dat? I thought it was from the all users folder, but deleted that and it still happens. the .dat seems to take prescedance over the .man, hence screws up the custom menu and security settings in place! Help!!
Will I have to overight the profile settings in 1500 student user areas? Not easy as they already have documents littered about al over there home drive!
ASKER
Thanks, but creating the profile isn't the problem. Works fine, for test users in the domain, but how do I roll it out to the 1500 exisiting accounts who already have documents stored on there H drive.
You are migrating local profiles to roaming profiles, so the best way is to have your users save their documents in their respective My Documents folders in their local profiles. Once that is done, change the profile to a roaming profile following the steps in the link above. The next time that the user logs on, the local profile will be automatically uploaded to the server and that will become the users roaming profile. Try it on a few of your test users.
ASKER
can't do this either I'm afraid. As a school we want all users to have the same settings etc. Which means if users upload existing profiles then they wont see what we want them to see. We are ghosting machines with the new default profile as we type. All the time the system is in use, so as users log on at older machines there getting an older non-standard profile. I think the onluy way is to copy the default profile to all 1500 users folders.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Managed to solve this on our own. Using everyone as the same profile was a non starter as dependent on what my users needs are their profile changes,
We created blank profile folders on a spare server, and xcopied the the default user profile to all 1555 folders. using xcopy /h /k /s /e /c /y c:\defaultuser\* c:\profile path\
Then we used a batch file to remove unwanted files in the old homeDrive's before xcopying all the remaining docs to the my documents folder of the new share.
We created blank profile folders on a spare server, and xcopied the the default user profile to all 1555 folders. using xcopy /h /k /s /e /c /y c:\defaultuser\* c:\profile path\
Then we used a batch file to remove unwanted files in the old homeDrive's before xcopying all the remaining docs to the my documents folder of the new share.
http://techrepublic.com.com/5100-6268-1031655.html