Remove Exchange 2007 from an Exchange 2013 coexistence.

Hey everyone,
I've just installed Exchange 2013 on a new server and all is working great. It is currently in coexistence with our old Exchange 2007 server. I've since shut the server down and Exchange 2013 has been working without issue. However, I haven't
been able to find any articles on this matter so I figured I would ask the question here.
How do you remove Exchange 2007 from the coexistence. Do I just uninstall Exchange 2007 from the old server and it will remove itself from the server and the domain? Any help/link on this matter would be greatly appreciated.
Thank you,
Chris

Hi Simon,
I am about to do the same exercise as Chris, I just would like some clarity.
1) When you say mailbox Database, do you mean make sure there are no more mailboxes that you want to move over, or are you actually meaning delete the physical DB on the exchange 2007 server.
2) If there is no use of public folders does anything need to happen?
Thanks,
Terry

Similar Messages

Removing Exchange 2007 from SBS 2008 (In an Exchange 2010 Coexistance Scenario) - In order to remove 2007 Mailbox Objects from Active Directory and remove the SBS2008 server completely

I'm trying to remove Exchange 2007 from an SBS 2008 server
(Server 2008 Standard FE). My ultimate goal is to completely remove the SBS 2008 Server from the network environment.
We have an Exchange 2010 Coexistence Scenario and Mailboxes/Public Folders/etc have been moved over to the 2010 mail server, on Server 2008 R2.
I have moved all Shares, FSMO roles, DHCP, DNS, etc over to their respective servers. We have two full blown DC's in the environment.
I'm ready to remove Exchange 2007 from SBS 2008 and DCPROMO the server. I can NOT seem to find a TechNet article that shows me how
to proceed in this kind of scenario. I am trying to use the TechNet article:
http://technet.microsoft.com/en-us/library/dd728003(v=ws.10).aspx
This article references Disabling Mailboxes, Removing OAB, Removing Public Folder Databases, then uninstalling Exchange using the Setup Wizard.
When I go to Disable Mailboxes I get the following error:
Microsoft Exchange Error
Action 'Disable' could not be performed on object 'Username (edited)'.
Username (edited)
Failed
Error:
Object cannot be saved because its ExchangeVersion property is 0.10 (14.0.100.0), which is not supported by the current version 0.1 (8.0.535.0). You will need a later version of Exchange.
OK
I really don't see why I need to Disable Mailboxes, Remove OAB and Public Folder Databases since they have been moved to 2010. I just want
to remove Exchange 2007 and DCPROMO this server (actually I just want to remove any lingering Exchange AD Objects referring to the SBS 2008 Server, using the easiest and cleanest method possible).
Can someone point me in the right direction?
Thanks!

Hi,
Based on your description, it seems that you are in a migration process (migrate SBS 2008 to Windows Server
2008 R2). Now, you want to remove Exchange Server and demote server. If anything I misunderstand, please don’t hesitate to let me know.
On current situation, please refer to following articles and check if can help you.
Transition
from Small Business Server to Standard Windows Server
Removing SBS 2008 –
Step 1: Exchange 2007
Removing SBS 2008 – Step 2:
ADCS
Removing
SBS 2008 – Step 3: remove from domain / DCPROMO
Please Note: Since the web site is not hosted by Microsoft, the link may change without notice. Microsoft
does not guarantee the accuracy of this information.
Hope this helps.
Best regards,
Justin Gu

Migration from Exchange 2007 SP3 to Exchange 2010

Hello,
We are planning a single server migration from Exchange 2007 SP3 to Exchange 2010. I'll be building the 2010 server on a 2008 R2 box. My question is, can I make the jump directly to Exchange 2010 SP3, or do I need to install exchange 2010 SP1 first
- migrate from 2007 SP3, and then install SP3 for exchange 2010 later?
Thanks,
Eric

@ Hasan
Dimdik - TAT,
That's not correct at all, you can migrate exchange server 2007 SP3 and RollUp Update 10 minimum to Exchange Server 2013 with minimum CU1.
Cheers,
Gulab Prasad,
Technology Consultant
Blog:
www.exchangeranger.com
Twitter:
LinkedIn:
Check out CodeTwo’s tools for Exchange admins
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.

I update my exchange server 2013 cu6 with exchange 2007 and my exchange 2013 db shutdown every 25 minute and recover. You have any hotfix I can use for this solution.

