Exchange 2016 Domain Schema change in Hybrid

%3CLINGO-SUB%20id%3D%22lingo-sub-1525311%22%20slang%3D%22en-US%22%3EExchange%202016%20Domain%20Schema%20change%20in%20Hybrid%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1525311%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20All%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%20We%20have%20a%20Hybrid%20setup%20with%20O365.%20On-premise%20Exchange%202010.%20We%20are%20planning%20to%20set%20up%20new%20Exchange%202016%20server%20and%20noticed%20two%20ways%20to%26nbsp%3B%3CSPAN%3EPrepare%26nbsp%3BActive%20Directory%20and%20please%20clarify%3F%3C%2FSPAN%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E1.%26nbsp%3B%3CSPAN%3EPrepare%26nbsp%3BActive%20Directory%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%20data-contrast%3D%22auto%22%3EExamples%3A%26nbsp%3B%3C%2FSPAN%3E%3CSPAN%3E%26nbsp%3B%3CBR%20%2F%3E%3C%2FSPAN%3E%3CEM%3EE%3A%5CSetup.exe%20%2FIAcceptExchangeServerLicenseTerms%20%2FPrepareSchema%3C%2FEM%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CEM%3EE%3A%5CSetup.exe%20%2FIAcceptExchangeServerLicenseTerms%20%2FPrepareAD%26nbsp%3B%26nbsp%3B%3C%2FEM%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%20class%3D%22Code%22%3E%26nbsp%3B%3C%2FP%3E%3CP%20class%3D%22Code%22%3E%26nbsp%3B2.%20To%20extend%20your%20AD%20schema%20for%20the%20Exchange%202016%20attributes.%20%26nbsp%3BThis%20is%20done%20as%20follows%3B%3C%2FP%3E%3CP%20class%3D%22Code%22%3E%26nbsp%3B%3C%2FP%3E%3CP%20class%3D%22Code%22%3EConnect%20to%20Exchange%20Online%20PowerShell%20as%20below%3B%3C%2FP%3E%3CP%20class%3D%22Code%22%3E%26nbsp%3B%3C%2FP%3E%3CDIV%3E%3CP%20class%3D%22Code%22%3E%3CSTRONG%3E%24Cred%3DGET-CREDENTIAL%26nbsp%3B%3C%2FSTRONG%3E%3C%2FP%3E%3CP%20class%3D%22Code%22%3E%3CSTRONG%3E%24s%20%3D%20NEW-PSSESSION%20-ConfigurationName%20Microsoft.Exchange%20-ConnectionUri%26nbsp%3B-ERR%3AREF-NOT-FOUND-%3CA%20href%3D%22https%3A%2F%2Fps.outlook.com%2Fpowershell%26nbsp%3B-Credential%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fps.outlook.com%2Fpowershell%26nbsp%3B-Credential%3C%2FA%3E%20%24Cred%20-Authentication%20Basic%20-AllowRedirection%26nbsp%3B%3C%2FSTRONG%3E%3C%2FP%3E%3CP%20class%3D%22Code%22%3E%3CSTRONG%3E%24importresults%3Dimport-pssession%20%24s%26nbsp%3B%3C%2FSTRONG%3E%3C%2FP%3E%3C%2FDIV%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EExport%20the%20tenantconfig.xml%20file%20by%20running%20the%20following%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CDIV%3E%3CP%20class%3D%22Code%22%3E%3CSTRONG%3EGet-OrganizationConfig%20%7C%20Export-Clixml%20-Path%20TenantConfig.XML%3C%2FSTRONG%3E%3C%2FP%3E%3CP%20class%3D%22Code%22%3E%26nbsp%3B%3C%2FP%3E%3CP%20class%3D%22Code%22%3ENext%2C%20prepare%20the%20schema%20as%20below%20-%20setting%20the%20folder%20path%20to%20where%20you%20saved%20the%20xml%20file.%2C%3C%2FP%3E%3CP%20class%3D%22Code%22%3E%26nbsp%3B%3C%2FP%3E%3CDIV%3E%3CP%20class%3D%22Code%22%3E%3CSTRONG%3E.%2FSetup.exe%20%2FPrepareAD%20%2FTenantOrganizationConfig%20c%3A%5Ctemp%5CTenantConfig.xml%20%2FIAcceptExchangeServerLicenseTerms%3C%2FSTRONG%3E%3C%2FP%3E%3CP%20class%3D%22Code%22%3E%26nbsp%3B%3C%2FP%3E%3CP%20class%3D%22Code%22%3EThen%2C%20prepare%20the%20domains%26nbsp%3B%3C%2FP%3E%3CP%20class%3D%22Code%22%3E%26nbsp%3B%3C%2FP%3E%3CDIV%3E%3CP%20class%3D%22Code%22%3E%3CSTRONG%3E.%2FSetup.exe%20%2FPrepareAllDomains%20%2FIAcceptExchangeServerLicenseterms%3C%2FSTRONG%3E%3C%2FP%3E%3CP%20class%3D%22Code%22%3E%26nbsp%3B%3C%2FP%3E%3CP%20class%3D%22Code%22%3E%26nbsp%3B%3C%2FP%3E%3CP%20class%3D%22Code%22%3EAs%3C%2FP%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1525311%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EHybrid%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1525581%22%20slang%3D%22en-US%22%3ERe%3A%20Exchange%202016%20Domain%20Schema%20change%20in%20Hybrid%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1525581%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F644958%22%20target%3D%22_blank%22%3E%40aussupport%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHi%2C%20I'm%20not%20quite%20sure%20what%20your%20question%20is%20here%20as%20you%20have%20all%20of%20the%20appropriate%20steps%20listed%20already.%26nbsp%3B%20Please%20can%20you%20explain%20a%20little%20further%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1525826%22%20slang%3D%22en-US%22%3ERe%3A%20Exchange%202016%20Domain%20Schema%20change%20in%20Hybrid%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1525826%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F616707%22%20target%3D%22_blank%22%3E%40PeterRising%3C%2FA%3E%26nbsp%3BHi%20Peter%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%20Want%20to%20know%20the%20difference%20between%20above%201%20and%202%3F%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3BI%20mean%20one%20without%26nbsp%3B%3CSTRONG%3ETenantConfig.XML%3F%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSTRONG%3EAs%3C%2FSTRONG%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1528580%22%20slang%3D%22en-US%22%3ERe%3A%20Exchange%202016%20Domain%20Schema%20change%20in%20Hybrid%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1528580%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F644958%22%20target%3D%22_blank%22%3E%40aussupport%3C%2FA%3E%26nbsp%3B%20Came%20to%20know%20that%20few%20Exchange%202016%20servers%20were%20decommissioned%20with%20the%20O365%20migration.%20So%20when%20I%20install%20a%20new%20server%2C%20need%20to%20run%20the%20forest%20prep%20and%20domain%20again%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E
Contributor

