Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 181
  • Last Modified:

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.
0
VSE ITSD
Asked:
VSE ITSD
  • 4
1 Solution
 
JeffG2583Commented:
Are the two drives showing on the clients as mapped to the new server and share?
0
 
VSE ITSDAuthor Commented:
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.
0
 
lancecurwensvilleCommented:
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?
0
Get your problem seen by more experts

Be seen. Boost your question’s priority for more expert views and faster solutions

 
VSE ITSDAuthor Commented:
These settings that seem to stick are all in the registry, so not sure net delete and net use would come into play?  We don't net delete, what I have to do to change the L: drive mapping is change it in the gp editor for the respective site (for example purposes we'll call it Florida), so I go to GP editor and then down to the Florida OU and change the login script there to say FILE81 instead of FILE01, the next time they login that gets mapped automatically for them.

The H: drive is mapped via the profile tab of their AD object.  So on the profile tab for home folder we say use H: and map to XXX-XXX-FILE81.

Another interesting tidbit is that we recently relocated our entire headquarters and those drives are mapped via login script as well, and the servers were recently changed and this issue did not arise.
0
 
VSE ITSDAuthor Commented:
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\Riverside /persistent:no
NET USE R: \\Contoso.COM\\VSE_Tree /persistent:no
REGEDIT /S "\\XXX-XXX-file02\VSE_Global\Everest\PrintLabels.Reg"
START /MIN \\XXX-XXX-APPS33\Utilities\Logon\logonev.cmd
START \\XXX-XXX-trak01\TrackIt80\AUDIT32.EXE

C:
CD "C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727"
regasm /codebase "C:\program files\Icode\everest\client\addins\Interop.EverestConsts.dll"
regasm /codebase "C:\program files\Icode\everest\client\addins\TestAddIn.dll"
regasm /codebase "C:\program files\Icode\everest\client\addins\Interop.Everest.dll"
regasm /codebase "C:\program files\Icode\everest\client\addins\Interop.EverestAddin.dll"

EXIT
0
 
VSE ITSDAuthor Commented:
I fixed it on my own
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now