SOLVED

Decommission your on-premises Exchange 2010 server in a hybrid deployment

%3CLINGO-SUB%20id%3D%22lingo-sub-1528080%22%20slang%3D%22en-US%22%3EDecommission%20your%20on-premises%20Exchange%202010%20server%20in%20a%20hybrid%20deployment%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1528080%22%20slang%3D%22en-US%22%3E%3CH3%20id%3D%22toc-hId-1198151775%22%20id%3D%22toc-hId-1198152559%22%20id%3D%22toc-hId-1198152559%22%20id%3D%22toc-hId-1198152559%22%20id%3D%22toc-hId-1198152559%22%3EScenario%20two%3C%2FH3%3E%3CP%3E%3CSTRONG%3EIssue%3C%2FSTRONG%3E%3A%20My%20organization%20has%20been%20running%20in%20a%20hybrid%20configuration%20for%20about%20a%20year%20now%20and%20have%20finally%20moved%20my%20last%20mailbox%20to%20the%20cloud.%20I%20plan%20to%20keep%20Active%20Directory%20Federation%20Services%20(AD%20FS)%20for%20user%20authentication%20of%20my%20Exchange%20Online%20mailboxes.%20(This%20scenario%20would%20apply%20to%20any%20customer%20that%20is%20planning%20on%20keeping%20directory%20synchronization).%3C%2FP%3E%3CP%3E%3CSTRONG%3ESolution%3C%2FSTRONG%3E%3A%20Since%20the%20customer%20is%20planning%20on%20keeping%20AD%20FS%2C%20they%20will%20also%20have%20to%20keep%20directory%20synchronization%20since%20it%20is%20a%20prerequisite.%20Because%20of%20that%2C%20they%20cannot%20fully%20remove%20the%20Exchange%20servers%20from%20the%20on-premises%20environment.%20However%2C%20they%20can%20decommission%20most%20of%20the%20Exchange%20servers%2C%20but%20leave%20a%20couple%20of%20servers%20behind%20for%20user%20management.%20Keep%20in%20mind%20that%20the%20servers%20that%20are%20left%20running%20can%20be%20run%20on%20virtual%20machines%20since%20the%20workload%20is%20almost%20completely%20shifted%20to%20Exchange%20Online.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESo%20if%20we%20need%20to%20keep%20one%20Exchange%202016%20server.%20After%20the%20Server%20install%2C%20I%20have%20noticed%20that%20may%20ask%20to%20update%20the%26nbsp%3B%20Service%20SCP%20on%20Windows%202016%20server%20and%20configure%20Virtual%20directory%20URL%20etc%20etc%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EBut%26nbsp%3B%20this%26nbsp%3B%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fexchange%2Fdecommission-on-premises-exchange%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fexchange%2Fdecommission-on-premises-exchange%3C%2FA%3E%3C%2FP%3E%3CP%3Esay%20SCP%20set%20to%20null%20and%20remove%20the%20hybrid%20configuration%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAs%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1528080%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EMigration%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOffice%20365%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1535811%22%20slang%3D%22en-US%22%3ERe%3A%20Decommission%20your%20on-premises%20Exchange%202010%20server%20in%20a%20hybrid%20deployment%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1535811%22%20slang%3D%22en-US%22%3ESince%20you%20already%20had%202016%20in%20your%20environment%20so%20your%20schema%20is%20already%20expanded.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1537820%22%20slang%3D%22en-US%22%3ERe%3A%20Decommission%20your%20on-premises%20Exchange%202010%20server%20in%20a%20hybrid%20deployment%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1537820%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F333418%22%20target%3D%22_blank%22%3E%40DeepakRandhawa%3C%2FA%3E%26nbsp%3B%20Thanks%20for%20your%20reply%20but%20do%20I%20have%20to%20run%20that%20again%20or%20setup%20will%20pickup%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1538124%22%20slang%3D%22en-US%22%3ERe%3A%20Decommission%20your%20on-premises%20Exchange%202010%20server%20in%20a%20hybrid%20deployment%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1538124%22%20slang%3D%22en-US%22%3Esetup%20should%20pick%20it%20up%3C%2FLINGO-BODY%3E
New Contributor

Scenario two

Issue: My organization has been running in a hybrid configuration for about a year now and have finally moved my last mailbox to the cloud. I plan to keep Active Directory Federation Services (AD FS) for user authentication of my Exchange Online mailboxes. (This scenario would apply to any customer that is planning on keeping directory synchronization).

Solution: Since the customer is planning on keeping AD FS, they will also have to keep directory synchronization since it is a prerequisite. Because of that, they cannot fully remove the Exchange servers from the on-premises environment. However, they can decommission most of the Exchange servers, but leave a couple of servers behind for user management. Keep in mind that the servers that are left running can be run on virtual machines since the workload is almost completely shifted to Exchange Online.

 

So if we need to keep one Exchange 2016 server. After the Server install, I have noticed that may ask to update the  Service SCP on Windows 2016 server and configure Virtual directory URL etc etc,

 

But  this  https://docs.microsoft.com/en-us/exchange/decommission-on-premises-exchange

say SCP set to null and remove the hybrid configuration?

 

We had few Exchange 2016 servers and they all were decommissioned. So installing the new Exchange 2016 need schema update and domain update? 

 

We can see some send and receive connectors and mail flow through this server. 

 

As

 

 

 

3 Replies
Since you already had 2016 in your environment so your schema is already expanded.

@DeepakRandhawa  Thanks for your reply but do I have to run that again or setup will pickup?

best response confirmed by Aussupport30 (New Contributor)
Solution
setup should pick it up