Home

Understanding the Channel-attribute of the Office Deployment Tool & how to optimize your deployment

%3CP%3EIn%20nearly%20every%20configuration%20file%20(aka%20config.xml)%20you%20will%20find%20this%20attribute%2C%20but%20have%20you%20known%20that%20this%20is%20actually%20an%20optional%20attribute%20and%20can%20be%20used%20to%20build%20leaner%20deployments%20which%20require%20less%20maintenance%3F%20I%20will%20walk%20you%20through%20the%20steps%20on%20how%20the%20Channel-attribute%20works%20during%20the%20initial%20installation%20of%20Office%20365%20Client%20Apps%20and%20how%20to%20leverage%20it%20for%20reducing%20your%20effort%20when%20building%20sub-sequent%20installs%20(Project%2C%20Visio%2C%20%E2%80%A6).%3C%2FP%3E%0A%3CP%3E%3CSPAN%3EWhen%20designing%20an%20Office%20365%20ProPlus%20deployment%2C%20especially%20in%20larger%20organizations%2C%20the%20%E2%80%9CUpdate%20Channel%E2%80%9D%20to%20use%20is%20an%20important%20factor.%20It%20controls%20the%20balance%20between%20receiving%20new%20features%20quickly%20and%20providing%20phases%20of%20%E2%80%9Cno%20changes%E2%80%9D%20for%20the%20IT.%20It%E2%80%99s%20important%20to%20understand%20%3C%2FSPAN%3Ethe%20%3CSPAN%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fdeployoffice%2Foverview-of-update-channels-for-office-365-proplus%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Efoundational%20concepts%3C%2FA%3E%3C%2FSPAN%3E%2C%20%3CSPAN%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fdeployoffice%2Fmanage-updates-to-office-365-proplus-with-system-center-configuration-manager%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Eways%20to%20implement%20it%3C%2FA%3E%3C%2FSPAN%3Eas%20well%20as%20the%20%3CSPAN%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fdeployoffice%2Fchange-management-for-office-365-clients%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Echange%20management%3C%2FA%3E%3C%2FSPAN%3Eview%20on%20this%20topic.%20But%20this%20post%20will%20just%20focus%20on%20the%20channel%20assignment%20done%20through%20the%20ODT.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CH2%20id%3D%22toc-hId-1817374720%22%20id%3D%22toc-hId-1817374721%22%20id%3D%22toc-hId-1817374721%22%20id%3D%22toc-hId-1817374721%22%20id%3D%22toc-hId-1817374721%22%20id%3D%22toc-hId-1817374721%22%20id%3D%22toc-hId-1817374721%22%20id%3D%22toc-hId-1817374721%22%20id%3D%22toc-hId-1817374721%22%20id%3D%22toc-hId-1817374721%22%3E%3CSPAN%3EScenario%3A%20Initial%20installation%3C%2FSPAN%3E%3C%2FH2%3E%0A%3CP%3EWhen%20you%20deploy%20Office%20365%20ProPlus%20for%20the%20first%20time%20to%20a%20device%2C%20the%20channel%20attribute%20works%20pretty%20straight%20forward%3A%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3EIf%20you%20have%20specified%20the%20channel%20(usually%20Monthly%20or%20Semi-Annual)%2C%20ODT%20will%20just%20install%20the%20latest%2Favailable%20or%20specified%20version%20of%20Office%20from%20this%20channel.%3C%2FLI%3E%0A%3CLI%3EIf%20you%20haven%E2%80%99t%20specified%20the%20channel%2C%20the%20%3CSPAN%3E%3CA%20href%3D%22https%3A%2F%2Faka.ms%2FODT%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3EOffice%20Deployment%20Tool%3C%2FA%3E%3C%2FSPAN%3E(ODT)%20will%20use%20the%20following%20%3CSPAN%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fdeployoffice%2Fconfiguration-options-for-the-office-2016-deployment-tool%23add-element%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Edefault%20values%3C%2FA%3E%3C%2FSPAN%3E%3A%0A%3CUL%3E%0A%3CLI%3ESemi-Annual%20Channel%20for%20Office%20365%20ProPlus.%3C%2FLI%3E%0A%3CLI%3ESemi-Annual%20Channel%20for%20Visio%2FProject%20when%20installed%20at%20the%20same%20time%20as%20Office.%3C%2FLI%3E%0A%3CLI%3EMonthly%20Channel%20for%20Visio%2FProject%2C%20if%20not%20installed%20alongside%20Office.%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EMost%20IT%20admins%20are%20not%20aware%20of%20the%20optional%20nature%20of%20the%20channel%20assignment%2C%20but%20there%20is%20not%20too%20much%20we%20can%20optimize%20here.%20The%20meat%20and%20potatoes%20lies%20in%20the%202%3CSUP%3End%3C%2FSUP%3Einstall%20scenario.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CH2%20id%3D%22toc-hId--734782241%22%20id%3D%22toc-hId--734782240%22%20id%3D%22toc-hId--734782240%22%20id%3D%22toc-hId--734782240%22%20id%3D%22toc-hId--734782240%22%20id%3D%22toc-hId--734782240%22%20id%3D%22toc-hId--734782240%22%20id%3D%22toc-hId--734782240%22%20id%3D%22toc-hId--734782240%22%20id%3D%22toc-hId--734782240%22%3E%3CSPAN%3EScenario%3A%20Adding%20Visio%2C%20Project%2C%20Language%20Packs%2C%20Proofing%20Tools%20or%20other%20components%3C%2FSPAN%3E%3C%2FH2%3E%0A%3CP%3E%3CSPAN%3ELet%E2%80%99s%20assume%20that%20Office%20365%20ProPlus%20is%20already%20deployed%20to%20a%20device%20and%20you%20as%20the%20IT%20admin%20has%20to%20provide%20ways%20to%20install%20additional%20Language%20Packs%2C%20Visio%2C%20Project%2C%20and%20Proofing%20Tools.%20Most%20organizations%20run%20a%20mix%20of%20SAC%20and%20SAC-T%20%2C%20more%20often%20than%20not%20you%20also%20have%20a%20small%20population%20on%20Monthly%20Channel.%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%3CSPAN%3EThis%20poses%20two%20%3CSTRONG%3Echallenges%3C%2FSTRONG%3Ewhen%20going%20with%20the%20common%20approach%20of%20specifying%20the%20Channel%20attribute%3A%20%3C%2FSPAN%3E%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3E%3CSPAN%3EYou%20end%20up%20with%20a%20high%20number%20of%20install%20packages.%20E.g.%20when%20you%20want%20to%20provide%20one%20additional%20language%20as%20well%20as%20Visio%20and%20Project%20to%20your%20users%2C%20you%20end%20up%20with%20three%20install%20packages%20multiplied%20by%20the%20number%20of%20update%20channels%20you%20support.%3C%2FSPAN%3E%3C%2FLI%3E%0A%3CLI%3E%3CSPAN%3EYour%20users%20are%20confused.%20If%20you%20want%20to%20provide%20a%20self-service%20to%20your%20users%2C%20e.g.%20through%20SCCM%20Software%20Center%2C%20they%20will%20see%20all%20these%20install%20packages%20and%20must%20pick%20the%20one%20which%20is%20matching%20their%20currently%20installed%20update%20channel.%20Most%20users%20don%E2%80%99t%20have%20a%20clue%20which%20channel%20they%20are%20on.%3C%2FSPAN%3E%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%3CSPAN%3EBut%20ODT%20to%20the%20rescue!%20A%20little%20known%20fact%20is%2C%20that%20ODT%20will%20default%20to%20the%20assigned%20channel%20of%20the%20existing%20installation%2C%20if%20the%20attribute%20is%20not%20set.%20We%20can%20leverage%20this%20behavior%20to%20remove%20the%20(perceived)%20need%20to%20build%20one%20configuration%20file%20per%20deployed%20update%20channel.%20This%20reduces%20the%20number%20of%20required%20configuration%20files%20(and%20install%20packages)%20significantly.%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%3CSPAN%3EHere%20is%20an%20example%20of%20a%20configuration%20file%20which%20adds%20Visio%20to%20an%20existing%20installation%20and%20will%20work%20for%20any%20update%20channel%3A%3C%2FSPAN%3E%3C%2FP%3E%0A%3CPRE%20class%3D%22lia-code-sample%20language-markup%22%3E%3CCODE%3E%3CCONFIGURATION%3E%0A%20%3CADD%20version%3D%22MatchInstalled%22%3E%0A%20%20%3CPRODUCT%20id%3D%22VisioProRetail%22%3E%0A%20%20%20%3CLANGUAGE%20id%3D%22MatchInstalled%22%20targetproduct%3D%22O365ProPlusRetail%22%3E%3C%2FLANGUAGE%3E%20%0A%20%20%3C%2FPRODUCT%3E%0A%20%3C%2FADD%3E%0A%3C%2FCONFIGURATION%3E%0A%3C%2FCODE%3E%3C%2FPRE%3E%0A%3CP%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%3CSPAN%3EAbove%20XML%20will%20do%20the%20following%20for%20you%3A%3C%2FSPAN%3E%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3E%3CSPAN%3EAs%20OfficeClientEdition%20is%20not%20specified%2C%20the%20ODT%20will%20automatically%20match%20the%20new%20install%20to%20the%20already%20installed%20product.%20So%20this%20is%20a%20x86%2Fx64%20universal%20configuration%20(%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FOffice-365-ProPlus%2FInsights-into-OfficeClientEdition-and-how-to-make-it-work-for%2Fm-p%2F767577%22%20target%3D%22_blank%22%3Eread%20more%20about%20it%20here%3C%2FA%3E).%3C%2FSPAN%3E%3C%2FLI%3E%0A%3CLI%3E%3CSPAN%3EThe%20to-be%20installed%20version%20will%20match%20the%20installed%20one.%20Even%20if%20a%20newer%20version%20is%20available%20e.g.%20on%20the%20OfficeCDN%2C%20it%20will%20not%20do%20an%20implicit%20update%20(Read%20more%20about%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FOffice-365-ProPlus%2FNew-feature-Make-changes-to-Office-deployments-without-changing%2Fm-p%2F481948%2Fthread-id%2F655%22%20target%3D%22_blank%22%3EVersion%3D%22MatchInstalled%22%3C%2FA%3E).%3C%2FSPAN%3E%3C%2FLI%3E%0A%3CLI%3E%3CSPAN%3EVisio%20will%20be%20deployed%20with%20the%20very%20same%20languages%20as%20Office%20365%20ProPlus%20is%20already%20installed%20with.%20For%20more%20details%20please%20check%20out%20this%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FOffice-365-ProPlus%2FDynamically-match-already-existing-languages-when-installing%2Fm-p%2F716927%22%20target%3D%22_blank%22%3Eblog%20post%3C%2FA%3E.%3C%2FSPAN%3E%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%3CSPAN%3ESo%2C%20we%20have%20a%20dynamic%20configuration%20file%20which%20has%20no%20hard-coded%20architecture%2C%20languages%2C%20update%20channel%20or%20version.%20You%20can%20build%20this%20e.g.%20SCCM%20application%20once%20and%20use%20it%20for%20all%20update%20channels.%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CH2%20id%3D%22toc-hId-1008028094%22%20id%3D%22toc-hId-1008028095%22%20id%3D%22toc-hId-1008028095%22%20id%3D%22toc-hId-1008028095%22%20id%3D%22toc-hId-1008028095%22%20id%3D%22toc-hId-1008028095%22%20id%3D%22toc-hId-1008028095%22%20id%3D%22toc-hId-1008028095%22%20id%3D%22toc-hId-1008028095%22%20id%3D%22toc-hId-1008028095%22%3E%3CSPAN%3EBenefits%3C%2FSPAN%3E%3C%2FH2%3E%0A%3CP%3EIn%20the%20past%20configuration%20files%20were%20static%2C%20each%20covering%20one%20specific%20scenario%2Fconfiguration.%20By%20using%20new%20features%20like%20Version%3DMatchInstalled%2C%20Language%3DMatchInstalled%20together%20with%20dynamic%20OfficeClientEdition%20and%20update%20channel%2C%20you%20can%20build%20universal%20configuration%20files%20which%20cover%20multiple%20scenarios.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThis%20resolves%20the%20two%20issues%20described%20above%3A%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3EYou%20only%20need%20one%20installation%20package%20(e.g.%20an%20SCCM%20app)%20per%20component.%20For%20most%20environments%20(running%20MC%2C%20SAC%20and%20SAC-T)%20this%20reduces%20the%20effort%20by%2066%25%2C%20because%20you%20don%E2%80%99t%20have%20to%20build%20each%20package%20three%20times.%3C%2FLI%3E%0A%3CLI%3EYour%20users%20will%20be%20happy%2C%20as%20they%20can%20easily%20identify%20what%20they%20need%20from%20the%20Software%20Center.%20They%20don%E2%80%99t%20have%20to%20worry%20about%20which%20update%20channels%20they%20are%20on.%20It%20just%20works.%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CH2%20id%3D%22toc-hId--1544128867%22%20id%3D%22toc-hId--1544128866%22%20id%3D%22toc-hId--1544128866%22%20id%3D%22toc-hId--1544128866%22%20id%3D%22toc-hId--1544128866%22%20id%3D%22toc-hId--1544128866%22%20id%3D%22toc-hId--1544128866%22%20id%3D%22toc-hId--1544128866%22%20id%3D%22toc-hId--1544128866%22%20id%3D%22toc-hId--1544128866%22%3E%3CSPAN%3EPrerequisites%3C%2FSPAN%3E%3C%2FH2%3E%0A%3CUL%3E%0A%3CLI%3EThe%20ODT%20must%20be%20able%20to%20locate%20the%20matching%20source%20files%20on%20the%20Office%20CDN.%20Including%20the%20source%20files%20in%20the%20SCCM%20app%20would%20require%20having%20the%20exactly%20matching%20version%20included.%20Same%20goes%20for%20network%20shares%2Flocal%20folders.%20We%20recommend%20using%20the%20Office%20CDN%20instead.%3C%2FLI%3E%0A%3CLI%3EI%20always%20recommend%20to%20also%20make%20sure%20that%20you%20use%20the%20latest%20ODT%20available.%20There%20is%20no%20specific%20min.%20version%20for%20the%20Channel-attribute%2C%20but%20it%20is%20a%20good%20practice%20to%20always%20update%20the%20ODT%20when%20you%E2%80%99re%20touching%20it%20anyways.%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CH2%20id%3D%22toc-hId-198681468%22%20id%3D%22toc-hId-198681469%22%20id%3D%22toc-hId-198681469%22%20id%3D%22toc-hId-198681469%22%20id%3D%22toc-hId-198681469%22%20id%3D%22toc-hId-198681469%22%20id%3D%22toc-hId-198681469%22%20id%3D%22toc-hId-198681469%22%20id%3D%22toc-hId-198681469%22%20id%3D%22toc-hId-198681469%22%3EThe%20Author%3C%2FH2%3E%0A%3CP%3EThis%20blog%20post%20is%20brought%20to%20you%20by%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F6347%22%20target%3D%22_blank%22%3E%40Martin%20Nothnagel%3C%2FA%3E%26nbsp%3B%2C%20a%20senior%20ProPlus%20deployment%20expert%20and%20ProPlus%20Ranger%20at%20Microsoft.%20Feel%20free%20to%20share%20your%20questions%20and%20feedback%20in%20the%20comments%20below.%3C%2FP%3E%0A%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIn%20nearly%20every%20configuration%20file%20(aka%20config.xml)%20you%20will%20find%20this%20attribute%2C%20but%20have%20you%20known%20that%20this%20is%20actually%20an%20optional%20attribute%20and%20can%20be%20used%20to%20build%20leaner%20deployments%20which%20require%20less%20maintenance%3F%20I%20will%20walk%20you%20through%20the%20steps%20on%20how%20the%20Channel-attribute%20works%20during%20the%20initial%20installation%20of%20Office%20365%20Client%20Apps%20and%20how%20to%20leverage%20it%20for%20reducing%20your%20effort%20when%20building%20sub-sequent%20installs%20(Project%2C%20Visio%2C%20%E2%80%A6).%3C%2FP%3E%0A%3CP%3E%3CSPAN%3EWhen%20designing%20an%20Office%20365%20ProPlus%20deployment%2C%20especially%20in%20larger%20organizations%2C%20the%20%E2%80%9CUpdate%20Channel%E2%80%9D%20to%20use%20is%20an%20important%20factor.%20It%20controls%20the%20balance%20between%20receiving%20new%20features%20quickly%20and%20providing%20phases%20of%20%E2%80%9Cno%20changes%E2%80%9D%20for%20the%20IT.%20It%E2%80%99s%20important%20to%20understand%20%3C%2FSPAN%3Ethe%20%3CSPAN%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fdeployoffice%2Foverview-of-update-channels-for-office-365-proplus%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Efoundational%20concepts%3C%2FA%3E%3C%2FSPAN%3E%2C%20%3CSPAN%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fdeployoffice%2Fmanage-updates-to-office-365-proplus-with-system-center-configuration-manager%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Eways%20to%20implement%20it%3C%2FA%3E%3C%2FSPAN%3Eas%20well%20as%20the%20%3CSPAN%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fdeployoffice%2Fchange-management-for-office-365-clients%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Echange%20management%3C%2FA%3E%3C%2FSPAN%3Eview%20on%20this%20topic.%20But%20this%20post%20will%20just%20focus%20on%20the%20channel%20assignment%20done%20through%20the%20ODT.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CH2%20id%3D%22toc-hId-1817374721%22%20id%3D%22toc-hId-1941491804%22%20id%3D%22toc-hId-1941491804%22%20id%3D%22toc-hId-1941491804%22%20id%3D%22toc-hId-1941491804%22%20id%3D%22toc-hId-1941491804%22%20id%3D%22toc-hId-1941491804%22%20id%3D%22toc-hId-1941491804%22%20id%3D%22toc-hId-1941491804%22%3E%3CSPAN%3EScenario%3A%20Initial%20installation%3C%2FSPAN%3E%3C%2FH2%3E%0A%3CP%3EWhen%20you%20deploy%20Office%20365%20ProPlus%20for%20the%20first%20time%20to%20a%20device%2C%20the%20channel%20attribute%20works%20pretty%20straight%20forward%3A%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3EIf%20you%20have%20specified%20the%20channel%20(usually%20Monthly%20or%20Semi-Annual)%2C%20ODT%20will%20just%20install%20the%20latest%2Favailable%20or%20specified%20version%20of%20Office%20from%20this%20channel.%3C%2FLI%3E%0A%3CLI%3EIf%20you%20haven%E2%80%99t%20specified%20the%20channel%2C%20the%20%3CSPAN%3E%3CA%20href%3D%22https%3A%2F%2Faka.ms%2FODT%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3EOffice%20Deployment%20Tool%3C%2FA%3E%3C%2FSPAN%3E(ODT)%20will%20use%20the%20following%20%3CSPAN%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fdeployoffice%2Fconfiguration-options-for-the-office-2016-deployment-tool%23add-element%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Edefault%20values%3C%2FA%3E%3C%2FSPAN%3E%3A%0A%3CUL%3E%0A%3CLI%3ESemi-Annual%20Channel%20for%20Office%20365%20ProPlus.%3C%2FLI%3E%0A%3CLI%3ESemi-Annual%20Channel%20for%20Visio%2FProject%20when%20installed%20at%20the%20same%20time%20as%20Office.%3C%2FLI%3E%0A%3CLI%3EMonthly%20Channel%20for%20Visio%2FProject%2C%20if%20not%20installed%20alongside%20Office.%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EMost%20IT%20admins%20are%20not%20aware%20of%20the%20optional%20nature%20of%20the%20channel%20assignment%2C%20but%20there%20is%20not%20too%20much%20we%20can%20optimize%20here.%20The%20meat%20and%20potatoes%20lies%20in%20the%202%3CSUP%3End%3C%2FSUP%3Einstall%20scenario.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CH2%20id%3D%22toc-hId--734782240%22%20id%3D%22toc-hId--610665157%22%20id%3D%22toc-hId--610665157%22%20id%3D%22toc-hId--610665157%22%20id%3D%22toc-hId--610665157%22%20id%3D%22toc-hId--610665157%22%20id%3D%22toc-hId--610665157%22%20id%3D%22toc-hId--610665157%22%20id%3D%22toc-hId--610665157%22%3E%3CSPAN%3EScenario%3A%20Adding%20Visio%2C%20Project%2C%20Language%20Packs%2C%20Proofing%20Tools%20or%20other%20components%3C%2FSPAN%3E%3C%2FH2%3E%0A%3CP%3E%3CSPAN%3ELet%E2%80%99s%20assume%20that%20Office%20365%20ProPlus%20is%20already%20deployed%20to%20a%20device%20and%20you%20as%20the%20IT%20admin%20has%20to%20provide%20ways%20to%20install%20additional%20Language%20Packs%2C%20Visio%2C%20Project%2C%20and%20Proofing%20Tools.%20Most%20organizations%20run%20a%20mix%20of%20SAC%20and%20SAC-T%20%2C%20more%20often%20than%20not%20you%20also%20have%20a%20small%20population%20on%20Monthly%20Channel.%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%3CSPAN%3EThis%20poses%20two%20%3CSTRONG%3Echallenges%3C%2FSTRONG%3Ewhen%20going%20with%20the%20common%20approach%20of%20specifying%20the%20Channel%20attribute%3A%20%3C%2FSPAN%3E%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3E%3CSPAN%3EYou%20end%20up%20with%20a%20high%20number%20of%20install%20packages.%20E.g.%20when%20you%20want%20to%20provide%20one%20additional%20language%20as%20well%20as%20Visio%20and%20Project%20to%20your%20users%2C%20you%20end%20up%20with%20three%20install%20packages%20multiplied%20by%20the%20number%20of%20update%20channels%20you%20support.%3C%2FSPAN%3E%3C%2FLI%3E%0A%3CLI%3E%3CSPAN%3EYour%20users%20are%20confused.%20If%20you%20want%20to%20provide%20a%20self-service%20to%20your%20users%2C%20e.g.%20through%20SCCM%20Software%20Center%2C%20they%20will%20see%20all%20these%20install%20packages%20and%20must%20pick%20the%20one%20which%20is%20matching%20their%20currently%20installed%20update%20channel.%20Most%20users%20don%E2%80%99t%20have%20a%20clue%20which%20channel%20they%20are%20on.%3C%2FSPAN%3E%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%3CSPAN%3EBut%20ODT%20to%20the%20rescue!%20A%20little%20known%20fact%20is%2C%20that%20ODT%20will%20default%20to%20the%20assigned%20channel%20of%20the%20existing%20installation%2C%20if%20the%20attribute%20is%20not%20set.%20We%20can%20leverage%20this%20behavior%20to%20remove%20the%20(perceived)%20need%20to%20build%20one%20configuration%20file%20per%20deployed%20update%20channel.%20This%20reduces%20the%20number%20of%20required%20configuration%20files%20(and%20install%20packages)%20significantly.%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%3CSPAN%3EHere%20is%20an%20example%20of%20a%20configuration%20file%20which%20adds%20Visio%20to%20an%20existing%20installation%20and%20will%20work%20for%20any%20update%20channel%3A%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CPRE%20class%3D%22lia-code-sample%20language-markup%22%3E%3CCODE%3E%3CCONFIGURATION%3E%0A%20%3CADD%20version%3D%22MatchInstalled%22%3E%0A%20%20%3CPRODUCT%20id%3D%22VisioProRetail%22%3E%0A%20%20%20%3CLANGUAGE%20id%3D%22MatchInstalled%22%20targetproduct%3D%22O365ProPlusRetail%22%3E%3C%2FLANGUAGE%3E%20%0A%20%20%3C%2FPRODUCT%3E%0A%20%3C%2FADD%3E%0A%3C%2FCONFIGURATION%3E%0A%3C%2FCODE%3E%3C%2FPRE%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%3CSPAN%3EAbove%20XML%20will%20do%20the%20following%20for%20you%3A%3C%2FSPAN%3E%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3E%3CSPAN%3EAs%20OfficeClientEdition%20is%20not%20specified%2C%20the%20ODT%20will%20automatically%20match%20the%20new%20install%20to%20the%20already%20installed%20product.%20So%20this%20is%20a%20x86%2Fx64%20universal%20configuration%20(%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FOffice-365-ProPlus%2FInsights-into-OfficeClientEdition-and-how-to-make-it-work-for%2Fm-p%2F767577%22%20target%3D%22_blank%22%20rel%3D%22noopener%22%3Eread%20more%20about%20it%20here%3C%2FA%3E).%3C%2FSPAN%3E%3C%2FLI%3E%0A%3CLI%3E%3CSPAN%3EThe%20to-be%20installed%20version%20will%20match%20the%20installed%20one.%20Even%20if%20a%20newer%20version%20is%20available%20e.g.%20on%20the%20OfficeCDN%2C%20it%20will%20not%20do%20an%20implicit%20update%20(Read%20more%20about%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FOffice-365-ProPlus%2FNew-feature-Make-changes-to-Office-deployments-without-changing%2Fm-p%2F481948%2Fthread-id%2F655%22%20target%3D%22_blank%22%20rel%3D%22noopener%22%3EVersion%3D%22MatchInstalled%22%3C%2FA%3E).%3C%2FSPAN%3E%3C%2FLI%3E%0A%3CLI%3E%3CSPAN%3EVisio%20will%20be%20deployed%20with%20the%20very%20same%20languages%20as%20Office%20365%20ProPlus%20is%20already%20installed%20with.%20For%20more%20details%20please%20check%20out%20this%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FOffice-365-ProPlus%2FDynamically-match-already-existing-languages-when-installing%2Fm-p%2F716927%22%20target%3D%22_blank%22%20rel%3D%22noopener%22%3Eblog%20post%3C%2FA%3E.%3C%2FSPAN%3E%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%3CSPAN%3ESo%2C%20we%20have%20a%20dynamic%20configuration%20file%20which%20has%20no%20hard-coded%20architecture%2C%20languages%2C%20update%20channel%20or%20version.%20You%20can%20build%20this%20e.g.%20SCCM%20application%20once%20and%20use%20it%20for%20all%20update%20channels.%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CH2%20id%3D%22toc-hId-1008028095%22%20id%3D%22toc-hId-1132145178%22%20id%3D%22toc-hId-1132145178%22%20id%3D%22toc-hId-1132145178%22%20id%3D%22toc-hId-1132145178%22%20id%3D%22toc-hId-1132145178%22%20id%3D%22toc-hId-1132145178%22%20id%3D%22toc-hId-1132145178%22%20id%3D%22toc-hId-1132145178%22%3E%3CSPAN%3EBenefits%3C%2FSPAN%3E%3C%2FH2%3E%0A%3CP%3EIn%20the%20past%20configuration%20files%20were%20static%2C%20each%20covering%20one%20specific%20scenario%2Fconfiguration.%20By%20using%20new%20features%20like%20Version%3DMatchInstalled%2C%20Language%3DMatchInstalled%20together%20with%20dynamic%20OfficeClientEdition%20and%20update%20channel%2C%20you%20can%20build%20universal%20configuration%20files%20which%20cover%20multiple%20scenarios.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThis%20resolves%20the%20two%20issues%20described%20above%3A%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3EYou%20only%20need%20one%20installation%20package%20(e.g.%20an%20SCCM%20app)%20per%20component.%20For%20most%20environments%20(running%20MC%2C%20SAC%20and%20SAC-T)%20this%20reduces%20the%20effort%20by%2066%25%2C%20because%20you%20don%E2%80%99t%20have%20to%20build%20each%20package%20three%20times.%3C%2FLI%3E%0A%3CLI%3EYour%20users%20will%20be%20happy%2C%20as%20they%20can%20easily%20identify%20what%20they%20need%20from%20the%20Software%20Center.%20They%20don%E2%80%99t%20have%20to%20worry%20about%20which%20update%20channels%20they%20are%20on.%20It%20just%20works.%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CH2%20id%3D%22toc-hId--1544128866%22%20id%3D%22toc-hId--1420011783%22%20id%3D%22toc-hId--1420011783%22%20id%3D%22toc-hId--1420011783%22%20id%3D%22toc-hId--1420011783%22%20id%3D%22toc-hId--1420011783%22%20id%3D%22toc-hId--1420011783%22%20id%3D%22toc-hId--1420011783%22%20id%3D%22toc-hId--1420011783%22%3E%3CSPAN%3EPrerequisites%3C%2FSPAN%3E%3C%2FH2%3E%0A%3CUL%3E%0A%3CLI%3EThe%20ODT%20must%20be%20able%20to%20locate%20the%20matching%20source%20files%20on%20the%20Office%20CDN.%20Including%20the%20source%20files%20in%20the%20SCCM%20app%20would%20require%20having%20the%20exactly%20matching%20version%20included.%20Same%20goes%20for%20network%20shares%2Flocal%20folders.%20We%20recommend%20using%20the%20Office%20CDN%20instead.%3C%2FLI%3E%0A%3CLI%3EI%20always%20recommend%20to%20also%20make%20sure%20that%20you%20use%20the%20latest%20ODT%20available.%20There%20is%20no%20specific%20min.%20version%20for%20the%20Channel-attribute%2C%20but%20it%20is%20a%20good%20practice%20to%20always%20update%20the%20ODT%20when%20you%E2%80%99re%20touching%20it%20anyways.%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CH2%20id%3D%22toc-hId-198681469%22%20id%3D%22toc-hId-322798552%22%20id%3D%22toc-hId-322798552%22%20id%3D%22toc-hId-322798552%22%20id%3D%22toc-hId-322798552%22%20id%3D%22toc-hId-322798552%22%20id%3D%22toc-hId-322798552%22%20id%3D%22toc-hId-322798552%22%20id%3D%22toc-hId-322798552%22%3EThe%20Author%3C%2FH2%3E%0A%3CP%3EThis%20blog%20post%20is%20brought%20to%20you%20by%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F6347%22%20target%3D%22_blank%22%3E%40Martin%20Nothnagel%3C%2FA%3E%26nbsp%3B%2C%20a%20senior%20ProPlus%20deployment%20expert%20and%20ProPlus%20Ranger%20at%20Microsoft.%20Feel%20free%20to%20share%20your%20questions%20and%20feedback%20in%20the%20comments%20below.%3C%2FP%3E%0A%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIn%20nearly%20every%20configuration%20file%20(aka%20config.xml)%20you%20will%20find%20this%20attribute%2C%20but%20have%20you%20known%20that%20this%20is%20actually%20an%20optional%20attribute%20and%20can%20be%20used%20to%20build%20leaner%20deployments%20which%20require%20less%20maintenance%3F%20I%20will%20walk%20you%20through%20the%20steps%20on%20how%20the%20Channel-attribute%20works%20during%20the%20initial%20installation%20of%20Office%20365%20Client%20Apps%20and%20how%20to%20leverage%20it%20for%20reducing%20your%20effort%20when%20building%20sub-sequent%20installs%20(Project%2C%20Visio%2C%20%E2%80%A6).%3C%2FP%3E%0A%3CP%3E%3CSPAN%3EWhen%20designing%20an%20Office%20365%20ProPlus%20deployment%2C%20especially%20in%20larger%20organizations%2C%20the%20%E2%80%9CUpdate%20Channel%E2%80%9D%20to%20use%20is%20an%20important%20factor.%20It%20controls%20the%20balance%20between%20receiving%20new%20features%20quickly%20and%20providing%20phases%20of%20%E2%80%9Cno%20changes%E2%80%9D%20for%20the%20IT.%20It%E2%80%99s%20important%20to%20understand%20%3C%2FSPAN%3Ethe%20%3CSPAN%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fdeployoffice%2Foverview-of-update-channels-for-office-365-proplus%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Efoundational%20concepts%3C%2FA%3E%3C%2FSPAN%3E%2C%20%3CSPAN%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fdeployoffice%2Fmanage-updates-to-office-365-proplus-with-system-center-configuration-manager%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Eways%20to%20implement%20it%3C%2FA%3E%3C%2FSPAN%3Eas%20well%20as%20the%20%3CSPAN%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fdeployoffice%2Fchange-management-for-office-365-clients%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Echange%20management%3C%2FA%3E%3C%2FSPAN%3Eview%20on%20this%20topic.%20But%20this%20post%20will%20just%20focus%20on%20the%20channel%20assignment%20done%20through%20the%20ODT.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CH2%20id%3D%22toc-hId-1817374721%22%20id%3D%22toc-hId--1344081844%22%20id%3D%22toc-hId--1344081844%22%20id%3D%22toc-hId--1344081844%22%20id%3D%22toc-hId--1344081844%22%20id%3D%22toc-hId--1344081844%22%20id%3D%22toc-hId--1344081844%22%20id%3D%22toc-hId--1344081844%22%3E%3CSPAN%3EScenario%3A%20Initial%20installation%3C%2FSPAN%3E%3C%2FH2%3E%0A%3CP%3EWhen%20you%20deploy%20Office%20365%20ProPlus%20for%20the%20first%20time%20to%20a%20device%2C%20the%20channel%20attribute%20works%20pretty%20straight%20forward%3A%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3EIf%20you%20have%20specified%20the%20channel%20(usually%20Monthly%20or%20Semi-Annual)%2C%20ODT%20will%20just%20install%20the%20latest%2Favailable%20or%20specified%20version%20of%20Office%20from%20this%20channel.%3C%2FLI%3E%0A%3CLI%3EIf%20you%20haven%E2%80%99t%20specified%20the%20channel%2C%20the%20%3CSPAN%3E%3CA%20href%3D%22https%3A%2F%2Faka.ms%2FODT%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3EOffice%20Deployment%20Tool%3C%2FA%3E%3C%2FSPAN%3E(ODT)%20will%20use%20the%20following%20%3CSPAN%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fdeployoffice%2Fconfiguration-options-for-the-office-2016-deployment-tool%23add-element%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Edefault%20values%3C%2FA%3E%3C%2FSPAN%3E%3A%0A%3CUL%3E%0A%3CLI%3ESemi-Annual%20Channel%20for%20Office%20365%20ProPlus.%3C%2FLI%3E%0A%3CLI%3ESemi-Annual%20Channel%20for%20Visio%2FProject%20when%20installed%20at%20the%20same%20time%20as%20Office.%3C%2FLI%3E%0A%3CLI%3EMonthly%20Channel%20for%20Visio%2FProject%2C%20if%20not%20installed%20alongside%20Office.%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EMost%20IT%20admins%20are%20not%20aware%20of%20the%20optional%20nature%20of%20the%20channel%20assignment%2C%20but%20there%20is%20not%20too%20much%20we%20can%20optimize%20here.%20The%20meat%20and%20potatoes%20lies%20in%20the%202%3CSUP%3End%3C%2FSUP%3Einstall%20scenario.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CH2%20id%3D%22toc-hId--734782240%22%20id%3D%22toc-hId-398728491%22%20id%3D%22toc-hId-398728491%22%20id%3D%22toc-hId-398728491%22%20id%3D%22toc-hId-398728491%22%20id%3D%22toc-hId-398728491%22%20id%3D%22toc-hId-398728491%22%20id%3D%22toc-hId-398728491%22%3E%3CSPAN%3EScenario%3A%20Adding%20Visio%2C%20Project%2C%20Language%20Packs%2C%20Proofing%20Tools%20or%20other%20components%3C%2FSPAN%3E%3C%2FH2%3E%0A%3CP%3E%3CSPAN%3ELet%E2%80%99s%20assume%20that%20Office%20365%20ProPlus%20is%20already%20deployed%20to%20a%20device%20and%20you%20as%20the%20IT%20admin%20has%20to%20provide%20ways%20to%20install%20additional%20Language%20Packs%2C%20Visio%2C%20Project%2C%20and%20Proofing%20Tools.%20Most%20organizations%20run%20a%20mix%20of%20SAC%20and%20SAC-T%20%2C%20more%20often%20than%20not%20you%20also%20have%20a%20small%20population%20on%20Monthly%20Channel.%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%3CSPAN%3EThis%20poses%20two%20%3CSTRONG%3Echallenges%3C%2FSTRONG%3Ewhen%20going%20with%20the%20common%20approach%20of%20specifying%20the%20Channel%20attribute%3A%20%3C%2FSPAN%3E%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3E%3CSPAN%3EYou%20end%20up%20with%20a%20high%20number%20of%20install%20packages.%20E.g.%20when%20you%20want%20to%20provide%20one%20additional%20language%20as%20well%20as%20Visio%20and%20Project%20to%20your%20users%2C%20you%20end%20up%20with%20three%20install%20packages%20multiplied%20by%20the%20number%20of%20update%20channels%20you%20support.%3C%2FSPAN%3E%3C%2FLI%3E%0A%3CLI%3E%3CSPAN%3EYour%20users%20are%20confused.%20If%20you%20want%20to%20provide%20a%20self-service%20to%20your%20users%2C%20e.g.%20through%20SCCM%20Software%20Center%2C%20they%20will%20see%20all%20these%20install%20packages%20and%20must%20pick%20the%20one%20which%20is%20matching%20their%20currently%20installed%20update%20channel.%20Most%20users%20don%E2%80%99t%20have%20a%20clue%20which%20channel%20they%20are%20on.%3C%2FSPAN%3E%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%3CSPAN%3EBut%20ODT%20to%20the%20rescue!%20A%20little%20known%20fact%20is%2C%20that%20ODT%20will%20default%20to%20the%20assigned%20channel%20of%20the%20existing%20installation%2C%20if%20the%20attribute%20is%20not%20set.%20We%20can%20leverage%20this%20behavior%20to%20remove%20the%20(perceived)%20need%20to%20build%20one%20configuration%20file%20per%20deployed%20update%20channel.%20This%20reduces%20the%20number%20of%20required%20configuration%20files%20(and%20install%20packages)%20significantly.%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%3CSPAN%3EHere%20is%20an%20example%20of%20a%20configuration%20file%20which%20adds%20Visio%20to%20an%20existing%20installation%20and%20will%20work%20for%20any%20update%20channel%3A%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CPRE%20class%3D%22lia-code-sample%20language-markup%22%3E%3CCODE%3E%3CCONFIGURATION%3E%0A%20%3CADD%20version%3D%22MatchInstalled%22%3E%0A%20%20%3CPRODUCT%20id%3D%22VisioProRetail%22%3E%0A%20%20%20%3CLANGUAGE%20id%3D%22MatchInstalled%22%20targetproduct%3D%22O365ProPlusRetail%22%3E%3C%2FLANGUAGE%3E%20%0A%20%20%3C%2FPRODUCT%3E%0A%20%3C%2FADD%3E%0A%3C%2FCONFIGURATION%3E%0A%3C%2FCODE%3E%3C%2FPRE%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%3CSPAN%3EAbove%20XML%20will%20do%20the%20following%20for%20you%3A%3C%2FSPAN%3E%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3E%3CSPAN%3EAs%20OfficeClientEdition%20is%20not%20specified%2C%20the%20ODT%20will%20automatically%20match%20the%20new%20install%20to%20the%20already%20installed%20product.%20So%20this%20is%20a%20x86%2Fx64%20universal%20configuration%20(%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FOffice-365-ProPlus%2FInsights-into-OfficeClientEdition-and-how-to-make-it-work-for%2Fm-p%2F767577%22%20target%3D%22_blank%22%20rel%3D%22noopener%22%3Eread%20more%20about%20it%20here%3C%2FA%3E).%3C%2FSPAN%3E%3C%2FLI%3E%0A%3CLI%3E%3CSPAN%3EThe%20to-be%20installed%20version%20will%20match%20the%20installed%20one.%20Even%20if%20a%20newer%20version%20is%20available%20e.g.%20on%20the%20OfficeCDN%2C%20it%20will%20not%20do%20an%20implicit%20update%20(Read%20more%20about%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FOffice-365-ProPlus%2FNew-feature-Make-changes-to-Office-deployments-without-changing%2Fm-p%2F481948%2Fthread-id%2F655%22%20target%3D%22_blank%22%20rel%3D%22noopener%22%3EVersion%3D%22MatchInstalled%22%3C%2FA%3E).%3C%2FSPAN%3E%3C%2FLI%3E%0A%3CLI%3E%3CSPAN%3EVisio%20will%20be%20deployed%20with%20the%20very%20same%20languages%20as%20Office%20365%20ProPlus%20is%20already%20installed%20with.%20For%20more%20details%20please%20check%20out%20this%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FOffice-365-ProPlus%2FDynamically-match-already-existing-languages-when-installing%2Fm-p%2F716927%22%20target%3D%22_blank%22%20rel%3D%22noopener%22%3Eblog%20post%3C%2FA%3E.%3C%2FSPAN%3E%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%3CSPAN%3ESo%2C%20we%20have%20a%20dynamic%20configuration%20file%20which%20has%20no%20hard-coded%20architecture%2C%20languages%2C%20update%20channel%20or%20version.%20You%20can%20build%20this%20e.g.%20SCCM%20application%20once%20and%20use%20it%20for%20all%20update%20channels.%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CH2%20id%3D%22toc-hId-1008028095%22%20id%3D%22toc-hId-2141538826%22%20id%3D%22toc-hId-2141538826%22%20id%3D%22toc-hId-2141538826%22%20id%3D%22toc-hId-2141538826%22%20id%3D%22toc-hId-2141538826%22%20id%3D%22toc-hId-2141538826%22%20id%3D%22toc-hId-2141538826%22%3E%3CSPAN%3EBenefits%3C%2FSPAN%3E%3C%2FH2%3E%0A%3CP%3EIn%20the%20past%20configuration%20files%20were%20static%2C%20each%20covering%20one%20specific%20scenario%2Fconfiguration.%20By%20using%20new%20features%20like%20Version%3DMatchInstalled%2C%20Language%3DMatchInstalled%20together%20with%20dynamic%20OfficeClientEdition%20and%20update%20channel%2C%20you%20can%20build%20universal%20configuration%20files%20which%20cover%20multiple%20scenarios.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThis%20resolves%20the%20two%20issues%20described%20above%3A%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3EYou%20only%20need%20one%20installation%20package%20(e.g.%20an%20SCCM%20app)%20per%20component.%20For%20most%20environments%20(running%20MC%2C%20SAC%20and%20SAC-T)%20this%20reduces%20the%20effort%20by%2066%25%2C%20because%20you%20don%E2%80%99t%20have%20to%20build%20each%20package%20three%20times.%3C%2FLI%3E%0A%3CLI%3EYour%20users%20will%20be%20happy%2C%20as%20they%20can%20easily%20identify%20what%20they%20need%20from%20the%20Software%20Center.%20They%20don%E2%80%99t%20have%20to%20worry%20about%20which%20update%20channels%20they%20are%20on.%20It%20just%20works.%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CH2%20id%3D%22toc-hId--1544128866%22%20id%3D%22toc-hId--410618135%22%20id%3D%22toc-hId--410618135%22%20id%3D%22toc-hId--410618135%22%20id%3D%22toc-hId--410618135%22%20id%3D%22toc-hId--410618135%22%20id%3D%22toc-hId--410618135%22%20id%3D%22toc-hId--410618135%22%3E%3CSPAN%3EPrerequisites%3C%2FSPAN%3E%3C%2FH2%3E%0A%3CUL%3E%0A%3CLI%3EThe%20ODT%20must%20be%20able%20to%20locate%20the%20matching%20source%20files%20on%20the%20Office%20CDN.%20Including%20the%20source%20files%20in%20the%20SCCM%20app%20would%20require%20having%20the%20exactly%20matching%20version%20included.%20Same%20goes%20for%20network%20shares%2Flocal%20folders.%20We%20recommend%20using%20the%20Office%20CDN%20instead.%3C%2FLI%3E%0A%3CLI%3EI%20always%20recommend%20to%20also%20make%20sure%20that%20you%20use%20the%20latest%20ODT%20available.%20There%20is%20no%20specific%20min.%20version%20for%20the%20Channel-attribute%2C%20but%20it%20is%20a%20good%20practice%20to%20always%20update%20the%20ODT%20when%20you%E2%80%99re%20touching%20it%20anyways.%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CH2%20id%3D%22toc-hId-198681469%22%20id%3D%22toc-hId-1332192200%22%20id%3D%22toc-hId-1332192200%22%20id%3D%22toc-hId-1332192200%22%20id%3D%22toc-hId-1332192200%22%20id%3D%22toc-hId-1332192200%22%20id%3D%22toc-hId-1332192200%22%20id%3D%22toc-hId-1332192200%22%3EThe%20Author%3C%2FH2%3E%0A%3CP%3EThis%20blog%20post%20is%20brought%20to%20you%20by%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F6347%22%20target%3D%22_blank%22%3E%40Martin%20Nothnagel%3C%2FA%3E%26nbsp%3B%2C%20a%20senior%20ProPlus%20deployment%20expert%20and%20ProPlus%20Ranger%20at%20Microsoft.%20Feel%20free%20to%20share%20your%20questions%20and%20feedback%20in%20the%20comments%20below.%3C%2FP%3E%0A%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIn%20nearly%20every%20configuration%20file%20(aka%20config.xml)%20you%20will%20find%20this%20attribute%2C%20but%20have%20you%20known%20that%20this%20is%20actually%20an%20optional%20attribute%20and%20can%20be%20used%20to%20build%20leaner%20deployments%20which%20require%20less%20maintenance%3F%20I%20will%20walk%20you%20through%20the%20steps%20on%20how%20the%20Channel-attribute%20works%20during%20the%20initial%20installation%20of%20Office%20365%20Client%20Apps%20and%20how%20to%20leverage%20it%20for%20reducing%20your%20effort%20when%20building%20sub-sequent%20installs%20(Project%2C%20Visio%2C%20%E2%80%A6).%3C%2FP%3E%0A%3CP%3E%3CSPAN%3EWhen%20designing%20an%20Office%20365%20ProPlus%20deployment%2C%20especially%20in%20larger%20organizations%2C%20the%20%E2%80%9CUpdate%20Channel%E2%80%9D%20to%20use%20is%20an%20important%20factor.%20It%20controls%20the%20balance%20between%20receiving%20new%20features%20quickly%20and%20providing%20phases%20of%20%E2%80%9Cno%20changes%E2%80%9D%20for%20the%20IT.%20It%E2%80%99s%20important%20to%20understand%20%3C%2FSPAN%3Ethe%20%3CSPAN%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fdeployoffice%2Foverview-of-update-channels-for-office-365-proplus%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Efoundational%20concepts%3C%2FA%3E%3C%2FSPAN%3E%2C%20%3CSPAN%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fdeployoffice%2Fmanage-updates-to-office-365-proplus-with-system-center-configuration-manager%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Eways%20to%20implement%20it%3C%2FA%3E%3C%2FSPAN%3Eas%20well%20as%20the%20%3CSPAN%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fdeployoffice%2Fchange-management-for-office-365-clients%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Echange%20management%3C%2FA%3E%3C%2FSPAN%3Eview%20on%20this%20topic.%20But%20this%20post%20will%20just%20focus%20on%20the%20channel%20assignment%20done%20through%20the%20ODT.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CH2%20id%3D%22toc-hId-1817374721%22%20id%3D%22toc-hId--1219964761%22%20id%3D%22toc-hId--1219964761%22%20id%3D%22toc-hId--1219964761%22%20id%3D%22toc-hId--1219964761%22%20id%3D%22toc-hId--1219964761%22%20id%3D%22toc-hId--1219964761%22%3E%3CSPAN%3EScenario%3A%20Initial%20installation%3C%2FSPAN%3E%3C%2FH2%3E%0A%3CP%3EWhen%20you%20deploy%20Office%20365%20ProPlus%20for%20the%20first%20time%20to%20a%20device%2C%20the%20channel%20attribute%20works%20pretty%20straight%20forward%3A%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3EIf%20you%20have%20specified%20the%20channel%20(usually%20Monthly%20or%20Semi-Annual)%2C%20ODT%20will%20just%20install%20the%20latest%2Favailable%20or%20specified%20version%20of%20Office%20from%20this%20channel.%3C%2FLI%3E%0A%3CLI%3EIf%20you%20haven%E2%80%99t%20specified%20the%20channel%2C%20the%20%3CSPAN%3E%3CA%20href%3D%22https%3A%2F%2Faka.ms%2FODT%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3EOffice%20Deployment%20Tool%3C%2FA%3E%3C%2FSPAN%3E(ODT)%20will%20use%20the%20following%20%3CSPAN%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fdeployoffice%2Fconfiguration-options-for-the-office-2016-deployment-tool%23add-element%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Edefault%20values%3C%2FA%3E%3C%2FSPAN%3E%3A%0A%3CUL%3E%0A%3CLI%3ESemi-Annual%20Channel%20for%20Office%20365%20ProPlus.%3C%2FLI%3E%0A%3CLI%3ESemi-Annual%20Channel%20for%20Visio%2FProject%20when%20installed%20at%20the%20same%20time%20as%20Office.%3C%2FLI%3E%0A%3CLI%3EMonthly%20Channel%20for%20Visio%2FProject%2C%20if%20not%20installed%20alongside%20Office.%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EMost%20IT%20admins%20are%20not%20aware%20of%20the%20optional%20nature%20of%20the%20channel%20assignment%2C%20but%20there%20is%20not%20too%20much%20we%20can%20optimize%20here.%20The%20meat%20and%20potatoes%20lies%20in%20the%202%3CSUP%3End%3C%2FSUP%3Einstall%20scenario.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CH2%20id%3D%22toc-hId--734782240%22%20id%3D%22toc-hId-522845574%22%20id%3D%22toc-hId-522845574%22%20id%3D%22toc-hId-522845574%22%20id%3D%22toc-hId-522845574%22%20id%3D%22toc-hId-522845574%22%20id%3D%22toc-hId-522845574%22%3E%3CSPAN%3EScenario%3A%20Adding%20Visio%2C%20Project%2C%20Language%20Packs%2C%20Proofing%20Tools%20or%20other%20components%3C%2FSPAN%3E%3C%2FH2%3E%0A%3CP%3E%3CSPAN%3ELet%E2%80%99s%20assume%20that%20Office%20365%20ProPlus%20is%20already%20deployed%20to%20a%20device%20and%20you%20as%20the%20IT%20admin%20has%20to%20provide%20ways%20to%20install%20additional%20Language%20Packs%2C%20Visio%2C%20Project%2C%20and%20Proofing%20Tools.%20Most%20organizations%20run%20a%20mix%20of%20SAC%20and%20SAC-T%20%2C%20more%20often%20than%20not%20you%20also%20have%20a%20small%20population%20on%20Monthly%20Channel.%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%3CSPAN%3EThis%20poses%20two%20%3CSTRONG%3Echallenges%3C%2FSTRONG%3Ewhen%20going%20with%20the%20common%20approach%20of%20specifying%20the%20Channel%20attribute%3A%20%3C%2FSPAN%3E%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3E%3CSPAN%3EYou%20end%20up%20with%20a%20high%20number%20of%20install%20packages.%20E.g.%20when%20you%20want%20to%20provide%20one%20additional%20language%20as%20well%20as%20Visio%20and%20Project%20to%20your%20users%2C%20you%20end%20up%20with%20three%20install%20packages%20multiplied%20by%20the%20number%20of%20update%20channels%20you%20support.%3C%2FSPAN%3E%3C%2FLI%3E%0A%3CLI%3E%3CSPAN%3EYour%20users%20are%20confused.%20If%20you%20want%20to%20provide%20a%20self-service%20to%20your%20users%2C%20e.g.%20through%20SCCM%20Software%20Center%2C%20they%20will%20see%20all%20these%20install%20packages%20and%20must%20pick%20the%20one%20which%20is%20matching%20their%20currently%20installed%20update%20channel.%20Most%20users%20don%E2%80%99t%20have%20a%20clue%20which%20channel%20they%20are%20on.%3C%2FSPAN%3E%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%3CSPAN%3EBut%20ODT%20to%20the%20rescue!%20A%20little%20known%20fact%20is%2C%20that%20ODT%20will%20default%20to%20the%20assigned%20channel%20of%20the%20existing%20installation%2C%20if%20the%20attribute%20is%20not%20set.%20We%20can%20leverage%20this%20behavior%20to%20remove%20the%20(perceived)%20need%20to%20build%20one%20configuration%20file%20per%20deployed%20update%20channel.%20This%20reduces%20the%20number%20of%20required%20configuration%20files%20(and%20install%20packages)%20significantly.%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%3CSPAN%3EHere%20is%20an%20example%20of%20a%20configuration%20file%20which%20adds%20Visio%20to%20an%20existing%20installation%20and%20will%20work%20for%20any%20update%20channel%3A%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CPRE%20class%3D%22lia-code-sample%20language-markup%22%3E%3CCODE%3E%3CCONFIGURATION%3E%0A%20%3CADD%20version%3D%22MatchInstalled%22%3E%0A%20%20%3CPRODUCT%20id%3D%22VisioProRetail%22%3E%0A%20%20%20%3CLANGUAGE%20id%3D%22MatchInstalled%22%20targetproduct%3D%22O365ProPlusRetail%22%3E%3C%2FLANGUAGE%3E%20%0A%20%20%3C%2FPRODUCT%3E%0A%20%3C%2FADD%3E%0A%3C%2FCONFIGURATION%3E%0A%3C%2FCODE%3E%3C%2FPRE%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%3CSPAN%3EAbove%20XML%20will%20do%20the%20following%20for%20you%3A%3C%2FSPAN%3E%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3E%3CSPAN%3EAs%20OfficeClientEdition%20is%20not%20specified%2C%20the%20ODT%20will%20automatically%20match%20the%20new%20install%20to%20the%20already%20installed%20product.%20So%20this%20is%20a%20x86%2Fx64%20universal%20configuration%20(%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FOffice-365-ProPlus%2FInsights-into-OfficeClientEdition-and-how-to-make-it-work-for%2Fm-p%2F767577%22%20target%3D%22_blank%22%20rel%3D%22noopener%22%3Eread%20more%20about%20it%20here%3C%2FA%3E).%3C%2FSPAN%3E%3C%2FLI%3E%0A%3CLI%3E%3CSPAN%3EThe%20to-be%20installed%20version%20will%20match%20the%20installed%20one.%20Even%20if%20a%20newer%20version%20is%20available%20e.g.%20on%20the%20OfficeCDN%2C%20it%20will%20not%20do%20an%20implicit%20update%20(Read%20more%20about%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FOffice-365-ProPlus%2FNew-feature-Make-changes-to-Office-deployments-without-changing%2Fm-p%2F481948%2Fthread-id%2F655%22%20target%3D%22_blank%22%20rel%3D%22noopener%22%3EVersion%3D%22MatchInstalled%22%3C%2FA%3E).%3C%2FSPAN%3E%3C%2FLI%3E%0A%3CLI%3E%3CSPAN%3EVisio%20will%20be%20deployed%20with%20the%20very%20same%20languages%20as%20Office%20365%20ProPlus%20is%20already%20installed%20with.%20For%20more%20details%20please%20check%20out%20this%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FOffice-365-ProPlus%2FDynamically-match-already-existing-languages-when-installing%2Fm-p%2F716927%22%20target%3D%22_blank%22%20rel%3D%22noopener%22%3Eblog%20post%3C%2FA%3E.%3C%2FSPAN%3E%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%3CSPAN%3ESo%2C%20we%20have%20a%20dynamic%20configuration%20file%20which%20has%20no%20hard-coded%20architecture%2C%20languages%2C%20update%20channel%20or%20version.%20You%20can%20build%20this%20e.g.%20SCCM%20application%20once%20and%20use%20it%20for%20all%20update%20channels.%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CH2%20id%3D%22toc-hId-1008028095%22%20id%3D%22toc-hId--2029311387%22%20id%3D%22toc-hId--2029311387%22%20id%3D%22toc-hId--2029311387%22%20id%3D%22toc-hId--2029311387%22%20id%3D%22toc-hId--2029311387%22%20id%3D%22toc-hId--2029311387%22%3E%3CSPAN%3EBenefits%3C%2FSPAN%3E%3C%2FH2%3E%0A%3CP%3EIn%20the%20past%20configuration%20files%20were%20static%2C%20each%20covering%20one%20specific%20scenario%2Fconfiguration.%20By%20using%20new%20features%20like%20Version%3DMatchInstalled%2C%20Language%3DMatchInstalled%20together%20with%20dynamic%20OfficeClientEdition%20and%20update%20channel%2C%20you%20can%20build%20universal%20configuration%20files%20which%20cover%20multiple%20scenarios.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThis%20resolves%20the%20two%20issues%20described%20above%3A%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3EYou%20only%20need%20one%20installation%20package%20(e.g.%20an%20SCCM%20app)%20per%20component.%20For%20most%20environments%20(running%20MC%2C%20SAC%20and%20SAC-T)%20this%20reduces%20the%20effort%20by%2066%25%2C%20because%20you%20don%E2%80%99t%20have%20to%20build%20each%20package%20three%20times.%3C%2FLI%3E%0A%3CLI%3EYour%20users%20will%20be%20happy%2C%20as%20they%20can%20easily%20identify%20what%20they%20need%20from%20the%20Software%20Center.%20They%20don%E2%80%99t%20have%20to%20worry%20about%20which%20update%20channels%20they%20are%20on.%20It%20just%20works.%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CH2%20id%3D%22toc-hId--1544128866%22%20id%3D%22toc-hId--286501052%22%20id%3D%22toc-hId--286501052%22%20id%3D%22toc-hId--286501052%22%20id%3D%22toc-hId--286501052%22%20id%3D%22toc-hId--286501052%22%20id%3D%22toc-hId--286501052%22%3E%3CSPAN%3EPrerequisites%3C%2FSPAN%3E%3C%2FH2%3E%0A%3CUL%3E%0A%3CLI%3EThe%20ODT%20must%20be%20able%20to%20locate%20the%20matching%20source%20files%20on%20the%20Office%20CDN.%20Including%20the%20source%20files%20in%20the%20SCCM%20app%20would%20require%20having%20the%20exactly%20matching%20version%20included.%20Same%20goes%20for%20network%20shares%2Flocal%20folders.%20We%20recommend%20using%20the%20Office%20CDN%20instead.%3C%2FLI%3E%0A%3CLI%3EI%20always%20recommend%20to%20also%20make%20sure%20that%20you%20use%20the%20latest%20ODT%20available.%20There%20is%20no%20specific%20min.%20version%20for%20the%20Channel-attribute%2C%20but%20it%20is%20a%20good%20practice%20to%20always%20update%20the%20ODT%20when%20you%E2%80%99re%20touching%20it%20anyways.%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CH2%20id%3D%22toc-hId-198681469%22%20id%3D%22toc-hId-1456309283%22%20id%3D%22toc-hId-1456309283%22%20id%3D%22toc-hId-1456309283%22%20id%3D%22toc-hId-1456309283%22%20id%3D%22toc-hId-1456309283%22%20id%3D%22toc-hId-1456309283%22%3EThe%20Author%3C%2FH2%3E%0A%3CP%3EThis%20blog%20post%20is%20brought%20to%20you%20by%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F6347%22%20target%3D%22_blank%22%3E%40Martin%20Nothnagel%3C%2FA%3E%26nbsp%3B%2C%20a%20senior%20ProPlus%20deployment%20expert%20and%20ProPlus%20Ranger%20at%20Microsoft.%20Feel%20free%20to%20share%20your%20questions%20and%20feedback%20in%20the%20comments%20below.%3C%2FP%3E%0A%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIn%20nearly%20every%20configuration%20file%20(aka%20config.xml)%20you%20will%20find%20this%20attribute%2C%20but%20have%20you%20known%20that%20this%20is%20actually%20an%20optional%20attribute%20and%20can%20be%20used%20to%20build%20leaner%20deployments%20which%20require%20less%20maintenance%3F%20I%20will%20walk%20you%20through%20the%20steps%20on%20how%20the%20Channel-attribute%20works%20during%20the%20initial%20installation%20of%20Office%20365%20Client%20Apps%20and%20how%20to%20leverage%20it%20for%20reducing%20your%20effort%20when%20building%20sub-sequent%20installs%20(Project%2C%20Visio%2C%20%E2%80%A6).%3C%2FP%3E%0A%3CP%3E%3CSPAN%3EWhen%20designing%20an%20Office%20365%20ProPlus%20deployment%2C%20especially%20in%20larger%20organizations%2C%20the%20%E2%80%9CUpdate%20Channel%E2%80%9D%20to%20use%20is%20an%20important%20factor.%20It%20controls%20the%20balance%20between%20receiving%20new%20features%20quickly%20and%20providing%20phases%20of%20%E2%80%9Cno%20changes%E2%80%9D%20for%20the%20IT.%20It%E2%80%99s%20important%20to%20understand%20%3C%2FSPAN%3Ethe%20%3CSPAN%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fdeployoffice%2Foverview-of-update-channels-for-office-365-proplus%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Efoundational%20concepts%3C%2FA%3E%3C%2FSPAN%3E%2C%20%3CSPAN%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fdeployoffice%2Fmanage-updates-to-office-365-proplus-with-system-center-configuration-manager%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Eways%20to%20implement%20it%3C%2FA%3E%3C%2FSPAN%3Eas%20well%20as%20the%20%3CSPAN%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fdeployoffice%2Fchange-management-for-office-365-clients%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Echange%20management%3C%2FA%3E%3C%2FSPAN%3Eview%20on%20this%20topic.%20But%20this%20post%20will%20just%20focus%20on%20the%20channel%20assignment%20done%20through%20the%20ODT.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CH2%20id%3D%22toc-hId-1817374721%22%20id%3D%22toc-hId-1143430989%22%20id%3D%22toc-hId-1143430989%22%20id%3D%22toc-hId-1143430989%22%20id%3D%22toc-hId-1143430989%22%20id%3D%22toc-hId-1143430989%22%3E%3CSPAN%3EScenario%3A%20Initial%20installation%3C%2FSPAN%3E%3C%2FH2%3E%0A%3CP%3EWhen%20you%20deploy%20Office%20365%20ProPlus%20for%20the%20first%20time%20to%20a%20device%2C%20the%20channel%20attribute%20works%20pretty%20straight%20forward%3A%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3EIf%20you%20have%20specified%20the%20channel%20(usually%20Monthly%20or%20Semi-Annual)%2C%20ODT%20will%20just%20install%20the%20latest%2Favailable%20or%20specified%20version%20of%20Office%20from%20this%20channel.%3C%2FLI%3E%0A%3CLI%3EIf%20you%20haven%E2%80%99t%20specified%20the%20channel%2C%20the%20%3CSPAN%3E%3CA%20href%3D%22https%3A%2F%2Faka.ms%2FODT%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3EOffice%20Deployment%20Tool%3C%2FA%3E%3C%2FSPAN%3E(ODT)%20will%20use%20the%20following%20%3CSPAN%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fdeployoffice%2Fconfiguration-options-for-the-office-2016-deployment-tool%23add-element%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Edefault%20values%3C%2FA%3E%3C%2FSPAN%3E%3A%0A%3CUL%3E%0A%3CLI%3ESemi-Annual%20Channel%20for%20Office%20365%20ProPlus.%3C%2FLI%3E%0A%3CLI%3ESemi-Annual%20Channel%20for%20Visio%2FProject%20when%20installed%20at%20the%20same%20time%20as%20Office.%3C%2FLI%3E%0A%3CLI%3EMonthly%20Channel%20for%20Visio%2FProject%2C%20if%20not%20installed%20alongside%20Office.%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EMost%20IT%20admins%20are%20not%20aware%20of%20the%20optional%20nature%20of%20the%20channel%20assignment%2C%20but%20there%20is%20not%20too%20much%20we%20can%20optimize%20here.%20The%20meat%20and%20potatoes%20lies%20in%20the%202%3CSUP%3End%3C%2FSUP%3Einstall%20scenario.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CH2%20id%3D%22toc-hId--734782240%22%20id%3D%22toc-hId--1408725972%22%20id%3D%22toc-hId--1408725972%22%20id%3D%22toc-hId--1408725972%22%20id%3D%22toc-hId--1408725972%22%20id%3D%22toc-hId--1408725972%22%3E%3CSPAN%3EScenario%3A%20Adding%20Visio%2C%20Project%2C%20Language%20Packs%2C%20Proofing%20Tools%20or%20other%20components%3C%2FSPAN%3E%3C%2FH2%3E%0A%3CP%3E%3CSPAN%3ELet%E2%80%99s%20assume%20that%20Office%20365%20ProPlus%20is%20already%20deployed%20to%20a%20device%20and%20you%20as%20the%20IT%20admin%20has%20to%20provide%20ways%20to%20install%20additional%20Language%20Packs%2C%20Visio%2C%20Project%2C%20and%20Proofing%20Tools.%20Most%20organizations%20run%20a%20mix%20of%20SAC%20and%20SAC-T%20%2C%20more%20often%20than%20not%20you%20also%20have%20a%20small%20population%20on%20Monthly%20Channel.%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%3CSPAN%3EThis%20poses%20two%20%3CSTRONG%3Echallenges%3C%2FSTRONG%3Ewhen%20going%20with%20the%20common%20approach%20of%20specifying%20the%20Channel%20attribute%3A%20%3C%2FSPAN%3E%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3E%3CSPAN%3EYou%20end%20up%20with%20a%20high%20number%20of%20install%20packages.%20E.g.%20when%20you%20want%20to%20provide%20one%20additional%20language%20as%20well%20as%20Visio%20and%20Project%20to%20your%20users%2C%20you%20end%20up%20with%20three%20install%20packages%20multiplied%20by%20the%20number%20of%20update%20channels%20you%20support.%3C%2FSPAN%3E%3C%2FLI%3E%0A%3CLI%3E%3CSPAN%3EYour%20users%20are%20confused.%20If%20you%20want%20to%20provide%20a%20self-service%20to%20your%20users%2C%20e.g.%20through%20SCCM%20Software%20Center%2C%20they%20will%20see%20all%20these%20install%20packages%20and%20must%20pick%20the%20one%20which%20is%20matching%20their%20currently%20installed%20update%20channel.%20Most%20users%20don%E2%80%99t%20have%20a%20clue%20which%20channel%20they%20are%20on.%3C%2FSPAN%3E%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%3CSPAN%3EBut%20ODT%20to%20the%20rescue!%20A%20little%20known%20fact%20is%2C%20that%20ODT%20will%20default%20to%20the%20assigned%20channel%20of%20the%20existing%20installation%2C%20if%20the%20attribute%20is%20not%20set.%20We%20can%20leverage%20this%20behavior%20to%20remove%20the%20(perceived)%20need%20to%20build%20one%20configuration%20file%20per%20deployed%20update%20channel.%20This%20reduces%20the%20number%20of%20required%20configuration%20files%20(and%20install%20packages)%20significantly.%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%3CSPAN%3EHere%20is%20an%20example%20of%20a%20configuration%20file%20which%20adds%20Visio%20to%20an%20existing%20installation%20and%20will%20work%20for%20any%20update%20channel%3A%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CPRE%20class%3D%22lia-code-sample%20language-markup%22%3E%3CCODE%3E%3CCONFIGURATION%3E%0A%20%3CADD%20version%3D%22MatchInstalled%22%3E%0A%20%20%3CPRODUCT%20id%3D%22VisioProRetail%22%3E%0A%20%20%20%3CLANGUAGE%20id%3D%22MatchInstalled%22%20targetproduct%3D%22O365ProPlusRetail%22%3E%3C%2FLANGUAGE%3E%20%0A%20%20%3C%2FPRODUCT%3E%0A%20%3C%2FADD%3E%0A%3C%2FCONFIGURATION%3E%0A%3C%2FCODE%3E%3C%2FPRE%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%3CSPAN%3EAbove%20XML%20will%20do%20the%20following%20for%20you%3A%3C%2FSPAN%3E%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3E%3CSPAN%3EAs%20OfficeClientEdition%20is%20not%20specified%2C%20the%20ODT%20will%20automatically%20match%20the%20new%20install%20to%20the%20already%20installed%20product.%20So%20this%20is%20a%20x86%2Fx64%20universal%20configuration%20(%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FOffice-365-ProPlus%2FInsights-into-OfficeClientEdition-and-how-to-make-it-work-for%2Fm-p%2F767577%22%20target%3D%22_blank%22%20rel%3D%22noopener%22%3Eread%20more%20about%20it%20here%3C%2FA%3E).%3C%2FSPAN%3E%3C%2FLI%3E%0A%3CLI%3E%3CSPAN%3EThe%20to-be%20installed%20version%20will%20match%20the%20installed%20one.%20Even%20if%20a%20newer%20version%20is%20available%20e.g.%20on%20the%20OfficeCDN%2C%20it%20will%20not%20do%20an%20implicit%20update%20(Read%20more%20about%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FOffice-365-ProPlus%2FNew-feature-Make-changes-to-Office-deployments-without-changing%2Fm-p%2F481948%2Fthread-id%2F655%22%20target%3D%22_blank%22%20rel%3D%22noopener%22%3EVersion%3D%22MatchInstalled%22%3C%2FA%3E).%3C%2FSPAN%3E%3C%2FLI%3E%0A%3CLI%3E%3CSPAN%3EVisio%20will%20be%20deployed%20with%20the%20very%20same%20languages%20as%20Office%20365%20ProPlus%20is%20already%20installed%20with.%20For%20more%20details%20please%20check%20out%20this%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FOffice-365-ProPlus%2FDynamically-match-already-existing-languages-when-installing%2Fm-p%2F716927%22%20target%3D%22_blank%22%20rel%3D%22noopener%22%3Eblog%20post%3C%2FA%3E.%3C%2FSPAN%3E%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%3CSPAN%3ESo%2C%20we%20have%20a%20dynamic%20configuration%20file%20which%20has%20no%20hard-coded%20architecture%2C%20languages%2C%20update%20channel%20or%20version.%20You%20can%20build%20this%20e.g.%20SCCM%20application%20once%20and%20use%20it%20for%20all%20update%20channels.%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CH2%20id%3D%22toc-hId-1008028095%22%20id%3D%22toc-hId-334084363%22%20id%3D%22toc-hId-334084363%22%20id%3D%22toc-hId-334084363%22%20id%3D%22toc-hId-334084363%22%20id%3D%22toc-hId-334084363%22%3E%3CSPAN%3EBenefits%3C%2FSPAN%3E%3C%2FH2%3E%0A%3CP%3EIn%20the%20past%20configuration%20files%20were%20static%2C%20each%20covering%20one%20specific%20scenario%2Fconfiguration.%20By%20using%20new%20features%20like%20Version%3DMatchInstalled%2C%20Language%3DMatchInstalled%20together%20with%20dynamic%20OfficeClientEdition%20and%20update%20channel%2C%20you%20can%20build%20universal%20configuration%20files%20which%20cover%20multiple%20scenarios.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThis%20resolves%20the%20two%20issues%20described%20above%3A%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3EYou%20only%20need%20one%20installation%20package%20(e.g.%20an%20SCCM%20app)%20per%20component.%20For%20most%20environments%20(running%20MC%2C%20SAC%20and%20SAC-T)%20this%20reduces%20the%20effort%20by%2066%25%2C%20because%20you%20don%E2%80%99t%20have%20to%20build%20each%20package%20three%20times.%3C%2FLI%3E%0A%3CLI%3EYour%20users%20will%20be%20happy%2C%20as%20they%20can%20easily%20identify%20what%20they%20need%20from%20the%20Software%20Center.%20They%20don%E2%80%99t%20have%20to%20worry%20about%20which%20update%20channels%20they%20are%20on.%20It%20just%20works.%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CH2%20id%3D%22toc-hId--1544128866%22%20id%3D%22toc-hId-2076894698%22%20id%3D%22toc-hId-2076894698%22%20id%3D%22toc-hId-2076894698%22%20id%3D%22toc-hId-2076894698%22%20id%3D%22toc-hId-2076894698%22%3E%3CSPAN%3EPrerequisites%3C%2FSPAN%3E%3C%2FH2%3E%0A%3CUL%3E%0A%3CLI%3EThe%20ODT%20must%20be%20able%20to%20locate%20the%20matching%20source%20files%20on%20the%20Office%20CDN.%20Including%20the%20source%20files%20in%20the%20SCCM%20app%20would%20require%20having%20the%20exactly%20matching%20version%20included.%20Same%20goes%20for%20network%20shares%2Flocal%20folders.%20We%20recommend%20using%20the%20Office%20CDN%20instead.%3C%2FLI%3E%0A%3CLI%3EI%20always%20recommend%20to%20also%20make%20sure%20that%20you%20use%20the%20latest%20ODT%20available.%20There%20is%20no%20specific%20min.%20version%20for%20the%20Channel-attribute%2C%20but%20it%20is%20a%20good%20practice%20to%20always%20update%20the%20ODT%20when%20you%E2%80%99re%20touching%20it%20anyways.%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CH2%20id%3D%22toc-hId-198681469%22%20id%3D%22toc-hId--475262263%22%20id%3D%22toc-hId--475262263%22%20id%3D%22toc-hId--475262263%22%20id%3D%22toc-hId--475262263%22%20id%3D%22toc-hId--475262263%22%3EThe%20Author%3C%2FH2%3E%0A%3CP%3EThis%20blog%20post%20is%20brought%20to%20you%20by%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F6347%22%20target%3D%22_blank%22%3E%40Martin%20Nothnagel%3C%2FA%3E%2C%20a%20senior%20ProPlus%20deployment%20expert%20and%20ProPlus%20Ranger%20at%20Microsoft.%20Feel%20free%20to%20share%20your%20questions%20and%20feedback%20in%20the%20comments%20below.%3C%2FP%3E%0A%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIn%20nearly%20every%20configuration%20file%20(aka%20config.xml)%20you%20will%20find%20this%20attribute%2C%20but%20have%20you%20known%20that%20this%20is%20actually%20an%20optional%20attribute%20and%20can%20be%20used%20to%20build%20leaner%20deployments%20which%20require%20less%20maintenance%3F%20I%20will%20walk%20you%20through%20the%20steps%20on%20how%20the%20Channel-attribute%20works%20during%20the%20initial%20installation%20of%20Office%20365%20Client%20Apps%20and%20how%20to%20leverage%20it%20for%20reducing%20your%20effort%20when%20building%20sub-sequent%20installs%20(Project%2C%20Visio%2C%20%E2%80%A6).%3C%2FP%3E%0A%3CP%3E%3CSPAN%3EWhen%20designing%20an%20Office%20365%20ProPlus%20deployment%2C%20especially%20in%20larger%20organizations%2C%20the%20%E2%80%9CUpdate%20Channel%E2%80%9D%20to%20use%20is%20an%20important%20factor.%20It%20controls%20the%20balance%20between%20receiving%20new%20features%20quickly%20and%20providing%20phases%20of%20%E2%80%9Cno%20changes%E2%80%9D%20for%20the%20IT.%20It%E2%80%99s%20important%20to%20understand%20%3C%2FSPAN%3Ethe%20%3CSPAN%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fdeployoffice%2Foverview-of-update-channels-for-office-365-proplus%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Efoundational%20concepts%3C%2FA%3E%3C%2FSPAN%3E%2C%20%3CSPAN%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fdeployoffice%2Fmanage-updates-to-office-365-proplus-with-system-center-configuration-manager%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Eways%20to%20implement%20it%3C%2FA%3E%3C%2FSPAN%3Eas%20well%20as%20the%20%3CSPAN%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fdeployoffice%2Fchange-management-for-office-365-clients%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Echange%20management%3C%2FA%3E%3C%2FSPAN%3Eview%20on%20this%20topic.%20But%20this%20post%20will%20just%20focus%20on%20the%20channel%20assignment%20done%20through%20the%20ODT.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CH2%20id%3D%22toc-hId-1817374721%22%20id%3D%22toc-hId-1267548072%22%20id%3D%22toc-hId-1267548072%22%20id%3D%22toc-hId-1267548072%22%20id%3D%22toc-hId-1267548072%22%3E%3CSPAN%3EScenario%3A%20Initial%20installation%3C%2FSPAN%3E%3C%2FH2%3E%0A%3CP%3EWhen%20you%20deploy%20Office%20365%20ProPlus%20for%20the%20first%20time%20to%20a%20device%2C%20the%20channel%20attribute%20works%20pretty%20straight%20forward%3A%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3EIf%20you%20have%20specified%20the%20channel%20(usually%20Monthly%20or%20Semi-Annual)%2C%20ODT%20will%20just%20install%20the%20latest%2Favailable%20or%20specified%20version%20of%20Office%20from%20this%20channel.%3C%2FLI%3E%0A%3CLI%3EIf%20you%20haven%E2%80%99t%20specified%20the%20channel%2C%20the%20%3CSPAN%3E%3CA%20href%3D%22https%3A%2F%2Faka.ms%2FODT%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3EOffice%20Deployment%20Tool%3C%2FA%3E%3C%2FSPAN%3E(ODT)%20will%20use%20the%20following%20%3CSPAN%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fdeployoffice%2Fconfiguration-options-for-the-office-2016-deployment-tool%23add-element%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Edefault%20values%3C%2FA%3E%3C%2FSPAN%3E%3A%0A%3CUL%3E%0A%3CLI%3ESemi-Annual%20Channel%20for%20Office%20365%20ProPlus.%3C%2FLI%3E%0A%3CLI%3ESemi-Annual%20Channel%20for%20Visio%2FProject%20when%20installed%20at%20the%20same%20time%20as%20Office.%3C%2FLI%3E%0A%3CLI%3EMonthly%20Channel%20for%20Visio%2FProject%2C%20if%20not%20installed%20alongside%20Office.%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EMost%20IT%20admins%20are%20not%20aware%20of%20the%20optional%20nature%20of%20the%20channel%20assignment%2C%20but%20there%20is%20not%20too%20much%20we%20can%20optimize%20here.%20The%20meat%20and%20potatoes%20lies%20in%20the%202%3CSUP%3End%3C%2FSUP%3Einstall%20scenario.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CH2%20id%3D%22toc-hId--734782240%22%20id%3D%22toc-hId--1284608889%22%20id%3D%22toc-hId--1284608889%22%20id%3D%22toc-hId--1284608889%22%20id%3D%22toc-hId--1284608889%22%3E%3CSPAN%3EScenario%3A%20Adding%20Visio%2C%20Project%2C%20Language%20Packs%2C%20Proofing%20Tools%20or%20other%20components%3C%2FSPAN%3E%3C%2FH2%3E%0A%3CP%3E%3CSPAN%3ELet%E2%80%99s%20assume%20that%20Office%20365%20ProPlus%20is%20already%20deployed%20to%20a%20device%20and%20you%20as%20the%20IT%20admin%20has%20to%20provide%20ways%20to%20install%20additional%20Language%20Packs%2C%20Visio%2C%20Project%2C%20and%20Proofing%20Tools.%20Most%20organizations%20run%20a%20mix%20of%20SAC%20and%20SAC-T%20%2C%20more%20often%20than%20not%20you%20also%20have%20a%20small%20population%20on%20Monthly%20Channel.%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%3CSPAN%3EThis%20poses%20two%20%3CSTRONG%3Echallenges%3C%2FSTRONG%3Ewhen%20going%20with%20the%20common%20approach%20of%20specifying%20the%20Channel%20attribute%3A%20%3C%2FSPAN%3E%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3E%3CSPAN%3EYou%20end%20up%20with%20a%20high%20number%20of%20install%20packages.%20E.g.%20when%20you%20want%20to%20provide%20one%20additional%20language%20as%20well%20as%20Visio%20and%20Project%20to%20your%20users%2C%20you%20end%20up%20with%20three%20install%20packages%20multiplied%20by%20the%20number%20of%20update%20channels%20you%20support.%3C%2FSPAN%3E%3C%2FLI%3E%0A%3CLI%3E%3CSPAN%3EYour%20users%20are%20confused.%20If%20you%20want%20to%20provide%20a%20self-service%20to%20your%20users%2C%20e.g.%20through%20SCCM%20Software%20Center%2C%20they%20will%20see%20all%20these%20install%20packages%20and%20must%20pick%20the%20one%20which%20is%20matching%20their%20currently%20installed%20update%20channel.%20Most%20users%20don%E2%80%99t%20have%20a%20clue%20which%20channel%20they%20are%20on.%3C%2FSPAN%3E%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%3CSPAN%3EBut%20ODT%20to%20the%20rescue!%20A%20little%20known%20fact%20is%2C%20that%20ODT%20will%20default%20to%20the%20assigned%20channel%20of%20the%20existing%20installation%2C%20if%20the%20attribute%20is%20not%20set.%20We%20can%20leverage%20this%20behavior%20to%20remove%20the%20(perceived)%20need%20to%20build%20one%20configuration%20file%20per%20deployed%20update%20channel.%20This%20reduces%20the%20number%20of%20required%20configuration%20files%20(and%20install%20packages)%20significantly.%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%3CSPAN%3EHere%20is%20an%20example%20of%20a%20configuration%20file%20which%20adds%20Visio%20to%20an%20existing%20installation%20and%20will%20work%20for%20any%20update%20channel%3A%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CPRE%20class%3D%22lia-code-sample%20language-markup%22%3E%3CCODE%3E%3CCONFIGURATION%3E%0A%20%3CADD%20version%3D%22MatchInstalled%22%3E%0A%20%20%3CPRODUCT%20id%3D%22VisioProRetail%22%3E%0A%20%20%20%3CLANGUAGE%20id%3D%22MatchInstalled%22%20targetproduct%3D%22O365ProPlusRetail%22%3E%3C%2FLANGUAGE%3E%20%0A%20%20%3C%2FPRODUCT%3E%0A%20%3C%2FADD%3E%0A%3C%2FCONFIGURATION%3E%0A%3C%2FCODE%3E%3C%2FPRE%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%3CSPAN%3EAbove%20XML%20will%20do%20the%20following%20for%20you%3A%3C%2FSPAN%3E%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3E%3CSPAN%3EAs%20OfficeClientEdition%20is%20not%20specified%2C%20the%20ODT%20will%20automatically%20match%20the%20new%20install%20to%20the%20already%20installed%20product.%20So%20this%20is%20a%20x86%2Fx64%20universal%20configuration%20(%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FOffice-365-ProPlus%2FInsights-into-OfficeClientEdition-and-how-to-make-it-work-for%2Fm-p%2F767577%22%20target%3D%22_blank%22%20rel%3D%22noopener%22%3Eread%20more%20about%20it%20here%3C%2FA%3E).%3C%2FSPAN%3E%3C%2FLI%3E%0A%3CLI%3E%3CSPAN%3EThe%20to-be%20installed%20version%20will%20match%20the%20installed%20one.%20Even%20if%20a%20newer%20version%20is%20available%20e.g.%20on%20the%20OfficeCDN%2C%20it%20will%20not%20do%20an%20implicit%20update%20(Read%20more%20about%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FOffice-365-ProPlus%2FNew-feature-Make-changes-to-Office-deployments-without-changing%2Fm-p%2F481948%2Fthread-id%2F655%22%20target%3D%22_blank%22%20rel%3D%22noopener%22%3EVersion%3D%22MatchInstalled%22%3C%2FA%3E).%3C%2FSPAN%3E%3C%2FLI%3E%0A%3CLI%3E%3CSPAN%3EVisio%20will%20be%20deployed%20with%20the%20very%20same%20languages%20as%20Office%20365%20ProPlus%20is%20already%20installed%20with.%20For%20more%20details%20please%20check%20out%20this%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FOffice-365-ProPlus%2FDynamically-match-already-existing-languages-when-installing%2Fm-p%2F716927%22%20target%3D%22_blank%22%20rel%3D%22noopener%22%3Eblog%20post%3C%2FA%3E.%3C%2FSPAN%3E%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%3CSPAN%3ESo%2C%20we%20have%20a%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FOffice-365-Blog%2FBuilding-dynamic-lean-amp-universal-packages-for-Office-365%2Fba-p%2F839658%22%20target%3D%22_blank%22%20rel%3D%22noopener%22%3Edynamic%2C%20lean%20and%20universal%3C%2FA%3Econfiguration%20file%20which%20has%20no%20hard-coded%20architecture%2C%20languages%2C%20update%20channel%20or%20version.%20You%20can%20build%20this%20e.g.%20SCCM%20application%20once%20and%20use%20it%20for%20all%20update%20channels.%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CH2%20id%3D%22toc-hId-1008028095%22%20id%3D%22toc-hId-458201446%22%20id%3D%22toc-hId-458201446%22%20id%3D%22toc-hId-458201446%22%20id%3D%22toc-hId-458201446%22%3E%3CSPAN%3EBenefits%3C%2FSPAN%3E%3C%2FH2%3E%0A%3CP%3EIn%20the%20past%20configuration%20files%20were%20static%2C%20each%20covering%20one%20specific%20scenario%2Fconfiguration.%20By%20using%20new%20features%20like%20Version%3DMatchInstalled%2C%20Language%3DMatchInstalled%20together%20with%20dynamic%20OfficeClientEdition%20and%20update%20channel%2C%20you%20can%20build%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FOffice-365-Blog%2FBuilding-dynamic-lean-amp-universal-packages-for-Office-365%2Fba-p%2F839658%22%20target%3D%22_blank%22%20rel%3D%22noopener%22%3Euniversal%20configuration%20files%3C%2FA%3Ewhich%20cover%20multiple%20scenarios.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThis%20resolves%20the%20two%20issues%20described%20above%3A%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3EYou%20only%20need%20one%20installation%20package%20(e.g.%20an%20SCCM%20app)%20per%20component.%20For%20most%20environments%20(running%20MC%2C%20SAC%20and%20SAC-T)%20this%20reduces%20the%20effort%20by%2066%25%2C%20because%20you%20don%E2%80%99t%20have%20to%20build%20each%20package%20three%20times.%3C%2FLI%3E%0A%3CLI%3EYour%20users%20will%20be%20happy%2C%20as%20they%20can%20easily%20identify%20what%20they%20need%20from%20the%20Software%20Center.%20They%20don%E2%80%99t%20have%20to%20worry%20about%20which%20update%20channels%20they%20are%20on.%20It%20just%20works.%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CH2%20id%3D%22toc-hId--1544128866%22%20id%3D%22toc-hId--2093955515%22%20id%3D%22toc-hId--2093955515%22%20id%3D%22toc-hId--2093955515%22%20id%3D%22toc-hId--2093955515%22%3E%3CSPAN%3EPrerequisites%3C%2FSPAN%3E%3C%2FH2%3E%0A%3CUL%3E%0A%3CLI%3EThe%20ODT%20must%20be%20able%20to%20locate%20the%20matching%20source%20files%20on%20the%20Office%20CDN.%20Including%20the%20source%20files%20in%20the%20SCCM%20app%20would%20require%20having%20the%20exactly%20matching%20version%20included.%20Same%20goes%20for%20network%20shares%2Flocal%20folders.%20We%20recommend%20using%20the%20Office%20CDN%20instead.%3C%2FLI%3E%0A%3CLI%3EI%20always%20recommend%20to%20also%20make%20sure%20that%20you%20use%20the%20latest%20ODT%20available.%20There%20is%20no%20specific%20min.%20version%20for%20the%20Channel-attribute%2C%20but%20it%20is%20a%20good%20practice%20to%20always%20update%20the%20ODT%20when%20you%E2%80%99re%20touching%20it%20anyways.%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CH2%20id%3D%22toc-hId-198681469%22%20id%3D%22toc-hId--351145180%22%20id%3D%22toc-hId--351145180%22%20id%3D%22toc-hId--351145180%22%20id%3D%22toc-hId--351145180%22%3EThe%20Author%3C%2FH2%3E%0A%3CP%3EThis%20blog%20post%20is%20brought%20to%20you%20by%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F6347%22%20target%3D%22_blank%22%3E%40Martin%20Nothnagel%3C%2FA%3E%2C%20a%20ProPlus%20Ranger%20and%20senior%20ProPlus%20deployment%20expert%20at%20Microsoft.%20Feel%20free%20to%20share%20your%20questions%20and%20feedback%20in%20the%20comments%20below.%3C%2FP%3E%0A%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIn%20nearly%20every%20configuration%20file%20(aka%20config.xml)%20you%20will%20find%20this%20attribute%2C%20but%20have%20you%20known%20that%20this%20is%20actually%20an%20optional%20attribute%20and%20can%20be%20used%20to%20build%20leaner%20deployments%20which%20require%20less%20maintenance%3F%20I%20will%20walk%20you%20through%20the%20steps%20on%20how%20the%20Channel-attribute%20works%20during%20the%20initial%20installation%20of%20Office%20365%20Client%20Apps%20and%20how%20to%20leverage%20it%20for%20reducing%20your%20effort%20when%20building%20sub-sequent%20installs%20(Project%2C%20Visio%2C%20%E2%80%A6).%3C%2FP%3E%0A%3CP%3E%3CSPAN%3EWhen%20designing%20an%20Office%20365%20ProPlus%20deployment%2C%20especially%20in%20larger%20organizations%2C%20the%20%E2%80%9CUpdate%20Channel%E2%80%9D%20to%20use%20is%20an%20important%20factor.%20It%20controls%20the%20balance%20between%20receiving%20new%20features%20quickly%20and%20providing%20phases%20of%20%E2%80%9Cno%20changes%E2%80%9D%20for%20the%20IT.%20It%E2%80%99s%20important%20to%20understand%20%3C%2FSPAN%3Ethe%20%3CSPAN%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fdeployoffice%2Foverview-of-update-channels-for-office-365-proplus%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Efoundational%20concepts%3C%2FA%3E%3C%2FSPAN%3E%2C%20%3CSPAN%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fdeployoffice%2Fmanage-updates-to-office-365-proplus-with-system-center-configuration-manager%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Eways%20to%20implement%20it%3C%2FA%3E%3C%2FSPAN%3Eas%20well%20as%20the%20%3CSPAN%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fdeployoffice%2Fchange-management-for-office-365-clients%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Echange%20management%3C%2FA%3E%3C%2FSPAN%3Eview%20on%20this%20topic.%20But%20this%20post%20will%20just%20focus%20on%20the%20channel%20assignment%20done%20through%20the%20ODT.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CH2%20id%3D%22toc-hId-1817374721%22%20id%3D%22toc-hId--664023474%22%20id%3D%22toc-hId--664023474%22%20id%3D%22toc-hId--664023474%22%3E%3CSPAN%3EScenario%3A%20Initial%20installation%3C%2FSPAN%3E%3C%2FH2%3E%0A%3CP%3EWhen%20you%20deploy%20Office%20365%20ProPlus%20for%20the%20first%20time%20to%20a%20device%2C%20the%20channel%20attribute%20works%20pretty%20straight%20forward%3A%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3EIf%20you%20have%20specified%20the%20channel%20(usually%20Monthly%20or%20Semi-Annual)%2C%20ODT%20will%20just%20install%20the%20latest%2Favailable%20or%20specified%20version%20of%20Office%20from%20this%20channel.%3C%2FLI%3E%0A%3CLI%3EIf%20you%20haven%E2%80%99t%20specified%20the%20channel%2C%20the%20%3CSPAN%3E%3CA%20href%3D%22https%3A%2F%2Faka.ms%2FODT%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3EOffice%20Deployment%20Tool%3C%2FA%3E%3C%2FSPAN%3E(ODT)%20will%20use%20the%20following%20%3CSPAN%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fdeployoffice%2Fconfiguration-options-for-the-office-2016-deployment-tool%23add-element%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Edefault%20values%3C%2FA%3E%3C%2FSPAN%3E%3A%0A%3CUL%3E%0A%3CLI%3ESemi-Annual%20Channel%20for%20Office%20365%20ProPlus.%3C%2FLI%3E%0A%3CLI%3ESemi-Annual%20Channel%20for%20Visio%2FProject%20when%20installed%20at%20the%20same%20time%20as%20Office.%3C%2FLI%3E%0A%3CLI%3EMonthly%20Channel%20for%20Visio%2FProject%2C%20if%20not%20installed%20alongside%20Office.%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EMost%20IT%20admins%20are%20not%20aware%20of%20the%20optional%20nature%20of%20the%20channel%20assignment%2C%20but%20there%20is%20not%20too%20much%20we%20can%20optimize%20here.%20The%20meat%20and%20potatoes%20lies%20in%20the%202%3CSUP%3End%3C%2FSUP%3Einstall%20scenario.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CH2%20id%3D%22toc-hId--734782240%22%20id%3D%22toc-hId-1078786861%22%20id%3D%22toc-hId-1078786861%22%20id%3D%22toc-hId-1078786861%22%3E%3CSPAN%3EScenario%3A%20Adding%20Visio%2C%20Project%2C%20Language%20Packs%2C%20Proofing%20Tools%20or%20other%20components%3C%2FSPAN%3E%3C%2FH2%3E%0A%3CP%3E%3CSPAN%3ELet%E2%80%99s%20assume%20that%20Office%20365%20ProPlus%20is%20already%20deployed%20to%20a%20device%20and%20you%20as%20the%20IT%20admin%20has%20to%20provide%20ways%20to%20install%20additional%20Language%20Packs%2C%20Visio%2C%20Project%2C%20and%20Proofing%20Tools.%20Most%20organizations%20run%20a%20mix%20of%20SAC%20and%20SAC-T%20%2C%20more%20often%20than%20not%20you%20also%20have%20a%20small%20population%20on%20Monthly%20Channel.%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%3CSPAN%3EThis%20poses%20two%20%3CSTRONG%3Echallenges%3C%2FSTRONG%3Ewhen%20going%20with%20the%20common%20approach%20of%20specifying%20the%20Channel%20attribute%3A%20%3C%2FSPAN%3E%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3E%3CSPAN%3EYou%20end%20up%20with%20a%20high%20number%20of%20install%20packages.%20E.g.%20when%20you%20want%20to%20provide%20one%20additional%20language%20as%20well%20as%20Visio%20and%20Project%20to%20your%20users%2C%20you%20end%20up%20with%20three%20install%20packages%20multiplied%20by%20the%20number%20of%20update%20channels%20you%20support.%3C%2FSPAN%3E%3C%2FLI%3E%0A%3CLI%3E%3CSPAN%3EYour%20users%20are%20confused.%20If%20you%20want%20to%20provide%20a%20self-service%20to%20your%20users%2C%20e.g.%20through%20SCCM%20Software%20Center%2C%20they%20will%20see%20all%20these%20install%20packages%20and%20must%20pick%20the%20one%20which%20is%20matching%20their%20currently%20installed%20update%20channel.%20Most%20users%20don%E2%80%99t%20have%20a%20clue%20which%20channel%20they%20are%20on.%3C%2FSPAN%3E%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%3CSPAN%3EBut%20ODT%20to%20the%20rescue!%20A%20little%20known%20fact%20is%2C%20that%20ODT%20will%20default%20to%20the%20assigned%20channel%20of%20the%20existing%20installation%2C%20if%20the%20attribute%20is%20not%20set.%20We%20can%20leverage%20this%20behavior%20to%20remove%20the%20(perceived)%20need%20to%20build%20one%20configuration%20file%20per%20deployed%20update%20channel.%20This%20reduces%20the%20number%20of%20required%20configuration%20files%20(and%20install%20packages)%20significantly.%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%3CSPAN%3EHere%20is%20an%20example%20of%20a%20configuration%20file%20which%20adds%20Visio%20to%20an%20existing%20installation%20and%20will%20work%20for%20any%20update%20channel%3A%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CPRE%20class%3D%22lia-code-sample%20language-markup%22%3E%3CCODE%3E%3CCONFIGURATION%3E%0A%20%3CADD%20version%3D%22MatchInstalled%22%3E%0A%20%20%3CPRODUCT%20id%3D%22VisioProRetail%22%3E%0A%20%20%20%3CLANGUAGE%20id%3D%22MatchInstalled%22%20targetproduct%3D%22O365ProPlusRetail%22%3E%3C%2FLANGUAGE%3E%20%0A%20%20%3C%2FPRODUCT%3E%0A%20%3C%2FADD%3E%0A%3C%2FCONFIGURATION%3E%0A%3C%2FCODE%3E%3C%2FPRE%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%3CSPAN%3EAbove%20XML%20will%20do%20the%20following%20for%20you%3A%3C%2FSPAN%3E%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3E%3CSPAN%3EAs%20OfficeClientEdition%20is%20not%20specified%2C%20the%20ODT%20will%20automatically%20match%20the%20new%20install%20to%20the%20already%20installed%20product.%20So%20this%20is%20a%20x86%2Fx64%20universal%20configuration%20(%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FOffice-365-ProPlus%2FInsights-into-OfficeClientEdition-and-how-to-make-it-work-for%2Fm-p%2F767577%22%20target%3D%22_blank%22%20rel%3D%22noopener%22%3Eread%20more%20about%20it%20here%3C%2FA%3E).%3C%2FSPAN%3E%3C%2FLI%3E%0A%3CLI%3E%3CSPAN%3EThe%20to-be%20installed%20version%20will%20match%20the%20installed%20one.%20Even%20if%20a%20newer%20version%20is%20available%20e.g.%20on%20the%20OfficeCDN%2C%20it%20will%20not%20do%20an%20implicit%20update%20(Read%20more%20about%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FOffice-365-ProPlus%2FNew-feature-Make-changes-to-Office-deployments-without-changing%2Fm-p%2F481948%2Fthread-id%2F655%22%20target%3D%22_blank%22%20rel%3D%22noopener%22%3EVersion%3D%22MatchInstalled%22%3C%2FA%3E).%3C%2FSPAN%3E%3C%2FLI%3E%0A%3CLI%3E%3CSPAN%3EVisio%20will%20be%20deployed%20with%20the%20very%20same%20languages%20as%20Office%20365%20ProPlus%20is%20already%20installed%20with.%20For%20more%20details%20please%20check%20out%20this%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FOffice-365-ProPlus%2FDynamically-match-already-existing-languages-when-installing%2Fm-p%2F716927%22%20target%3D%22_blank%22%20rel%3D%22noopener%22%3Eblog%20post%3C%2FA%3E.%3C%2FSPAN%3E%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%3CSPAN%3ESo%2C%20we%20have%20a%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FOffice-365-Blog%2FBuilding-dynamic-lean-amp-universal-packages-for-Office-365%2Fba-p%2F839658%22%20target%3D%22_blank%22%20rel%3D%22noopener%22%3Edynamic%2C%20lean%20and%20universal%3C%2FA%3Econfiguration%20file%20which%20has%20no%20hard-coded%20architecture%2C%20languages%2C%20update%20channel%20or%20version.%20You%20can%20build%20this%20e.g.%20SCCM%20application%20once%20and%20use%20it%20for%20all%20update%20channels.%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CH2%20id%3D%22toc-hId-1008028095%22%20id%3D%22toc-hId--1473370100%22%20id%3D%22toc-hId--1473370100%22%20id%3D%22toc-hId--1473370100%22%3E%3CSPAN%3EBenefits%3C%2FSPAN%3E%3C%2FH2%3E%0A%3CP%3EIn%20the%20past%20configuration%20files%20were%20static%2C%20each%20covering%20one%20specific%20scenario%2Fconfiguration.%20By%20using%20new%20features%20like%20Version%3DMatchInstalled%2C%20Language%3DMatchInstalled%20together%20with%20dynamic%20OfficeClientEdition%20and%20update%20channel%2C%20you%20can%20build%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FOffice-365-Blog%2FBuilding-dynamic-lean-amp-universal-packages-for-Office-365%2Fba-p%2F839658%22%20target%3D%22_blank%22%20rel%3D%22noopener%22%3Euniversal%20configuration%20files%3C%2FA%3Ewhich%20cover%20multiple%20scenarios.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThis%20resolves%20the%20two%20issues%20described%20above%3A%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3EYou%20only%20need%20one%20installation%20package%20(e.g.%20an%20SCCM%20app)%20per%20component.%20For%20most%20environments%20(running%20MC%2C%20SAC%20and%20SAC-T)%20this%20reduces%20the%20effort%20by%2066%25%2C%20because%20you%20don%E2%80%99t%20have%20to%20build%20each%20package%20three%20times.%3C%2FLI%3E%0A%3CLI%3EYour%20users%20will%20be%20happy%2C%20as%20they%20can%20easily%20identify%20what%20they%20need%20from%20the%20Software%20Center.%20They%20don%E2%80%99t%20have%20to%20worry%20about%20which%20update%20channels%20they%20are%20on.%20It%20just%20works.%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CH2%20id%3D%22toc-hId--1544128866%22%20id%3D%22toc-hId-269440235%22%20id%3D%22toc-hId-269440235%22%20id%3D%22toc-hId-269440235%22%3E%3CSPAN%3EPrerequisites%3C%2FSPAN%3E%3C%2FH2%3E%0A%3CUL%3E%0A%3CLI%3EThe%20ODT%20must%20be%20able%20to%20locate%20the%20matching%20source%20files%20on%20the%20Office%20CDN.%20Including%20the%20source%20files%20in%20the%20SCCM%20app%20would%20require%20having%20the%20exactly%20matching%20version%20included.%20Same%20goes%20for%20network%20shares%2Flocal%20folders.%20We%20recommend%20using%20the%20Office%20CDN%20instead.%3C%2FLI%3E%0A%3CLI%3EI%20always%20recommend%20to%20also%20make%20sure%20that%20you%20use%20the%20latest%20ODT%20available.%20There%20is%20no%20specific%20min.%20version%20for%20the%20Channel-attribute%2C%20but%20it%20is%20a%20good%20practice%20to%20always%20update%20the%20ODT%20when%20you%E2%80%99re%20touching%20it%20anyways.%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CH2%20id%3D%22toc-hId-198681469%22%20id%3D%22toc-hId-2012250570%22%20id%3D%22toc-hId-2012250570%22%20id%3D%22toc-hId-2012250570%22%3EThe%20Author%3C%2FH2%3E%0A%3CP%3EThis%20blog%20post%20is%20brought%20to%20you%20by%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F6347%22%20target%3D%22_blank%22%3E%40Martin%20Nothnagel%3C%2FA%3E%2C%20a%20ProPlus%20Ranger%20and%20senior%20ProPlus%20deployment%20expert%20at%20Microsoft.%20Feel%20free%20to%20share%20your%20questions%20and%20feedback%20in%20the%20comments%20below.%3C%2FP%3E%0A%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIn%20nearly%20every%20configuration%20file%20(aka%20config.xml)%20you%20will%20find%20this%20attribute%2C%20but%20have%20you%20known%20that%20this%20is%20actually%20an%20optional%20attribute%20and%20can%20be%20used%20to%20build%20leaner%20deployments%20which%20require%20less%20maintenance%3F%20I%20will%20walk%20you%20through%20the%20steps%20on%20how%20the%20Channel-attribute%20works%20during%20the%20initial%20installation%20of%20Office%20365%20Client%20Apps%20and%20how%20to%20leverage%20it%20for%20reducing%20your%20effort%20when%20building%20sub-sequent%20installs%20(Project%2C%20Visio%2C%20%E2%80%A6).%3C%2FP%3E%0A%3CP%3E%3CSPAN%3EWhen%20designing%20an%20Office%20365%20ProPlus%20deployment%2C%20especially%20in%20larger%20organizations%2C%20the%20%E2%80%9CUpdate%20Channel%E2%80%9D%20to%20use%20is%20an%20important%20factor.%20It%20controls%20the%20balance%20between%20receiving%20new%20features%20quickly%20and%20providing%20phases%20of%20%E2%80%9Cno%20changes%E2%80%9D%20for%20the%20IT.%20It%E2%80%99s%20important%20to%20understand%20%3C%2FSPAN%3Ethe%20%3CSPAN%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fdeployoffice%2Foverview-of-update-channels-for-office-365-proplus%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Efoundational%20concepts%3C%2FA%3E%3C%2FSPAN%3E%2C%20%3CSPAN%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fdeployoffice%2Fmanage-updates-to-office-365-proplus-with-system-center-configuration-manager%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Eways%20to%20implement%20it%3C%2FA%3E%3C%2FSPAN%3Eas%20well%20as%20the%20%3CSPAN%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fdeployoffice%2Fchange-management-for-office-365-clients%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Echange%20management%3C%2FA%3E%3C%2FSPAN%3Eview%20on%20this%20topic.%20But%20this%20post%20will%20just%20focus%20on%20the%20channel%20assignment%20done%20through%20the%20ODT.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CH2%20id%3D%22toc-hId-1817374721%22%20id%3D%22toc-hId--539906391%22%20id%3D%22toc-hId--539906391%22%3E%3CSPAN%3EScenario%3A%20Initial%20installation%3C%2FSPAN%3E%3C%2FH2%3E%0A%3CP%3EWhen%20you%20deploy%20Office%20365%20ProPlus%20for%20the%20first%20time%20to%20a%20device%2C%20the%20channel%20attribute%20works%20pretty%20straight%20forward%3A%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3EIf%20you%20have%20specified%20the%20channel%20(usually%20Monthly%20or%20Semi-Annual)%2C%20ODT%20will%20just%20install%20the%20latest%2Favailable%20or%20specified%20version%20of%20Office%20from%20this%20channel.%3C%2FLI%3E%0A%3CLI%3EIf%20you%20haven%E2%80%99t%20specified%20the%20channel%2C%20the%20%3CSPAN%3E%3CA%20href%3D%22https%3A%2F%2Faka.ms%2FODT%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3EOffice%20Deployment%20Tool%3C%2FA%3E%3C%2FSPAN%3E(ODT)%20will%20use%20the%20following%20%3CSPAN%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fdeployoffice%2Fconfiguration-options-for-the-office-2016-deployment-tool%23add-element%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Edefault%20values%3C%2FA%3E%3C%2FSPAN%3E%3A%0A%3CUL%3E%0A%3CLI%3ESemi-Annual%20Channel%20for%20Office%20365%20ProPlus.%3C%2FLI%3E%0A%3CLI%3ESemi-Annual%20Channel%20for%20Visio%2FProject%20when%20installed%20at%20the%20same%20time%20as%20Office.%3C%2FLI%3E%0A%3CLI%3EMonthly%20Channel%20for%20Visio%2FProject%2C%20if%20not%20installed%20alongside%20Office.%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EMost%20IT%20admins%20are%20not%20aware%20of%20the%20optional%20nature%20of%20the%20channel%20assignment%2C%20but%20there%20is%20not%20too%20much%20we%20can%20optimize%20here.%20The%20meat%20and%20potatoes%20lies%20in%20the%202%3CSUP%3End%3C%2FSUP%3Einstall%20scenario.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CH2%20id%3D%22toc-hId--734782240%22%20id%3D%22toc-hId-1202903944%22%20id%3D%22toc-hId-1202903944%22%3E%3CSPAN%3EScenario%3A%20Adding%20Visio%2C%20Project%2C%20Language%20Packs%2C%20Proofing%20Tools%20or%20other%20components%3C%2FSPAN%3E%3C%2FH2%3E%0A%3CP%3E%3CSPAN%3ELet%E2%80%99s%20assume%20that%20Office%20365%20ProPlus%20is%20already%20deployed%20to%20a%20device%20and%20you%20as%20the%20IT%20admin%20has%20to%20provide%20ways%20to%20install%20additional%20Language%20Packs%2C%20Visio%2C%20Project%2C%20and%20Proofing%20Tools.%20Most%20organizations%20run%20a%20mix%20of%20SAC%20and%20SAC-T%20%2C%20more%20often%20than%20not%20you%20also%20have%20a%20small%20population%20on%20Monthly%20Channel.%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%3CSPAN%3EThis%20poses%20two%20%3CSTRONG%3Echallenges%3C%2FSTRONG%3Ewhen%20going%20with%20the%20common%20approach%20of%20specifying%20the%20Channel%20attribute%3A%20%3C%2FSPAN%3E%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3E%3CSPAN%3EYou%20end%20up%20with%20a%20high%20number%20of%20install%20packages.%20E.g.%20when%20you%20want%20to%20provide%20one%20additional%20language%20as%20well%20as%20Visio%20and%20Project%20to%20your%20users%2C%20you%20end%20up%20with%20three%20install%20packages%20multiplied%20by%20the%20number%20of%20update%20channels%20you%20support.%3C%2FSPAN%3E%3C%2FLI%3E%0A%3CLI%3E%3CSPAN%3EYour%20users%20are%20confused.%20If%20you%20want%20to%20provide%20a%20self-service%20to%20your%20users%2C%20e.g.%20through%20SCCM%20Software%20Center%2C%20they%20will%20see%20all%20these%20install%20packages%20and%20must%20pick%20the%20one%20which%20is%20matching%20their%20currently%20installed%20update%20channel.%20Most%20users%20don%E2%80%99t%20have%20a%20clue%20which%20channel%20they%20are%20on.%3C%2FSPAN%3E%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%3CSPAN%3EBut%20ODT%20to%20the%20rescue!%20A%20little%20known%20fact%20is%2C%20that%20ODT%20will%20default%20to%20the%20assigned%20channel%20of%20the%20existing%20installation%2C%20if%20the%20attribute%20is%20not%20set.%20We%20can%20leverage%20this%20behavior%20to%20remove%20the%20(perceived)%20need%20to%20build%20one%20configuration%20file%20per%20deployed%20update%20channel.%20This%20reduces%20the%20number%20of%20required%20configuration%20files%20(and%20install%20packages)%20significantly.%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%3CSPAN%3EHere%20is%20an%20example%20of%20a%20configuration%20file%20which%20adds%20Visio%20to%20an%20existing%20installation%20and%20will%20work%20for%20any%20update%20channel%3A%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CPRE%20class%3D%22lia-code-sample%20language-markup%22%3E%3CCODE%3E%3CCONFIGURATION%3E%0A%20%3CADD%20version%3D%22MatchInstalled%22%3E%0A%20%20%3CPRODUCT%20id%3D%22VisioProRetail%22%3E%0A%20%20%20%3CLANGUAGE%20id%3D%22MatchInstalled%22%20targetproduct%3D%22O365ProPlusRetail%22%3E%3C%2FLANGUAGE%3E%20%0A%20%20%3C%2FPRODUCT%3E%0A%20%3C%2FADD%3E%0A%3C%2FCONFIGURATION%3E%0A%3C%2FCODE%3E%3C%2FPRE%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%3CSPAN%3EAbove%20XML%20will%20do%20the%20following%20for%20you%3A%3C%2FSPAN%3E%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3E%3CSPAN%3EAs%20OfficeClientEdition%20is%20not%20specified%2C%20the%20ODT%20will%20automatically%20match%20the%20new%20install%20to%20the%20already%20installed%20product.%20So%20this%20is%20a%20x86%2Fx64%20universal%20configuration%20(%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FOffice-365-ProPlus%2FInsights-into-OfficeClientEdition-and-how-to-make-it-work-for%2Fm-p%2F767577%22%20target%3D%22_blank%22%20rel%3D%22noopener%22%3Eread%20more%20about%20it%20here%3C%2FA%3E).%3C%2FSPAN%3E%3C%2FLI%3E%0A%3CLI%3E%3CSPAN%3EThe%20to-be%20installed%20version%20will%20match%20the%20installed%20one.%20Even%20if%20a%20newer%20version%20is%20available%20e.g.%20on%20the%20OfficeCDN%2C%20it%20will%20not%20do%20an%20implicit%20update%20(Read%20more%20about%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FOffice-365-ProPlus%2FNew-feature-Make-changes-to-Office-deployments-without-changing%2Fm-p%2F481948%2Fthread-id%2F655%22%20target%3D%22_blank%22%20rel%3D%22noopener%22%3EVersion%3D%22MatchInstalled%22%3C%2FA%3E).%3C%2FSPAN%3E%3C%2FLI%3E%0A%3CLI%3E%3CSPAN%3EVisio%20will%20be%20deployed%20with%20the%20very%20same%20languages%20as%20Office%20365%20ProPlus%20is%20already%20installed%20with.%20For%20more%20details%20please%20check%20out%20this%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FOffice-365-ProPlus%2FDynamically-match-already-existing-languages-when-installing%2Fm-p%2F716927%22%20target%3D%22_blank%22%20rel%3D%22noopener%22%3Eblog%20post%3C%2FA%3E.%3C%2FSPAN%3E%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%3CSPAN%3ESo%2C%20we%20have%20a%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FOffice-365-Blog%2FBuilding-dynamic-lean-amp-universal-packages-for-Office-365%2Fba-p%2F839658%22%20target%3D%22_blank%22%20rel%3D%22noopener%22%3Edynamic%2C%20lean%20and%20universal%3C%2FA%3Econfiguration%20file%20which%20has%20no%20hard-coded%20architecture%2C%20languages%2C%20update%20channel%20or%20version.%20You%20can%20build%20this%20e.g.%20SCCM%20application%20once%20and%20use%20it%20for%20all%20update%20channels.%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CH2%20id%3D%22toc-hId-1008028095%22%20id%3D%22toc-hId--1349253017%22%20id%3D%22toc-hId--1349253017%22%3E%3CSPAN%3EBenefits%3C%2FSPAN%3E%3C%2FH2%3E%0A%3CP%3EIn%20the%20past%20configuration%20files%20were%20static%2C%20each%20covering%20one%20specific%20scenario%2Fconfiguration.%20By%20using%20new%20features%20like%20Version%3DMatchInstalled%2C%20Language%3DMatchInstalled%20together%20with%20dynamic%20OfficeClientEdition%20and%20update%20channel%2C%20you%20can%20build%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FOffice-365-Blog%2FBuilding-dynamic-lean-amp-universal-packages-for-Office-365%2Fba-p%2F839658%22%20target%3D%22_blank%22%20rel%3D%22noopener%22%3Euniversal%20configuration%20files%3C%2FA%3Ewhich%20cover%20multiple%20scenarios.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThis%20resolves%20the%20two%20issues%20described%20above%3A%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3EYou%20only%20need%20one%20installation%20package%20(e.g.%20an%20SCCM%20app)%20per%20component.%20For%20most%20environments%20(running%20MC%2C%20SAC%20and%20SAC-T)%20this%20reduces%20the%20effort%20by%2066%25%2C%20because%20you%20don%E2%80%99t%20have%20to%20build%20each%20package%20three%20times.%3C%2FLI%3E%0A%3CLI%3EYour%20users%20will%20be%20happy%2C%20as%20they%20can%20easily%20identify%20what%20they%20need%20from%20the%20Software%20Center.%20They%20don%E2%80%99t%20have%20to%20worry%20about%20which%20update%20channels%20they%20are%20on.%20It%20just%20works.%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CH2%20id%3D%22toc-hId--1544128866%22%20id%3D%22toc-hId-393557318%22%20id%3D%22toc-hId-393557318%22%3E%3CSPAN%3EPrerequisites%3C%2FSPAN%3E%3C%2FH2%3E%0A%3CUL%3E%0A%3CLI%3EThe%20ODT%20must%20be%20able%20to%20locate%20the%20matching%20source%20files%20on%20the%20Office%20CDN.%20Including%20the%20source%20files%20in%20the%20SCCM%20app%20would%20require%20having%20the%20exactly%20matching%20version%20included.%20Same%20goes%20for%20network%20shares%2Flocal%20folders.%20We%20recommend%20using%20the%20Office%20CDN%20instead.%3C%2FLI%3E%0A%3CLI%3EI%20always%20recommend%20to%20also%20make%20sure%20that%20you%20use%20the%20latest%20ODT%20available.%20There%20is%20no%20specific%20min.%20version%20for%20the%20Channel-attribute%2C%20but%20it%20is%20a%20good%20practice%20to%20always%20update%20the%20ODT%20when%20you%E2%80%99re%20touching%20it%20anyways.%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CH2%20id%3D%22toc-hId-198681469%22%20id%3D%22toc-hId-2136367653%22%20id%3D%22toc-hId-2136367653%22%3EThe%20Author%3C%2FH2%3E%0A%3CP%3EThis%20blog%20post%20is%20brought%20to%20you%20by%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F6347%22%20target%3D%22_blank%22%3E%40Martin%20Nothnagel%3C%2FA%3E%2C%20a%20ProPlus%20Ranger%20and%20senior%20ProPlus%20deployment%20expert%20at%20Microsoft.%20Feel%20free%20to%20share%20your%20questions%20and%20feedback%20in%20the%20comments%20below.%3C%2FP%3E%3CLINGO-SUB%20id%3D%22lingo-sub-813604%22%20slang%3D%22en-US%22%3EUnderstanding%20the%20Channel-attribute%20of%20the%20Office%20Deployment%20Tool%20%26amp%3B%20how%20to%20optimize%20your%20deployment%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-813604%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSPAN%3EIn%20today%E2%80%99s%20post%20I%20would%20like%20to%20provide%20some%20insights%20into%20the%20Channel-attribute%20used%20in%20the%20%3CADD%3E-section%20of%20the%20configuration%20files%20for%20the%20%3CA%20href%3D%22https%3A%2F%2Faka.ms%2FODT%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%22%3EOffice%20Deployment%20Tool%3C%2FA%3E%3C%2FADD%3E%3C%2FSPAN%3E(ODT)%20and%20how%20it%20can%20be%20used%20for%20implementing%20%22%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FOffice-365-Blog%2FBuilding-dynamic-lean-amp-universal-packages-for-Office-365%2Fba-p%2F839658%22%20target%3D%22_blank%22%20rel%3D%22noopener%22%3Edynamic%2C%20lean%20and%20universal%3C%2FA%3E%22%20packages%3A%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CPRE%20class%3D%22lia-code-sample%20language-markup%22%3E%3CCODE%3E%3CCONFIGURATION%3E%0A%20%3CADD%20channel%3D%22Broad%22%3E%3C%2FADD%3E%0A%20%20%3CPRODUCT%20id%3D%22O365ProPlusRetail%22%3E%0A%20%20%20%3CLANGUAGE%20id%3D%22de-de%22%3E%3C%2FLANGUAGE%3E%0A%20%20%3C%2FPRODUCT%3E%0A%20%3C%2FCONFIGURATION%3E%0A%3C%2FCODE%3E%3C%2FPRE%3E%3C%2FLINGO-BODY%3E%0A%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIn%20nearly%20every%20configuration%20file%20(aka%20config.xml)%20you%20will%20find%20this%20attribute%2C%20but%20have%20you%20known%20that%20this%20is%20actually%20an%20optional%20attribute%20and%20can%20be%20used%20to%20build%20leaner%20deployments%20which%20require%20less%20maintenance%3F%20I%20will%20walk%20you%20through%20the%20steps%20on%20how%20the%20Channel-attribute%20works%20during%20the%20initial%20installation%20of%20Office%20365%20Client%20Apps%20and%20how%20to%20leverage%20it%20for%20reducing%20your%20effort%20when%20building%20sub-sequent%20installs%20(Project%2C%20Visio%2C%20%E2%80%A6).%3C%2FP%3E%0A%3CP%3E%3CSPAN%3EWhen%20designing%20an%20Office%20365%20ProPlus%20deployment%2C%20especially%20in%20larger%20organizations%2C%20the%20%E2%80%9CUpdate%20Channel%E2%80%9D%20to%20use%20is%20an%20important%20factor.%20It%20controls%20the%20balance%20between%20receiving%20new%20features%20quickly%20and%20providing%20phases%20of%20%E2%80%9Cno%20changes%E2%80%9D%20for%20the%20IT.%20It%E2%80%99s%20important%20to%20understand%20%3C%2FSPAN%3Ethe%20%3CSPAN%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fdeployoffice%2Foverview-of-update-channels-for-office-365-proplus%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%22%3Efoundational%20concepts%3C%2FA%3E%3C%2FSPAN%3E%2C%20%3CSPAN%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fdeployoffice%2Fmanage-updates-to-office-365-proplus-with-system-center-configuration-manager%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%22%3Eways%20to%20implement%20it%3C%2FA%3E%3C%2FSPAN%3Eas%20well%20as%20the%20%3CSPAN%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fdeployoffice%2Fchange-management-for-office-365-clients%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%22%3Echange%20management%3C%2FA%3E%3C%2FSPAN%3Eview%20on%20this%20topic.%20But%20this%20post%20will%20just%20focus%20on%20the%20channel%20assignment%20done%20through%20the%20ODT.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CH2%20id%3D%22toc-hId-1817374721%22%20id%3D%22toc-hId-1823489359%22%3E%3CSPAN%3EScenario%3A%20Initial%20installation%3C%2FSPAN%3E%3C%2FH2%3E%0A%3CP%3EWhen%20you%20deploy%20Office%20365%20ProPlus%20for%20the%20first%20time%20to%20a%20device%2C%20the%20channel%20attribute%20works%20pretty%20straight%20forward%3A%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3EIf%20you%20have%20specified%20the%20channel%20(usually%20Monthly%20or%20Semi-Annual)%2C%20ODT%20will%20just%20install%20the%20latest%2Favailable%20or%20specified%20version%20of%20Office%20from%20this%20channel.%3C%2FLI%3E%0A%3CLI%3EIf%20you%20haven%E2%80%99t%20specified%20the%20channel%2C%20the%20%3CSPAN%3E%3CA%20href%3D%22https%3A%2F%2Faka.ms%2FODT%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%22%3EOffice%20Deployment%20Tool%3C%2FA%3E%3C%2FSPAN%3E(ODT)%20will%20use%20the%20following%20%3CSPAN%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fdeployoffice%2Fconfiguration-options-for-the-office-2016-deployment-tool%23add-element%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%22%3Edefault%20values%3C%2FA%3E%3C%2FSPAN%3E%3A%0A%3CUL%3E%0A%3CLI%3ESemi-Annual%20Channel%20for%20Office%20365%20ProPlus.%3C%2FLI%3E%0A%3CLI%3ESemi-Annual%20Channel%20for%20Visio%2FProject%20when%20installed%20at%20the%20same%20time%20as%20Office.%3C%2FLI%3E%0A%3CLI%3EMonthly%20Channel%20for%20Visio%2FProject%2C%20if%20not%20installed%20alongside%20Office.%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EMost%20IT%20admins%20are%20not%20aware%20of%20the%20optional%20nature%20of%20the%20channel%20assignment%2C%20but%20there%20is%20not%20too%20much%20we%20can%20optimize%20here.%20The%20meat%20and%20potatoes%20lies%20in%20the%202%3CSUP%3End%3C%2FSUP%3Einstall%20scenario.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CH2%20id%3D%22toc-hId--734782240%22%20id%3D%22toc-hId--728667602%22%3E%3CSPAN%3EScenario%3A%20Adding%20Visio%2C%20Project%2C%20Language%20Packs%2C%20Proofing%20Tools%20or%20other%20components%3C%2FSPAN%3E%3C%2FH2%3E%0A%3CP%3E%3CSPAN%3ELet%E2%80%99s%20assume%20that%20Office%20365%20ProPlus%20is%20already%20deployed%20to%20a%20device%20and%20you%20as%20the%20IT%20admin%20has%20to%20provide%20ways%20to%20install%20additional%20Language%20Packs%2C%20Visio%2C%20Project%2C%20and%20Proofing%20Tools.%20Most%20organizations%20run%20a%20mix%20of%20SAC%20and%20SAC-T%20%2C%20more%20often%20than%20not%20you%20also%20have%20a%20small%20population%20on%20Monthly%20Channel.%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%3CSPAN%3EThis%20poses%20two%20%3CSTRONG%3Echallenges%3C%2FSTRONG%3Ewhen%20going%20with%20the%20common%20approach%20of%20specifying%20the%20Channel%20attribute%3A%20%3C%2FSPAN%3E%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3E%3CSPAN%3EYou%20end%20up%20with%20a%20high%20number%20of%20install%20packages.%20E.g.%20when%20you%20want%20to%20provide%20one%20additional%20language%20as%20well%20as%20Visio%20and%20Project%20to%20your%20users%2C%20you%20end%20up%20with%20three%20install%20packages%20multiplied%20by%20the%20number%20of%20update%20channels%20you%20support.%3C%2FSPAN%3E%3C%2FLI%3E%0A%3CLI%3E%3CSPAN%3EYour%20users%20are%20confused.%20If%20you%20want%20to%20provide%20a%20self-service%20to%20your%20users%2C%20e.g.%20through%20SCCM%20Software%20Center%2C%20they%20will%20see%20all%20these%20install%20packages%20and%20must%20pick%20the%20one%20which%20is%20matching%20their%20currently%20installed%20update%20channel.%20Most%20users%20don%E2%80%99t%20have%20a%20clue%20which%20channel%20they%20are%20on.%3C%2FSPAN%3E%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%3CSPAN%3EBut%20ODT%20to%20the%20rescue!%20A%20little%20known%20fact%20is%2C%20that%20ODT%20will%20default%20to%20the%20assigned%20channel%20of%20the%20existing%20installation%2C%20if%20the%20attribute%20is%20not%20set.%20We%20can%20leverage%20this%20behavior%20to%20remove%20the%20(perceived)%20need%20to%20build%20one%20configuration%20file%20per%20deployed%20update%20channel.%20This%20reduces%20the%20number%20of%20required%20configuration%20files%20(and%20install%20packages)%20significantly.%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%3CSPAN%3EHere%20is%20an%20example%20of%20a%20configuration%20file%20which%20adds%20Visio%20to%20an%20existing%20installation%20and%20will%20work%20for%20any%20update%20channel%3A%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CPRE%20class%3D%22lia-code-sample%20language-markup%22%3E%3CCODE%3E%3CCONFIGURATION%3E%0A%20%3CADD%20version%3D%22MatchInstalled%22%3E%0A%20%20%3CPRODUCT%20id%3D%22VisioProRetail%22%3E%0A%20%20%20%3CLANGUAGE%20id%3D%22MatchInstalled%22%20targetproduct%3D%22O365ProPlusRetail%22%3E%3C%2FLANGUAGE%3E%20%0A%20%20%3C%2FPRODUCT%3E%0A%20%3C%2FADD%3E%0A%3C%2FCONFIGURATION%3E%0A%3C%2FCODE%3E%3C%2FPRE%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%3EAbove%20XML%20will%20do%20the%20following%20for%20you%3A%3C%2FSPAN%3E%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3E%3CSPAN%3EAs%20OfficeClientEdition%20is%20not%20specified%2C%20the%20ODT%20will%20automatically%20match%20the%20new%20install%20to%20the%20already%20installed%20product.%20So%20this%20is%20a%20x86%2Fx64%20universal%20configuration%20(%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FOffice-365-ProPlus%2FInsights-into-OfficeClientEdition-and-how-to-make-it-work-for%2Fm-p%2F767577%22%20target%3D%22_blank%22%20rel%3D%22noopener%22%3Eread%20more%20about%20it%20here%3C%2FA%3E).%3C%2FSPAN%3E%3C%2FLI%3E%0A%3CLI%3E%3CSPAN%3EThe%20to-be%20installed%20version%20will%20match%20the%20installed%20one.%20Even%20if%20a%20newer%20version%20is%20available%20e.g.%20on%20the%20OfficeCDN%2C%20it%20will%20not%20do%20an%20implicit%20update%20(Read%20more%20about%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FOffice-365-ProPlus%2FNew-feature-Make-changes-to-Office-deployments-without-changing%2Fm-p%2F481948%2Fthread-id%2F655%22%20target%3D%22_blank%22%20rel%3D%22noopener%22%3EVersion%3D%22MatchInstalled%22%3C%2FA%3E).%3C%2FSPAN%3E%3C%2FLI%3E%0A%3CLI%3E%3CSPAN%3EVisio%20will%20be%20deployed%20with%20the%20very%20same%20languages%20as%20Office%20365%20ProPlus%20is%20already%20installed%20with.%20For%20more%20details%20please%20check%20out%20this%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FOffice-365-ProPlus%2FDynamically-match-already-existing-languages-when-installing%2Fm-p%2F716927%22%20target%3D%22_blank%22%20rel%3D%22noopener%22%3Eblog%20post%3C%2FA%3E.%3C%2FSPAN%3E%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%3CSPAN%3ESo%2C%20we%20have%20a%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FOffice-365-Blog%2FBuilding-dynamic-lean-amp-universal-packages-for-Office-365%2Fba-p%2F839658%22%20target%3D%22_blank%22%20rel%3D%22noopener%22%3Edynamic%2C%20lean%20and%20universal%3C%2FA%3Econfiguration%20file%20which%20has%20no%20hard-coded%20architecture%2C%20languages%2C%20update%20channel%20or%20version.%20You%20can%20build%20this%20e.g.%20SCCM%20application%20once%20and%20use%20it%20for%20all%20update%20channels.%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CH2%20id%3D%22toc-hId-1008028095%22%20id%3D%22toc-hId-1014142733%22%3E%3CSPAN%3EBenefits%3C%2FSPAN%3E%3C%2FH2%3E%0A%3CP%3EIn%20the%20past%20configuration%20files%20were%20static%2C%20each%20covering%20one%20specific%20scenario%2Fconfiguration.%20By%20using%20new%20features%20like%20Version%3DMatchInstalled%2C%20Language%3DMatchInstalled%20together%20with%20dynamic%20OfficeClientEdition%20and%20update%20channel%2C%20you%20can%20build%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FOffice-365-Blog%2FBuilding-dynamic-lean-amp-universal-packages-for-Office-365%2Fba-p%2F839658%22%20target%3D%22_blank%22%20rel%3D%22noopener%22%3Euniversal%20configuration%20files%3C%2FA%3Ewhich%20cover%20multiple%20scenarios.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThis%20resolves%20the%20two%20issues%20described%20above%3A%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3EYou%20only%20need%20one%20installation%20package%20(e.g.%20an%20SCCM%20app)%20per%20component.%20For%20most%20environments%20(running%20MC%2C%20SAC%20and%20SAC-T)%20this%20reduces%20the%20effort%20by%2066%25%2C%20because%20you%20don%E2%80%99t%20have%20to%20build%20each%20package%20three%20times.%3C%2FLI%3E%0A%3CLI%3EYour%20users%20will%20be%20happy%2C%20as%20they%20can%20easily%20identify%20what%20they%20need%20from%20the%20Software%20Center.%20They%20don%E2%80%99t%20have%20to%20worry%20about%20which%20update%20channels%20they%20are%20on.%20It%20just%20works.%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CH2%20id%3D%22toc-hId--1544128866%22%20id%3D%22toc-hId--1538014228%22%3E%3CSPAN%3EPrerequisites%3C%2FSPAN%3E%3C%2FH2%3E%0A%3CUL%3E%0A%3CLI%3EThe%20ODT%20must%20be%20able%20to%20locate%20the%20matching%20source%20files%20on%20the%20Office%20CDN.%20Including%20the%20source%20files%20in%20the%20SCCM%20app%20would%20require%20having%20the%20exactly%20matching%20version%20included.%20Same%20goes%20for%20network%20shares%2Flocal%20folders.%20We%20recommend%20using%20the%20Office%20CDN%20instead.%3C%2FLI%3E%0A%3CLI%3EI%20always%20recommend%20to%20also%20make%20sure%20that%20you%20use%20the%20latest%20ODT%20available.%20There%20is%20no%20specific%20min.%20version%20for%20the%20Channel-attribute%2C%20but%20it%20is%20a%20good%20practice%20to%20always%20update%20the%20ODT%20when%20you%E2%80%99re%20touching%20it%20anyways.%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CH2%20id%3D%22toc-hId-198681469%22%20id%3D%22toc-hId-204796107%22%3EThe%20Author%3C%2FH2%3E%0A%3CP%3EThis%20blog%20post%20is%20brought%20to%20you%20by%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F6347%22%20target%3D%22_blank%22%3E%40Martin%20Nothnagel%3C%2FA%3E%2C%20a%20ProPlus%20Ranger%20and%20senior%20ProPlus%20deployment%20expert%20at%20Microsoft.%20Feel%20free%20to%20share%20your%20questions%20and%20feedback%20in%20the%20comments%20below.%3C%2FP%3E
Highlighted
Martin Nothnagel
Microsoft

