[Last Call] Learn how to a build a cloud-first strategyRegister Now

x
?
Solved

Complete Removal of Exchange 2003 after Upgrading to Exchange 2007

Posted on 2009-02-12
8
Medium Priority
?
198 Views
Last Modified: 2012-05-06
I have had Exchange 2007 Standard up and running since last summer.  In that process then, I remember moving over alot of services to the new exchange from 2003.  In the fall, I decided to decomission the old server and rebuild it for another use.  

Now, since fall, after I did that, I notice that everytime I start the Exchange Management Console, I get the attached message popping up which is telling me that last summer when I had Microsoft helping me, they did not thoruoghly remove any and all reference of my old exchange from the network and this new email server.  I will need assistance getting this completely removed from the network and will need as much detailed instructions as possible, thanks.
Pic.JPG
0
Comment
Question by:rswanigan
  • 4
  • 4
8 Comments
 

Author Comment

by:rswanigan
ID: 23624260
Also, get these errors listed in my Event Viewer on my current 07 box, it is Event ID 5006 for each of the 3.  Each of the descriptions are different and this is what they say:

A route to Mailbox server CN=SATURN,CN=Servers,CN=pdc,CN=Administrative Groups,CN=pcmaorg,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=hq,DC=pcma,DC=org could not be found for store CN=Mailbox Store (SATURN),CN=First Storage Group,CN=InformationStore,CN=SATURN,CN=Servers,CN=pdc,CN=Administrative Groups,CN=pcmaorg,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=hq,DC=pcma,DC=org in routing tables with timestamp 2/12/2009 3:15:36 PM. Recipients will not be routed to this store.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

---------------------------------------------------------------

A route to Mailbox server CN=SATURN,CN=Servers,CN=pdc,CN=Administrative Groups,CN=pcmaorg,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=hq,DC=pcma,DC=org could not be found for store CN=Public Folder Store (SATURN),CN=First Storage Group,CN=InformationStore,CN=SATURN,CN=Servers,CN=pdc,CN=Administrative Groups,CN=pcmaorg,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=hq,DC=pcma,DC=org in routing tables with timestamp 2/12/2009 3:15:36 PM. Recipients will not be routed to this store.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

----------------------------------------------------------------------------

The topology doesn't contain a route to Exchange 2000 Server or Exchange Server 2003 server SATURN.hq.pcma.org in Routing Group CN=pdc,CN=Routing Groups,CN=pdc,CN=Administrative Groups,CN=pcmaorg,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=hq,DC=pcma,DC=org in routing tables with the timestamp 2/12/2009 3:15:36 PM.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

0
 
LVL 65

Expert Comment

by:Mestha
ID: 23625317
The error that you have posted above can be fixed by moving the database files in to a folder. You shouldn't store Exchange directories in the root.

L:\Exchange Databases\priv1.edb

Use the tools in Exchange to move the mailboxes.

Is the server mentioned your live server?

-M
0
 

Author Comment

by:rswanigan
ID: 23626571
No, the server being mentioned was my old exchange 2003 server that i no longer have anymore, i ended up rebuilding it last year so that error popping up must be a refeence to the old path of where the old EX03 DB was located.  what tools would i use to correct this issue, the command shell?
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

 
LVL 65

Expert Comment

by:Mestha
ID: 23627830
That probably means there are remains left behind in the domain. That will mean some adsiedit hacking.
How did you remove the server originally? Did you remove it correctly using add/remove programs?

-M
0
 

Author Comment

by:rswanigan
ID: 23636007
I thought it was removed correctly.  Last summer, I had Microsoft go through the process of properly decomissioning the server fro the coexsistence of the 07.  They performed replicator, connection, and service move over to the new server using the command shell, Exchange System Manager, etc.  So, when they were done, they next moved to uninstalling the exchange core from the 2003 server but it kept giving them errors.  I eventually ended up telling them i was just going to rebuild the machine and they said, since i was going to do that, there was no need to go through with further uninstall.  Now, every time i open Exchange Managment Console on my 2007 server, it shows these comsmetic errors trying to reference the old server.  How would i go about doing the adsiedit hacking, im sure thats what has to be done to fix this.  Im mail flow is not affected although there are some moments where i do have free/busy issues to my clients but i always thought it could be the SSL causing that.  Your thoughts?  Could you walk me through the adsiedit, im not sure if i used that tool/process before?.
0
 
LVL 65

Expert Comment

by:Mestha
ID: 23638042
If you had a call with Microsoft, I would go back to them and inform them that they haven't finished the job. The advice you were given was incorrect. They should have finished removing the old server.

The problem with hacking about in adsiedit is that you have to be very careful, it is the heart of the domain, one false move and it could cause a problem.
There are KB articles on manually removing Exchange servers which will take you through the process, but MS might be the best option if that is available to you.

-M
0
 

Author Comment

by:rswanigan
ID: 23638230
I tried, trust me, 3 diffeent times but they keep coming back at me with because the case was opened up under a different scope, they cant do that for me.  The suggestion of removal of my old exchange i didnt bring up till the very end of my case but the support technician said he added it to his notes.  Thats the problem with Microsoft, they are just to damn difficult and picky.  Anyways, well, ok, so if asiedit is out of the question, what kb articles could you refer me to to look up how to remove the rest of my old exchange of my network, thanks?
0
 
LVL 65

Accepted Solution

by:
Mestha earned 1050 total points
ID: 23638785
The problem is that there is no single article for the process.
These are the two main articles for the manual removal of Exchange. However you have to be careful because they are for the total removal. What it should do is give you an idea of what needs to be looked at.
http://support.microsoft.com/kb/833396
http://support.microsoft.com/kb/273478

If there are references to the old machine in the domain are intact, then there is always a chance the DR install removal method might work. This is where a temporary machine is built using the same name, then Exchange installed using the DR options. Once complete the server is removed gracefully using add/remove programs.

-M
0

Featured Post

Hire Technology Freelancers with Gigs

Work with freelancers specializing in everything from database administration to programming, who have proven themselves as experts in their field. Hire the best, collaborate easily, pay securely, and get projects done right.

Question has a verified solution.

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

It’s time for spooky stories and consuming way too much sugar, including the many treats we’ve whipped for you in the world of tech. Check it out!
Eseutil Hard Recovery is part of exchange tool and ensures Exchange mailbox data recovery when mailbox gets corrupt due to some problem on Exchange server.
There are cases when e.g. an IT administrator wants to have full access and view into selected mailboxes on Exchange server, directly from his own email account in Outlook or Outlook Web Access. This proves useful when for example administrator want…
Whether it be Exchange Server Crash Issues, Dirty Shutdown Errors or Failed to mount error, Stellar Phoenix Mailbox Exchange Recovery has always got your back. With the help of its easy to understand user interface and 3 simple steps recovery proced…
Suggested Courses

829 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