• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 218
  • Last Modified:

Replacing a Windows Server 2003 with a new Windows Server 2008 R2

I am replacing a Server 2003 32 bit with a new Windows Server 2008 R2 64 bit.  The main purpose of this server is as a Terminal Server.  The goal has been to configure the new server the same as the replaced server so that remote users can connect as before.

Some info:
There is a second Server 2008 R2 64 bit connected to the current server that is running SQL Server 2008 Standard for a Line of Business Application.  It will be connected to the new Server 2008 R2 server once in place.

The network is setup as a workgroup.

I am naming the new server the same name as the server being replaced.

I am giving the new server the same IP address as the server being replaced.

I created the same users on the new server as on the server being replaced--with the same passwords.

Question:
Given the info above, will the remote computers connect to the new server using the Remote Desktop client in the same way on the new server as the Server 2003 that is being replaced?

Is there anything I need to add or chnage on the new server?

Is there anything I should be aware of in terms of finalizing the setup?

Thanks.
0
b1dupree
Asked:
b1dupree
1 Solution
 
Jeff PerkinsOwnerCommented:
I did a search for a similar task earlier and found this post, I think you may find it helpful in eliminating any missed tasks:  http://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Server/SBS_Small_Business_Server/A_2465-Migrate-Windows-2003-with-Exchange-to-Small-Business-Server-2008.html
0
 
Darius GhassemCommented:
When you rename the server everything should be the same and normal. If the licensing server is on the same server then you will need to call the MS clearing house to re-activate the license.
0

Featured Post

Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now