In today’s post I would like to provide some insights into the Channel-attribute used in the <Add>-section of the configuration files for the Office Deployment Tool (ODT) and how it can be used for implementing "dynamic, lean and universal" packages:

 

<Configuration>
	<Add Channel="Broad" />
		<Product ID="O365ProPlusRetail">
			<Language ID="de-de" />
		</Product>
	</Add>
</Configuration>

 

In nearly every configuration file (aka config.xml) you will find this attribute, but have you known that this is actually an optional attribute and can be used to build leaner deployments which require less maintenance? I will walk you through the steps on how the Channel-attribute works during the initial installation of Office 365 Client Apps and how to leverage it for reducing your effort when building sub-sequent installs (Project, Visio, …).

When designing an Office 365 ProPlus deployment, especially in larger organizations, the “Update Channel” to use is an important factor. It controls the balance between receiving new features quickly and providing phases of “no changes” for the IT. It’s important to understand the foundational concepts, ways to implement it as well as the change management view on this topic. But this post will just focus on the channel assignment done through the ODT.

 

Scenario: Initial installation

When you deploy Office 365 ProPlus for the first time to a device, the channel attribute works pretty straight forward:

 

  • If you have specified the channel (usually Monthly or Semi-Annual), ODT will just install the latest/available or specified version of Office from this channel.
  • If you haven’t specified the channel, the Office Deployment Tool (ODT) will use the following default values:
    • Semi-Annual Channel for Office 365 ProPlus.
    • Semi-Annual Channel for Visio/Project when installed at the same time as Office.
    • Monthly Channel for Visio/Project, if not installed alongside Office.

 

