i am also planning to use local mandatory Profiles.
The Goal is to assign a mandatory Profile to a shared account as described here:
I found that under some circumstances the history for IE9 would not revert back to the Mandory Profile after logon/logoff.
Instead before typed URLs for the same User do reappear. This typed URLs remain sticky even after i manually delete the cached Profile(!)
did you come across a problem like this?
One more note on this, the windows 7 profiles have the username hard coded in various places; if you are planning on using the same mandatory profile for multiple users when you load the ntuser.dat registry hive, export it to your desktop as "tempfile.reg" then open this tempfile.reg in notepad and do a search and replace. If the original user that setup the profile was "student123" then search for all instances if "student123" and replace it with %username%. Save the text file before closing it and then double click on the tempfile.reg that you just modified. It should load the changes you made back into the registry hive. unload the registry hive and then you can rename your ntuser.dat back to ntuser.man
Originally Posted by 3s-gtech
This can also be done in regedit itself with Find, by loading the hive. It is a good point though - however some programs may not read %username% correctly. Works for the most part though, i haven't found a fault yet on a broad suite of common educational software.
Interesting, I'm testing Win7 at the moment and have a mandatory profile with folder redirection and various Preferences (printers etc)... from powered off I get to the desktop in just under a minute (so that's BIOS, boot, profile, GPO, GPP etc). Only thing that might be different is that my redirected folder already exists as opposed to being auto-created on logon... not sure how much difference that makes.
Originally Posted by morganw
Made our mandatory profile on a VM via the MS-supported method then when I want to make changes I just revert to the snapshot I make before running sysprep, rinse and repeat as many times as you want :)
The only thing I do differently to the MS method is I keep the profile machine off the domain (stops accidental contamination with GPOs) and copy the resultant mandatory profile in two stages... first locally to the VM's C: drive then grab it via the admin C$ share. Reason being I found it doesn't like copying up in one stage when not on the domain.
Sorry to revive this one, but....
Originally Posted by stefpronti
Thanks, this was the only working way i found to get a local mandatory profile on Windows 7, without using AD.
In the above guide, the only edit i would make is to substitute "Disconnect" for "Log Off" in the early stpes where it is mentioned, the author correctly uses "Log Off" later in the guide.
Basically my need was to lock down one "guest" account and revert/discard and changes at logoff..i.e.e steadystate style...thanks MS for taking out the guest mode option in the final version of Windows 7!
So my shared PC setup is for:
* A static guest account that reverts/discards user changes at logoff - sorted due to above post. I'd tried a few different ways, the above was the winner!
* A custom "default user" profile for normal user accounts - ability to save etc, usual GPO lockdown - sorted out using the info ive posted below in case it helps others.
Copy user to default user profile issue on Vista/Windows 7...and solution
I also found the other issue with Windows 7, not being able to copy over a "templated" user profile over the default user one. In this instance, i used DelProf (Free), from ForensiT Free Downloads
It allows you to specify the customised profile at the command line, and it copies this over the default user profile, generalising it on the way... :)
As has been mentioned here and elsewhere where IT people gather, the only supported MS way is to do it via xml and sysprep as MS says that there are sections fo the profile that arent generalised/cleaned during this copy....stupid MS, rather than fix this, make it harder...
So ForensiT went and fixed this generalisation/chleaning during copy issue....so far in testing i havent found an issue....and it avoids the sysprep bs...
Hope the tip about the special ForensiT DelProf helps