Solved

sbs 2003 server to windows 2003 standard

Posted on 2011-09-21
1
171 Views
Last Modified: 2012-05-12
Hi,
we have a SBS 2003 server (server1) and a spare server (server2) running windows 2003 standard.  Spare server is no longer in use.
Exchange is no longer in use on the sbs server (it was moved to the hosted environment several months ago).  They're now just using the sbs 2003 server as a DC, DNS, DHCP, Print.

Idea is to move away from the sbs 2003 server (as the server is extremely old or wipe clean and make it an additional DC for redundancy).
would someone mind outlining the steps necessary.  Also, is it wise to use this opportunity to upgrade server 2 to windows 2008 or can we continue to use server2 as a windows 2003 and then reformat the old server to windows 2008. (this saves cost of buying an additional OS).
0
Comment
Question by:seven45
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
1 Comment
 
LVL 4

Accepted Solution

by:
Felicia King earned 500 total points
ID: 36577868
Here's the problem. SBS won't let you demote it. So you have two options.
1. Build new DC by adding to existing domain (do this only if you like the way the old domain was setup.) Then you have two DCs. Shut down the SBS server, sieze all the roles onto your new DC, and never bring that SBS2003 server back online. It has to be reformatted.
Then you have to clean out ADISEDIT from all the abandoned zombie objects associated with the old DC.

2. (My preferred) Build a new DC for a new domain. Migrate all users, etc. You start with something clean. I've never seen an SBS domain that I wanted to keep. SBS creates all kinds of SBS-only things that will hamper you in your development with a real domain. For instance, SBS creates all kinds of GPOs that you probably don't want. Look at the containers in AD. They are different from a standard domain. I have found it to be more work to try to clean up an SBS domain and get rid of all the legacy SBS-specific crud than to just start over.

I would not try to reuse the old server and put 2008 on it. The server probably doesn't have the horsepower to run 2008 properly. Also, 2008R2 requires 64-bit.
If you ever want to have the AD Recycle Bin, all of your domain controllers have to be 2008R2.

In-place-upgrade of servers .. I don't advise it. That process leads to pixies on workstations and even bigger pixies on servers, in my experience.
0

Featured Post

Resolve Critical IT Incidents Fast

If your data, services or processes become compromised, your organization can suffer damage in just minutes and how fast you communicate during a major IT incident is everything. Learn how to immediately identify incidents & best practices to resolve them quickly and effectively.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

The problem of the system drive in SBS 2003 getting full continues to be an issue, even though SBS 2008 and SBS 2011 are both in the market place.  There are several solutions to this, including adding additional drive space or using third party uti…
Restoring deleted objects in Active Directory has been a standard feature in Active Directory for many years, yet some admins may not know what is available.
The Email Laundry PDF encryption service allows companies to send confidential encrypted  emails to anybody. The PDF document can also contain attachments that are embedded in the encrypted PDF. The password is randomly generated by The Email Laundr…

733 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question