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

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

Steps for removing old exchange 2003 server

I need to to the real world steps (not the microsoft version) for removing an old Exchange 2003 server.

I have a 2003 AD domain that I have run the adprep for Server 2008. I have installed two server 2008 machines one running Exchange 2007 (hub or gateway) and one running Exchange 2007 (mailbox or backend). I have moved all the mailboxes using the Exchange 2007 tools and shut down mail services on the old 2003 exchange server. Everything seems to be working fine so I want to remove the old Exchange server and rebuild it for something else. Since it is integrated in the forest I was wondering what is the cleanest way to remove the server without leaving traces in AD.
0
BillPrice77
Asked:
BillPrice77
1 Solution
 
Glen KnightCommented:
Because the server will be the first Exchange Server in the organisation there are a few additional steps you need to take, like re-homing the Public folders.
See here for a guide on removing the FIRST Exchange Server: http://www.msexchange.org/tutorials/Removing-First-Exchange-2003-Server-Part1.html
0
 
Glen KnightCommented:
I would also recommend this guide: http://support.microsoft.com/kb/822931
I have used it many times when migrating to 2007 or 2010 and it works perfectly.
0
 
BillPrice77Author Commented:
I have followed the link provided by Demazter and the steps were very detailed.

I have Rehome the Offline Address Book folder, Change the server that is responsible for generating the Offline Address List , Rehome the Schedule+ Free Busy folder, Rehome the Organization Forms folder, Rehome the Recipient Update Service  but when I got to "Designate another server to be the routing group master" I found that the only server to select is the old server. So I am stuck on how to set the new server as master. Also I have a connector setup to the new "hub" 2007 server. Do I neeed to do anything to the new servers? I have called Microsoft to use my last FREE incident for this year to address these questions but any feeedback would be great. I think I am at the last step before inserting the CD and removing the services but I want to make sure before I do so.
0
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

 
Glen KnightCommented:
You won't need the routing group so it can be removed.
0
 
Glen KnightCommented:
>>> Also I have a connector setup to the new "hub" 2007 server

can you clarify this?
0
 
BillPrice77Author Commented:
The connector sends requests from the old 2003 server to the new 2007 "hub server" I put it in there for the mobile devices but I have reconfigured them since then so I think its OK to remove.
0
 
Glen KnightCommented:
You shouldn't need that exchange should deal with it without that.
Remove both and you should be good to go
0
 
MesthaCommented:
This is the Microsoft guide that you need.
http://technet.microsoft.com/en-us/library/bb288905(EXCHG.80).aspx

The KB article above is for Exchange 2003 type migrations only, so isn't really suitable.

The Microsoft documentation is very good and there is nothing in the above guide that I can quibble over.
The only thing I do differently to most migration guides is that I replicate the public folders, then remove the replicas once the mailboxes have gone across, rather than use the move all replicas script.

Simon.
0
 
BillPrice77Author Commented:
Thanks for all the help I am on the phone with microsoft now because when I shut down the info store on the old source server my client machines start asking for username and password. Yet when I fire the info store back up on the old source server it stops.
0
 
BillPrice77Author Commented:
Microsoft is telling me everything is configured to point to the new server, the tech even setup a remote session so he could look at the old server and the new server and he said everything was correct. So I am on hold while the he tries to find out why it is still asking for a login when I shut down the old server. I'll post what he finds if he finds something.
0
 
Glen KnightCommented:
is the new server installed on a Domain Controller?
If so is it a Global Catalogue server?
0
 
BillPrice77Author Commented:
no the new server is on a 2008 box all by itself but I think you are on the right track Microsoft is having me run some tests on my 2003 domain controllers right now.
0
 
Glen KnightCommented:
Interesting, are your DNS servers on Windows 2003?
If so have you set the config for support of IPv6? as per: http://technet.microsoft.com/en-us/library/cc738372(WS.10).aspx
0
 
BillPrice77Author Commented:
Thank you "Demazter" your link for removing the exchange server was right on but I ran into a problem where when I shut down the services on the old exchange server I started getting login prompts for the old server. I called microsoft and here is what we found:

Microsoft support:
For testing purpose we stopped all the Exchange services on Exchange 2003 Server. As soon as we stopped the services we found that all the
    Outlook users started getting prompts for credentials. If we start the Exchange services back such as the Microsoft Exchange System Attendant
     service we stop getting prompts for credentials. It also specifies that it is trying to connect to Exchange 2003 server (Old exchange server)

# We went to ADIEDIT under Domain partition, searched for a user who was getting the prompt for credentials and then found that we did not have the
    Allow Inheritable Permission checked for any of the migrated users. For testing we put a check for Allow Inheritable Permissions and then tried
     opening Outlook for one of the user, it still was prompting for credentials.

# When we created a new mailbox directly on the Exchange 2007 server, they did not give any prompts for credentials.

# We also ran a command SetSPN -L "FIREBIRD" and got the correct output.

# We then went to the properties of Mailbox Database under First Storage Group on Exchange 2007 server. Under the Client Settings Tab we found
    that the Default Public Folder Store was pointing to the Exchange 2003 server. We went ahead and re-pointed the Default Public Folder Store to the
    New server.

# Found that once that was done, we were no longer getting the prompt for credentials.

# Then we had a look at some basic settings for Offline Address Book. Created a new OAB and enabled both Public Folder Distribution as well as
     Web Based Distribution.

# Finally we also ensured that both the internal as well as the external mail flow was working fine.
0

Featured Post

Veeam Disaster Recovery in Microsoft Azure

Veeam PN for Microsoft Azure is a FREE solution designed to simplify and automate the setup of a DR site in Microsoft Azure using lightweight software-defined networking. It reduces the complexity of VPN deployments and is designed for businesses of ALL sizes.

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