I update my exchange server 2013 cu6 with exchange 2007 and my exchange 2013 db shutdown every 25 minute and recover. You have any hotfix I can use for this solution.

Hi,
From your description, you have deployed Microsoft Exchange Server 2013 and Microsoft Exchange Server 2007 in a co-existence environment. After you upgrade to CU6, databases unexpectedly shut down. In your case, here is a kb for your reference.
Exchange Server 2013 databases unexpectedly fail over in a co-existence environment with Exchange Server 2007
http://support2.microsoft.com/kb/2997209
Hope this can be helpful to you.
Best regards,
Amy Wang
TechNet Community Support

Uppgrading Exchange 2007 from sp1 to sp3 on small business server 2008 sp1

Hello everyone
I know this topic has been discused many time in this froum. but i have to ask it again in my exact situation.
I have a realy unstable and unsafe server which i am planing to migrate all the apps and services to some virtual servers soon.
first migrating is Exchange. i have Exchange 2007 sp1 on my server sbs 2008. i have my DC,AD, dns, DHCP, File, etc on the same server as well . So that is way it is scary for me (as i am not really experienced) to even upgrade one service pack.
Now, i want to know if anyone did it before. What should i expect during upgrading or after that? so i can be ready for that?
which kind of backup can save me if somethings happens to my Exchange? is there any way to install the new Exchange 2007 and sp3 rollup 10 and then migrate all databases and mailboxes to that new server? if yes, how to do that?
Thanks
Nima

Hi Nima,
Ok, I know your concern. Please make sure you have read the above KB I provided before installing SP3 for Exchange 2007. What's more, you need to make sure you right mouse click and run as admin to install it.
Moreover, here is a thread about migrating Exchange 2007 SP3 to Exchange 2013 for your reference.
Migrate SBS 2008 R2 running Exchange 2007 to Windows Server 2012 Exchange 2013
http://social.technet.microsoft.com/Forums/en-US/4c9b96c2-fd5e-4fbe-8b3a-fb5b3ab29da8/migrate-sbs-2008-r2-running-exchange-2007-to-windows-server-2012-exchange-2013?forum=smallbusinessserver
Hope it helps.
Best regards,
Amy Wang
TechNet Community Support

Redirection loop detected while opening Exchange 2007 mailboxes through Exchange 2013 OWA page

Team, in our infra Exchange 2013 CU8 & Exchange 2007 SP3 RU15 running. Exchange 2013 recently deployed but while opening exchange 2007 users mailbox through 2013 OWA getting error "Redirection loop detected". Want to update you few things :
Public DNS record created as mail.myinfra.in with x.x.x.2 IP and legacy.myinfra.in with x.x.x.3 IP.
Virtual directory modified mail.myinfra.in for 2013 & legacy.myinfra.in for 2007.
All the OWA request need to pass through public DNS only no internal DNS record for OWA.
Through ISA already rule created and tested also like https://mail.myinfra.in/owa giving me 2013 OWA page & https://legacy.myinfra.in/owa giving 2007 owa page. Only problem while opening https://mail.myinfra.in/owa with 2013 mailbox id/pwd working fine
but with 2007 mailbox id/pwd giving error "Redirection loop detected".
Appreciate if you can help quickly.

Hello
tip: check iis log on both of exch servers and check owa application haven't got "HTTP redirect" enabled.
sorry my english

Failing Exchange 2007 upgrade to Exchange 20113

I have a failing Exchange 2007 SP 2 that I need to upgrade to Exchange 2013. Yes, I do have consistent mail box backups to disk (Backup Exec 2014).
I have several failed attempts on creating a VMWare 5 machine out of this EX 7 server. We are out of hard drive space and unable to do the service pack 3. The new server (EX 13) will have a 300 gig root directory and data drive of over 1 terabyte.
I am looking for suggestions for the cleanest solutions to upgrading this server to 2013 since doing a migration with coexistence has been ruled out . I work for a small company without funds to allow me to purchase some really good software to assist
with this problem. I cannot have the email server down for more than over night unless I do it over the weekend.

Hi Praxis,
Thank you for your question.
If we could not recovery Exchange 2007 from Exec2014, we suggest you perform a disaster recovery for Exchange 2007 by the following link:
https://technet.microsoft.com/en-us/library/aa998890(v=exchg.80).aspx
Then, we could follow ExchangeITPro’s advice to upgrade Exchange 2007 SP2 to Exchange 2007 SP3 CU10.
Then we could start migration by the following link:
http://blogs.technet.com/b/meamcs/archive/2013/07/25/part-1-step-by-step-exchange-2007-to-2013-migration.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

