• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1823
  • Last Modified:

Cannot remove Exchange 2003 during SBS 2011 migration

I am in the middle of a SBS2011 migration and have been following the steps put forth in the article here on doing that and have gotten to the point of removing the Exchange 2003 server from the old server. When I do that I get the error that it cannot be completed because a prequisite has not been met. When I dug deeper I found that even though all the mailboxes migrated over to the new server without errors, there is still a System Mailbox in the old store that has about 2,600 messages in it. If you right click on it, the Reconnect and Purge options are greyed out and selecting Exchange Tasks for that box comes back with no tasks to do. I have hand walked through all the live accounts in the AD Users and Computers/General Exchange Tabs and everyone is properly pointing to the new server. How do I:

A) Figure out who/what this mailbox belongs to?
B) Empty it, Move it, or Delete it?

This is my last steps before repurposing the old server, and doing that repurposing was scheduled for tonight. I have a long night of load and patch ahead of me (Slow link here), so would really appreciate any help you can give me here. The old server was a bit messed up before we came in and took over administration of it, and we managed to get almost everything on it working again, or at least we thought so, but there could still be remenants of the bad configuration left behind. That was why we finaly convinced them to let us migrate them over to a new SBS 2011. I have attached a screen shot of the offending mailbox listing in the 2003 Exchange Administrator. Please let me know what else you need to help me figure this out. The only other option that I can see is manual removal of Exchange, but I was afraid I would miss something if I went that route. It's so much easier when the tools work as designed...
 Orphaned-System-Mailbox-Screen-S.doc
0
oneobserver
Asked:
oneobserver
  • 7
  • 2
1 Solution
 
oneobserverAuthor Commented:
In digging deeper, it appears that the SystemMailbox is actually as it should be, as is the Mailbox Store on the old system. I.E no mailboxes. Going back to the MS article http://support.microsoft.com/kb/283089 and diggin deeper.
0
 
oneobserverAuthor Commented:
Method 1 in that article is not an option, as Change is not presented as an option on the Drop Down list.

Following Number 2, still has the issue after reassigning the postmaster account to:

CN=Net Admin,OU=SBSUsers,OU=Users,OU=MyBusiness,DC=ClaremontGroup,DC=Local

This is the new Admin user that I created to do the migration. I confirmed that it's HomeMDB is the new one on the 2011 server. Still no joy. How do I safely take the next step and demote the server?
0
 
oneobserverAuthor Commented:
More information. The Schema does not appear to include the machine that contains the mailbox anymore. I can tell which one it is in by the database name, but that is the only indication. Is that why the remove fails? the error lines in the log that are causing the problem are as follows:

[19:26:12] This prerequisite has PASSED -- ID:62235 --
[19:26:12] Leaving ScPRQ_DoesNotContainLastMAPIMDBInMixedModeAG
[19:26:12]  ScPRQ_ServerIsNotRUSResponsibleServerInTheNonEmptyOrg (f:\titanium\admin\src\udog\excommon\prereq.cxx:3133)
           Error code 0X80072030 (8240): There is no such object on the server.
[19:26:12]  CCompServer::ScCheckEVSPrerequisites (f:\titanium\admin\src\udog\exsetdata\components\server\compserver.cxx:1358)
           Error code 0X80072030 (8240): There is no such object on the server.
[19:26:12]  CCompServer::ScCheckPrerequisites (f:\titanium\admin\src\udog\exsetdata\components\server\compserver.cxx:955)
           Error code 0X80072030 (8240): There is no such object on the server.
[19:26:12]  CComExchSetupComponent::ScCheckPrerequisites (f:\titanium\admin\src\udog\bo\comboifaces.cxx:1598)
           Error code 0X80072030 (8240): There is no such object on the server.
[19:26:12]  CComExchSetupComponent::ScCheckPrerequisites (f:\titanium\admin\src\udog\bo\comboifaces.cxx:1598)
           Error code 0X80072030 (8240): There is no such object on the server.
[19:26:12] === IGNORING PREVIOUS ERRORS === HrSetProblemOnInstallAction, while calling ScCheckPrerequisites (f:\titanium\admin\src\udog\bo\comboifaces.cxx:1399)
           The operation has completed successfully.
[19:26:12] Setup encountered an error while checking prerequisites for the component "Microsoft Exchange":
0X80072030 (8240): There is no such object on the server.
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

 
oneobserverAuthor Commented:
Out of things to discuss with myself on this. Will pick it up with a MS tech tomorrow.
0
 
Philip ElderTechnical Architect - HA/Compute/StorageCommented:
Are all of the user's mailboxes and the Public Folders moved over?

Philip
0
 
oneobserverAuthor Commented:
Yes. When you look specifically at the old server and look at te mailbox stores, it shows just the systemic boxes you cannot move.
0
 
Philip ElderTechnical Architect - HA/Compute/StorageCommented:
Yes, the content in the System Mailbox may or may not be relevant.

Using ESM on the source, go through _EVERY_ single folder that is left in PF because we have found that some sub-folders were still set to SOURCE which ended up being the source of our own failures.

See attached for the settings.

Philip
11-05-12-Exchange-PF-Replication.png
0
 
oneobserverAuthor Commented:
I did that and still had no joy. I ended up calling Microsoft and paying for the incident fee with them. Due to another issue that happened in parallel, it ended up being the longest phone call I have ever been on: 12 1/2 hours start to finish. I ran through three technicians during the call as they kept going off shift on me.

They went through the system, end to end, and after about 7 hours finally determined that there was a corruption in the installation that was not visible. To fix it, they had to rerun the SBS setup utility with the DisasterRecover flag set and reinstalled all of Exchange. Be warned if you ever have to do this, set aside several hours for it to complete, as it is an extremely slow processs while it checks every file and every permission. Once that process completed, it allowed us to rerun setup and remove Exchange as per the migration instructions. Once both servers were rebooted, the old server was finally fully removed from the configuration.
0
 
oneobserverAuthor Commented:
No Points to award, unless Microsoft has a standing account...
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Cloud Class® Course: Microsoft Exchange Server

The MCTS: Microsoft Exchange Server 2010 certification validates your skills in supporting the maintenance and administration of the Exchange servers in an enterprise environment. Learn everything you need to know with this course.

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