Most IT admins are not aware of the optional nature of the channel assignment, but there is not too much we can optimize here. The meat and potatoes lies in the 2nd install scenario.

 

Scenario: Adding Visio, Project, Language Packs, Proofing Tools or other components

Let’s assume that Office 365 ProPlus is already deployed to a device and you as the IT admin has to provide ways to install additional Language Packs, Visio, Project, and Proofing Tools. Most organizations run a mix of SAC and SAC-T , more often than not you also have a small population on Monthly Channel.

This poses two challenges when going with the common approach of specifying the Channel attribute:

  • You end up with a high number of install packages. E.g. when you want to provide one additional language as well as Visio and Project to your users, you end up with three install packages multiplied by the number of update channels you support.
  • Your users are confused. If you want to provide a self-service to your users, e.g. through SCCM Software Center, they will see all these install packages and must pick the one which is matching their currently installed update channel. Most users don’t have a clue which channel they are on.

But ODT to the rescue! A little known fact is, that ODT will default to the assigned channel of the existing installation, if the attribute is not set. We can leverage this behavior to remove the (perceived) need to build one configuration file per deployed update channel. This reduces the number of required configuration files (and install packages) significantly.

Here is an example of a configuration file which adds Visio to an existing installation and will work for any update channel:

 

<Configuration>
	<Add Version="MatchInstalled">
		<Product ID="VisioProRetail">
			<Language ID="MatchInstalled" TargetProduct="O365ProPlusRetail" /> 
		</Product>
	</Add>
