Errors Decommissioning Exchange 2007 Server

We are attempting to decommission an Exchange 2007 Server (single server). We have already gotten 2010 set up, installed, mailboxes moved and public folders moved. We went through and removed the replicas on the old server as well as removing the mailbox
database and public folder database.
From this point we are attempting to Uninstall Exchange 2007 using either the Wizard or through cmd using setup.com /mode:uninstall after navigating to the Bin folder in the Exchange server. Each time however, we get the same error regardless of how we are
doing it.
We uncheck all roles, hit Next, and it fails during the Readiness Check within 10 seconds on each role (Mailbox, Client Access, Hub Transport) each time saying: 'An error occurred while running the test. The Computer may be out of Memory, or the XML files
have been modified. Parameter name: ConfigurationFileLocation'
I've gone through using ADSI Edit and removed the server from the Configuration>Services>SiteDomain>Administrative Groups>Exchange Administrative Groups>Servers
and it was none existent in the Databases section.
Even after all of these steps I'm still getting the error about the memory or XML file issue. Is there a way to replace the XML files with 'clean' ones or a way to repair the existing ones? I'm just simply wanting to uninstall it at this point.
Thanks!

Hi,
From your description, I would like to clarify the following things:
1. It is not recommended to uninstall Exchange server in ADSIEdit.
2. The above error indicates that one of the xml files is corrupted, you need to re-download it for troubleshooting.
Hope my clarification can be helpful to you.
Best regards,
Amy Wang
TechNet Community Support

Similar Messages

Address list service failed to respond error on Exchange 2007 (after adding first 2013 server)

Hi,
We just installed an Exchange 2013 server within an Exchange 2007 environment.
The Exchange 2013 (CU6) server will be used to setup a hybrid connection with O365, and move mailboxes to O365.
After installing the Exchange 2013 server it isn't possible anymore to create/enable mailboxes on the Exchange 2007 server.
We end up with an error :
Mig1 TestAccount
Failed
Error:
The Exchange server address list service failed to respond. This could be because of an address list or email address policy configuration error.
Exchange Management Shell command attempted:
Enable-Mailbox -Identity 'domain.be/customer/TEMP/Mig1 TestAccount' -Alias 'mig1' -Database 'Exchange2007\SG01\DB02'
When executed via EMS we receive this error :
The Exchange server address list service failed to respond. This could be because of an address list or email address policy configuration error

Hi Lyncer
This error can be caused if the default Public Folder Database not being pointed to the exchange 2007 database which you are trying to create a new mailbox.
Also it can happen if System Attendant service is not running.
Troubleshooting steps:
1) Restart the System Attendant Service
2) Point the affected database to the default public folder
Follow the below steps to do that
Open EMC
Go to Organization Configuration > Mailbox.
Select the mailbox database that you want to change the default public folder database.
Right click the database and select properties
In <Mailbox Database Name> Properties, click the Client Settings tab.
Next to the Default public folder database box, click Browse.
In Select Public Folder Database, select the public folder database from the list of public folder databases, and then click OK.
Cheers!!!
Remember to mark as helpful if you find my contribution useful or as an answer if it does answer your question.That will encourage me - and others - to take time out to help you Check out my latest blog posts on http://exchangequery.com Thanks Sathish
(MVP)

Exchange 2007 EXCDO 8206 error in Exchange 2007 SP2 with Rollup 4

Dear sir,
    We have a problem on Exchange 2007 Server. When user use OWA to access web mail calendar, server event log will show EXCDO error 8206:
Calendaring agent failed with error code 0x8000ffff while saving appointment
Type: Error
Event ID: 8207
Category: General.
     Moreover server becomes working in very slow web mail response during any user click web mail calendar.   Server performance return back after error message appeared in event log.
It doesn't has problem if using Outlook to access mailbox calendar.
Any suggestion to fix it ?
Joe

Hi Joe,
We are also finding the same issue with getting that EXCDO error. The problem stemmed when users noticed some previously accepted appointments disappeared (As I suspect you discovered with your users).
The workaround has been to get the user to accept the appointment again by going into deleted items, this seems to add the appointment as it should have the first time.
We have done the following but it didn't fix the problem:
Disabled extra SEP features on the clients - No Change
Disabled non-essential Outlook add-ons - No Change
Removed BES Express and CDO MAPI From Exchange server - No Change
Disabled MS Defender on Exchange - No Change
Fixed any Public folder errors - No Change
Disable Window services WSS and UNC sharing feature in Active Sync - No Change
Also ensured Autoupdate and auto process was enabled for affected users - No Change
I'm going to try the reg change mentioned in this thread but other than the built in MS Defender we don't have anti-virus on our mail server.
At first we thought it was Active Sync as it only seem to impact those with a A/S device, but now it's intermittent for other users using Outlook.  We are currently using Exchange 2007 SP3 with RU13. We are looking at trying an update
to RU14 but I am doubtful it will fix the problem. Did you have any luck finding a solution?
Thank you in Advance.

