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)

Similar Messages

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.

Cannot Access EAC/ECP on exchange server 2013 after installation

Hi,
I can not Cannot Access EAC/ECP on exchange server 2013 after installation . Error 404.4 code 0x80070002
Help!
Thanks,

Hi Florin
Did you try accessing EAC by using below link
https://<Exchange_2013_CAS_FQDN>/ecp?ExchClientVer=15
Please access EAC via Internal URL: https://<CASServerName>/ecp
Finally ensure that you have logged in as administrator as well as this might be problem as well
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

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

Exchange Server 2013: no send/receive after failed CU1- CU2 and machine restore

Hi!
For several reasons, I decided to fully restore my Exchange Server 2013 machine today.
The machine is virtualized on Hyper-V.
I rebooted the server and recovered from backup and Exchange seems to be working fine. However, I cannot receive or send mail. If I try to send a message it goes to the "drafts" folder. OWA and EMC is working. I can not send mail between interna mailboxes
either. Outlook says disconnected.
When running the Exhchange Connectivity Analyzer, I get the following:
- Receive: Connection was successful but no banner was received.
- Send: Successfull. However when trying to send mail to external mailbox it does not reach that mailbox.
Mailflow was working perfectly at the time of the backup.
Help is much appreciated!
UPDATE 1: When telnet on local server i get SMTP banner. But not on other computers in same subnet.

OK. After fiddeling around in ADSIedit and trying to rebuild my Exchange environment I ended ut breaking it completely.
I then restored both my DC (Exchange schema CU2) and my EX (Exchange schema CU1). Scema Versions where the inconsistent as stated.
Then I uninstalled the KB2874216 successfully. After that i tried to Upgrade Exchange to CU2. The Upgrade failed at Mailbox Role: Mailbox Service With error Message:
The following error was generated when "$error.Clear();
          if (($RoleIsDatacenter -ne $true) -and ($RoleIsDatacenterDedicated -ne $true))
            if (test-ExchangeServersWriteAccess -DomainController $RoleDomainController -ErrorAction SilentlyContinue)
              $sysMbx = $null;
              $name = "SystemMailbox{e0dc1c29-89c3-4034-b678-e6c29d823ed9}";
              $dispname = "Microsoft Exchange";
              $mbxs = @( get-mailbox -arbitration -Filter {name -eq $name} -IgnoreDefaultScope -resultSize 1 );
              if ( $mbxs.length -eq 0)
                $dbs = @(get-MailboxDatabase -Server:$RoleFqdnOrName -DomainController $RoleDomainController);
                if ($dbs.Length -ne 0)
                  $arbUsers = @(get-user -Filter {name -eq $name} -IgnoreDefaultScope -ResultSize 1);
                  if ($arbUsers.Length -ne 0)
                    $sysMbx = enable-mailbox -Arbitration -identity $arbUsers[0] -DisplayName $dispname -database $dbs[0].Identity;
              else
                if ($mbxs[0].DisplayName -ne $dispname )
                   set-mailbox -Arbitration -identity $mbxs[0] -DisplayName $dispname -Force;
                $sysMbx = $mbxs[0];
              # Set the Organization Capabilities needed for this mailbox
              if ($sysMbx -ne $null)
                  Write-ExchangeSetupLog -Info ("Setting mailbox properties.");
                  set-mailbox -Arbitration -identity $sysMbx -UMDataStorage:$true -Force;
                  # No RetentionPolicy assigned to E-Discovery arbitration mailbox currently, we need to set it here.
                  # This can be remove after BUG(O15#2555914) is fixed.
                  if ($sysMbx.RetentionPolicy -eq $null )
                     $arbitrationRetentionPolicy = @(Get-RetentionPolicy -DomainController $RoleDomainController | where {$_.Name -eq 'ArbitrationMailbox'});
                     set-mailbox -Arbitration -identity $sysMbx -RetentionPolicy $arbitrationRetentionPolicy[0].Identity -Force;
              else
                Write-ExchangeSetupLog -Info ("Cannot find E-discovery arbitration mailbox with name=$name.");
            else
              write-exchangesetuplog -info "Skipping creating Discovery Arbitration Mailbox because of insufficient permission."
        " was run: "Database is mandatory on UserMailbox. Property Name: Database".
