• This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn more.

Strange Drive mapping problem

#1
Users have an H drive. Which is their home folder setup in the users profile in AD, under the "Home Folder" section. The path set to their home folder is \\servername\2008\%username%

99% of the time it works. SOMETIMES users will login and they will get a mapping of \\servername\homes. Instead of \\servername\2008\%username%

The directory on the server is e:\homes\students\class of 2008
with class of 2008 shared out with the share name of 2008

Permissions are not the issue. This is not specific to any one user, or any one computer. From what i can tell it is completely random. It also does it with login scripts. It will create the wrong drive mapping.

Any thoughts?
 
#2
On a side note , i have narrowed this down to 1 model of PCs. All of which were imaged from the same image. Which would make sence. Rebuilding and reimaging is not a possibility right now. I cant imagine what it would be on those PCs, any ideas?
 

profquatermass

OSNN Junior Addict
#3
This drive letter is set on your Windows server in the Users account properties.
Assuming you're using Windows 2003 R2 SP2 of course.
Look in the Profile setting the user should have a drive letter set.
If not set one.
Remove any such drive letter in any logon script.
 
#4
This drive letter is set on your Windows server in the Users account properties.
Assuming you're using Windows 2003 R2 SP2 of course.
Look in the Profile setting the user should have a drive letter set.
If not set one.
Remove any such drive letter in any logon script.
no no, all users are setup correctly with an H drive in the profile setting. The login script is a long VB script that maps drive letters depending on if your in a security group or not. That VB script does not map any drives to the H drive. The H drive being the home drive.
 

profquatermass

OSNN Junior Addict
#5
It's not a drive map problem it's a share problem.
You're getting H: set to the wrong share not the wrong drive letter. Duh..my mistake.

Don't set your share path to a UNC path. Use a local path.

Change in user profile \\servername\2008\%username% to
e:\homes\students\class of 2008\%username%
for example.
I bet that works.
 
#7
Oh i cant do that, the AD server is not on the server as the Home drives.

Also note that all 1500 users in this school system work perfectly except for this class room.
 

profquatermass

OSNN Junior Addict
#8
Oh i cant do that, the AD server is not on the server as the Home drives.

Also note that all 1500 users in this school system work perfectly except for this class room.
So the question to ask is why would it default to \\servername\homes. when its defined as a completely different path. It must be getting it from somewhere?

Windows does remap shortcuts of UNC paths to another UNC path if it can't find the original. Perhaps it's doing this due to a DNS or network problem in a branch of your network?

You can switch this option off in the Registry.
Just takes one duff shortcut anywhere that's visible with Explorer and then it'll cached the new path and throw away the original. Damn annoying.
 
#9
So the question to ask is why would it default to \\servername\homes. when its defined as a completely different path. It must be getting it from somewhere?

Windows does remap shortcuts of UNC paths to another UNC path if it can't find the original. Perhaps it's doing this due to a DNS or network problem in a branch of your network?

You can switch this option off in the Registry.
Just takes one duff shortcut anywhere that's visible with Explorer and then it'll cached the new path and throw away the original. Damn annoying.
Well id say no on the network because that particular room spans 2 diff switches. Which uplinks to a another closet via fiber, and no other rooms from that original closet have problems. So id say thats prob not it. However that second thing you were talking abotu with the registry, could you explain that further?
 

Electronic Punk

willalwaysbewithyou
Staff member
Political User
#10
What happens, on an affected machine, if you

- Try to browse to the correct folder manually or map the drive manually
- Go to the command prompt and type 'echo %username%' ?

Is anything appearing in the application or system logs for these machines?
 

profquatermass

OSNN Junior Addict
#11
Well id say no on the network because that particular room spans 2 diff switches. Which uplinks to a another closet via fiber, and no other rooms from that original closet have problems. So id say thats prob not it. However that second thing you were talking abotu with the registry, could you explain that further?
What more do I need to say?
It's a common enough problem.

[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer]
"NoResolveTrack"=dword:1
Look it up.
 
#12
What happens, on an affected machine, if you

- Try to browse to the correct folder manually or map the drive manually
- Go to the command prompt and type 'echo %username%' ?

Is anything appearing in the application or system logs for these machines?
nothing shows up in the event logs on the servers or local PCs
the users dont have access to the command prompt
nor can they map a network drive. However they CAN goto their personal folder from the driving mapping of \\storage\homes.
 
#13
What more do I need to say?
It's a common enough problem.



Look it up.
This did not work however i found a solution that sounds promising:

In GP Computer Configuration\Administrative Templates\System\Logon\ Always wait for the network at computer startup and logon (the description reads)

Details on this GPO:
Determines whether Windows XP waits for the network during computer startup and user logon. By default, Windows XP does not wait for the network to be fully initialized at startup and logon. Existing users are logged on using cached credentials, which results in shorter logon times. Group Policy is applied in the background once the network becomes available.

Note that because this is a background refresh, extensions such as Software Installation and Folder Redirection take two logons to apply changes. To be able to operate safely, these extensions require that no users be logged on. Therefore, they must be processed in the foreground before users are actively using the computer. In addition, changes that are made to the user object, such as adding a roaming profile path, home directory, or user object logon script, may take up to two logons to be detected.

If a user with a roaming profile, home directory, or user object logon script logs on to a computer, Windows XP always waits for the network to be initialized before logging the user on.

If a user has never logged on to this computer before, Windows XP always waits for the network to be initialized.

If you enable this setting, logons are performed in the same way as for Windows 2000 clients, in that Windows XP waits for the network to be fully initialized before users are logged on. Group Policy is applied in the foreground, synchronously.

If you disable or do not configure this setting, Windows does not wait for the network to be fully initialized and users are logged on with cached credentials. Group Policy is applied asynchronously in the background.

Note: If you want to guarantee the application of Folder Redirection, Software Installation, or roaming user profile settings in just one logon, enable this setting to ensure that Windows waits for the network to be available before applying policy.
 

profquatermass

OSNN Junior Addict
#15
This did not work however i found a solution that sounds promising:

In GP Computer Configuration\Administrative Templates\System\Logon\ Always wait for the network at computer startup and logon (the description reads)
I use roaming profiles and I've always got that particular option on.
Doesn't make sense not to with RP.

Do you also make the users logon script run in the background?
 
#16
I use roaming profiles and I've always got that particular option on.
Doesn't make sense not to with RP.

Do you also make the users logon script run in the background?
Ya i never had to use this GP before so i forgot about it. There is only 1 VB script that runs for users and that does run in the background. When we took over this school system there was practically no GPOs enforced and the servers were fallin apart. The joys of fixing things and making them right :)
 

Members online

No members online now.

Latest posts

Latest profile posts

Hello, is there anybody in there? Just nod if you can hear me ...
Xie
What a long strange trip it's been. =)

Forum statistics

Threads
61,961
Messages
673,239
Members
89,013
Latest member
Pdawgintown