Move data to new Win2k server

  • Thread starter Thread starter Gerry Hickman
  • Start date Start date
G

Gerry Hickman

Hi,

I need to move 35Gb of data to a new server, consisting of home
directories, application run points, Admin installation points (Office etc).

The old file server is running NT4. It's a PDC but there's nothing left
in that domain except itself, and one other NT print server (BDC). All
client PCs have been joined to the new native mode AD domain.

The tricky part is that the new server MUST have the same name an IP as
the old server; there's dozens of shortcuts, scheduled jobs and logon
scripts that will break if they can not find \\ServerName

Here's my plan:

1. Promote the NT print server to a PDC
2. Full backup of old File server to tape (backup exec)
3. Disconnect old server from network (or try to rename it?)
4. Rename the new server and set IP to be that of the old server
5. Join it to the new AD domain as a member server
6. Restore all the data from tape
7. Recreate the share points

Is there anything I've missed?

One thing I'm concerned about is that there are thousands of ACLs on the
files, some of which either map to the old NT4 server itself, or to
the old domain. (e.g. SERVERNAME\Administrator and
OLDDOM\Administrators), the rest map to the new AD domain an are already
being used. I'm not sure what will happen to all these ACLs? Maybe I
need to use CACLS or something to clean them up before the move?
 
Hi Benn,

No no no! I'm not trying to migrate user accounts. The AD domain is
already set up and all the users and client computers have been moved
into it. I just have ONE NT4 file server (PDC with two way trusts to new
domain) with Word documents etc. I've built a new Win2k server which
will become a member server in the AD domain - I've just got to get the
data off one server and onto the other, and make it LOOK like the new
server is the old server.
 
Hi Gerry,

We had a similar problem with moving machines from one child domain to
another (domain consolidation). As you know, it is difficult to move Office
install points without just reinstalling.

We used ADMT to move the servers so the ACLs were preserved, including
Office install points. Even the print servers were happy afterwards. You
may need to:

1. Add the Win2KServer to the NT domain as a file server.
2. Use Backup Exec to add the files shares and data from BDC and the PDC so
the NT domain ACLs (and cross-domain ACLs) are in place on the Win2k Server.
3. move Win2KServer to the new domain as Win2KServer with ADMT,
4. Take the old NT Server that you want to replace offline.
5. Rename the Win2K server to desired name, change IPs.

Doing things in that order will leave the BDC untouched so it can be brought
back online in case the **it hits the fan during the process. You may still
need to reinstall the Office install points since you are swapping hardware.

--
Scott Baldridge
Windows Server MVP, MCSE


"Gerry Hickman"
 
Hi Scott,
We had a similar problem with moving machines from one child domain to
another (domain consolidation).
Click to expand...

That's similar to what I'm doing. I'm actually disolving a child domain
and moving everything into the "big" AD domain. All the users and
computers have already been moved. It's just the old file server and
print server that are still running NT4 via two way trust.
As you know, it is difficult to move Office
install points without just reinstalling.
Click to expand...

You are starting to SCARE me! Why is it difficult? What exact technical
reason is there for this to be problematic? I have numerous install
points from different vendors and it will be a disaster if any of them
break.
1. Add the Win2KServer to the NT domain as a file server.
Click to expand...

I can see sense to this; ACLs won't break.
2. Use Backup Exec to add the files shares and data from BDC and the PDC so
the NT domain ACLs (and cross-domain ACLs) are in place on the Win2k Server.
Click to expand...

Why the BDC and PDC? The user data is all on the one server. I don't
care about the old NT SAM (I don't think) or the old C: drives. I just
need the install points and Word documents to magically exist on the new
box, and for client PCs to not even notice they've been moved.
3. move Win2KServer to the new domain as Win2KServer with ADMT,
Click to expand...

Hmm, I'm not sure why we need ADMT? Can't I just join it to the new
domain as if it was a client PC? The broken ACLS should (??) start to
resolve again as soon as it's joined to the new domain?

Actually, I could test this quite easily before I do the move for real.
I could just do a small restore from Backup Exec, join the new box to
the domain with a temp name, and see what happens.
4. Take the old NT Server that you want to replace offline.
Click to expand...

That bit should be easy:)
5. Rename the Win2K server to desired name, change IPs.
Click to expand...

Again, I'm hoping this part will also be easy.
Doing things in that order will leave the BDC untouched so it can be brought
back online in case the **it hits the fan during the process. You may still
need to reinstall the Office install points since you are swapping hardware.
Click to expand...

Regarding the "fallback" BDC. Bear in mind there's no users or computers
in the old NT domain (except things like "OLDDOM\Administrator"), but if
I need accounts from the old domain, my old print server (now the PDC)
will still be whirring away in the corner with the old NT SAM.
 
As you know, it is difficult to move Office install points without just
reinstalling.
----------
Well, you know, I don't think there are registry entries made so maybe you
can just copy the program files\Office xxx folder? I've always been fearful
of just copying that one directory and never tried it. I usually reinstall
since the only program that we use that has a proper administrative install
is Office.
----------
Well, I mean only the install points, shares, user data, etc. Just move
what is necessary to the new server since it is not a domain controller and
will transfer easily to the new domain.

The use of ADMT was painless for us, it reACLs all the data and shares, but
we had dozens of file servers to move. Certainly you are correct about the
test being easy to try, let me know how it goes.

--
Scott Baldridge
Windows Server MVP, MCSE


"Gerry Hickman" <
 
NIC said:
Well, you know, I don't think there are registry entries made so maybe you
can just copy the program files\Office xxx folder? I've always been fearful
of just copying that one directory and never tried it.
Click to expand...

Ah, I see what you mean. You are referring to a "real" server based
Office install, whereas I'm referring to an "Administrative Installation
Point". The latter is really just the source files for Office, but with
all the Service packs and patches rolled in. When the user tries to use
an import filter, they get "The feature is not installed, would you like
to install it now". If they click "yes", the installation point supplies
the files.

However, I also have quite a few other applications running in the mode
you describe "Program files\SomeApp", and as you say the reg keys are
either on the local machines in HKLM, or in the user's roaming profile
so I'm not too worried about these.

On a side note, it can get in a real mess if you upgrade the Office
installation point and don't instantly upgrade all the clients. They get
horrible errors when it searches for the install point and finds the
"wrong product" in there. Another thing, is that you can slipstream
Office 2000 SP3 to the install point, but there's one file,
OUTLCTLX.EXE, which must be installed locally to every machine! Failure
to do so will cause MBSA to indicate SP3 as "not installed". This file
only contains one useful DLL, so it's a lot of messing around just to
update one file.
what is necessary to the new server since it is not a domain controller and
will transfer easily to the new domain.
Click to expand...

Yup, that's what I'm thinking.
 
Back
Top