Decommission Exchange Server 2003 after migration to Office 365

Hello,
We recently made the switch from our Exchange 2003 server to Office 365 with a Directory Sync Server.
Right now both the server is acting as a domain controller and the legacy exchange server. What I would like to do is keep the server as a domain controller and decommission the exchange services.
What do I need to do in order to properly decommission the exchange services without any loss of data/functionality with the directory sync server?
I previously posted this thread http://community.office365.com/en-us/forums/148/p/231357/719776.aspx#719776 but was redirected here.

Directory sync is done through your domain controller, not your Exchange server. True, your server serves both roles, but the Exchange services are not required for DirSync. What I would do, though, if I were you, would be to create a temporary
domain controller in your organization and point your DirSync to it. If that doesn't work, you know there is something on your current system that is required for the DirSync and there is possibly some reliance on Exchange. I'd then remove Exchange
from your server (I'd be sorely tempted to rebuild the server, using the same name and IP as before, just to be sure I started with a clean slate) and re-home the DirSync to it.
Good luck ... HTH.

Similar Messages

Decommission Exchange Server 2013 after migration to Office365

We had an on-premises Exchange Server 2013 failure with multiple hard disk failures.
Since we already had an Office365 E3 plan, we decided to bite the bullet and move to Exchange Online. Since we did not have ADFS or Dirsync yet and time was against us to get email flowing as quickly as possible, we imported all the users into Office365,
i.e. disconnected from our AD.
We then setup all their Outlook 2013 profiles with Office365 and imported their mailboxes from PSTs, so they are all up and running on Office365 now (still disconnected from our AD).
I would like to decommission our on-premises Exchange 2013, since our current setup is not very common, i.e. Office365 mailboxes which are not linked to our AD.
I would like some pointers and guidance how to go about this.
Thanks
Chris

Hi
As per your description i can see that your on-premise exchange servers are running with no users, no services integrated with Office 365 users and no adfs dirsync
So in this scenario you can do a normal uninstallation of Exchange 2013 servers
Before uninstalling a Exchange 2013 Server,
Make sure all the console related to Exchange server are closed
Mailbox databases on that server has to be removed
Uninstall Exchange server from control panel
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)

Decommissioning Exchange Server 2007 after staged migration to Exchange Online

Hi there,
I have recently migrated all our on-premise Exchange 2007 user mailboxes to Exchange Online/Office 365 using a staged migration running DIRSYNC (Windows Azure Directory Services Directory Synchronization Tool). Now I would like to remove the old on-premise
Exchange server but I am not sure if that would break things.
Also with Disync enabled you cannot manage some mailbox properties in Exchange Online, it needs to be done with AD, right? If that is the case is it a good idea to have Exchange 2010/2013 Management Tools installed to manage the mailboxes?
Thank you,
Pieter

Hello,
Windows Azure Directory Services Directory Synchronization Tool is used to synchronize on-premises directory objects(users, groups, contacts) to cloud. If you want to remove the old on-premise Exchange server, you need to make sure you have moved mailboxes
to o365 successfully, the mail flow is ok and the user can access their mailboxes.
Here is an article for your reference.
http://technet.microsoft.com/en-us/library/jj898486(v=exchg.150).aspx
Not all operations for mailbox can be done via AD, so I recommend you install Exchange Management Tools to manage the mailboxes.
If you have any feedback on our support, please click here
Cara Chen
TechNet Community Support

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

Summary Report after migrating to Office 365

Hi all,
I just successfully performed a cutover migration off a SBS 2011 Server.
Admins are missing the Daily/Weekly Status report email generated by SBS. The report still goes to the on-premises mailbox. I also unticked the users from the list and created new emails as "external" recipients but did not work.
The DNS is authoritative for contoso.local. I don't know how to create a MX record for contoso.com within that zone.
I think it may be an attribute in AD that needs to be changed.
Could you guys provide help with this?
Regards,
Frank

Hi Frank,
On current situation, please refer to following thread and check if can help you.
Change
email address of SBSMonAcct on SBS 2011
Meanwhile, please refer to the “Completion of the Migration”
section in following article.
Step-By-Step:
Migrating from Exchange 2007 to Office 365
If any update, please feel free to let me know.
Hope this helps.
Best regards,
Justin Gu

Emails not being kept on server anymore after installation of office 365

since installing office 365 my emailsare no longer kept on the server The settings om outlook havn't changed and they should stay there for weeks Any suggestion ?

I'd check to make sure it's not set to download/delete email from the server when fetching it, just in case.