After Exchange 2007 Migration to Exchange 2010, OAB is erroring

Hello all,
I migrated from single server Exchange 2007 to single Exchange 2010 2 months ago using a co-existence environment. The 2007 server is still running, but it's not doing anything but SMTP relay, as I am waiting on Oracle admin to point their server at
my new 2010 server. Yesterday, I noticed a new mail enabled user we created was not showing up in the Address Book. He is in the Global Address list when I check it from OWA. And I can see him in my Address book if I search All Users,
instead of the Global Address List. Everytime I try to update the Offline Address Book, I get the following error
OABGen encountered error 80004005 while cleaning the offline address list public folders under /o=2007Server/cn=addrlists/cn=oabs/cn=Default Offline Address Book. Please make sure the public folder database is mounted and replicas exist of the offline
address list folders. No offline address lists have been generated. Please check the event log for more information.
- \Default Offline Address Book
There was a Public Folder on the 2007 server, but I don't think anyone was using it. All of our clients our 2007 or later. Enable Web-based distribution is enabled and Generation server is my new 2010 server. Enable public folder distribution
not enabled.
Any help would be greatly appreciated.

No, the Enable public folder check box is not ticked. However, the link you provided has led me to other clues. The author says "To locate the actual
OAB distribution point on the Client Access Server, the Outlook client will use the autodiscover service." I wonder if still having the CAS role on the old 2007 Exchange Server still installed is causing issues with Autodiscover. Below
are the results of the Test E-mail AutoConfiguration from Outlook.
The Results tab of the Test E-mail AutoConfiguration:
Autoconfiguration found the following settings:
Display Name: User1
Redirect URL: https://Exchange2010.Contoso.com/Autodiscover/Autodiscover.xml
Internal OWA URL: https://Exchange2010.Contoso.com/owa
External OWA URL: https://Exchange2007.Contoso.com/owa
Protocol: Exchange RPC
Server: Exchange2010.Contoso.com
Login Name: user1
Availability Service URL: https://Exchange2010.Contoso.com/EWS/Exchange.asmx
OOF URL: https://Exchange2010.Contoso.com/EWS/Exchange.asmx
OAB URL: https://Exchange2010.Contoso.com/OAB/43e497ff-6fc4-47f8-8e7b-fe252e84ddf6/
Unified Messaging Service URL: https://Exchange2010.Contoso.com/EWS/UM2007Legacy.asmx
Auth Package: Unspecified
Exchange Control Panel URL: https://Exchange2010.Contoso.com/ecp/
ECP Sub URL: ?p=customize/voicemail.aspx&exsvurl=1
ECP Sub URL: ?p=personalsettings/EmailSubscriptions.slab&exsvurl=1
ECP Sub URL: PersonalSettings/DeliveryReport.aspx?exsvurl=1&IsOWA=Is<IsOWA>&MsgID=<MsgID>&Mbx=<Mbx>
ECP Sub URL: ?p=organize/retentionpolicytags.slab&exsvurl=1
Protocol: Exchange HTTP
Server: Exchange2010.Contoso.com
Login Name: user1
SSL: Yes
Mutual Authentication: Yes
Availability Service URL: https://Exchange2007.Contoso.com/ews/exchange.asmx
OOF URL: https://Exchange2007.Contoso.com/ews/exchange.asmx
OAB URL: https://Exchange2010.Contoso.com/OAB/43e497ff-6fc4-47f8-8e7b-fe252e84ddf6
Unified Message Service URL: https://Exchange2007.Contoso.com/ews/UM2007Legacy.asmx
Auth Package: Basic
Certificate Principal Name: msstd:Exchange2010.Contoso.com
Exchange Control Panel URL: https://Exchange2007.Contoso.com
ECP Sub URL: ?p=customize/voicemail.aspx&exsvurl=1
ECP Sub URL: ?p=personalsettings/EmailSubscriptions.slab&exsvurl=1
ECP Sub URL: Personalsettings/DeliveryReport.aspx?exsvurl=1&IsOWA=<IsOWA>&MsgID=<MsgID>&Mbx=<Mbx>
ECP Sub URL: ?p=organize/retentionpolicytags.slab&exsvurl=1
The Log tab of the Test E-mail AutoConfiguration:
[email protected]
Attempting URL https://Exchange2007.Contoso.com/Autodiscover/Autodiscover.xml found through SCP
Autodiscover to https://Exchange2007.Contoso.com/Autodiscover/Autodiscover.sml starting
GetLastError=0; httpStatus=401.
GetLastError=0; httpStatus=302.
Autodiscover to https://Exchange2007.Contoso.com/Autodiscover/Autodiscover.xml Failed (0x800C8204)
Autodiscover URL redirection to https://Exchange2010.Contoso.com/Autodiscover/Autodiscover.xml
Autodiscover to https://Exchange2010.Contoso.com/Autodiscover/Autodiscover.xml starting
GetLastError=0; httpsStatus=200
Autodiscover to https://carus.Contoso.com/Autodiscover/Autodiscover.xml Succeeded (0x00000000)
The XML tab of the Test E-mail AutoConfiguration:
<?xml version="1.0" encoding="utf-8"?>
<Autodiscover xmlns="http://schemas.microsoft.com/exchange/autodiscover/responseschema/2006">
<Response xmlns="http://schemas.microsoft.com/exchange/autodiscover/outlook/responseschema/2006a">
<User>
<DisplayName>Chad Wingo</DisplayName>
<LegacyDN>/o=Exchange2007/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=cwingo</LegacyDN>
<AutoDiscoverSMTPAddress>[email protected]</AutoDiscoverSMTPAddress>
<DeploymentId>c389bc85-adbe-4481-aa25-1fbc209a6fde</DeploymentId>
</User>
<Account>
<AccountType>email</AccountType>
<Action>settings</Action>
<Protocol>
<Type>EXCH</Type>
<Server>Exchange2010.contoso.com</Server>
<ServerDN>/o=Exchange2007/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=Exchange2010</ServerDN>
<ServerVersion>738280F7</ServerVersion>
<MdbDN>/o=Exchange2007/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=Exchange2010/cn=Microsoft Private MDB</MdbDN>
<PublicFolderServer>Exchange2010.contoso.com</PublicFolderServer>
<AD>DATA.domainskc.com</AD>
<ASUrl>https://Exchange2010.contoso.com/EWS/Exchange.asmx</ASUrl>
<EwsUrl>https://Exchange2010.contoso.com/EWS/Exchange.asmx</EwsUrl>
<EcpUrl>https://Exchange2010.contoso.com/ecp/</EcpUrl>
<EcpUrl-um>?p=customize/voicemail.aspx&exsvurl=1</EcpUrl-um>
<EcpUrl-aggr>?p=personalsettings/EmailSubscriptions.slab&exsvurl=1</EcpUrl-aggr>
<EcpUrl-mt>PersonalSettings/DeliveryReport.aspx?exsvurl=1&IsOWA=<IsOWA>&MsgID=<MsgID>&Mbx=<Mbx></EcpUrl-mt>
<EcpUrl-ret>?p=organize/retentionpolicytags.slab&exsvurl=1</EcpUrl-ret>
<OOFUrl>https://Exchange2010.contoso.com/EWS/Exchange.asmx</OOFUrl>
<UMUrl>https://Exchange2010.contoso.com/EWS/UM2007Legacy.asmx</UMUrl>
<OABUrl>http://Exchange2010.contoso.com/OAB/43e497ff-6fc4-47f8-8e7b-fe252e84ddf6/</OABUrl>
</Protocol>
<Protocol>
<Type>EXPR</Type>
<Server>Exchange2010.contoso.com</Server>
<SSL>On</SSL>
<AuthPackage>Basic</AuthPackage>
<ASUrl>https://Exchange2007.contoso.com/ews/exchange.asmx</ASUrl>
<EwsUrl>https://Exchange2007.contoso.com/ews/exchange.asmx</EwsUrl>
<EcpUrl>https://Exchange2007.contoso.com/ecp/</EcpUrl>
<EcpUrl-um>?p=customize/voicemail.aspx&exsvurl=1</EcpUrl-um>
<EcpUrl-aggr>?p=personalsettings/EmailSubscriptions.slab&exsvurl=1</EcpUrl-aggr>
<EcpUrl-mt>PersonalSettings/DeliveryReport.aspx?exsvurl=1&IsOWA=<IsOWA>&MsgID=<MsgID>&Mbx=<Mbx></EcpUrl-mt>
<EcpUrl-ret>?p=organize/retentionpolicytags.slab&exsvurl=1</EcpUrl-ret>
<OOFUrl>https://Exchange2007.contoso.com/ews/exchange.asmx</OOFUrl>
<UMUrl>https://Exchange2007.contoso.com/ews/UM2007Legacy.asmx</UMUrl>
<OABUrl>https://Exchange2010.contoso.com/OAB/43e497ff-6fc4-47f8-8e7b-fe252e84ddf6/</OABUrl>
</Protocol>
<Protocol>
<Type>WEB</Type>
<Internal>
<OWAUrl AuthenticationMethod="Basic, Fba">https://Exchange2010.contoso.com/owa/</OWAUrl>
<Protocol>
<Type>EXCH</Type>
<ASUrl>https://Exchange2010.contoso.com/EWS/Exchange.asmx</ASUrl>
</Protocol>
</Internal>
<External>
<OWAUrl AuthenticationMethod="Fba">https://Exchange2007.contoso.com/owa/</OWAUrl>
<Protocol>
<Type>EXPR</Type>
<ASUrl>https://Exchange2007.contoso.com/ews/exchange.asmx</ASUrl>
</Protocol>
</External>
</Protocol>
</Account>
</Response>
</Autodiscover>
Unified Messaging role has not been installed on 2010 Exchange Server yet and UM has been uninstalled on 2007 Exchange Server. The URLs are just left in IIS I'm guessing.
I have also noticed that this directory has not updated since the 11/12/2013 C:\Program Files\Microsoft\Exchange Server\V14\ExchangeOAB. While this directory continues to update C:\Program Files\Microsoft\Exchange Server\V14\ClientAccess\OAB