Exchange 2010 - Decommissioning Exchange 2007 Coexistence and Removal of Public Folders

We are about to decommission exchange 2007, currently in coexistence with Exchange 2010.
We do not want to use ANY public folders in exchange 2010 going forward. Will do this after decom of 2007:
http://technet.microsoft.com/en-us/library/dd876883(v=exchg.141).aspx
I see this in the outlook connection status in outlook:
I have changed all Exchange 2010 mailbox databases to use a temporary 2010 public folders db named "public1" so that it is not communicating with the 2007 mailbox virtual server. However, the exact same connection status appears after I changed
the 2010 mailbox DBs to use a 2010 public folder db instead of the old 2007.
Question is, is it safe to decom the 2007 environment now? Is it normal to still have a connection to 2007 in "connection status" in outlook when the users mailbox is on a 2010 mailbox db? Is this connection related to public folders or something
else that needs modified before decom?
Thanks,
Josh

So, that wasn't the answer. I switched the Public folder DB on each mailbox database to a exchange 2010 server, PF DB, but hadn't actually moved any data from 2007 to 2010.
I didnt realize this is needed when we don't use public folders except for free-busy, default, etc.
What is the correct way to move the default public folders to a 2010 public folder?
I'm using the below URL as a template to migrate this info to a 2010 PF db.
https://www.simple-talk.com/sysadmin/exchange/upgrade-from-exchange-2007-to-exchange-2010---part-ii/
"The user Public Folders then need to be replicated to the Exchange 2010 Public Folder database as well. It is possible to manually configure
all Public Folders with a new replication partner, but it’s better to use PowerShell scripts that Microsoft delivers with Exchange Server 2010. Open the Exchange Management Shell and navigate to the Scripts directory
by entering the CD $ExScripts command,
and execute the following script:
AddReplicaToPFRecursive.ps1 -Server 2007MBX -TopPublicFolder "\"
-ServerToAdd 2010MBX"
My question is, do I have to do this "3rd step" since I don't think i have any custom "user public folders". Is this the user's free busy that I have to migrate, or is this author referring to custom PF db info?
Do I have to have public folders for free-busy and default exchange services at all in 2010?

Exchange 2007 server problems

Hello everyone,
I am having some trouble with our Exchange 2007.
Since some days ago I am having extrange troubles with out Exchange 2007 server. Users are been asked to write their user and password very oftenly, and I don't know the reason. Additionaly I have realised the OAB is not downloading properly in any Outlook
client. If I try to do it I am given an error number0x8004010F
I have been checking exhange server 2007 event viewer and I found a 80040115 error saying OALGen found an error accessing public folders while trying to generate OAL
Another error comes out inmediately after saying to check if Public folder store is mounted and there are replicas of Address Lists folders.
Another event viewer error says there was a problema trying to update availability information for the public folder in the virtual machine NAMESERVER
We have other 3 Exchange 2003 servers which I cannot remove because of an application we are using, accessing to them. As long as I know public flders are stored in Exchange 2007 server and not replicated in any other server, so I don't know if this has
something to do with the error.
Any idea of what might be going on?
Thank you very much.
Best regards,
David.

I know I'm not addressing your direct issue, but at this point you need to seriously be looking at removing all Exchange 2003 boxes. Exchange 2003 has left extended support:
http://blogs.technet.com/b/rmilne/archive/2013/10/08/save-the-date-end-of-exchange-2003-support-t-minus-6-months.aspx
What exactly is it with this app that causes it to lock on to 2003 only?
Cheers,
Rhoderick
Microsoft Senior Exchange PFE
Blog:
http://blogs.technet.com/rmilne
Twitter:   LinkedIn:
  Facebook:
  XING:
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

Delete old exchange 2007 server

Hi,
We have 2 exchange 2007 server(a and b) a is v very old hardware so we have configure new exchange 2007 name is b after configure create new data base and moved all mail box A to B server but if now server A is shutdown user prompting put user name and password.

