Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 240
  • Last Modified:

Replacing a 2003 Standard server with 2008 Enterprise

I am replacing one of our older servers with a new one.  Here are some of the considerations & questions I have...

1. First of all, should I really go with 2008?  All the rest of our servers run 2003 Standard & our AD domain level is 2003.  I think I want to upgrade, but if it is less trouble I'll stick with 2003.

2. If I do go with 2008, what will I need to do to prepare the domain for a mixed environment?  This server will be a DC.

3. The old server held the Operation Master roles, SQL databases, and Backup Exec to disks...all of which will need transferred to the new server.  What's the best way to "replace" a server, including the DNS name/IP address?  Software on all our clients is set to point to the old server name.  Can I somehow use the same name?

~bruno71
0
bruno71
Asked:
bruno71
  • 2
1 Solution
 
tigermattCommented:

What roles will the server run? If it's Microsoft-based roles, or roles using software applications which support Server 2008, then I'd suggest you go for Windows Server 2008. There is no major reason to go for an older version of Windows; in fact, installing the latest OS will put that particular server in good stead without the need to upgrade for several years.

>> If I do go with 2008, what will I need to do to prepare the domain for a mixed environment?  This server will be a DC.

Simply prepare the domain prior to installing the server as a DC. ADPrep /forestprep followed by ADPrep /domainprep /gpprep from the ADPrep tool on the Server 2008 DVD media. You can then install the server as a DC, just like a 2003 server, and it will readily integrate itself into the Server 2003 network. No further work required to get it working as a DC.

>> The old server held the Operation Master roles, SQL databases, and Backup Exec to disks...all of which will need transferred to the new server.  What's the best way to "replace" a server, including the DNS name/IP address?  Software on all our clients is set to point to the old server name.  Can I somehow use the same name?

You'll need to transfer the FSMO roles per http://www.petri.co.il/transferring_fsmo_roles.htm over to the new server. The SQL Server databases would need to be taken down and migrated, as will the Backup Exec databases.

Only once the old server is demoted and removed can you consider referring to the new server using the old name. I never rename any server after it's promoted; I'd simply map a CNAME of the old name to the new name in DNS, add the old IP address as an additional IP on the new server, and add the old name as an additional NetBIOS name: http://thelazyadmin.com/blogs/thelazyadmin/archive/2006/07/18/Configuring-Additional-NetBIOS-Names.aspx. This is sufficient and will enable the new server to still be contacted using its old names/IPs.

-Matt
0
 
bruno71Author Commented:
Thanks Matt.  I will give this a try.

~bruno71
0
 
bruno71Author Commented:
Follow up...

I just migrated the server this past weekend.  Everything seemed to go just as it should

- ADPrep
- DCPromo / DNS
- DHCP
- FSMO
- Demote old server
- Setup DNS alias and add additional IP address

Thanks again
~bruno71
0

Featured Post

Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

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