Seems the problem was corrupted arbitrary system mailboxes from previous Exchange 2010 to Exchange 2013 migration.
The solution for me was to restore the corrupted arbitrary mailboxes using this
LINK. It is for 2010 but Works on 2013.
I am now currently on Exchange CU2 on both my EX server and on my DC. Now I have to check mail flow and will report back.

Exchange Server 2013 Database not showing in ECP after removal of Exchange Server 2010

I recently complete the migration of my Exchange 2010 server to Exchange 2013. I then proceeded to uninstall the 2010 server using setup.com /m:uninstall. At the end of the process I received an error that it did not complete the uninstall.
I checked the server and Exchanged 2010 was removed. When I checked ECP on 2013 it still showed the old 2010 server listed. I used ADSI edit and manually removed the old sever.
Now when I log into 2013 ECP I only see the one serve but when I go into databases, none are listed. I check under the server itself and it shows the database that it is using but it is not listed under the database tab.
If I do a search under the database tab I can find it and adds it to the list. I can then open and view details.
My issue is, after I log out and then back in, I have to run the search to find the database again. In ideas on how to have it show up in the list like it did before I removed the 2010 Exchange server?
Thank you,

Hi,
From your description, I recommend you verify the following things for troubleshooting:
1. Please make sure that AD replication is completely by checking the user object's homeMDB attribute. This value should contain the DN value of the Exchange Server 2013 mailbox database.
2. Wait 30 minutes for the cache on the Exchange Server 2013 Client Access Server to clear or restart the MSExchangeOWAAppPool on the Exchange Server 2013 Client Access Server.
For more information, here is a kb for your reference.
Exchange 2013 Redirects to Exchange 2010 for OWA and ECP
http://support.microsoft.com/kb/2931385
Hope it helps.
Best regards,
Amy Wang
TechNet Community Support

Migration from Exchange server 2010 to Exchange server 2013

Hi All,
We have migrate Exchange Server 2010 to Exchange Server 2013. When I turned off my Exchange Server 2010, Outlook is not able to connect through Exchange 2013. It's prompting for user name and password again and again and nothing would happen
after provide user name and password. So, we are not able to uninstall exchange 2010 from old server.

Run these commands and post the update.
Get-WebservicesVirtualDirectory -Server E2K13SERVER |Fl internalURL,ExternalURL
Get-OWAVirtualDirectory -Server E2K13SERVER | Fl internalUrl,ExternalURL
Get-ClientAccessServer E2K13SERVER | Fl AutodiscoverServiceInternalUri
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 2013 POP3 Service on CAS cannot after Upgrade to SP1

Exchange Server 2013 POP3 Service on CAS cannot after Upgrade to SP1
When I manual start MSExchangepop3 Service on CAS It show "The Microsoft Exchange POP3 Service on Local Computer started and then stopped. Some services stop automatically if they are not in use by other services or programs."
In event log show POP3 EventID 1018 , 1019 , 1036
It said like this blinding already use (0.0.0.0)
The point is "IF I SET BINDING FOR 995 , MSEXCHANGE POP3 Service will automatic stop"
Does anyone face this issue please?
Thank you

You could check what (if anything) else is running on that port.
From a command prompt, type netstat -ano | find 995
This will give you the Process Identifier (PID) for the process that is running on port 995. Then you can open Task Manager, add PID as an additional column, and find out what that process is.
Hope that helps.

Exchange Server 2013 migration and high avalability

Hello,
We are using Office 365 online and will be migrating onto an in-house Exchange Server 2013 on a new Windows Server box.
I have two questions:
1. What is the best way to migrate everything from the Office 365 to the in house server? Do I setup a hybrid environment and then move the mailboxes and then remove the hybrid environment?
2. What is the best way to setup high availability for the in-house Exchange server? I found out that in order to setup Exchange 2013 as high availability it needs to run on Windows server 2012 STD or Windows server 2008 Enterprise.
Please let me know and provide links to step by step instructions if possible.
Thank you, Karel
Thank you. Karel Grulich, MCSE, SBS

