Networks

Ask something
Question Locked

Problems with Active Directory Profile Mapping

0 helpful
5 replies

by vabui

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

My users are experiencing sporadic instances of 'Access Denied' when they try to access their 'X' drive. This mapping is established via the user profile setting in 'Active Directory Users and Computers' for Server 2003. I've thoroughly gone over share and security permissions so that is not the issue; I even tested this by typing in the full UNC path in Explorer and Run that the 'X' drive maps, to with no access problems.

I currently have scripts that map certain users to network shares which I believe may somehow be conflicting with AD's mapping of the profile to the 'X' drive. I read somewhere that the Group Policy engine that runs these scripts during logon creates a conflict/glitch with the AD engine.

Because this problem is random it is hard to pinpoint what exactly is the root of this issue. Anyone ever experience this, if so, please help!!!

Thanks

5 replies

by triathlete1981

to run scripts to map network drives for people. as long as the local pc is connected to the network and there is no problem with access to the folder (which your x drive maps to), just right-click my computer, map the drive and make sure the reconnect at logon check box is marked. everyone at my network signs on to the domain and we have a g drive rather than an x drive (we both know the letter's irrelevant) that maps to the major share on our file server. i mapped everyone locally without using any group policy or scripts. the only involvement with permissions i worried about with mapping was when the map was originally made and each local pc used the user's credentials to log onto the file server so their permissions were appropriate.

by vabui

Thanks anyways. I've already considered mapping manually, but I'm not about to visit 250 people's computers to map it for them (because end-users don't have the IT know-how to do it themselves). So the pseudo-solution is listed below in response to the comment. Thanks for your help/suggestion.

Vu

by jamesmondtan

As i know, if you are using script to run the mapping in the start up you should not do a manual mapping.
did you try disconnect the mapping drive and restart see if the map drive appear, if appear it means the script is running.

by vabui

This is just a temporary fix. My goal here is to prevent ANY instances of this occurrence. If this happens 2-3 times a week x 250 users, it could get quite messy. Anyhow, I came across a few users in another forum that have experienced the same problems and basically, its a glitch in AD 2003 that does not have a fix. To rid myself of the problem it was recommended that I not connect a user's 'Home folder' via the 'connect' option, rather to select 'Logon script' under 'User profile'. This will prevent conflicts encountered between GPO scripts and AD mappings.

Thanks for the suggestions.

This discussion is closed to new replies.