To keep the profile as clean as possible, customize only what is necessary. Login with the local user account created in step 3 and do the necessary customizations. Step 4 – Login with the Template account you just created The last registry hive has a lot of setting… and why should you’re creating an administrator account anyway?įor this guide I will create a Template user with the name “robinhobo-com”. Software\Microsoft\Windows\CurrentVersion\Internet Settings\Zones\1 (through 4) Software\Microsoft\Microsoft Management Console
If you do create a Local administrator account you get the following unnecessary settings within the profile On a Windows Server 2008 R2 (or Windows 7 client) create a Local non-administrative user account. To configure that users only can see the files and folders they have access rights to, enable Access Based Enumeration on the share. SYSTEM (This folder, subfolders and files)Īdministrators (This folder, subfolders and files) On a central file server, create and share a folder that you want to use for the folder redirections and apply the following share and NTFS permissions.ĬREATOR OWNER (Subfolders and files only) Step 2 – Create a Share for the Folder Redirections Make sure you set the following NTFS access permissions (including child objects) To provide better security, always create the share on a NTFS volume. On a central file server, create and share a folder that you want to use for the Mandatory profile. Step 1 – Create a share for the Mandatory profile There are quite a few ways to create a mandatory profile, with this blog I want to explain my way of creating a mandatory profile and what I think is the most efficient.īefore you begin, go to the Folder Options and make sure “Show hidden files, folders, and drives” is selected and that “Hide extensions for known file types” and “Hide protected operating system files (Recommended)” is deselected. Not surprising because with mandatory profiles in combination with user virtualization software, the user logon times are pretty reduced and there is less risk of profile corruption.
This is partly due the rise of user virtualizations software like AppSense, RES Software and Microsoft UE/V, which use a mandatory profile as a basis.
Mandatory profiles are increasingly being used.
0 kommentar(er)