Hi Karel,
Thank you for your question.
In addition Ed’s suggestion, moving mailbox form Exchange online to Exchange on premise could be refer to the following link:
https://technet.microsoft.com/en-us/library/jj906432(v=exchg.150).aspx
Exchange 2013 high availability could be referred by the following link:
https://technet.microsoft.com/en-us/library/dd638137(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

Mails struck in Drafts folder after Transport Agent installed in Exchange Server 2013

Hi all,
I created Transport Agent and installed successfully in exchange server 2013.
After that mails are struck in drafts folder.
I thought because of My Custom transport Agent , then i Uninstall Transport agent.
but still no use.
I restart Microsoft Exchange Transport Service and restart my server also.
Here is the code i used
public sealed class MyAgentFactory : RoutingAgentFactory
public override RoutingAgent CreateAgent(SmtpServer server)
return new MyAgent();
public class MyAgent : RoutingAgent
public MyAgent()
this.OnSubmittedMessage += new SubmittedMessageEventHandler(this.MySubmittedMessageHandler);
public void MySubmittedMessageHandler(SubmittedMessageEventSource source, QueuedMessageEventArgs e)
e.MailItem.Message.Subject = "This message passed through my agent: " + e.MailItem.Message.Subject;
I search in google about mails struck in drafts folder, all replies are
restore Default Receive Connectors. How can i restore it.
here is the link i see
http://community.spiceworks.com/topic/309145-exchange-2013-messages-stuck-in-drafts

Hi Martina
Miskovic,
Here I am facing some weird situation.
Mails again stuck in Drafts folder.
i didn't installed anything. just checking again after some
time gap .
I tried again by restarting all services
, but no use.

Migrate Exchange Server 2010 Public Folder shared calendars to Exchange Server 2013

Dear All,
I have an question about calendars under public folder migrating to new exchange server 2013. When completed the PF migration progress, will it also migrate calendars under sub-folder under PF to new PF mailbox?
For example: in exchange 2010 PF:
In exchange 2013
\Public Folder\sales\A1_calendar
--->
\ Public Folder\sales\A2_calendar
---> ?
\Public Folder\sales\A3_calendar
---> ?
\Public Folder\sales\A4_calendar
---> ?
Thanks in advance.
Regards,
Willis Wong

Hi Willis,
This forum is for general questions and feedback related to Outlook. Since your question is more related to Exchange server, I'd recommend you post a new question in the Exchange forum for further assistance:
https://social.technet.microsoft.com/Forums/office/en-US/home?category=exchangeserver
The reason why we recommend posting appropriately is you will get the most qualified pool of respondents, and other partners who read the forums regularly can either share their knowledge or learn from your interaction with us. Thank you for your understanding.
Steve Fan
TechNet Community Support
It's recommended to download and install
Configuration Analyzer Tool (OffCAT), which is developed by Microsoft Support teams. Once the tool is installed, you can run it at any time to scan for hundreds of known issues in Office
programs.
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]

Folders Exist After Installing Exchange Server 2013

Hi,
We installed Exchange Server 2013 SP1 a while ago and noticed two directories were created:
D:\MonitoringDiagnosticLogs\MSExchangeHMHost (Contains a file called MSExchangeHMHost20141231-1)
and
D:\TransportRoles\Logs\SyncHealth\Hub
I also noticed the second folder is addressed in Cumulative Update 5.
I have the following questions:
1. Does applying CU5 remove the second directory? If not, is it safe for me to delete this directory?
2. What about the first directory? How do I get rid of that? Is it safe for me to delete it?
3. If I cannot get rid of the two directories is it safe for me to create a new partition, move the directories to it, and mark it as D:\ so the path remains the same?
Thanks for the help!

Hi,
Based on my research, the two additional directories are created on this D:\ drive during installation of Exchange 2013 automatically:
D:\MonitoringDiagnosticLogs\MSExchangeHMHost
D:\TransportRoles\Logs\SyncHealth
Currently, there is no official document about this issue. Since it will not cause any issue, you can leave it there.
We will wait for the official explanation of the issue. We highly appreciate your kindly understanding and patience.
Best regards,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Belinda Ma
TechNet Community Support

