[John]

Set up:
Active directory (native mode)
Windows 2003 Applicance Edition File Server
Windows 2003 Enterprise
User Account Profile contains path for mapped home drive
(H:\<servername>\Home$\User.Account)

File Server has a shared drive called Home which contains all folders for
user home drives. The drive is shared out to Everyone with Full Control. The
security settings are set to the following:
Root of Home is set to Deny Traverse, List Folder, Read Attribute, Read
Extended Attribute, Read Permissions
Users have Full Control of their own folder

(I have a division drive on the same server with similiar rights and has no
problems(I:\<servername\<divisionname>)

Situation: Upon logon, users are normally connected to their home drive.
Users intermittenly do not get fully connected to their Home Drive, but
rather connected to the root of the drive. At this point, the home folder is
compromised as the user can browse the folders although the NTFS permissions
are set to not allow this.

Probably a separate issue, but often the user gets only the Home drive (via
the user profile) and not the drive mappings from the logon script that runs
from the Group Policy. After a reboot or two, or manually running one time,
seems to work fine.

I have also now seen a script that has worked fine for a very long time that
maps to division 1 drive map to division 2 drive. Are there any thoughts out
there? Some assistance would be greatly appreciated.