Member Avatar for G_Waddell

Hi All,

Two questions really:

  1. Is Windows 2003 still supported? (With all the fuss about XP support ending, I'm not sure if I missed it)

  2. We have an old Windows 2003 Small Business Server as our domain controller, Exchange server and file server which is coming to the end of it's life.

We also have a Hyper-V (not service but bare bones server) with an iSCSI connection to a NASbox for the VM disks.

I'm thinking of creating an Exchange VM and Maybe getting another NASbox to use as a file server. But I'm not sure what to do with the SBS box. From my understanding of SBS, it is supposed to function as a sole domain controller and does not play well with other domain controllers. Does this mean if I want to build a replacement SBS box or move us over to a "proper" domain controller I will have to build the new machine "off of the domain" and then swap it out? Or create a new domain?

  • 2 Contributors
  • 2 Replies
  • 331 Views
  • 2 Weeks Discussion Span
  • Latest Post Latest Post by G_Waddell

Dani AI

Generated

Quick, practical summary and a safe path forward for this older SBS build.

Windows Server 2003 and its SBS variants are no longer supported by Microsoft — Windows Server 2003 went out of extended support in July 2015, and Small Business Server 2003 R2 has its own lifecycle that ended later. Running production services on these OSes today is a security and compliance risk; plan a migration rather than a repair. Windows Server 2003 lifecycle | SBS 2003 R2 lifecycle. (learn.microsoft.com)

About SBS and domain controllers: the common belief that SBS “can’t live with other DCs” is a myth. You may add additional domain controllers for redundancy, but SBS domains have constraints (single SBS per domain, SBS must be the forest root, and SBS expects to hold the FSMO roles and be a GC until you migrate). That means the safest migration is to introduce a new supported server as an additional DC, replicate, transfer roles, then demote the old SBS. . ()

A practical checklist (apply to ’s Hyper-V + iSCSI setup): inventory roles (AD, DNS, DHCP, Exchange, file shares), get full system-state + Exchange backups, deploy a new supported Windows Server VM on trusted storage, run any required adprep, promote it as an additional DC and let AD replicate, transfer all FSMO roles and make it a GC, move file shares and printers, migrate mailboxes (cutover/staged/hybrid or to Exchange Online depending on mailbox count), verify, then demote and remove SBS. Use Microsoft procedures for transferring FSMO roles and for Exchange migration planning. FSMO transfer guidance | Exchange migration options. (learn.microsoft.com)

Virtualization and operational cautions: running DCs as VMs is fine, but do not rely on VM snapshots or VHD copies as your AD backup — they can cause USN rollback and replication problems. Use AD-aware backups inside the guest, keep at least two DCs on separate hosts if possible, and test restores before you retire the old server. If you want a like-for-like SBS replacement path, Microsoft’s Essentials migration guide is a useful walkthrough. Virtualized DC best practices | Migrate to Windows Server Essentials. (learn.microsoft.com)

If a checklist or terse commands would help, an ordered step-by-step tailored to your exact Exchange version and user count can be added.

Recommended Answers

All 2 Replies

Member Avatar for tigergeek

1) Extended support to 2015
2) If you use some of the other features of SBS 2003 (or 2003 R2) you might want to upgrade to SBS 2008, unless you have outgrown it by size or number of users. Then a 2008 R2 server, set up as a new domain controller then move the other server's over to new domain. ( no more Service packs or bug fixes since 2009 for 2003 )

Unless you have grown larger than 25 users or 50 total devices, moving to 2008 SBS would be the easiest and cheapest way to go. If you have grown to large, you might want to engage a consultant for Small businesses to creat and update your backend infrastructure.

Setting up your domain for a Hyper-V exchange server is a good idea if you have grown large enough or just want to play with servers but 2008 is much more complex to do what you are saying you want to do with 2008 than 2003, if you are not a systems engeineer or Sr. level Admin I would recommend at least a meeting with a good local consultant to come up with a realistic plan.

Member Avatar for G_Waddell

Thanks Tigergeek,
Thats the joys of working in a small company, I'm a developer by trade but you have to be willing to try your hand at everything. I think an upgrade to 2008 SBS then may be the easiest move.

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.