Hi All,

 

  We have a Hybrid setup with O365. On-premise Exchange 2010. We are planning to set up new Exchange 2016 server and noticed two ways to Prepare Active Directory and please clarify? 

 

1. Prepare Active Directory

Examples:  
E:\Setup.exe /IAcceptExchangeServerLicenseTerms /PrepareSchema 

E:\Setup.exe /IAcceptExchangeServerLicenseTerms /PrepareAD  

 

 

 2. To extend your AD schema for the Exchange 2016 attributes.  This is done as follows;

 

Connect to Exchange Online PowerShell as below;

 

$Cred=GET-CREDENTIAL 

$s = NEW-PSSESSION -ConfigurationName Microsoft.Exchange -ConnectionUri https://ps.outlook.com/powershell -Credential $Cred -Authentication Basic -AllowRedirection 

$importresults=import-pssession $s 

 

Export the tenantconfig.xml file by running the following;

 

Get-OrganizationConfig | Export-Clixml -Path TenantConfig.XML

 

Next, prepare the schema as below - setting the folder path to where you saved the xml file.,

 

./Setup.exe /PrepareAD /TenantOrganizationConfig c:\temp\TenantConfig.xml /IAcceptExchangeServerLicenseTerms

 

Then, prepare the domains 

 

./Setup.exe /PrepareAllDomains /IAcceptExchangeServerLicenseterms

 

 

As

3 Replies
Highlighted

@aussupport 

 

Hi, I'm not quite sure what your question is here as you have all of the appropriate steps listed already.  Please can you explain a little further?

Highlighted

@PeterRising Hi Peter,

 

  Want to know the difference between above 1 and 2? 

 

     I mean one without TenantConfig.XML?

 

As

Highlighted

@aussupport  Came to know that few Exchange 2016 servers were decommissioned with the O365 migration. So when I install a new server, need to run the forest prep and domain again?