Migrating to New Terminal Server

[Guest SJMP]

I am planning a migration from my current Windows 2003 SP2 Terminal Server to

a new Windows 2003 TErminal Server. I will rebuild a new box - fresh windows

2003 server SP2 and installed the software currently on my TS box.

 

A few questions -

 

1 - What is the best approach for migrating the following:

 

- licenses

- profiles

- printers ( specifically remote TS printers)

 

I would also like to disable the desktop for Users - so they only have

access to what I decide. How can I deploy a custom desktop to the Users?

 

Thanks,

 

SJMP

[Guest Ken Zhao [MSFT]]

RE: Migrating to New Terminal Server

 

Hello,

 

Thank you for using newsgroup!

 

From your post, I suggest you refer to the following steps to migrate

Terminal Server:

 

Set all of the TS users to have roaming profiles. Point this to another

network share and give them a few days or a week on the old server. Then

move forward with you IP change and the profiles will follow the users.

Thins would be your best solutions since you are considering load balancing

the two servers. Once the second server is available the settings will

follow them as they move from server to server.

 

First create the share location on another file server.

 

Next, go into AD and set the location on the Terminal Server Profile tab.

Depending on the number of users you should be able to get this done fairly

fast.

 

As the users log off the profile will be saved to the network for you. Then

it is just a matter of making sure that the users all log in/out during

this timeframe.

 

Thanks & Regards,

 

Ken Zhao

 

Microsoft Online Support

Microsoft Global Technical Support Center

 

Get Secure! - http://www.microsoft.com/security <http://www.microsoft.com/security>

====================================================

When responding to posts, please "Reply to Group" via your newsreader so

that others may learn and benefit from your issue.

====================================================

This posting is provided "AS IS" with no warranties, and confers no rights.

[Guest sen_ismail@web.de]

Re: Migrating to New Terminal Server

 

Hi,

 

2. you can u se printmgr tool for your printers

3. Lockdown Ts:

 

How to lock down a Windows Server 2003 or Windows 2000 Terminal Server

session

http://support.microsoft.com/default.aspx?scid=kb;en-us;278295

Windows Server 2003 Terminal Server Security

http://www.microsoft.com/downloads/details.aspx?familyid=402A0CD1-9E4D-4007-8EAF-C30623E71250&displaylang=en

 

Windows 2003 Terminal Server Lockdown Whitepaper:

http://www.microsoft.com/downloads/details.aspx?FamilyID=7f272fff-9a6e-40c7-b64e-7920e6ae6a0d&DisplayLang=en

 

3. License Server: f you use License Server on same Server you have

to install it new and add you Cal's > there no method to move TS

License!!

 

 

cheers,

Ismail

[Guest BradleyD]

Re: Migrating to New Terminal Server

 

Last year I did the same thing, move local profiles from an existing piece of

hardware to a new hardware platform. It took me the longest time to

understand a good plan to move the profiles. In conversation with Peter

Zawadzki of MS Enterprise Support, he communicated this process. It leaves

all the profiles intact as it only copies them. With a little trial it worked

very well.

 

1. Exported (using regedit) the following 2 Keys on the machine you are

exporting the profiles from:

 

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows

NT\CurrentVersion\ProfileGuid

 

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows

NT\CurrentVersion\ProfileList

 

- after you browse to ProfileGuid/ProfileList in regedit just

right-click on it and click Export – choose name and location and then click

OK

 

2. Do the same on new server just to have back up of original keys

 

3. Use robocopy to copy profiles between servers – I run that tool on target

server

 

 

Usage :: ROBOCOPY source destination [file [file]...] [options]

 

 

source :: Source Directory (drive:\path or \\server\share\path).

 

destination :: Destination Dir (drive:\path or \\server\share\path).

 

file :: File(s) to copy (names/wildcards: default is "*.*").

 

Copy options :

 

/S :: copy Subdirectories, but not empty ones.

 

/COPYALL :: COPY ALL file info (equivalent to /COPY:DATSOU).

 

/XD dirs [dirs]... :: eXclude Directories matching given names/paths.

 

4. In the example I gave you when still on the call I used /XD switch and

then specified directories which I did not want to copy

Ex.

robocopy "\\sourcemachine\c$\documents and settings" "c:\documents and

settings" /COPYALL /S /XD "\\sourcemachine\c$\documents and

settings\Administrator.JUPITER" "\\sourcemachine\c$\documents and

settings\Administrator" "\\sourcemachine\c$\documents and

settings\LocalService" "\\sourcemachine\c$\documents and

settings\NetworkService" "\\sourcemachine\c$\documents and settings\Default