Hi There,
You need move all the services to the server B before decommission server A.
The services that you need to move are:
Offline address book
Public Folders
System mailboxes (hidden)
Change OWA host name to point to server
When do.
Uninstall server A.
Exchange Blog:
www.ntweekly.com
MCSA, MCSE, MCITP:SA, MCITP:EA, MCITP:Enterprise Messaging Administrator 2010,MCTS:Virtualization

Treo 755p can't sync w/Exchange 2007 Server - AirSAMStateMachine.c 1913 14594

We recently migrated to an Exchange 2007 server and would like our phones to start using ActiveSync. All our Windows Mobile phones have no problem at all. However, we have two users who have the Treo 755p (running Palm OS), and they can't synch.
After some research I believe this is likely an SSL issue, and so I tried downloading the Palm Certificates Tool and uploading the root cert (GoDaddy whom issues us the cert that we use on our Exchange server), but that didn't work. I tried the actual cert issues to us, and a bunch of other combos, nothing works. The error is the same on both phones. Disabling the SSL in the settings simply gives us another error: AirSAMStateMachine.c 1913 4682
Any ideas? Maybe I'm uploading the SSL certs wrong?
Post relates to: Treo 755p (Sprint)

I wouldn't give up so soon. Imag here. Part time Exhange Admin, snowboarder, and denture wearer.
Your IT crew may have installed the SSL certificate correctly, and then again, maybe not. I've seen a few 2007 migrations that have missed some crucial steps that are fairly easy to fix. And given the symptoms you're seeing, it sounds like they missed something (left the default self-signed exchange cert enabled - oopsie-dah)
Check with your IT staff and ensure they IMPORTED and ENABLED the SSL cert using the Exchange Management Shell. If they applied it via IIS console, that may be the problem right there. With luck, we can debunk and put an end to this godaddy panic. Tell your admin they can PM me for additional details if they need any.
Post relates to: Centro (Sprint)

Certificate errors on Exchange 2007

We have a Exchange 2007 server that is recording certificate errors in the event log (server & domain names changed for post):
Microsoft Exchange could not find a certificate that contains the domain name contoso.com in the personal store on the local computer. Therefore, it is unable to support the STARTTLS SMTP verb for the connector DNS with a FQDN parameter of contoso.com.
Microsoft Exchange could not find a certificate that contains the domain name server.contoso.com in the personal store on the local computer.
I have checked the configuration of the send and receive connectors:
Get-SendConnector | FL name, fqdn, objectClass
Name : DNS
Fqdn : contoso.com
ObjectClass : {top, msExchConnector, mailGateway, msExchRoutingSMTPConnector}
Name : Host IT SMTP
Fqdn : contoso.com
ObjectClass : {top, msExchConnector, mailGateway, msExchRoutingSMTPConnector}
Get-ReceiveConnector | FL name, fqdn, objectClass
Name : Default servername
Fqdn : servername.contoso.com
ObjectClass : {top, msExchSmtpReceiveConnector}
Name : Client servername
Fqdn : servername.contoso.com
ObjectClass : {top, msExchSmtpReceiveConnector}
There is an installed certificate:
{mail2.contoso.com, www.mail2.contoso.com, autodiscover.contoso.com, legacy.contoso.com} - IMAP, POP, IIS, SMTP valid until 09/01/2016
There was a expired certificate:
{servername, servername.contoso.com} - SMTP valid until 08/12/2010
The fact that the mail is still working despite the expired certificate, makes me wonder if I could just change the receive connectors to use mail2.contoso.com instead of servername.contoso.com
In the same vein, could I change the send connector to mail2.contoso.com from contoso.com

Hi,
Don’t modify the FQDN value on the default Receive connector Default <Server Name> that's automatically created on Mailbox servers. If you have multiple Mailbox servers in your Exchange organization and you change the FQDN value on the Default
<Server Name> Receive connector, internal mail flow between Mailbox servers fails. For more information about it, please refer to fqdn parameter in the following article:
http://technet.microsoft.com/en-us/library/bb125140(v=exchg.80).aspx
I suggest we can renew the expired certificate with names: contoso.com, servername.contoso.com instead of changing the FQDN of receive connector and send connector:
http://blogs.technet.com/b/exchange/archive/2007/07/02/3403301.aspx
Thanks,
Winnie Liang
TechNet Community Support

I have a problem connecting to my company exchange 2007 server from my IPAD2 the same settings worked with the IPAD1

