Dear Customer,
Thank you for posting in newsgroup.
According to the description, you want to know what can be migrated from a
Windows Server 2003 based stand-alone box to a Window Server 2008 based
stand-alone box. If I have any misunderstanding, please feel free to let me
know.
Based on the experience, here is some information for your reference.
Analysis and Suggestions:
==========================
If we establish a new box installed with Windows Server 2008 and make it as
a stand-alone server, we cannot migrate the "User profiles” "Desktop" and
“TS setup” from the old Windows Server 2003 based stand-alone box. The
reason is that the security identifiers of the users and groups on the two
different operation system are totally different. If we simply copy the
"user profile" and the "Folders" from the old box to the new box, the NTFS
security settings of them will lose. In this case, the user profile and
Folders cannot serve the clients normally.
To resolve the potential problem of SID, I would like to suggest that you
promote the old Windows Server 2003 system to be domain controller first,
and then you may extend the forest schema and domain schema, afterwards you
can promote the new Windows Server 2008 box to be an additional domain
controller of the current domain.
Since there are only 5 users on the old box, I recommend that you migrate
"User profile" which includes "Desktop" settings by configuring roaming
profile on the domain controller to save the "User profile” on the new
Windows Server 2008 box.
For more detailed information, please refer to:
Configuring Roaming User Profiles
http://technet2.microsoft.com/Window...2-c982-4bfb-89
1e-91b47f211e181033.mspx?mfr=true
And we can also migrate the "Folders" from the Windows Server 2003 DC to
the Windows Server 2008 DC by using File Server Migration Toolkit.
For your convenience, I have list the general steps to migrate files and
folders with File Server Migration Toolkit.
Steps:
1. You may install File Server Migration Tool on the new file server.
2. Launch the File Server Migration Wizard.
3. Create a new migration project and save it in "C:\FileServerMigration"
4. When you add source file server, please input hostname (inputting IP
address of server is not supported)
5. Please unselect the checkbox of "Resolve invalid Security descriptors"
and select the checkbox of "Copy security settings"
6. You may find that all the files and folders with Share and Security
permission have been replicated to the target server.
7. Since the Security descriptors (users and groups) are stored in Active
Directory Database, all the folders and files can be accessible as normally.
8. Please remove old file server and rename new file server to the old
server name.
9. Please note: you may perform the migration in the spare time since this
migration can be transplant to the clients.
For more information, please refer to:
File Server Migration Toolkit Whitepaper
http://download.microsoft.com/downlo...5-a2af-35e0b81
046af/FSMT%20Whitepaper.doc
You may download the FSMT from the following link
Download: Microsoft File Server Migration Toolkit
http://www.microsoft.com/downloads/d...eae-930a-42b0-
b595-66f462f5d87b&DisplayLang=en
We can also migrate the Terminal Service setting from the old Windows
Server 2003 box to the Windows Server 2008 box.
For your convenience, I have list the general steps to migrate Terminal
Service.
1. Install and then activate Terminal Server Licensing on the new Windows
Server 2008 license server.
For step-by-step instructions, please refer to:
Install Terminal Server Licensing
http://go.microsoft.com/fwlink/?LinkId=62988
Activate a Terminal Server License Server
http://go.microsoft.com/fwlink/?LinkId=62991
2. Install the same number and type of TS CALs on the new license server
that you had on the Windows 2008 license server. To do this, please call
the Microsoft Clearinghouse. When you call the Clearinghouse, make sure
that you have your License Purchase Agreement information (documentation of
your purchased TS CALs) readily available to facilitate the re-issuance of
the CALs.
For step-by-step instructions on how to locate the correct telephone number
for the Clearinghouse, please see Locate the Microsoft Clearinghouse
telephone number for your country or region
http://go.microsoft.com/fwlink/?LinkId=62994
3. Make sure that your terminal server can discover the new license server.
For step-by-step instructions, please refer to:
The terminal server cannot locate the license server
http://go.microsoft.com/fwlink/?LinkId=62995
(you may refer to "verify whether the terminal server can discover the
license server")
Please note:
Clients that received CALs from the previous license server will continue
to operate as normal until their CALs expire. When the previously issued
CALs expire, new licenses will be requested for these clients from the new
license server.
For information about license issuance and expiration, please refer to:
Recovering client access licenses on a Terminal Server license server
http://go.microsoft.com/fwlink/?LinkId=62996
Please note:
To be discoverable in a domain, a license server must be a domain
controller. If you did not install Terminal Server Licensing on a domain
controller, then, on the terminal servers, configure the new license server
as a preferred license server, so that it can be discovered in the domain.
For step-by-step instructions, please refer to:
"Set a preferred license server" in The terminal server cannot locate the
license server
http://go.microsoft.com/fwlink/?LinkId=62995
For detailed information about the license server discovery process, see
“Licensing Service Discovery” in Windows Server 2003 Terminal Server
Licensing (
http://go.microsoft.com/fwlink/?LinkId=26220).
4. Deactivate the previous license server.
For step-by-step instructions, please see Deactivate a Terminal Server
license server
http://go.microsoft.com/fwlink/?LinkId=62998
Hope all the information can help.
David Shen
Microsoft Online Partner Support
Similar Threads
Linear Mode