</Configuration>

 

Above XML will do the following for you:

  • As OfficeClientEdition is not specified, the ODT will automatically match the new install to the already installed product. So this is a x86/x64 universal configuration (read more about it here).
  • The to-be installed version will match the installed one. Even if a newer version is available e.g. on the OfficeCDN, it will not do an implicit update (Read more about Version="MatchInstalled").
  • Visio will be deployed with the very same languages as Office 365 ProPlus is already installed with. For more details please check out this blog post.

So, we have a dynamic, lean and universal configuration file which has no hard-coded architecture, languages, update channel or version. You can build this e.g. SCCM application once and use it for all update channels.

 

Benefits

In the past configuration files were static, each covering one specific scenario/configuration. By using new features like Version=MatchInstalled, Language=MatchInstalled together with dynamic OfficeClientEdition and update channel, you can build universal configuration files which cover multiple scenarios.

 

This resolves the two issues described above:

  • You only need one installation package (e.g. an SCCM app) per component. For most environments (running MC, SAC and SAC-T) this reduces the effort by 66%, because you don’t have to build each package three times.
  • Your users will be happy, as they can easily identify what they need from the Software Center. They don’t have to worry about which update channels they are on. It just works.

 

Prerequisites

  • The ODT must be able to locate the matching source files on the Office CDN. Including the source files in the SCCM app would require having the exactly matching version included. Same goes for network shares/local folders. We recommend using the Office CDN instead.
  • I always recommend to also make sure that you use the latest ODT available. There is no specific min. version for the Channel-attribute, but it is a good practice to always update the ODT when you’re touching it anyways.

 

The Author

This blog post is brought to you by @Martin Nothnagel, a ProPlus Ranger and senior ProPlus deployment expert at Microsoft. Feel free to share your questions and feedback in the comments below.

Related Conversations
Extentions Synchronization
Deleted in Discussions on
3 Replies
Tabs and Dark Mode
cjc2112 in Discussions on
36 Replies
flashing a white screen while open new tab
Deleted in Discussions on
14 Replies
Stable version of Edge insider browser
HotCakeX in Discussions on
35 Replies
Security Community Webinars
Valon_Kolica in Security, Privacy & Compliance on
9 Replies