[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

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

Removing SBS 2000 from network and installing Exchange 2010

Hi Guys.

I have an issue where I have the following:

Windows SBS 2000
Windows 2003 Domain Controller with Exchange 2003
Windows 2008 R2 Domain Controller

Now. I need to remove the Windows SBS 2000. This is a problem. I also need to remove the Windows 2003 server with Exchange 2003 on it.

This is how I plan to tackle this problem:

1) Install a new server in to the domain. The server will be Windows 2003
2) Install Exchange 2003 on the new Windows 2003 server
3) Move Exchange mailboxes and roles to the new server
4) Test then remove Exchange 2003 from the original server
5) Demote Windows 2003 Domain Controller
6) Turn off the SBS 2000 server and remove the entries in AD manually
7) Ensure all ad has replicated correctly etc and test
8) Install Exchange 2010 on one of the new R2 servers

How does this look?
0
Layer3User
Asked:
Layer3User
  • 7
  • 6
  • 3
1 Solution
 
Glen KnightCommented:
Why install a second Exchange 2003 server?

You already have one and a DC other than the SBS server so just decommission the SBS server and then install the new Exchange 2010 server.
0
 
naveencnairCommented:
Hi ,

Fist migrate the sbs 2000 to sbs 2008 trial version. Then do a migration from sbs 2008 to std 2008 R2.
Setup exchange 2010 and Move the mailboxes from 2003 exchange.

Below link will help you to migrate from sbs 2008 to std 2008 R2.

http://social.technet.microsoft.com/Forums/en-US/smallbusinessserver/thread/2302c957-7db5-4c7c-8d40-81895bf9fc3a/
0
 
Layer3UserAuthor Commented:
You have to add a second Exchange server because you cannot remove AD on a Exchange 2003 server. This server needs to be decommissioned.

Re SBS 2008, would that be quicker than my way?
0
Veeam and MySQL: How to Perform Backup & Recovery

MySQL and the MariaDB variant are among the most used databases in Linux environments, and many critical applications support their data on them. Watch this recorded webinar to find out how Veeam Backup & Replication allows you to get consistent backups of MySQL databases.

 
naveencnairCommented:
you can demote the domain after moving the mailboxes to the new server.
I Hope this is the quickest way, than the conventional way.
0
 
Layer3UserAuthor Commented:
That's actually something I never considered. Are the wizards quite good for a 2000->2008 SBS migration? I've just done a 2008-2011 migration and it was easy as.
0
 
Layer3UserAuthor Commented:
I'll leave this question open a bit longer to see if anyone can answer my original post. Just wondering if my way is correct doing it the traditional way. SBS 2000 throws a fit when you remove roles or dcpomo it.
0
 
naveencnairCommented:
It should work with your way also, but it was too confusing.

best of luck.
0
 
Glen KnightCommented:
First of all you don't need to demote the exchange server from being a DC before you install Exchange 2010.

What I would do:

> decommission SBS2000
> install Exchange 2010 on new Windows 2008 R2 server
> migrate exchange data to new server
> uninstall exchange 2003 and then demote that server

Nice and easy.  Absolutely no need for SBS2008 however, depending on the size of your network you may want to consider SBS2011 once the SBS2000 server has been decommissioned as this includes Exchange 2010
0
 
Glen KnightCommented:
Also, once the SBS2000 server is gone you can follow my guide here: 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 to migrate from Windows2003 with Exchange to SBS2008/2011.

The guide is for2008 but the steps are identical for SBS2011.

If you don't need the capability ignore than 75 users/devices or trusts (which assuming your notbecause you have an SBS2000 domain) migrating to SBS2011 is considerably cheaper than buying the full Exchange server product.
0
 
Layer3UserAuthor Commented:
Ok, What is the correct way to remove SBS2000 now that the network has grown? I did a trial run of this and ended up losing AD. I claimed the roles on another DC and basically switched the SBS 2000 server off, as I was told not to demote it. Doing this caused some kind of AD Desynch, and I lost AD off my Win2k8R2 sever and Win2k3. I managed to restore ad from a Directory Services restore.
0
 
Layer3UserAuthor Commented:
Just to clarify, we are not adding SBS back in to the mix. There are about 8 servers now, really have out grown it.
0
 
Glen KnightCommented:
The number of servers make no difference. If you have less than 75 users then SBS is still a very validsolurion regardless of the number of servers.

Either way you need to remove that SBS2000 server before you can do anything.

If you have tried and failed and seized roles (which is what it sounds like) then I would recommend hiring in some specialist assistance.  It sounds like there could be more wrong.
0
 
Layer3UserAuthor Commented:
I don't think that's the case... I have asked this on the Microsoft Forums and got a different answer. The reason I am asking here is for a second opinion.

Please see the following:
http://social.technet.microsoft.com/Forums/en-US/smallbusinessserver/thread/cb2f8315-a06b-4614-a910-e4f7c744effc
0
 
Glen KnightCommented:
Which part are you referring to?
The information I have provided is correct.

I have tested and completed most migration paths myself.
0
 
Layer3UserAuthor Commented:
Ok no problem.

So was I correct in siezing the roles of the SBS 2000 server? Or should I DCPromo it?

The reason I was talking about removing the Windows 2003 DC is they thought that could be a problem. It was better removing that first then switching the SBS 2000 server off. This was to stop replication issues in AD (Since this is what I believe happened in the first instance).

Now, I could not demote the Windows 2003 server without moving Exchange first to another server. We already have the new infrastructure setup so SBS 2008/2011 isn't an option long term. The plan was to move Exchange 2003 to a new server, demote Windows 2003 server, drop SBS 2000.

From here I could move with the Exchange 2010 install...

I don't know how much experience you've had with SBS 2000, but I've always had real issues removing it from a domain.
0
 
Glen KnightCommented:
I've had a lot of experience with SBS2000 but none for a while.

If you prefer, just turn it off and seize the roles and then cleanup AD.

You can then migrate to 2010 on a new server or SBS2011 if you don't exceed the 75 user limit.
0

Featured Post

Get your Disaster Recovery as a Service basics

Disaster Recovery as a Service is one go-to solution that revolutionizes DR planning. Implementing DRaaS could be an efficient process, easily accessible to non-DR experts. Learn about monitoring, testing, executing failovers and failbacks to ensure a "healthy" DR environment.

  • 7
  • 6
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now