This is an old revision of the document!
See also Windows Roaming Profiles
See also Folder Redirection
This folder structure supports implementation of these four functions and permits the functions to be implemented separately at different times or together at once.
E:\Shares \Share1 \Share2 E:\Homes \User1 \User2 E:\Profiles \User1 \User2 E:\Redirected \User1 \User2 \My Documents \Application Data
User or Group | File/Folder Permissions (Security Tab) | Comment |
---|---|---|
Administrators | Full Control | This Folder, Subfolders and Files |
SYSTEM | Full Control | This Folder, Subfolders and Files |
CREATOR OWNER | Full Control | Subfolders and Files Only |
Authenticated Users | Read & Execute, List Folder Contents, Read Perms | This Folder Only |
User or Group | Share Permissions (Sharing Tab) |
---|---|
Administrators | Full Control |
SYSTEM | Full Control |
Authenticated Users | Full Control |
Modify each user with the Active Directory Users and Computers (ADUC) tool.
Connect
\\DC1\Homes$\%username%
The first troubleshooting step should be to examine the Application event log on the client computer, and determine the error.
If this is a roaming profile, be sure to check for the correct permissions on the 'Profiles' folder. Check share permissions as well as NTFS permissions.
In addition to logging events in the Application Event log, User Profiles can provide a detailed log to aid troubleshooting. To create a detailed log file for user profiles, use regedit and locate the following path:
HKEY_LOCAL_MACHINE\Software\Microsoft\WindowsNT\CurrentVersion\Winlogon
Create a new value called UserEnvDebugLevel as a REG_DWORD and set the value to 30002 in hexadecimal format.
The log file can be found at: %windir%\debug\usermode\userenv.log
.
View all shares including hidden shares (share name ending with $ symbol):
net share