Home

Exchange 2010 SP3 RU29 with 2019 Domain Controllers

%3CLINGO-SUB%20id%3D%22lingo-sub-1047659%22%20slang%3D%22en-US%22%3EExchange%202010%20SP3%20RU29%20with%202019%20Domain%20Controllers%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1047659%22%20slang%3D%22en-US%22%3E%3CP%3EHello%2C%20I%20wonder%20if%20someone%20can%20give%20a%20bit%20of%20clarification%20regarding%20the%20Microsoft's%20matrix%20for%20Exchange%202010%20support%20here.%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fexchange%2Fplan-and-deploy%2Fsupportability-matrix%3Fview%3Dexchserver-2019%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Edocs.microsoft.com%2Fen-us%2Fexchange%2Fplan-and-deploy%2Fsupportability-matrix%3Fview%3Dexchserver-2019%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20am%20currently%20upgrading%20domain%20controllers%20from%202008%20R2%20(2%20of%20them)%20to%202019%2C%20and%20have%20already%20promoted%20and%20setup%202%20new%20ones.%20Domain%20and%20Forest%20level%20is%20still%20set%20to%202008%20R2.%20All%20FSMO%20roles%20have%20been%20transferred%20and%20Exchange%202010%20successfully%20picked%20up%20and%20using%20see%20the%20new%202%202019%20DCs.%3C%2FP%3E%3CP%3ENow%20Microsoft's%20site%20says%20it%20does%20not%20support%202019%20environment%3F%20This%20is%20the%20part%20that%20concerns%20me%2C%20because%20it%20clearly%20does.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20haven't%20demoted%202%20old%20DCs%20yet%2C%20but%20based%20on%20all%20info%20I%20could%20find%20Exchange%20is%20already%20using%202019%20DCs.%3C%2FP%3E%3CP%3EAlso%20all%20flags%20look%20proper%20in%20Exchange%20Discovery%20event%20viewer%20(event%202080)%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CEM%3EProcess%20STORE.EXE%20(PID%3D5108).%20Exchange%20Active%20Directory%20Provider%20has%20discovered%20the%20following%20servers%20with%20the%20following%20characteristics%3A%20%3C%2FEM%3E%3CBR%20%2F%3E%3CEM%3E(Server%20name%20%7C%20Roles%20%7C%20Enabled%20%7C%20Reachability%20%7C%20Synchronized%20%7C%20GC%20capable%20%7C%20PDC%20%7C%20SACL%20right%20%7C%20Critical%20Data%20%7C%20Netlogon%20%7C%20OS%20Version)%20%3C%2FEM%3E%3CBR%20%2F%3E%3CEM%3EIn-site%3A%3C%2FEM%3E%3C%2FP%3E%3CP%3E%3CEM%3ECDG%201%207%207%201%200%201%201%207%201%20for%20both%20new%202019%20DCs.%3C%2FEM%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EShould%20I%20be%20concerned%20with%20demoting%202%20old%20ones%3F%20Based%20on%20the%20matrix%20Exchange%202010%20should%20work%20with%202016%20functional%20level%2C%20so%20if%20I%20were%20to%20raise%20it%20to%20that%20level%20after%20demoting%20the%20old%20ones%20everything%20should%20still%20be%20OK%3F%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIs%20there%20another%20test%20I%20can%20run%20to%20make%20sure%20exchange%20will%20still%20be%20fine%20after%20demoting%26nbsp%3B%20old%20ones%3F%3C%2FP%3E%3CP%3EI%20was%20thinking%20explicitly%20excluding%202%20old%20ones%20using%20-StaticExcludedDomainControllers%20on%20the%20exchange%20to%20make%20sure%20its%20not%20using%20them%20at%20all%3F%20Will%20that%20be%20sufficient%20to%20make%20sure%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20have%20attached%20a%20screenshot%20from%20exchange%20console%20with%20more%20info.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIt%20would%20be%20nice%20to%20find%20why%20Microsoft%20is%20saying%20that%20Exchange%202010%20is%20not%20able%20to%20communicate%20with%202019%20DCs...%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%3C%2FP%3E%3CP%3E%26nbsp%3B%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-1047659%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EActive%20Directory%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3Eexchange%202010%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EWindows%20Server%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1047786%22%20slang%3D%22en-US%22%3ERe%3A%20Exchange%202010%20SP3%20RU29%20with%202019%20Domain%20Controllers%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1047786%22%20slang%3D%22en-US%22%3E%3CP%3EThe%20document%20does%20not%20outline%20what%20appears%20to%20work%20or%20not%20work%20but%20instead%20documents%20what%20has%20been%20tested%20and%20is%20currently%20supported.%20If%20it's%20working%20for%20you%20then%20that's%20a%20good%20sign%20but%20if%20some%20problems%20arise%20it%20simply%20is%20not%20a%20supportable%20configuration.%20The%20risks%20%2F%20burden%20of%20support%20is%20left%20to%20end%20user.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1047819%22%20slang%3D%22en-US%22%3ERe%3A%20Exchange%202010%20SP3%20RU29%20with%202019%20Domain%20Controllers%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1047819%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F51719%22%20target%3D%22_blank%22%3E%40Dave%20Patrick%3C%2FA%3E%26nbsp%3BThanks%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESo%20If%20I%20were%20to%20promote%20another%20DC%20but%202016%20and%20point%20Exchange%20to%20use%20it%2C%20then%20it%20becomes%20supportable%20configuration%20correct%3F%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1047824%22%20slang%3D%22en-US%22%3ERe%3A%20Exchange%202010%20SP3%20RU29%20with%202019%20Domain%20Controllers%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1047824%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F51719%22%20target%3D%22_blank%22%3E%40Dave%20Patrick%3C%2FA%3E%26nbsp%3B%20Also%20the%20document%20seems%20to%20clearly%20state%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CEM%3EThe%20following%20table%20identifies%20the%20Active%20Directory%20environments%20that%20Exchange%20%3CSTRONG%3Ecan%20communicate%20with.%26nbsp%3B%3C%2FSTRONG%3E%3C%2FEM%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThis%20is%20the%20confusing%20part%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1047831%22%20slang%3D%22en-US%22%3ERe%3A%20Exchange%202010%20SP3%20RU29%20with%202019%20Domain%20Controllers%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1047831%22%20slang%3D%22en-US%22%3E%3CP%3EMy%20read%20of%20the%20document%20is%20that%20if%202019%20domain%20controllers%20are%20introduced%20then%20it%20would%20be%20an%20untested%20unsupported%20configuration.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
muhoboika
New Contributor