Exchange Server 2013 restarts frequently after Cumulative Update 3 is installed

Hi All,
In our Environment Exchange Server 2013 CU3 is installed and restarts every alternate days.Below are the details
Event Id : 6008
The previous system shutdown at 03:13:44 on ‎12-‎06-‎2014 was unexpected.
Evend Id : 1001
The computer has rebooted from a bugcheck. The bugcheck was: 0x000000ef (0xfffffa800e9a8080, 0x0000000000000000, 0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 061214-30108-01.
Event 41, Kernal Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Can somebody help me through this because it was causing severe to our organization and restarts frequently as well.

Hello,
Try following solutions:
http://support.microsoft.com/kb/2883203/en-us
http://itsalwaysmyproblem.com/2013/08/27/exchange-2013-and-bugcheck-0x000000ef/
Also installing CU5 may be helpful.
Hope it helps,
Adam
www.codetwo.com
If this post helps resolve your issue, please click the "Mark as Answer" or "Helpful" button at the top of this message. By marking a post as Answered, or Helpful you help others
find the answer faster.

Exchange Server 2013: Installation fails

Migrating SBS 2008 to Windows Server 2012 R2 (no virtualization) and Exchange Server 2013 SP1
(1) ADprep on SBS 2008 went fine
(2) Installed necessary feature for Exchange (website “Part 1: Step-by-Step Exchange 2007 to 2013 Migration”)
A) the first time I installed Exchange 2013, the setup succeeded, however there were several ecp/WinRM errors.
B) restored Windows Server 2012 R2 to the state (2). Removed from AD (ADSI Edit)
… CN=Services; CN=Exchange; CN=First Organization; CN=Exchange Administrator Group; CN=Servers
delete new Win 2012 server
Run Exchange setup again:
The following error was generated when "$error.Clear();
if ($RoleStartTransportService)
start-SetupService -ServiceName MSExchangeTransport -MaxWaitTimeForRunningState 0:0:40
" was run: "Service 'MSExchangeTransport' failed to reach status 'Running' on this server.".
Checked:
- IPv6 is enabled, but was setup correctly after installing ADDS role)
- Administrators (Group) is a member of the Exch. Trusted Subsystem
Probably there is an AD problem, after the restoration (B) (bare metal) of the Win 2012 server.
Please help!
Fulco

Hi
the error states that the MSExchangeTransport service failed to start. Can you manually try starting the service and then run the setup again?
Hope this helps. Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Exchange Server 2013 Toolbox MMC Error ConsoleInitialize.ps1 not recognised

Hello, after installing and configuring Exchange 2013 during a migration from 2010 (with both versions still running), I am now receiving a ConsoleInitialize.ps1 System.Management.Automation.RemoteException exception when trying to run the Management Toolbox
(I am really after the Queue Viewer).
This is the same when trying to connect locally on the server and remotely on a client computer with Management Tools installed - I can use EMC without any errors locally or remotely.
I have tried various fixes found around the net, including:
Changing the Identity of the Classic and DefaultAppPools in IIS and resetting - from LocalSystem to ApplicationPoolIdentity
Adding the roles to Exchange Organisation Management in AD
Disabling SSL on the Powershell virtual Directory and setting auth to anonymous
I have not tried recreating the Powershell virtual directory as mentioned on a few sites, as I have not been able to test that in the lab, and I am not sure how it affects the powershell session that I am doing it from.
The only thing that I can think that could be an issue is that Ex2010 is still up and running, could it be that Management Tools is looking at the old server, instead of the new?
Can anyone point me in the right direction with this one?
I can post more info if required.
Thank you.
Xpost here: http://serverfault.com/questions/666054/exchange-server-2013-toolbox-mmc-error-consoleinitialize-ps1-not-recognised

Hi,
If the EMS and EMC work properly, I think the powershell cannot be the problem. Is it possible to build up a new Exchange 2013 Server in test environment and make a replacement of
the ConsoleInitialize.ps1 file?
Thanks,
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Simon Wu
TechNet Community Support

Decommission Exchange Server 2013 after migration to Office365

Similar Messages

Maybe you are looking for