Hi all,
I'm experiencing a bit of a strange issue. The behaviour I'm seeing is if a user logs in quickly (as in immedaitely upon the logon prompt being presented), their drives do not map correctly. However, if the user waits a few seconds (10 is usually enough) or logs out and logs back in, the drives appear.
One of the drives, their home drive (H:), is set via AD in the user object. The other drives are controlled via a Group Policy using Group Policy preferences. The Group Policy is linked to the OU containing computers, with the actual settings under User Configuration. There is another group policy that enables Loopback Processing. There are a large number of drive items in the group policy (in the case of one drive letter, there's about 60 mapping settings for it), with Item-level Targeting in use. The targeting method is security group, so if the user is a member of the right security group, they get the drive. Some of the drives are mapping to server-based UNC paths (ie. \\servername\folder) while others are mapping to a DFS-based location (ie. \\domain.com\folder\). The drive mappings are set with the following options:
- Reconnect is set to Disable
- Use First Available is set to Enable
- Run in logged-on user security context is set Yes
- Remove this item when it no longer applies and Apply ones and do not reapply are set to No
From some research I've done, there's things that could cause this sort of problem but they aren't valid in this case. For example, the Group Policy setting "Always wait for the network at computer startup and logon" is set to Enable. When the issue happens, there doesn't seem to be any obvious error messages in the event log.
The environment where this is happening is at Windows 2003 forest and domain functional level. The clients are running Windows 7 SP1 with the affected machines all being desktop computers connected via a LAN cable. 802.1x authentication is in place on the wired network.
Is there anything else I could look at to fix this problem? Thanks.