abillybob (12th June 2014)
The file won't exist yet, it's created with the Windows AIK (or just in Notepad etc).
Easiest method (if you're relatively technically minded) is the copy profile method - I'll outline a very simplified version below.
Create a base user in AD, with no GPs applied other than the default ones. Don't set a profile path.
Log in to a PC with this account. Set up your profile settings that you may like (classic ones are first-run settings for things like Adobe CS, Office, that sort of thing). By doing so, you are changing and creating registry settings in the ntuser.dat hive for that user.
Copy the entire user profile from the base PC (or VM) into a network share that will host that profile for all users.
Set permissions on the profile folder so that your users can read it (no need for write perms).
Open ntuser.dat in regedit (File/Load hive). Change the permissions on the registry hive so that Everyone has full control - if you don't do this, no-one else will be able to load this profile. Delete any unnecessary gunk from the hive if it exists - you can also tweak certain settings directly such as usernames etc. Unload the hive when finished (right click it).
Rename ntuser.dat to ntuser.man
Point a test user's profile path to you new shared profile area. Don't include the .v2 extension in this path (if you've made separate XP and Vista/7/8 profiles.)
Log on and test, test, test.
abillybob (12th June 2014)
I might just give them local profiles and be done with it this mandatory business is pretty damn hard to understand and do! I just want a standard Windows 7 Profile, no special theme or anything like that just a basic Windows 7 Aero Profile without anything on it, why is this so hard to do!
When I started here, we had roaming profiles, I quickly changed this to mandatory profiles under XP.
Since moving to windows 7 I use local profiles and redirect everything. No-one has complained, its all just works just as well.
Yeh I said it earlier, there is no need to roaming or mandatory profiles.
Local profiles are fine. Just remove the profile field from the user in active directory. Job done.
Though surely Mandatory profiles would be better, because it means once that child has logged out anything they've messed up on their desktop will be reset for next time they login? Plus the fact you can make a tiny mandatory profile so it means the user will be logged in just as fast as a local profile?
I could be wrong though but for an all-rounder I think Mandatory Profiles would be the best choice - I've since found this and seeing how it's done make it loads easier so may give that another go tomorrow
Chockster (13th June 2014)
There are currently 1 users browsing this thread. (0 members and 1 guests)