Use Current Exchange Rate from the Exchange Rate Table itu00B4s not working

Hi Experts:
Working with manager user, Iu2019m trying to create a Goods Receipt PO through the Draw Document Wizard, but the option u201CUse Current Exchange Rate from the Exchange Rate Tableu201D it is not working, it does not bring me the USD exchange rate of today defined in the table; it brings the USD exchange rate from the base document (AP Reserve Invoice), and Iu2019m not allowed to change it. What should I do?. We are working wih SAP Business One SP01 PL06. Thanks
CLAUDIA

Hi,
There is a SAP Note related to your issue, have a look at this.
[http://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/oss_notes/sdn_oss_sbo_adm/~form/handler%7b5f4150503d3030323030363832353030303030303031393732265f4556454e543d444953504c4159265f4e4e554d3d373033303238%7d]
...For companies using the Continous Stock System feature, there are three additional scenarios in which the row Exchange Rate will be copied from the base document regardless of the calculation method chosen in the 'Draw Document Wizard':
a) Goods Receipt PO -> Goods Return.
b) Goods Return -> Goods Receipt PO.
c) AP Reserve Invoice -> Goods Receipt PO.
Hope this helps,
Son.

Issue removing Exchange 2007 after migration to 2013

After migrating relatively successfully from Exchange 2007 to 2013, I am in the process of trying to decommission and uninstall 2007 from the servers. Through this process I have been following a guide found
here. Our old 2007 servers have been off for over two weeks and it seems like a good time to remove them and reclaim some space. I removed the old OAB and Mailbox DB, however when I attempted to remove the Public Folders so I could take the PF DB out the
following error appeared.
Get-PublicFolder : There is no existing PublicFolder that matches the following Identity: '\'.
I know that there are Public Folders existing as I can see them when I run Get-PublicFolderStatistics:
I've been back and forth across the forums and web and haven't been able to find a solution to this. Ultimately we never have and are not interested in using public folders but they were originally configured when we had a contractor move us from 2003 >
2007 several years ago. What I would like is to remove all traces of this garbage and just be able to uninstall/delete the old servers and move on with life.
Any help is greatly appreciated. Thank you in advance.
Jon Howard

