Re: Migrating DC/File Server to new hardware...

Interesting. Post the script here and I'll look at it.
LJ

"Xpert888" wrote:

I don't currently have the new server setup, but I filled in another
servers name on the network for "NewServer". I didn't have the old
server filled in on the arrNames line, but now I do. However, I still
get the same error message.

Little-Joe wrote:
Modify this line and put your new server name between the quotes
strNewServer = "\\NewServer\"

Modify this line and put your old server name between the quotes
arrNames = Split(strUNC, "\\OldServer\")

LJ

"Xpert888" wrote:

I'm getting an error:

Line: 29
Char: 9
Error: Subscript out of range: '[number: 1]'
Code: 800A0009
Source: Microsoft VBScript runtime error


Little-Joe wrote:
Steve,
Yes, you need to save it as a .VBS file. Then you can double click on the
file and it will go to work doing its thing. I would test run this on YOUR
local computer prior to using it via the GPO that runs your other login
scripts.

Not sure about creating a .bat file to run this script as I have not done
that in many many years, I normally run my scripts via a GPO's.
LJ

"Xpert888" wrote:

Question for your script....do I have to save this as a .vbs and then
make a .bat that runs this and set it in the user account profile to
test it?


Little-Joe wrote:
Steve,
Ask and ye shall receive, OK I lied, it is 11 lines of code.

'=====================================================
'
' NAME: Map new UNC to existing drive letter
'
' AUTHOR: Joe Anderson ,
' DATE : 6/30/2006
'
' COMMENT: Script was written to run upon login and map a users drive from
' the old server to the new server.
'
'=====================================================

Set objNetwork = CreateObject("Wscript.Network")

strNewServer = "\\NewServer\"
strOldServer = "\\OldServer\"

Set colDrives = objNetwork.EnumNetworkDrives

For i = 0 to colDrives.Count-1 Step 2
strLetter = colDrives.Item (i)
strUNC = colDrives.Item (i+1)
arrNames = Split(strUNC, "\\OldServer\")
objNetwork.RemoveNetworkDrive strLetter
objNetwork.MapNetworkDrive strLetter, strNewServer & arrNames(1)
Next

LJ

"Steve" wrote:

If there is a logon script that will search for the old server's name and
replace it with the new servers name in drive mappings, and there is no other
easier way to do it, then I will do it that way...of course, I'll have to
find that script lol.

Steve

"Little-Joe" wrote:

Steve,
UNC's as I see them are \\server\share\directory, while the drive mappings
take the UNC and port them to a drive letter like g:\directory. I mainly see
UNC refrences within applications (that is the quandry that I am in now). I
am planning on doing a backup/restore to get around the drive/file rights
issue, you might consider the same method.

The VBScript that I wrote simply take the drive letter and maps it to the
same destination on the new server. Down and dirty, like 10 lines of code.

Hope this helps, LJ

"Xpert888" wrote:

Correct, it said you couldn't use DFS Root Consolidation Wizard on a DC
and it had to be Enterprise or Webcenter...and I have Standard.

UNC references ARE the problem with the drive mappings...moving the
files to the new server will negate the user's current drive mappings
since the files will no longer exist at the server they are mapped to
look at. I need to be able to copy all files over to the new server,
keep permissions intact, and attempt to minimize the amount of
administration needed as far as re-mapping drives goes.

Can you explain your specific difference between drive mappings and UNC
references so I can understand why they are different to you?


Little-Joe wrote:
Steve,
If you are just worried about drive mappings then a Login VBScript that
searches and remaps the drives on the local machine is the way to go. I have
done this and it works great.

If you are worried about UNC refrences then that is another situation (one
that I am in right now). What W2k3 did you purchase ? I think that you need
to have Enterprise to use the DFS UNC consolidation feature refrenced in the
FSMT.

LJ

"Xpert888" wrote:

I have a PDC running Windows 2000 SP4. It is the DHCP, DNS, WINS, all
5 FSMO roles holder, and file server. I bought new hardware that will
be running Windows 2003 R2, and want to migrate the PDC to it. The
clean way to me is promoting the new server in the domain as a DC,
which will replicate our AD-integrated DNS...moving the DHCP database
over...making it a WINS partner...using Print Migrator for the
printers...and transferring all 5 FSMO roles to it. The part I'm
having questions about is the files. I've read about using the FSMT,
but it says for maintaining the UNC paths you can't use it on a DC, and
this is a domain controller. I've read that I can use Robocopy to copy
the files (WITH their permissions) to the new server, but then I lost
the original UNC paths. Every single user (100) has mapped drives
setup, and I'd like to not have to change any one of them if possible.
Has anyone run the FSMT on a DC and had it work correctly, or is there
another way of doing this easy?

Help! :)

Thanks,

Steve










.

Relevant Pages

  • Re: Migrating DC/File Server to new hardware...
    ... Any luck Little-Joe? ... Notice the only thing I changed was the server names...I also tried ... Not sure about creating a .bat file to run this script as I have not done ... searches and remaps the drives on the local machine is the way to go. ...
    (microsoft.public.windows.server.migration)
  • Re: Moving Drive Map role
    ... wrote a KIX script to map drive letters based on AD group membership. ... Have question regarding Drive Mapping on Windows 2000 Server. ... box which is mainly acting as a Drive Map to one of the drives in SAN. ...
    (microsoft.public.windows.server.general)
  • Re: Accessing Source File on Client
    ... I have not used UNC before so here goes. ... > Mapped drives are user specific. ... > Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP) ... >> If I run this application on the server with the source file on a local ...
    (microsoft.public.sqlserver.dts)
  • Re: Migrating DC/File Server to new hardware...
    ... Modify this line and put your new server name between the quotes ... Map new UNC to existing drive letter ... replace it with the new servers name in drive mappings, ... searches and remaps the drives on the local machine is the way to go. ...
    (microsoft.public.windows.server.migration)
  • Re: Migrating DC/File Server to new hardware...
    ... Map new UNC to existing drive letter ... replace it with the new servers name in drive mappings, ... same destination on the new server. ... searches and remaps the drives on the local machine is the way to go. ...
    (microsoft.public.windows.server.migration)