Replacing Win2k Terminal Server in SBS2k Enviroment

[Peter]

I am replacing a terminal server (Win2k Advanced Server) in our SBS2k
environment.

The new replacement server is Dell hardware. I intend on building the new
server up with a different name and copying the user profiles across from
the existing server. Once completed (with installing Office and other
applications), I will change the DNS records so users still wishing to
access the existing server will be directed to the new server once
completely configured.

My question(s):

1. Is this method the preferred course of action?
2. What tool would I use to bring the user profiles across? (User state
migration tool)?
3. Since the TS licensing server is on the SBS box - there should be no
problems with TS licencing?
4. Any other advice before deployment?

Peter

 

[NIC Student]

Hi Peter,

You should ask SBS licensing questions in their newsgroup, there are
excellent MVPs there who know a ton about SBS config, however I think your
licensing is ok as long as the new server is also Win2k and you have
purchased a new server license for the new server (or decommission the old
one after moving hardware).

microsoft.public.windows.server.sbs

As long as the new server is already a domain member, use something like
BackupExec, NT Backup, or even an XCOPY to move the data from the old
profile source to the new one. The ACLs will remain intact if you do this
correctly (/O switch on XCOPY I believe).


--
Scott Baldridge
Windows Server MVP, MCSE


"Peter"