Member Avatar for Andrew Wiggin

We have an SBS Server as PDC, exchange server & SQL server. It is old and in need of upgrading. We have an office nearing the limit of SBS.

So, we bought a new non-SBS server as well as exchange & SQL. Now the question is how to best go about replacing the old server with the new server.

Both boxes are running 2003 - I know it is getting old, but the software they run doesn't support anything better. Besides, we have the license to upgrade to 08 at our convenience.

Is it as simple as:
- adding the new server as a DC
- moving the FSMO roles
- removing the SBS box
- promoting the new box and
- cleaning the meta data?

  • 1 Contributor
  • 2 Replies
  • 194 Views
  • 1 Week Discussion Span
  • Latest Post Latest Post by Andrew Wiggin

Dani AI

Generated

As ’s plan shows the right high‑level direction, here are the practical details and common pitfalls that the short checklist misses.

Start with a strict preflight: take full system‑state and bare‑metal backups of the SBS box, a verified full backup of Exchange databases and of all SQL databases, and document service account passwords, SPNs, DNS names and any hardcoded machine names used by apps. Schedule a maintenance window and a rollback plan.

Before moving FSMO or demoting the old DC, add the new server as an additional domain controller, enable DNS and make it a Global Catalog, then verify AD health and replication (dcdiag, repadmin /showrepl). Transfer FSMO roles gracefully (do not seize unless a DC is lost). Keep the PDC emulator/time master role on the intended machine and do not raise domain/forest functional levels until every DC and needed application supports the new level.

Exchange and SQL require their own migration steps. Prepare AD/schema for Exchange 2007 and install the appropriate Exchange roles (Hub/CAS/Mailbox) for coexistence; move mailboxes and replicate public folders before removing Exchange 2003. Take care with certificates, OAB/Autodiscover and Outlook profiles so client connectivity is not broken. For SQL, move databases and recreate or map logins so SIDs match (don’t forget SQL Agent jobs, linked servers and connection strings used by applications).

When ready to remove the SBS DC, uninstall Exchange from it after verifying all mail/data moved, then demote with dcpromo and clean up metadata only if required. Preserve the old server offline (but powered) for several days until clients and services are validated. Final checks: mail flow, client Outlook access, application connectivity, DNS/SRV records, and a tested restore from backups.

Member Avatar for Andrew Wiggin

additional notes:
we are going from exchange 2003 to exchange 2007

Member Avatar for Andrew Wiggin

I haven't tried it yet, but it looks like exactly what we need.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.