Hi,
Have you tried to use Exfolders tool to remove PF?
More details about exfolders tool refer to the following article:
http://gallery.technet.microsoft.com/office/Exchange-2010-SP1-ExFolders-e6bfd405
Thanks.
Niko Cheng
TechNet Community Support

Remove various accepted domains (exchange 2007) from a list file via powershell

hello!
i'm a newbie with powershell and i'm trying to find if is it possible to remove a lot of exchange 2007 accepted domains from a csv file using powershell.
I want to delete accepted domains contained in a csv, it has only domains name and powershell requires the name , that is different from the domain.
example of accepted domain in my organization:
Name DomainName DomainType Default
Domain0001
domain1.com Authoritative False
Domain0002 hello1.com
Authoritative False
I've only a csv with domains name:
domain.csv:
Domain
domain1.com
hello1.com
Deleting an accepted domain via powershell requires the name so I need to extract first the name of , i've tried with this command and it works:
Get-AcceptedDomain | Where{$_.DomainName -eq 'domain1.com'}
This works only for 1 domain, I've a lot of domains to delete so it's inviable
Now, i'm trying to launch this command without success:
import-csv domain.csv | foreach {Get-AcceptedDomain | Where{$_.DomainName -eq '$_.Domain'}}
Probably there is a syntax error, or maybe I just can't do it.
Any help?
Many thanks in advance!!

