This procedure was used to create a mandatory profile to be used in a XenApp deployment. Using a mandatory profile will cause a user's environment to be "reset" each time they log on since a mandatory profile cannot be written to. Because of this, you will need to employ some type of profile management solution if you want to allow users to customize their environment. We use triCerat Simplify in my shop, but there are many other solutions available. The advantage of using a mandatory profile is that you don't need to use roaming profiles which have traditionally been a nightmare as time passes and they become bloated and even corrupt.
1 – Create a folder on a file server to house the share.
2 – Share the folder with proper permissions. Since this is going to house a mandatory profile, we only need to give authenticated users Read access, but leave Admins at Full Control:
3 – Create a folder within the share folder you just created to house the actual mandatory profile.
Add a .V2 extension to the folder’s name.
4 – Log on to a 2008 server that will only be loading up a local profile for an end user. Run any programs, make any changes you want and then log back out.
5 – Log in as an admin on the same 2008 server and go to view the user profiles on the system.
6 – Select the user you logged on as before and click the “Copy To” button. Then enter the path to your mandatory profile folder in the “Copy profile to” field. Do NOT click OK yet.
7 – Click the Change button under “Permitted to use” and add Everyone. Click OK.
8 – Click OK in the “Copy To” dialog. Confirm the copy if prompted.
9 – Go back to the file server and verify the profile is copied into the folder you specified.
10 – Rename the ntuser.dat file inside the profile to ntuser.man.
11 - Go back to the 2008 server and remove the local profile for your template user. Click OK all the way out of profiles and system settings.
12 – Set any policy or account attributes necessary to specify the use of the mandatory profile.
No comments:
Post a Comment