Hello, I wonder if someone can give a bit of clarification regarding the Microsoft's matrix for Exchange 2010 support here.

docs.microsoft.com/en-us/exchange/plan-and-deploy/supportability-matrix?view=exchserver-2019

 

I am currently upgrading domain controllers from 2008 R2 (2 of them) to 2019, and have already promoted and setup 2 new ones. Domain and Forest level is still set to 2008 R2. All FSMO roles have been transferred and Exchange 2010 successfully picked up and using see the new 2 2019 DCs.

Now Microsoft's site says it does not support 2019 environment? This is the part that concerns me, because it clearly does.

 

I haven't demoted 2 old DCs yet, but based on all info I could find Exchange is already using 2019 DCs.

Also all flags look proper in Exchange Discovery event viewer (event 2080)

 

Process STORE.EXE (PID=5108). Exchange Active Directory Provider has discovered the following servers with the following characteristics:
(Server name | Roles | Enabled | Reachability | Synchronized | GC capable | PDC | SACL right | Critical Data | Netlogon | OS Version)
In-site:

CDG 1 7 7 1 0 1 1 7 1 for both new 2019 DCs.

 

Should I be concerned with demoting 2 old ones? Based on the matrix Exchange 2010 should work with 2016 functional level, so if I were to raise it to that level after demoting the old ones everything should still be OK? 

 

Is there another test I can run to make sure exchange will still be fine after demoting  old ones?

I was thinking explicitly excluding 2 old ones using -StaticExcludedDomainControllers on the exchange to make sure its not using them at all? Will that be sufficient to make sure?

 

I have attached a screenshot from exchange console with more info.

 

It would be nice to find why Microsoft is saying that Exchange 2010 is not able to communicate with 2019 DCs...

 

Thanks

 

 

 

 

4 Replies

The document does not outline what appears to work or not work but instead documents what has been tested and is currently supported. If it's working for you then that's a good sign but if some problems arise it simply is not a supportable configuration. The risks / burden of support is left to end user.

 

 

@Dave Patrick Thanks

 

So If I were to promote another DC but 2016 and point Exchange to use it, then it becomes supportable configuration correct? 

@Dave Patrick  Also the document seems to clearly state:

 

The following table identifies the Active Directory environments that Exchange can communicate with. 

 

This is the confusing part

 

 

My read of the document is that if 2019 domain controllers are introduced then it would be an untested unsupported configuration.