Dear All,

I have a group of 150 users on my domain that I would like to setup to have temporary profiles when the log onto the computer. Do help me get the procedure of setting up these settings.

We don't have enough space for roaming profiles and yet wwe don't want them to have any of there work left on the desktop once they log off.

Dani AI

Generated

Short summary: is on the right track — mandatory profiles are the usual way to give users a “clean” desktop at every logon. Below are practical considerations and deployment tips that go beyond the how‑to so the rollout stays secure, reliable and fast.

Profile-store security and backups: treat the profile share like any other critical file server data. Do not expose it unnecessarily; use least‑privilege share/NTFS ACLs, keep Administrators and SYSTEM with full control, and put users into a narrow security group for any needed read access. Keep regular backups of the master mandatory profile so you can restore or test changes quickly.

Performance and application compatibility: keep the master profile tiny and remove temp files, but avoid unsupported hacks that relocate core system folders. Redirect user data (Documents, Pictures, etc.) to network locations if you need persistence; do not rely on AppData relocation — many apps break or are unsupported when AppData is moved. Exclude the profile store from on‑access antivirus scans and preinstall drivers and common applications so logon work is minimal.

Deployment and testing checklist: pilot with a small representative group and test on every OS and image in your environment. Verify network availability at logon, validate NTFS/share permissions, test printing and mapped drives, and confirm critical apps behave under a read‑only profile. Keep a documented rollback procedure (how to swap back to a normal profile) and a pristine copy of the master profile.

Troubleshooting hints: when a logon behaves oddly, check the machine’s Application/System event logs (User Profile Service messages), confirm the user’s profile path in AD, and test with a clean workstation image. For 150 users, automate the cleanup/rollback step during maintenance windows (GPO scripts or a controlled cleanup task) rather than manual per‑machine work.

Hi what you need are mandatory profiles not temporary profiles. I use them for over 1000 users and work a treat. You can get an xp mandatory profile down to as little as 3mb while a 7 profile to about 25mb so will not take up much room on your server.

For xp you need to do following:

Create local user account on workstation and give local admin rights.

Login to the workstation with the user you have just created and customise settings as desired. At this point a neat trick is open the registry hkey current user software Microsoft windows explorer user shell folders and change the app data folder location to c:\appdata (create this folder manually) and give everyone full control permissions. Copy the contents of all users appdata and current user appdata to c:\appdata

This helps you with profile size, speed and consistent user application experience. Now delete contents if current user app data and all users but leave root folder there.

Now add/remove desktop shortcuts and start menu items as required in the current user profile best to do it this way than use gpo folder redirection of start menu and desktop as it can slow performance if there are dead links.

Then once done log off user and then log back in just to test everything is ok.

Once happy log back off and log on as domain admin

Go to system properties and click the advanced tab. Then user profiles. Select the user profilemyou have just created and click copy to

In location unc path to profile share on network or you can choose default user on the local machine. Change the permission to use to everyone and click ok.

Once done. Go to the profile location you have just sent it to and change ntuser.dat to ntuser.man to make it mandatory.

Make sure that the profile location folder share has full control for everyone or desired user security group.

If copied to default user on local machine your job is done. Just delete the local old profiles of users using delprof.exe and next time they login they will have mandatory profile!

If network profile path change the profile path on users active directory properties to unc to profile share. If you have many use admodify.net

Then run delprof.exe on all machines (can do via shutdown script) and everyone will have a mandatory profile in next login!

Now win7 a completely different animal!

First create a local user like before and make your customisations as before. Redirect appdata/roaming to c:\appdata and set permission as before in xp.

Finish making customisations.

Log off

Log back in to check

Now the official way to now get a mandatory profile is this. There are shortcuts likemusing windows enabler or a manual copy with reg permission changes but no matter what people say on here they don't always work properly.

Create an unattend.XML file with the <copyprofile>1</copyprofile> tag added into the generalize phase. Use windows system image manager for this by downloading the wi 7 aik - for thus I am assuming you will find out how it works elsewhere.

Once your unattend.XML is created copy to c:\windows\system32\sysprep

Log in as the user you want to copy the profile from

Open command prompt and type c:\windows\system32\sysprep\sysprep.exe /oobe /restart /generalize /unattend:c:\windows\system32\sysprep\unattend.XML

Press enter.

Wait for sysprep to complete. Not important that your pc doesn't die right now! Lol

This copies the active profile to the local default user profile.

On restart login as domain admin and then go to advanced system properties user profiles and click on default profile. Then press copy to and choose location as before. Rename folder if on a share to folder name.v2 this is important!! The .v2 suffix tells win 7 it is a version 2 profile. If you don't do this your user experience will fail.

Change ntuser.dat to ntuser.man at default user profile location on workstation if using local profile location or at unc location. You

It is important to note that if you expect a user to have a mandatory profile for xp and win 7 simultaneously you must make the profile share location the same folder name as the each other but the win7 folder should have the .v2 suffix. E.g. Mandatoryprofile (for xp profile) and mandatoryprofile.v2 (for win7 profile). This applies to network share using ad only.

Modify users ad properties using admodify for bulk edits to unc location and delprof the same as before. If wanting user to have both xp and win7 mandatory profile enter the location of the xp profile in the ad profile properties tab. Applying the logic above the system will recognise both profiles dependant on the machine o/s

Hope this helps

Thanks

Mark

By the way mandatory profiles will not allow a user to save any settings on log off. So every time they login it will be as it was the very first time thus achieving you goal.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.