Don't know what to tell you, then. If I create a test file with that data, the Import-CSV works for me:
Domain
3414257440.domain.com
domain1.domain.com
'@ | set-content c:\testfiles\domain.csv
$DomainNames =
Import-CSV 'c:\testfiles\domain.csv' |
Select -ExpandProperty Domain
$DomainNames
3414257440.domain.com
domain1.domain.com
[string](0..33|%{[char][int](46+("686552495351636652556262185355647068516270555358646562655775 0645570").substring(($_*2),2))})-replace " "

Removing Exchange 2007 from SBS 2008 after Migrating to Office 365 Mid Sized with DirSync and SSO

We have recently completed off a Migration of Exchange 2007 to Office 365 Mid Sized platform.
I now need to decomission the old SBS 2008 server as they have moved to a Windows Server 2012 R2 server setup for DC, File and print and application servers.
I need to know what are the ramifications of removing the Exchange 2007 server from the SBS 2008 server and will this remove the LegacyDN details from AD and cause any issues with internal emails between users using Outlook linked through to Office365.
I understand that after removing Exchange 2007 there will be no friendly GUI to update and maintain proxyAddress, targetAddress and LegacyDN addresses, I am comfortable doing this in ADSI edit or with a script.
Will this remove the x500 addresses relating to the on premise Exchange Orgainisation and just leave behind the x500 addresses for Exchange Labs which I assume is the x500 addresses for the Azure AD intergration for Office365.

Hi ,
Thank you for posting your issue in the forum.
I am trying to involve someone familiar with this topic to further look at this issue. There might be some time delay. Appreciate your patience.
Thank you for your understanding and support.
Best Regards,
Andy Qi
Andy Qi
TechNet Community Support

Remove and reconnect Exchange 2007 from Domain

I have an Exchange 2007 server running on a Windows 2008 server. For some reason the server will not run group policies. It hangs for a very long time when logging in on "Applying Group Policy Printers Policy" And also won't shutdown hanging on
"Applying Group Policy". The only wany I can shut it down is to manually power off the server.
I also ran the Group Policy Results Wizard and get a timeout when I run it against the Exchange server. DNS is working fine. I have tested all of the other servers using the same DNS and they all work fine. The server in question has been having other problems
for a while now, but I have been able to resolve all the other problems except for this one. The server is old and will be replaced this year, but I have to make it work until I get a new server. Maybe 6 months or so.
I am thinking of removing the server from the domain and then joining the domain again. I'm not sure that will fix it, but I hope it will. The only thing I'm worried about is getting the Exchange database and server running again after I remove and rejoin
it to the domain. I have heard I can shutdown and disable all Exchange services, then remove the server from the domain and rejoin. But I have never done that and want to be sure it can be done without destroying connectivity to AD and the users. So, is this
possible?
Any help is appreciated.
Doug

