Checks before remove with Exchange System Manager an Exchange Server 2003 from an 2010 exchange organization.
My problem is a variant of a classic unsolved. Our Exchange Organization contains two Exchange servers: the “new 2010” and the “old 2003” that I want to remove. I have followed all previous steps, but in the final step, remove server with add-remove programs in panel control, an error has prevented the complete removal of the “old 2003” server. The error code is 0x80072030 and arises during OMA and ActiveSync removal. More precisely the file “Exchange Server Setup Progress.log” tells us that the problem is the absence of the object HTTP protocol: (…… [13:26:15] Creating Ldob from "/dc=org/dc=MyCompany/cn=Configuration/cn=Services/cn=Microsoft Exchange/cn=MyCompany/cn=Administrative Groups/cn=correo/cn=Servers/cn=DDT/cn=Protocols/cn=HTTP" [13:26:15] CAtomOMASync::ScRemoveDSObjects (f:\titanium\admin\src\udog\exsetdata\components\server\a_omasync.cxx:376) Error code 0X80072030 (8240): No existe tal objeto en el servidor. ……) At the server level there are some remnants, but “Exchange Server” has disappeared from the list “add/remove programs” on the control panel. The services and executables have been removed (but still registered). The problems arises at active directory configuration level, the “new 2010” servers think that the LEGACY “old 2003” is still alive, it complains when “old 2003” do not answer and does not allow certain actions because there are a legacy server in the organization. Luckily no mail flow problems have appeared. Surfing the net I have found two ways out of the jam: a) Using Exchange System Manager to remove the “old 2003” server (without eliminating old administrative groups) b) Use ADSIEdit to create the protocol object that causes the error and run setup from CD. It is assumed that there will be no problems and that the removal will be completed successfully The way a) has MS references in the net, but also I’ve read some “I did this and had problems”. Way b) is one-reference-only. Well, I’ve ready ESM 2003 on another server to proceed with a). But, does anyone have any good advice for me before proceed? More info: I've exported Active Directory Domain and Configuration, wiht csvde utility. The only references to "old 2003" are at "HomeMTA" atribute on all mailbox and at "HomeMDB" on system mailgbox (GUID of old 2003). I think that this should not worry. The analysis of the configuration is too complex for me.Orutra
April 21st, 2010 5:18pm

Hi, What is the scenario now? Exchange 2010 has been installed into the network? Have you moved all the mailbox to the Exchange 2010 Mailbox Server? Please run ExBPA to have a health scan and then post the report here. Besides, I'd like to know which article that you use to remove the exchange server 2003 server. Error 0x80072030 ( ERROR_DS_NO_SUCH_OBJECT), please check the msExchAdminMailbox attribute of Message Delivery, it should points to a valid distinguishedName for User account Note: Configuration\CN=Services\CN=Microsoft Exchange\CN=<Your Org>\CN=Global Settings\CN=Message Delivery Regards, Xiu
Free Windows Admin Tool Kit Click here and download it now
April 22nd, 2010 6:18am

Thank you for your interest Xiu, - Exchange 2010 has been installed and in production. - All mailbox moved. - You can download xPBA XML file (and setup log) at http://www.ascer.es/publico/details.zip (It has given me new surprises) Servers: · DDT: Old server Exchange 2003 · Correo: New server Exchange 2010 (Mailbox, hub transpor, client Access,..roles) · Cortafuegos: Exchange Edge Server on Forefront TMG 2010 · Impresion: AD controller - I have read several articles about remove, the most significant o http://www.simple-talk.com/sysadmin/exchange/upgrade-exchange-2003-to-exchange-2010-%E2%80%93-part-ii/ o http://technet.microsoft.com/en-us/library/bb288905(EXCHG.80).aspx - msExchAdminMailbox attribute of Message Delivery, Value <No Set> Two more things. I think my problem is similar to this: http://www.sch0.org/index.php/2010/04/07/exchange-2003-uninstall-error-0x80072030 One possible origin of the problems was that the first time the setup asked for the CDROM, I’ve inserted “Outlook 2001 for Mac”.!!!!. The program seemed to accept and continue… But in the end I got an unexpected error. Then, I checked everything once more, until I read the label on the CD. Orutra
April 22nd, 2010 12:00pm

Hi, I have try to import your ExBPA report to my lab, but that is not in English. It is hard to me to read the information. Could you try to just post the warning and error event from ExBPA ? Besides, if you do not have any data remain on the Exchange Server 2003, then please try to just delete Exchange 2003 server container from ADSIedit. Note: Please ensure that all the users have accessed outlook since their mailbox moved to Exchange Server 2010. Regards, Xiu
Free Windows Admin Tool Kit Click here and download it now
April 23rd, 2010 6:23am

Excuse me Xiu, Critical Errors: · Schema versión incorrect 12639. (Fake, it is a known issue exPBA) · Exchange Server not suported (old server 2003) · Cannot Access WMI Edge Server (probably because lack of policy on Forefront TMG) Warnings: · Original OAB Public Folder not found. This arises before I try to remove 2003. I’ve moved with the shell all the IPM folders to new store. To resolve I have created another one based on web and set to default and and I erase the old when everything is stable. · There are other warnings that I do not consider significant. Number of threads under VSAPI, running on VM-vmWare, network adapter disabled. Yes, finally I will try to remove with ADSIEdit or Exchange System Manager 2003, but I'm waiting for answers from colleagues whom I consulted. When I do I'll post it One question about "ensure that all the users have accessed outlook", the reason is to verify that all mailboxes have been moved, or access to the mailbox causes an update? I´m having issues with resource mailbox and delegates.Orutra
April 23rd, 2010 11:41am

The resean that we need to ensure all the outlook users have access mailbox on Exchange 2010 first time is that it will do the update on the server that the mailbox remain. Note: When outlook try to connect to the mailbox, it will try to find the old exchange server first and then query DC to find where is the mailbox. After we access mailbox on Exchange 2010, it will update to connect the exchange server 2010. It will try to connect to the Exchange Server 2010 directly. Regards, Xiu
Free Windows Admin Tool Kit Click here and download it now
April 26th, 2010 8:44am

Ready. I've removed Old Exchange 2003 with ADSIedit without problems. Thanks Xiu.Orutra
April 29th, 2010 5:12pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics