- Assuming successful migration of the mailboxes to the Exchange online, the user can point the MX and Autodiscover DNS records to Exchange Online, instead of on-premises.
- Remove Service Connection Point (SCP) values on your Exchange servers. It ensures that no SCPs are returned and client will be using DNS method for Autodiscover.
- Now, it is required to delete the inbound and outbound connectors created by Hybrid Configuration Wizard. To do this log on to Office 365 admin portal and sign in as Tenant Administrator.
- Select the option to manage Exchange.
- Navigate to Mail Flow->Connection.
- Now, delete the inbound outbound connectors.
- To remove the organization relationship created y the Hybrid Configuration Wizard, log-in to Office 365 Admin Portal and sign in as Tenant Administrator.
- Select the option to manage Exchange.
- Navigate Organization-> Organization Sharing->Remove the organization named O365 to On-Premises-<unique identifier>.
- Now, uninstall the Exchange from on-premises server.
Remove the organizational relationship from the on-premises environment:
‘Remove-OrganizationalRelationship -identity “name_of_org_relationship”. The identity of the organizational relationship can be obtained by using the ‘Get-OrganizationalRelationship’ if required.
Get-OrganizationRelationship |fl
Remove-OrganizationalRelationship -identity “On-premises to O365 – d40db1fd-758f-4c70-a4d9-3d6027d03a6b”
Remove the organizational relationship from the Office 365 tenant:
‘Remove-OrganizationalRelationship -identity “name of_org_relationship”. Again, the identity of the organizational relationship can be obtained by using the ‘Get-OrganizationalRelationship’ if required.
Remove-OrganizationRelationship -identity “O365 to On-premises – d40db1fd-758f-4c70-a4d9-3d6027d03a6b”
Remove the federated domain(s) from the on-premises environment:
‘Remove-FederatedDomain -domainname name_of_domain
Remove-FederationTrust -Identity “Microsoft Federation Gateway”
If you receive an error , you have to remove the federated domain...
To do this issue this commands..
Get-FederatedOrganizationIdentifier
now remove it with this command:
Remove-FederatedDomain -DomainName softcomet.it
now we can remove the Federation Gateway…
Remove-FederationTrust -Identity “Microsoft Federation Gateway”
Remove the Email Address Policy/Policies associated with SMTP domains that have been moved to Office 365.
This can simply be performed from the on-premises Exchange admin console.
At this point you have to remove, under address policy the “onmicrosoft.com” domain.
Remove the Accepted Domain entries from the on-premises Exchange admin console for SMTP domains that have been moved to Office 365.
This can be performed from the on-premises Exchange admin console as well.
Remove the federation trust from the on-premises Exchange environment:
‘Remove-FederationTrust -Identity “Microsoft Federation Gateway”. By default, the hybrid configuration wizard in Exchange 2010/2013 names the federation trust “Microsoft Federation Gateway”.
Remove the remote domain associated with the Exchange hybrid configuration using the on-premises Exchange Admin Console.
This will be named something like “Hybrid Domain – tenant_name.mail.onmicrosoft.com”.
Remove the SMTP send connector from the on-premises environment:
‘Remove-SendConnector “Connector_Name”‘.
Remove the send connector:
Get-SendConnector and remove it with remove-sendconnector
Remove the inbound and outbound SMTP connectors that were created by the hybrid configuration wizard
in the Exchange Online Protection Administration Console.
Finally, remove the HybridConfiguration object from within Active Directory.
This isn’t supported in Exchange 2010, and it’s perfectly fine to leave the object in AD without any adverse effects. If, however, Exchange 2013 is being used in the hybrid configuration, the following PS command can be used to remove the HybridConfiguration object: Remove-HybridConfiguration. Open ADSI and delete it .
Uninstall Exchange….
Questo articolo ti è stato utile?
Fantastico!
Grazie per il tuo feedback
Siamo spiacenti di non poterti essere di aiuto
Grazie per il tuo feedback
Feedback inviato
Apprezziamo il tuo sforzo e cercheremo di correggere l’articolo