Solved

New file server

Posted on 2013-01-08
6
166 Views
Last Modified: 2013-08-07
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
Comment
Question by:VSE ITSD
  • 4
6 Comments
 
LVL 6

Expert Comment

by:JeffG2583
ID: 38757461
Are the two drives showing on the clients as mapped to the new server and share?
0
 

Author Comment

by:VSE ITSD
ID: 38757470
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
 
LVL 8

Expert Comment

by:lancecurwensville
ID: 38757566
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
NFR key for Veeam Backup for Microsoft Office 365

Veeam is happy to provide a free NFR license (for 1 year, up to 10 users). This license allows for the non‑production use of Veeam Backup for Microsoft Office 365 in your home lab without any feature limitations.

 

Accepted Solution

by:
VSE ITSD earned 0 total points
ID: 38758366
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
 

Author Comment

by:VSE ITSD
ID: 38758512
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
 

Author Closing Comment

by:VSE ITSD
ID: 39388622
I fixed it on my own
0

Featured Post

VMware Disaster Recovery and Data Protection

In this expert guide, you’ll learn about the components of a Modern Data Center. You will use cases for the value-added capabilities of Veeam®, including combining backup and replication for VMware disaster recovery and using replication for data center migration.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

A Bare Metal Image backup allows for the restore of an entire system to a similar or dissimilar hardware. They are highly useful for migrations and disaster recovery. Bare Metal Image backups support Full and Incremental backups. Differential backup…
If you get continual lockouts after changing your Active Directory password, there are several possible reasons.  Two of the most common are using other devices to access your email and stored passwords in the credential manager of windows.
In this video, we discuss why the need for additional vertical screen space has become more important in recent years, namely, due to the transition in the marketplace of 4x3 computer screens to 16x9 and 16x10 screens (so-called widescreen format). …
Windows 8 came with a dramatically different user interface known as Metro. Notably missing from that interface was a Start button and Start Menu. Microsoft responded to negative user feedback of the Metro interface, bringing back the Start button a…

840 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question