User" "\\sourcemachine\c$\documents and settings\All Users"

 

- please readjust paths and names for your environment

 

5. You can also copy everything in Documents and Settings directory

 

Ex. robocopy "\\sourcemachine\c$\documents and settings" "c:\documents and

settings" /COPYALL /S

 

6. Please remember to copy both reg keys from source server to new one and

then import them by double-clicking on them

 

7. Log on with few user accounts to check if profiles load properly

 

8. If everything works fine you can disjoin old server from domain and take

it offline

 

- please check Active Directory Users and Computers if that account is gone

and that change replicated to all Domain Controllers

 

- clean up DNS if necessary

 

9. You can change new server name to the name old one was using and readjust

IP address

 

10. Reboot should reregister proper DNS records in DNS for this server

 

11. If It did not then please open command prompt on that server and run

 

Ipconfig /flushdns

 

Ipconfig /registerdns

 

Brad

 

"sen_ismail@web.de" wrote:

> Hi,

>

> 2. you can u se printmgr tool for your printers

> 3. Lockdown Ts:

>

> How to lock down a Windows Server 2003 or Windows 2000 Terminal Server

> session

> http://support.microsoft.com/default.aspx?scid=kb;en-us;278295

> Windows Server 2003 Terminal Server Security

> http://www.microsoft.com/downloads/details.aspx?familyid=402A0CD1-9E4D-4007-8EAF-C30623E71250&displaylang=en

>

> Windows 2003 Terminal Server Lockdown Whitepaper:

> http://www.microsoft.com/downloads/details.aspx?FamilyID=7f272fff-9a6e-40c7-b64e-7920e6ae6a0d&DisplayLang=en

>

> 3. License Server: f you use License Server on same Server you have

> to install it new and add you Cal's > there no method to move TS

> License!!

>

>

> cheers,

> Ismail

>

>

[Guest Ken Zhao [MSFT]]

Re: Migrating to New Terminal Server

 

Thanks Brad for your great information sharing!

 

Thanks & Regards,

 

Ken Zhao

 

Microsoft Online Support

Microsoft Global Technical Support Center

 

Get Secure! - http://www.microsoft.com/security <http://www.microsoft.com/security>

====================================================

When responding to posts, please "Reply to Group" via your newsreader so

that others may learn and benefit from your issue.

====================================================

This posting is provided "AS IS" with no warranties, and confers no rights.

[Guest Ken Zhao [MSFT]]

Re: Migrating to New Terminal Server

 

Hi,

 

I am just writing to see how everything is going. If you have any updates

or need any further assistance on this issue, please feel free to let me

know.

 

Thanks & Regards,

 

Ken Zhao

 

Microsoft Online Support

Microsoft Global Technical Support Center

 

Get Secure! - http://www.microsoft.com/security <http://www.microsoft.com/security>

====================================================

When responding to posts, please "Reply to Group" via your newsreader so

that others may learn and benefit from your issue.

====================================================

This posting is provided "AS IS" with no warranties, and confers no rights.

[Guest Labsy]

Re: Migrating to New Terminal Server

 

Many thanx to Brad and Ken for really great posts.

Now, I would have some additional questions, since I am just to begin such

the migration to new hardware.

 

My client has Windows 2003 terminal server in domain with one additional

server, being just the backup DC. On terminal server there are few hundreds

of clients with 150 CALs.

Now, since clients are from all over the whole country, it is almost

impossible to plan doing anything on the client side.

 

And clients are connecting to terminal server via IP, all use VPN and all of

them have shortcuts and shares either to IP or to NetBIOS name of TS.

So, customer's request is to keep the same machine name and the same IP

after migration.

 

Now, do I think right:

0.) Take preparation steps, installing new Windows server 2003 and terminal

services;

- new server will temporarily have different IP and machine name

1.) Install brand new 150 CALs onto new server

2.) Starting with friday, I disconnect old TS from public internet and leave

it on LAN

3.) Join the new TS to domain

4.) I follow Brad's instructions to move TS profiles from old to new server

4a.) Do I need to install all TS printer drivers to new TS??

5.) Test connection to new TS

6.) Disjoin old TS from domain and take it down

7.) Change new TS IP and machine name...hmmm, is this possible without

disjoining and rejoining to domain?

8.) Finish

 

I am mostly concerned about printer drivers, because sbdy told me I need to

install all drivers for all different printers, which are in use by terminal

users.

 

Also, changing IP and machine name of working terminal server is bothering

me - aren't profiles created in folder like "C:\Documents and

Settings\Username.SERVERNAME"? What happens when I change server name?

 

Any advice I'll appreciate. :)