[Exchange-Online][EWS][EWS-XML] Exchange server version "V2_22" returned for Office 365 breaks pattern - consequences?

I just notice that talking to Office365 Exchange Web Services at https://outlook.office365.com/ews/exchange.asmx I get this in my SOAP response header:
<Envelope>
<Header>
    <ServerVersionInfo MajorVersion="15" MinorVersion="0" MajorBuildNumber="1049" MinorBuildNumber="23" Version="V2_22"/>
</Header>
This means that the Version 'schema version' property (http://msdn.microsoft.com/en-us/library/exchangewebservices.serverversioninfo.version%28v=exchg.150%29.aspx) now breaks the pattern of versions that we had earlier: Exchange2007, Exchange2007_SP1, Exchange2010,
Exchange2010_SP1, Exchange2010_SP2, Exchange2013
In the schema files I found through Google (searching for <xs:simpleType name="ExchangeVersionType">) I could not find anything later than <xs:enumeration value="Exchange2013"/> (e.g. at http://msdn.microsoft.com/en-us/library/ee237685%28v=exchg.80%29.aspx)
If I do a SOAP request with this "V2_22" string, I still get valid answers.
<soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:typ="http://schemas.microsoft.com/exchange/services/2006/types"
xmlns:mes="http://schemas.microsoft.com/exchange/services/2006/messages">
   <soapenv:Header>
      <typ:RequestServerVersion Version="V2_22"/>
   </soapenv:Header>
But it now looks as if the returned Version is no longer a reliable way to determine the Exchange server version. If V2_22 is not documented anywhere, who says it will not suddenly change to V2_23 tomorrow?
Question: Does this mean I will now have to change my version detection code to look at MajorVersion and then maintain a cross reference between MajorVersion and ExchangeVersionType **myself**? That is horrible: another dependency to maintain
is another potential code break.
As an aside: Note that the "Exchange Server Updates: build numbers and release dates" at http://technet.microsoft.com/en-us/library/hh135098%28v=exchg.150%29.aspx is no longer up to date, it does not mention the 15.0.1049.23 that my XML just returned

What really matters in EWS is the SchemaVersion as that will tell you what operations you can and can't use. From 2010 on you can use AutoDiscover to find what SchemaVersions are supported which is the best way to do version detection. eg
AutodiscoverService adAutoDiscoverService = new AutodiscoverService(ExchangeVersion.Exchange2010);
adAutoDiscoverService.Credentials = ncCred;
adAutoDiscoverService.EnableScpLookup = false;
adAutoDiscoverService.RedirectionUrlValidationCallback = adAutoDiscoCallBack;
adAutoDiscoverService.PreAuthenticate = true;
GetUserSettingsResponse adResponse = adAutoDiscoverService.GetUserSettings("[email protected]", (new UserSettingName[1] { UserSettingName.EwsSupportedSchemas }));
if (adResponse.Settings.Count >= 1)
String schemas = (String)adResponse.Settings[UserSettingName.EwsSupportedSchemas];
I would be careful using the Major build going forward if you have a look at the requests in OWA in Office365 you'll see they are using version 16 in cookies etc
Cheers
Glen

Disabling AD Autodiscover while migrating to Office 365

I'm in the middle of migrating from Exchange 2007 to Office 365. I can autodiscover to the Office 365 service successfully in every instance except when I'm on a PC joined to the AD domain and the domain is accessible. I have added a registry
key on my test PC that keeps it from using the AD SCP to autodiscover but it still gets my Exchange server mailbox instead of the Office 365 mailbox even without using SCP.
If I remove the PC from the domain, it works both locally and remotely so I know all my other settings are okay, it's only giving me this issue when it's a domain member and is running local to the AD domain. Tried a laptop, joined it to the domain,
took it home and let it autoconfigure, worked great. Same laptop, when local to the domain, tries to autoconfigure using the local Exchange server settings.
I'd like to give my users back their Outlook (rather than OWA) after I migrate them. How do I prevent my locally deployed, AD-joined computers from getting autodiscover info from my local Exchange CAS server while I complete my migration to Office
365?

Hi,
I ran into the same problem. I came up with a work around but I’m not sure this is the correct approach.
First, with Outlook 2010 already installed I had to run the Set up and configure your Office desktop apps from Office 365. I’m not sure of all the configuration changes this makes but I know after you install it that it will allow
you to change the username field when trying to authenticate to Office 365 (will get back to that in a minute)
Second, from my domain joined computer where outlook was connected to my on premise exchange 2007 server mailbox, I setup a new outlook account, either from the control panel mail icon, or from within outlook (both worked) Note; doing from within your already
existing configured outlook allowed me to migrate my email from on-premise to office 365.
From Control Panel/Mail , I created profile name “Office 365”
In the next window it then auto discovered my on premise exchange mailbox email address
[email protected] (which in my case is the same as the office 365 email address
[email protected] )
I replaced the email address with the secondary domain email address that Microsoft office 365 created
[email protected]. I did not put in password at this point and clicked next. It then searched for mailbox, a windows security mail application windows will pop up.
This is where I then replace username
[email protected] with
[email protected] and put in my office 365 account password.
As mentioned above when I said I would get back to that in a minute, if you don’t run the
Set up and configure your Office desktop apps from Office 365. You will not have the option to replace the username from the windows security mail application windows.
It finishes configuration and you’re now connected.
Worth mentioning though that I’m still having some funky mail delivery issues with on-premise users with my imported “contacts” in outlook. The contacts work from office 365 web apps, but not from outlook. If I type the address everything
is fine, but using contacts or replying to on-premise users is giving me some grief. It’s a contact issue but I’m still unable to resolve it.

Winmail.dat attachments from Exchange 2013 on premi and Hosted Office 365 set up.

Hello TechNet,
I have an on going situation with winmail.dat attachments. I currently have a ticket open with Microsoft, but I want to see if anyone has personal experience with this. Here is the rundown.
We have migrated from an Exchange 2007 server to Exchange 2013 for the migration to Office 365. We also have a hosted Office 365 server with half of our mailboxes in the cloud and half of them on the Exchange 2013 on premise server.
The current settings for TNEFEnabled:
On Premise: False
Hosted: False
Whenever a internal email with a calendar invite(exchange calendar, go to meeting) goes out to any external domain the recipients receive winmail.dat.
When settings for TNEFEnabled On Premise and Hosted are set to true both calendar invites and PDF, Excel attachments etc the recipients receive winmail.dat.
When speaking with Microsoft about this issue. The representative was watching me through a LogMeIn session as I set both TNEFEnabled false on both on Premise and Hosted.
This is really frustrating as many employees depend on this to be fully functional, and to be honest am tired of dealing with this.
I need help.
-Ben

I am having the same issue.
Luckily I have only migrated my own mailbox to office365.
Tried both true and false TNEFEnabled on both onpremise and office365 via powershell and confirmed that both have been applied.
If I send the email as a plain text then the attachment works ok. If I send it as HTML then I get winmail.dat.
The above KB doesnt really help me, sending plain text emails is like going back to the dark ages!
I am sending from outlook to outlook (I send from my external email address, to my work email address and visa-versa)
If someone with an onpremise mailbox sends me an email, the attachment works ok.
If someone sends me an attachment via hotmail, the attachment works ok.
It seems to only effect emails I send to myself through outlook, i am sending it through a POP3 account to our onpremise exchange 2010 which forwards the email to office365

Exchange server 2003 restartштп, after DC shutdown

We have Exchange server 2003 and two DC on server 2008 r2 in organization.
When main DC is shutting down, exchange server restarting. There are no scrips\GPO that orders to restart Exchange after shutting down the DC.
What can cause this occurrence? How can I fix it?

Hello,
to work correct with Windows server 2008 r2 DCs it is important that Exchange 2003 SP2 is installed.
Beside this you may create an additional GC in the ESM Recipient update service fo the second GC, so the connection is still available.
We are also running Exchange 2003 with multiple Windows server 2008 R2 machine without any problems.
Best regards
Meinolf Weber
MVP, MCP, MCTS
Microsoft MVP - Directory Services
My Blog: http://msmvps.com/blogs/mweber/
Disclaimer: This posting is provided AS IS with no warranties or guarantees and confers no rights.

Migration Of Exchange Server 2003

Good Day ,
I need to Upgrade Exchange server 2003 to Exchange Server 2010 , I read a lot of documents but realy I m confused :
I have DC in windows 2008R2 and I have exchange 2003( vesrion 6.5 Built 7638:2 service pack 2) in windows 2003 R2 .
I m worry to fail in the Upgrade , can you please advise me to do the upgrade in good way .I will be thankful .
All The Best
e

What are you worried about?
Cheers,
Gulab Prasad
Technology Consultant
Blog:
http://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.

Upgrading Exchange Server 2003 to 2010 to 2013 is worth???

Hello there, I am planning to upgrade about 30 users from exchange server 2003 to 2010 and finally to 2013. Is it worth to upgrade in this way because this steps are hard and very time consuming. What if, if I just copy all the user mailboxes directly to
exchange server 2013 and configure 2013 as a new exchange server and decommission old exchange server 2003?
How to copy user mailboxes to fresh exchange server 2013?
Please help me out.
Thankx

Yes, Export the PST from User Mailbox and Import it into Exchange 2013 Mailbox. But the problem is, you can't install Exchange 2013 in your current Exchange 2003 environment.
Only option is to install Exchange 2010 first and migrate all the users to Exchange 2010. Also Replicate the Public Folders too(If you are using)
Decommission Exchange 2003 entirely. Install Exchange 2013 SP1 and Migrate the User to Exchange 2013.
Cheers,
Gulab Prasad
Technology Consultant
Blog:
http://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.

Exchange server 2003 public folders

Hi Microsoft,
I am trying to decommission an Exchange 2003 server. It has public folders on it. How do I tell if they are the master replica?
Kind Regards,
Jerome Green

as long as you don't remove anything you will be save.
check these articles
http://www.petenetlive.com/KB/Article/0000426.htm
http://www.msexchange.org/articles-tutorials/exchange-server-2003/migration-deployment/PFMIGRATE.html
http://blogs.technet.com/b/agobbi/archive/2010/08/04/how-to-move-public-folder-from-exchange-2003-to-exchagne-2010.aspx
http://careexchange.in/moving-public-folders-from-exchange-2003-to-exchange-2010/
hope this will help -
Where Technology Meets Talent

A problem with Win 7 Pro, Outlook Web Access based on Exchange Server 2003, and two different domains

Dear Microsoft Support,
As mentioned in the title,
I have two domains. One is Domain A at HQ. The other one is Domain A at branch office. A laptop having Win 7 Pro OS is a client of Domain A. The Domain A has Exchange Server 2003. Users of Domain B get connected to Exchange Server for email services. In
all clients of the Domain B, IP address of the email server added in C:\Windows\System 32\drivers\etc\host file.
Whereas in the clients of Domain A it was not done, because all the servers including the email server belong to the Domain A.
Now, a user with Domain A's client (it is a laptop) came to Branch office and wanted to access the Outlook (using Outlook Web Access). since there is no IP address added in the Host file of the laptop, connectivity to email is not possible. When I try to
add the IP address, I was not able to do so due to Domain A's security reasons.
So, let me know, is there a way out to add the IP address in the host file of the Domain A's client.
Thanks in advance.
Ravi Sekhar Modukuru

I would suggest adding the mailserver address in Domain B's DNS. Would that be possible?
I agree. The correct solution in this case (since it appears you already have a two-way Domain Trust in place) is to properly configure DNS in Domain 'B' to be a secondary of Domain 'A' and completely eliminate the need to maintain the HOSTS file.
Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
SolarWinds Head Geek
Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
http://www.solarwinds.com/gotmicrosoft
The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

Portal integration with Exchange server 2003 issues.

Hello,
We are using NW04s EP 7.0 SP16 and Exchange server 2003. We are trying to perform OWA and Groupware integration. Both the servers are in the same domain.
I have followed all the steps in the notes and documents available there in SDN. There are few issues:
1) The latest KerbMap filter has been configured in Exchange backend server. SAP note 785343 says that the exchange frontend server needs to be configured for anonymous authentication to enable pass-through authentication. But doing this breaks the form based authentication in exchange server, and it also poses security risk when the backend exchange server is behind the firewall. How do we enable pass-through authentication so that the exchange frontend passes the mysapsso2 cookie to the exchange backend server?
2) When I try to create an appointment or try to view the appointments, it gives an error message saying " No logon data found for system Exchange". The Exchange system has been configured for SAP Logon Ticket, and the user mapping fields were left empty. Why should it prompt for user mapping when the logon method is "SAP Logon Ticket"?
There are many documents out there, but none is the latest with clear steps. Can anyone point me in the right direction please?
Thanks,
~Yasin

As far as I remember, when Exchange 2003 is installed on a Domain Controller, it uses the local DC as a GC. You need to set back the 2003 DC as GC and restart it.
I believe, you are aware that demoting/promoting a DC with Exchange server on it is not supported by MS. The best approach is to:
Introduce an Exchange 2010 member server
Move all resources from Exchange 2003 to Exchange 2010
Decommission Exchange 2003
Demote the 2003 DC
Step by Step Screencasts and Video Tutorials

Decommission Exchange Server 2003 after migration to Office 365

Similar Messages

Maybe you are looking for