MS KB 304970 addresses the need for Always wait for the network at computer startup and logon in conjunction with Run logon scripts synchronously, and using Run logon scripts synchronously comes from a forum post I read on the mapping problem.



"Bahta, Nathaniel V CTR USAF NASIC/SCNA" <[EMAIL PROTECTED]>
Sent by: [EMAIL PROTECTED]

07/18/2006 02:13 PM

Please respond to
ActiveDir@mail.activedir.org

To
<ActiveDir@mail.activedir.org>
cc
Subject
RE: [ActiveDir] Home directories issue





Andrew, do you know of any documents that address this or support your resolution?  Where do you get your information from?


From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED]
Sent:
Tuesday, July 18, 2006 1:32 PM
To:
ActiveDir@mail.activedir.org
Subject:
Re: [ActiveDir] Home directories issue



The problem with XP clients mapping to the base of a share instead of the users folder can be solved by enabling Computer Configuration\Administrative Templates\System\Scripts\Run logon scripts synchronously. Depending on your environment you might also need to enable Computer Configuration\Administrative Templates\System\Logon\Always wait for the network at computer startup and logon. Warning the latter policy can significantly increase login time depending on your GPO complexity, the first will increase login time if you have large, complex login scripts! As always test in a lab environment before rolling to production. Unfortunatly this particular issue is hard to reproduce in the lab so testing is difficult for a cure, but impact testing should be easier.


Andrew Fidel



"Matt Hargraves" <[EMAIL PROTECTED]>
Sent by: [EMAIL PROTECTED]

07/17/2006 07:42 AM

Please respond to
ActiveDir@mail.activedir.org


To
ActiveDir@mail.activedir.org
cc
Subject
Re: [ActiveDir] Home directories issue







For some odd reason Google didn't show me your original message (it hides 'quoted' material for some messsages).  I didn't see that portion of your message (that it was intermittent) and was trying to think of what all things would cause this.

There are a few questions that I have:

1) Are they always connecting from the same computer.

2) Are you using DHCP or static mapping?

3) AD Integrated DNS?

I'll look around and see what I run into.  I haven't run into this personally (intermittent mapping of home drives) and just to be honest, I use a \\servername\driveletter$\directory mapping for my home drive (mostly so that I can always reach a particular drive location when on a network without having to share it out) and even I don't see it with this somewhat non-standard homedrive location type.



On 7/16/06, Arnold Arce <
[EMAIL PROTECTED]> wrote:
Taking everything you said, why would this problem be intermittent and not every single time the user logs in?


From: [EMAIL PROTECTED] [mailto: [EMAIL PROTECTED]] On Behalf Of Matt Hargraves
Sent:
Sunday, July 16, 2006 6:03 PM


To:
ActiveDir@mail.activedir.org
Subject:
Re: [ActiveDir] Home directories issue

Well, when you're mapping to \\server\share\directory, if the user has permission issues at the directory level (their actual home share location), I believe that it will simply map to the share and not go into the directory.

Make sure that you have granted all users "Full Control" at the share level.  You don't need to grant them anything more than "Read" at the NTFS level (since I believe the System account creates their home directory), but to have full control (which is required for the home drive location), you have to be *able* to have full control and you can only have full control on a share if *both* the Share-level permissions and the directory level permissions state that.

Example:

The "\\server01\users" share is located on the E drive in the directory "users".  You can have the perms on that directory to be "Administrators: Full, System: Full, Everyone: Read", the System will create the user directories (E:\users\joebloe\) and grant the required permissions for that directory (full control for joebloe).  However, if the share perms state "Change" or "Read Only", then the user can only have that level *or lower* of effective permissions on the files.  So even if joebloe has "Full Control" on his directory, if the share says "Everyone: Change", then his effective permissions on everything in that share (including his directory) won't ever be more than "Change".  You could actually have "E:\users" shared out as "\\server01\users" and "\\server01\home" and if you have everyone as "Change" on the users share and "Full Control" on the home share, even though it's the exact same location on the system and the NTFS permissions haven't changed, the people who are mapped to "\\server01\home" will work, while the people who are mapped to "\\server01\users" won't work.  Change everyone's mapping to "\\server01\home" (or change "\\server01\users" to have Everyone: Full) and they will all work.

Some of this is speculation and while I seem to remember running into this in someone's network before, that was something like 6 years ago and haven't run into it since.  I could be mistaken.

On 7/16/06, Arnold Arce < [EMAIL PROTECTED]> wrote:

Has any headway been made with this problem?   I can't find any solutions out there.  


From: [EMAIL PROTECTED] [mailto: [EMAIL PROTECTED]] On Behalf Of Conrad, Daniel C Mr. Nortel PEC Solutions
Sent:
Tuesday, December 13, 2005 3:17 PM
To:
ActiveDir@mail.activedir.org
Subject:
RE: [ActiveDir] Home directories issue

It's all AD on 2k3 with XP Pro clients, connecting to a real share (both by IP and NetBIOS to ensure name resolution isn't an issue.  No DFS.

On behalf of Jerry

Dan

Nortel PEC Solutions

From: [EMAIL PROTECTED] [mailto: [EMAIL PROTECTED]] On Behalf Of Dan Holme
Sent:
Tuesday, December 13, 2005 12:57 PM
To:
ActiveDir@mail.activedir.org
Subject:
RE: [ActiveDir] Home directories issue

%USERNAME% won't help, as it is translated "on the fly" to the user's name the moment you use it, so it ends up joe.user anyway.

Are your users having the problem using W2K or later, I assume?  (if not, there's your answer)  And you ARE using a "real" share, not a DFS root share, right?


From: [EMAIL PROTECTED] [mailto: [EMAIL PROTECTED]] On Behalf Of Arnold Arce
Sent:
Monday, December 12, 2005 9:00 PM
To:
ActiveDir@mail.activedir.org
Subject:
RE: [ActiveDir] Home directories issue

I have experienced this same problem.  Usually logging off and logging on fixes it.  I need to find a better answer.  I'll try the %USERNAME% variable like someone else suggested.


From: [EMAIL PROTECTED] [mailto: [EMAIL PROTECTED]] On Behalf Of Condra, Jerry W Mr HP
Sent:
Monday, December 12, 2005 3:42 PM
To:
ActiveDir@mail.activedir.org
Subject:
[ActiveDir] Home directories issue

Hoping someone has seen this problem before.

Users are mapping home folders using AD profile tab which maps X: to \\servername\home\joe.user .   Occasionally, upon logon, users will map to \\servername\home and not all the way to their own home directory. I've seen several blogs and the same problem posted elsewhere but no cause or solution.  

Thanks

Jerry

Reply via email to