You should try fixing the AD issues instead of removing the Exchange server from the domain. You should start by analyzing what was done to cause the issue in the first place and remedy that.
Here is a bit similar concern that has been discussed earlier and has been suggested some good steps to sort-out the issue :
http://community.spiceworks.com/topic/267400-removing-and-re-joining-an-e2k7-server-to-the-domain
Moreover, when need to recover mailbox items back into previous format, you may also give shot to this automated solution (http://www.exchangeserverrecovery.com/) that could be a good approach while dealing
in such crucial circumstance.

Remove Exchange 2007 from AD (manually)

In the lab I had Exchange 2007 running and someone pulled my VM. It's not the end of the world because I'm done with what I was doing in 2007 however I've got other things running in the lab and I'd rather not rebuild the domain.
Does anyone know what the process would be to clean up AD (remove the Exchange org) without having the Exchange server to do an uninstall on? Can I Install the Exchange admin console on another box and than remove the mail attributes from the accounts that has them and just remove the Exchange Systems Object container in AD or is there more?
Erik

I did run into one problem while trying to install RTM:
Organization Preparation
Failed
Error:
The well-known object entry B:32:A7D2016C83F003458132789EEB127B84:CN=Exchange Servers\0ADEL:e60b372e-cd97-4fc2-bc8f-907728f0bc8d,CN=Deleted Objects,DC=domain,DC=com of the otherWellKnownObjects attribute on container object CN=Configuration,DC=domain,DC=com
points to an invalid DN or a deleted object. Please remove the entry and rerun the task.
I was able to resolve the issue by launching adsiedit.msc (part of the support tools) and going to the Configuration partion and bringng up the properties for Configuration,DC=domain,DC=com
I edited the "othereWellKnownObjects" attribute to be "not set" (which it should be) by leaving it blank and clicking "add" (adding nothing) than applying the changes and re-running setup.
Kudos to this thread for the fix:
http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=839779&SiteID=17
Cheers,
Erik
otherWellKnownObjects is a multi-valued object. You need to remove the bad value, NOT ALL OF THEM!!
Mike Crowley | MVP
My Blog --
Planet Technologies

Exchange 2007 migrate to Exchange 2013

Dear MS Support,
I did migrate Exchange 2007 to Exchange 2013
The install complete, the exchange 2007 and 2013 can work together successful
DAG has created and work fine
Below is capture on exchange group after migrate
The exchange 2007 work fine with outlook anywhere, all the users can connected and send and receive mail in 5 year
The cerificate enroll with
Alternative Names: mail.biendongpoc.vn
The autodiscover on exchange 2007:
[PS] C:\Windows\system32>Get-ClientAccessServer | ft Identity,*uri* -AutoSize
Creating a new session for implicit remoting of "Get-ClientAccessServer" command...
Identity AutoDiscoverServiceInternalUri
BDPOC-SERVER1 https://mail.biendongpoc.vn/Autodiscover/Autodiscover.xml
I have created new certificate for Two exchange 2013
The certificate enroll with
Alternative Names: cas.biendongpoc.vn
I have create cname cas point to dag on DNS server
I have create A record autodiscover.biendongpoc.vn point to IP of dag.biendongpoc.vn
I did migrate mailbox from exchange 2007 to exchange 2013, the migrate successful , the outlook can
connected to Exchange 2013 and working perfectly
Our problem, the account exchange 2007 work not stable ,
sometime it connect to mail.abc.com, sometime it connect to cas.abc.com
If the outlook connect to cas.biendongpoc.vn, the request put password and i can't connect to exchange 2007, if outlook connect to mail.biendongpoc.vn i can connect
It is not stable for current exchange 2007
Anyone who can help me ?
Thanks

Hi
huynhtrongnhatminh,
I suggest you please go through this article.
http://blogs.technet.com/b/exchange/archive/2014/03/12/client-connectivity-in-an-exchange-2013-coexistence-environment.aspx
Please check this for step by step guide.
http://blogs.technet.com/b/meamcs/archive/2013/07/25/part-1-step-by-step-exchange-2007-to-2013-migration.aspx
Please point your autodiscover and commonname to Exchange2013 CAS
Please configure your URLs. There is no CAS array in Exchange2013 but the concept of single name space remains.
You need to have an A record (e.g. legacy.domain.com) in yout external DNS and add that name (legacy.domain.com) in your certificate for exchange 2007 users to have access externally.
Configure your commonname URLs in Exchange2013. Point commonname and autodiscover to exchange2013 in both external and internal DNS servers
Configure URLshttp://www.mustbegeek.com/configure-external-and-internal-url-in-exchange-2013/
No CASARRAY in 2013http://exchangeserverpro.com/exchange-2013-client-access-server-high-availability/
Please configure splitdns or pinpoint DNS in your internal DNS server if not configured
http://exchange.sembee.mobi/network/split-dns.asp
Thanks, MAS
Please mark as helpful if you find my comment helpful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you.

Remove Exchange 2007 from an Exchange 2013 coexistence.

Similar Messages

Maybe you are looking for