New file server
So we have been having this issue at work and I can't seem to nail down a fix, short of manually editing the registry which is cumbersome and a pain.
We have file server A named XXX-XXX-File01 (Windows 2003) and we're replacing them with file server B named XXX-XXX-FILE81 (Windows 2008 R2). What seems to be happening is that on all laptops and desktops when users try to open an attachment or file saved on the :L: or H: drives it looks for the old server first them times out and looks for the new server, this causes a lag and complaining from the users.
The L: drive is their local drive for users to share locally and the H: drive is their home drive that only they have access to.
Right now what I have done to resolve it is edit the registry and anywhere there is FILE01 I'm changing it to FILE81, but there HAS to be a better easier way.
What am I missing? Hope the post is clear enough.
We have file server A named XXX-XXX-File01 (Windows 2003) and we're replacing them with file server B named XXX-XXX-FILE81 (Windows 2008 R2). What seems to be happening is that on all laptops and desktops when users try to open an attachment or file saved on the :L: or H: drives it looks for the old server first them times out and looks for the new server, this causes a lag and complaining from the users.
The L: drive is their local drive for users to share locally and the H: drive is their home drive that only they have access to.
Right now what I have done to resolve it is edit the registry and anywhere there is FILE01 I'm changing it to FILE81, but there HAS to be a better easier way.
What am I missing? Hope the post is clear enough.
Are the two drives showing on the clients as mapped to the new server and share?
ASKER
Yes they are, that was my first inclination but that is handled by a login script which was changed and indeed they are showing mapped to server B and not A.
It sounds like one of two things may be happening....
1. Could someone at some point and time tried to map drives using group policy? The policy would be applied prior to logon script.
2. As you using net delete lines in your script to delete mapped drives prior to the net use command?
1. Could someone at some point and time tried to map drives using group policy? The policy would be applied prior to logon script.
2. As you using net delete lines in your script to delete mapped drives prior to the net use command?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Sample logon script that maps their L: drive and other share drives. The spot where FILE81 is is where FILE01 used to be.
NET USE L: \\XXX-XXXX-FILE81\Riversid
NET USE R: \\Contoso.COM\\VSE_Tree /persistent:no
REGEDIT /S "\\XXX-XXX-file02\VSE_Glob
START /MIN \\XXX-XXX-APPS33\Utilities
START \\XXX-XXX-trak01\TrackIt80
C:
CD "C:\WINDOWS\Microsoft.NET\
regasm /codebase "C:\program files\Icode\everest\client
regasm /codebase "C:\program files\Icode\everest\client
regasm /codebase "C:\program files\Icode\everest\client
regasm /codebase "C:\program files\Icode\everest\client
EXIT
NET USE L: \\XXX-XXXX-FILE81\Riversid
NET USE R: \\Contoso.COM\\VSE_Tree /persistent:no
REGEDIT /S "\\XXX-XXX-file02\VSE_Glob
START /MIN \\XXX-XXX-APPS33\Utilities
START \\XXX-XXX-trak01\TrackIt80
C:
CD "C:\WINDOWS\Microsoft.NET\
regasm /codebase "C:\program files\Icode\everest\client
regasm /codebase "C:\program files\Icode\everest\client
regasm /codebase "C:\program files\Icode\everest\client
regasm /codebase "C:\program files\Icode\everest\client
EXIT
ASKER
I fixed it on my own