Hi All
Can anybody help with this problem when trying to authenticate on the Microsoft Exchange Sever.
I have been trying to connect the mail client on the IPAD2 to my company email (Exchange 2007 server)
There appears to be an issue with the SSL settings for the IPAD 2 and Apples new OS
I know that it’s not supported but I also know that the previous version of the IPAD worked fine using the same settings.
Just to confirm I can access the email via Safari therefore I know that the Public Key is loaded in the web browser.
Can anyone confirm that the Public Key has been installed on the IPAD 2 email client?
Is there anyway to edit the SSL settings?
Thanks in advance fro your help
Regards
Pat

Try using Static IP and force a connection.
You can get the settings from your other devices that are connected to the router.

Exchange 2013 SP1 Readiness Checks: No Exchange 2007 server detected

Hi there,
We are planning to upgrade our current Exchange 2007 server with the new Exchange 2013 SP1. I have been following Exchange Server Deployment Assistant to assist me with this task. Only schema update (setup /PrepareSchema) had been done so
far. I didn’t run setup /PrepareAD command manually because I wasn’t sure if I need to provide ‘Organisation Name’ with it or not?! I have installed all of the prerequisites as noted in the Microsoft documentation.
Now, I am a bit confuse with the ‘Readiness Checks’ page during graphical user installation of Exchange 2013 SP1 setup on Windows 2012 R2. Windows 2012 R2 server has all available updates applied.
===
Warning:
Setup will prepare the organization for Exchange 2013 by using 'Setup /PrepareAD'. No Exchange 2010 server roles have been detected in this topology. After this operation, you will not be able to install any Exchange 2010 servers.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.NoE14ServerWarning.aspx
===
I get the message why setup wants to run preparation for the Ex2013 with the ‘Setup /PrepareAD’. But, why ‘No Exchange 2010 server role have been detected in this topology’?! Ok, in my case setup doesn’t detect Exchange 2007 server. Is that ok to proceed
with the installation or something else needs to be done first?
Thanks in advance.

I need Exchange guru advice here please. Since we already have Exchange 2007 SP3 RU 10 in our Windows 2008R2 Active Directory domain here I need to be 100% confident that pushing Exchange 2013 SP1 “Install” will not override our existing Ex2007 environment.
That would be a huge disaster!
Microsoft is saying that: “Microsoft Exchange Server 2013 Setup displayed this warning because
no Exchange Server 2010 or Exchange Server 2007 server roles exist in the organization.”
http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.NoE14ServerWarning.aspx
Ok, I get the message about if I continue with Exchange Server 2013 installation, I won’t be able to add Exchange 2010 or Exchange 2007 servers to the organization at a future date..., and why would I need to do that anyway?!
Microsoft wording about “some solutions may require the use...” are very confusing since we will require to consider “Coexistence or migration requirements"
Perhaps, before running Exchange 2013 SP1 setup I need to run setup for preparing AD without “Organisation Name” parameter?! Something like this:
setup /PrepareAD /IAcceptExchangeServerLicenseTerms

Exfolders.exe tool crashes on Exchange 2007 server

I've downloaded Exfolders.exe and I'm trying to run it on my Exchange 2007 server but it crashes everytime. I get an APPCRASH with a fault module name of kernel32.dll
http://gallery.technet.microsoft.com/Exchange-2010-RTM-<//wbr>ExFolders-c76c3649
I followed all the instructions step by step.
How do I fix this?

Hi,
You didn't see this information?
ExFolders must be run from an
Exchange 2010 server - it cannot be run from a workstation as PFDAVAdmin could. It can connect to Exchange 2010 or Exchange 2007, but not older versions.
PFDavAdmin is the tool to use on Exchange 2007
http://www.microsoft.com/en-us/download/details.aspx?id=22427
Martina Miskovic

Running Exchange 2007 server in unsynchronized RU levels

We have Exchange 2013 with legacy 2007/2010. My 2007 servers are at RU10. one of my sites has a need to replace their edge server and wants to install a 2013 edge server, but the internal 2007 hub server will require RU13 to communicate with the 2013 edge.
Will updating that single hub server to RU10, and leaving the rest of my 2007 environment at RUY10 cause issues?
Tom

Hi Tom,
Thank you for your question.
We could make internal Exchange at different CU level, but it didn’t recommend by Microsoft, as Hinte’s said. Because there are some improvements at new CU for us to avoid issue, include communicate between internal Exchange 2007 server.
We could refer to the following link:
https://technet.microsoft.com/en-us/library/aa996719(v=exchg.150).aspx
If there are any questions regarding this issue, please be free to let me know.
Best Regard,
Jim
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Jim Xu
TechNet Community Support

Removing Exchange 2007 Server from Management Console List

Hello,
We have an organization with a single Exchange 2007 Server running in production. It is working fine.
However, we brought up another server (we'll call it the secondary server for purposes of this thread) and linked it into this organization several months ago. Our plans for this box changed and we have kept it powered off, unlicensed, and unused.
Now, when we manage our production server, the management console keeps complaining about how the secondary server is almost at the end of its trial period, needs licensed, etc.
Since we might or might not use the secondary server in the future, it is possible to "unlink" it (or set it dormant somehow) from the server list to stop the license warnings? Or is our only recourse to remove Exchange and take it down if we don't
intend to license it and bring it into production? Our hope is that it can wait in the wings until such time as we decide to user & license it.
What are the implications if we ignore the license warnings and continue not to use it? Will it impact management of the production server at all or just continue to annoy?
TIA, Tom W.
JTW

Hello,
"What are the implications if we ignore the license warnings and continue not to use it? Will it impact management of the production server at all or just continue to annoy?"
You should have all production servers licensed but after trial period expiration the server will have all Exchange capabilities and features. Also trial period expiration should not have any negative impact on your environment. The EMC will simply prompt
to license that server correctly.
"Our plans for this box changed and we have kept it powered off, unlicensed, and unused."
In my opinion it is bad idea to have Exchange server installed but powered off. Note that this server still resides as object in Active Directory and it may complicate any future modifications of your environment (migration to newer versions of Exchange
etc.). I think you should use this server to provide some kind of high availability (and provide proper license for it) or remove it completely.
Once again: trial expiration is not a problem from server's functionality perspective, Exchange server powered down - it can be a problem.

Cannot connect to Exchange 2007 server on OS 3.1

Hi
Since I've upgraded to OS 3.1 on my iPhone 3GS I cannot connect to my Exchange 2007 server. The phone simply tells me "The connection to the server failed.".
What could this be? I've read the problems that 3G people are experiencing, but I've got the 3GS.
Is there anyway to debug this? The Exchange server works fine in Outlook and I can even connect to the web interface through Safari on the iPhone.
Any suggestions?
Best regards,
Thomas René Sidor

Hi,
Seems you have found the solution here:
http://social.technet.microsoft.com/Forums/exchange/en-US/5b7d250e-c995-4322-b1e7-5ad14ace81c5/cannot-connect-to-exchange-2013-server-prompt-for-username-and-password-that-are-not-accepted?forum=exchangesvrgeneral#d266273b-e04c-45a9-8b0f-8b48bf647a86
I'm post the answers here so that it will benefit for other community members who have similar qustions:
Install the
November
2012 Update for Outlook 2007 SP3 to resolve the problem.
Thanks for our MCC steve siyavaya.
Cheers,
Steve Fan
TechNet Community Support

Decommission Exchange 2007 Mailbox Server from Cluster

Hi! I realize this is an Exchange 2013 forum, however as I do not see any forums for older flavors of Exchange I'm going to post this here. If a better forum exists please let me know and I'll happily move to that forum for my answers.
I am just finishing a migration from Exchange 2007 to Exchange 2013. In the Exchange 2007 environment I have 2 CCR Mailbox Clusters. While working to decommission the first of the two clusters I successfully evicted the passive node, however
I mistakenly evicted the active node rather than removing it by running the Exchange Setup Wizard as outlined in the TechNet article "How to Remove the Active Mailbox Role from a CCR Environment".
Now, when attempting to uninstall Exchange 2007 using the Setup Wizard in Add/Remove Program I get the following error during the prerequisite check for the 'Mailbox Role':
Error:
Exchange server FQDN was not found. Please make sure you have typed it correctly."
Setup then completes.
Is there a way to cleanly uninstall Exchange 2007 and clean-up Active Directory?
Thanks!

Hi Jesse,
Thank you for your question.
We could run “ADsiedit.msc” in run, then navigate
Configuration [<domainController>.contoso.com]> CN=Configuration,DC=contoso,DC=com> CN=Services> CN=Microsoft Exchange> CN=<OrganizationName> CN=Administrative Group> CN=Exchange Administrative Group>CN=Server
We could check if mailbox server is existed in this container, we could remove it.
Notice: Before we remove it, we could make a backup for AD database. We suggest you call MS engineer for help.
If there are any questions regarding this issue, please be free to let me know.
Best Regard,
Jim
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Jim Xu
TechNet Community Support

Errors Decommissioning Exchange 2007 Server

Similar Messages

Maybe you are looking for