Home

Confused about Semi-Annual Channel (Pilot) and Semi-Annual Channel (Broad) Timing

%3CLINGO-SUB%20id%3D%22lingo-sub-67179%22%20slang%3D%22en-US%22%3EConfused%20about%20Semi-Annual%20Channel%20(Pilot)%20and%20Semi-Annual%20Channel%20(Broad)%20Timing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-67179%22%20slang%3D%22en-US%22%3E%3CP%3ESo%20the%20pilot%20comes%20on%20on%20a%20March%20and%20September%20timing.%20So%20the%20first%20will%20be%201709.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESo%20right%20now%20the%20latest%20CB%20is%201703.%20Does%20it%20become%20the%20last%20CBB%20or%20the%20first%20Semi-Annual%20Channel%20(Broad)%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIs%20the%20approximately%20four%20months%20between%20the%20release%20of%20a%20Semi-Annual%20Branch%20(Pilot)%20and%20the%20Semi-Annual%20Branch%20Channel%20(Broad)%3F%20Or%20are%20Semi-Annual%20Channel%20(Pilots)%20promoted%20to%20Semi-Annual%20Channel%20(Broads)%20on%20six%20month%20boundaries%20too%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EOn%20the%2018%20months%20support%3F%20Is%20that%20measured%20against%20both%20channels%20or%20the%20first%20(Pilot)%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAs%20you%20throttle%20release%20(based%20on%20hardware)%2C%20does%2018%20months%20come%20from%20the%20date%20first%20released%20for%20first%20hardware%20platform%2C%20or%20when%20available%20to%20all%20platforms%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-77678%22%20slang%3D%22en-US%22%3ERe%3A%20Confused%20about%20Semi-Annual%20Channel%20(Pilot)%20and%20Semi-Annual%20Channel%20(Broad)%20Timing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-77678%22%20slang%3D%22en-US%22%3E%3CBLOCKQUOTE%3E%3CHR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F3377%22%20target%3D%22_blank%22%3E%40Abhimanyu%20Singh%3C%2FA%3E%20wrote%3A%3CBR%20%2F%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F21544%22%20target%3D%22_blank%22%3E%40Michael%20Niehaus%3C%2FA%3E%2C%20Will%20the%20change%20in%20terminilogy%20affect%20the%20way%20configuration.xml%20is%20set%20for%20ODT%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20have%20ODT%20configured%20for%20two%20sets%20of%20people%20with%3C%2FP%3E%3CPRE%3Echannel%3D%22current%22%3C%2FPRE%3E%3CP%3E%26nbsp%3Band%3C%2FP%3E%3CPRE%3Echannel%3D%22deferred%22%3C%2FPRE%3E%3CP%3EAfter%20Sep-2017%2C%20will%20the%20terms%20need%20to%20be%20changed%20to%20something%20like%3C%2FP%3E%3CPRE%3Echannel%3D%22Semi-Annual%20Channel%20(Pilot)%22%3C%2FPRE%3E%3CP%3E%3CSPAN%3E%3F%3C%2FSPAN%3E%3C%2FP%3E%3CHR%20%2F%3E%3C%2FBLOCKQUOTE%3E%3CP%3E%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F21544%22%20target%3D%22_blank%22%3E%40Michael%20Niehaus%3C%2FA%3E%26nbsp%3B-%20Any%20clarification%20on%20the%20ODT%20channel%20names%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-71419%22%20slang%3D%22en-US%22%3ERe%3A%20Confused%20about%20Semi-Annual%20Channel%20(Pilot)%20and%20Semi-Annual%20Channel%20(Broad)%20Timing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-71419%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F21544%22%20target%3D%22_blank%22%3E%40Michael%20Niehaus%3C%2FA%3E%2C%20Will%20the%20change%20in%20terminilogy%20affect%20the%20way%20configuration.xml%20is%20set%20for%20ODT%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20have%20ODT%20configured%20for%20two%20sets%20of%20people%20with%3C%2FP%3E%3CPRE%3Echannel%3D%22current%22%3C%2FPRE%3E%3CP%3E%26nbsp%3Band%3C%2FP%3E%3CPRE%3Echannel%3D%22deferred%22%3C%2FPRE%3E%3CP%3EAfter%20Sep-2017%2C%20will%20the%20terms%20need%20to%20be%20changed%20to%20something%20like%3C%2FP%3E%3CPRE%3Echannel%3D%22Semi-Annual%20Channel%20(Pilot)%22%3C%2FPRE%3E%3CP%3E%3CSPAN%3E%3F%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-68297%22%20slang%3D%22en-US%22%3ERE%3A%20Confused%20about%20Semi-Annual%20Channel%20(Pilot)%20and%20Semi-Annual%20Channel%20(Broad)%20Timing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-68297%22%20slang%3D%22en-US%22%3EHi%20Michael%2C%20Will%20this%20naming%20convention%20also%20be%20used%20for%20ConfigMgr%3F%20And%0Aas%20ConfigMgr%20only%20has%20CB%20versions%2C%20will%20ConfigMgr%201709%20(assuming%20that%0Athey%20will%20also%20follow%20March-September%20cycle%20and%20not%20the%204-month%20cycle)%0Abe%20called%20Semi-Annual%20Channel%20%22Pilot%22%20too%3F%20That%20may%20not%20go%20down%20well%0Awith%20customers%2C%20running%20a%20Pilot%20version%20in%20their%20production.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-67893%22%20slang%3D%22en-US%22%3ERe%3A%20Confused%20about%20Semi-Annual%20Channel%20(Pilot)%20and%20Semi-Annual%20Channel%20(Broad)%20Timing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-67893%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Michael!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ENoticed%20too%20late%20that%20I%20missed%20the%20whole%20AMA%20sessions%20that%20would%20have%20been%20a%20very%20imporant%20one%20right%20now%20as%20I%20need%20to%20plan%20the%20months%20and%20years%20ahead.%20Is%20there%20any%20existing%20blog%20or%20presentation%20that%20would%20explain%20the%20timeline%20in%20a%20more%20detailed%20level%20forward.%20I%20should%20be%20able%20to%20present%20the%20critical%20timepoints%26nbsp%3Bto%20our%20Windows%2010%20migration%20project%20where%20we%20need%20to%20jump%20from%20one%20version%20to%20another%20and%20all%20help%20with%20timing%20would%20be%20very%20great.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAlso%20a%20question%20(that%20may%20have%20been%20answered%20during%20AMA)%3A%20is%20Office%20switching%20to%203-6%20month%20update%20cycles%20to%20stay%20in%20sync%20with%20Windows%2010%20feature%20updates%3F%20We%20need%20that%20info%20also%20to%20plan%20for%20things%20ahead.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-67711%22%20slang%3D%22en-US%22%3ERe%3A%20Confused%20about%20Semi-Annual%20Channel%20(Pilot)%20and%20Semi-Annual%20Channel%20(Broad)%20Timing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-67711%22%20slang%3D%22en-US%22%3E%3CP%3EI%20think%20changing%20the%20name%20completely%20would%20be%20more%20confusing.%20I%20like%20CB%20and%20CBB%20it%20made%20sence%20and%20it%20still%20does.%20I'm%20not%20realy%20looking%20forward%20to%20having%20to%20explain%20the%20road%20map%20all%20over%20again%20to%20my%20peers%20%3A(%3C%2Fimg%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-67259%22%20slang%3D%22en-US%22%3ERe%3A%20Confused%20about%20Semi-Annual%20Channel%20(Pilot)%20and%20Semi-Annual%20Channel%20(Broad)%20Timing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-67259%22%20slang%3D%22en-US%22%3E%3CP%3EYes%2C%20that's%20pretty%20much%20accurate.%20%26nbsp%3BWe%20do%20have%20to%20work%20out%20the%20finer%20points%20(e.g.%20if%20a%20release%20happens%20on%20the%202nd%20of%20the%20month%2C%20does%20the%2018%20months%20mean%20the%20last%20security%20update%20will%20be%20on%20the%20Patch%20Tuesday%20before%20that%2C%20or%20the%20Patch%20Tuesday%20after%20that).%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-67258%22%20slang%3D%22en-US%22%3ERe%3A%20Confused%20about%20Semi-Annual%20Channel%20(Pilot)%20and%20Semi-Annual%20Channel%20(Broad)%20Timing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-67258%22%20slang%3D%22en-US%22%3E%3CP%3ESorry%2C%20I%20meant%20that%20%22Pilot%22%20and%20%22Broad%22%20don't%20matter%20from%20the%20perspective%20of%20the%20servicing%2Fsupport%20timeline.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-67253%22%20slang%3D%22en-US%22%3ERe%3A%20Confused%20about%20Semi-Annual%20Channel%20(Pilot)%20and%20Semi-Annual%20Channel%20(Broad)%20Timing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-67253%22%20slang%3D%22en-US%22%3E%3CP%3EThis%20is%20what%20I'm%20hearing%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3COL%3E%3CLI%3E1709%20is%20released%20in%20September%202017.%20It's%20dubbed%20%22Semi%20Annual%20(Pilot)%22%2C%20and%20the%2018%20month%20clock%20starts%20ticking%20immediately.%3C%2FLI%3E%3CLI%3EA%20few%20months%20later%20(January%202018%2C%20if%20we're%20matching%20the%20Office%20Pro%20Plus%20timeline)%2C%201709%20is%20declared%20ready%20for%20Semi%20Annual%20(Broad).%20The%2018%20month%20clock%20is%20now%20at%2015%20months.%3C%2FLI%3E%3CLI%3E15%20Months%20later%20(March%202019)%2C%201709%20is%20no%20longer%20supported.%20There%20is%20no%2060-day%20%22grace%20period%22%2C%20as%20that%20was%20removed%20with%20implementation%20of%20this%20new%20servicing%20schedule.%3C%2FLI%3E%3C%2FOL%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWould%20that%20be%20an%20accurate%20life%20for%201709%2C%20under%20the%20new%20model%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-67224%22%20slang%3D%22en-US%22%3ERe%3A%20Confused%20about%20Semi-Annual%20Channel%20(Pilot)%20and%20Semi-Annual%20Channel%20(Broad)%20Timing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-67224%22%20slang%3D%22en-US%22%3E%3CP%3EMichael%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESorry%20I%20don't%20follow.%20Pilot%20and%20Broad%20do%20matter%3F%20I%20want%20a%20small%20trusted%20number%20of%20people%20on%20the%20non-supported%20preview%20just%20to%20track%20features%20and%20provide%20feedback.%20I%20want%20a%20only%20marginally%20slightly%20number%20of%20trusted%20people%20on%20Pilot%20to%20test%20with%20our%20hardware%20and%20software.%20The%20major%20of%20people%20will%20be%20on%20Broad.%20So%20I%20have%20to%20understand%20when%20a%20Pilot%20comes%20out%20and%20when%20it%20is%20promoted%20to%20a%20Broad.%20Finally%20some%20number%20of%20devices%2C%20not%20running%20Office%20may%20be%20on%20the%20LTSB.%20Correct%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESo%20I%20miss%20your%20point%20on%20them%20not%20mattering.%20We%20need%20to%20know%20the%20names%2C%20the%20constant%20changes%20are%20problematic.%20If%20you%20want%20to%20show%20consistency%20then%20you%20have%20to%20show%20this%20more%20than%20aspirational%20it%20is%20consistently%20repeatable.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-67220%22%20slang%3D%22en-US%22%3ERe%3A%20Confused%20about%20Semi-Annual%20Channel%20(Pilot)%20and%20Semi-Annual%20Channel%20(Broad)%20Timing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-67220%22%20slang%3D%22en-US%22%3E%3CP%3ESo%20in%20the%20case%20of%20v1703%2C%20announced%20late%20March%2C%20but%20released%20April%2011th%2C%20support%20will%20therefore%20end%20on%20October%2011th%202018%2C%20or%20the%20date%20that%20v1809%20is%20released%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-67214%22%20slang%3D%22en-US%22%3ERe%3A%20Confused%20about%20Semi-Annual%20Channel%20(Pilot)%20and%20Semi-Annual%20Channel%20(Broad)%20Timing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-67214%22%20slang%3D%22en-US%22%3E%3CP%3EThat's%20why%20we're%20changing%20the%20terminology%20%3A)%3C%2Fimg%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EWhat's%20important%20are%20releases%20to%20the%20Semi-Annual%20Channel.%20%26nbsp%3BDon't%20focus%20so%20much%20on%20%22Pilot%22%20vs.%20%22Broad%22%20-%20those%20are%20just%20%22states%22%20or%20%22statuses%22%20of%20a%20particular%20release.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-67208%22%20slang%3D%22en-US%22%3ERe%3A%20Confused%20about%20Semi-Annual%20Channel%20(Pilot)%20and%20Semi-Annual%20Channel%20(Broad)%20Timing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-67208%22%20slang%3D%22en-US%22%3E%3CP%3ESo%20the%20branches%20don't%20transition%20to%20channels.%20Branches%20end%20when%201703%20ends%20out%20as%20CB.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EFirst%20channel%20starts%20with%201709.%2018%20Months%20measured%20from%20first%20day%20as%20a%20channel.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-67207%22%20slang%3D%22en-US%22%3ERe%3A%20Confused%20about%20Semi-Annual%20Channel%20(Pilot)%20and%20Semi-Annual%20Channel%20(Broad)%20Timing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-67207%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%20Michael%3A%3C%2FP%3E%3CP%3E%22%3CSPAN%3ERegardless%20of%20the%20terms%2C%20the%2018%20months%20is%20for%20the%20release%2C%20e.g.%20Windows%2010%201703%2C%20and%20that%2018%20months%20starts%20from%20the%20date%20that%20it%20was%20released.%22%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3EBy%20%22released%22%2C%20do%20you%20mean%20%22released%20to%20the%20Semi-annual%20(Pilot)%20Channel%22%3F%20Or%20Semi-annual%20(Broad)%3F%20Insider%3F%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-67202%22%20slang%3D%22en-US%22%3ERe%3A%20Confused%20about%20Semi-Annual%20Channel%20(Pilot)%20and%20Semi-Annual%20Channel%20(Broad)%20Timing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-67202%22%20slang%3D%22en-US%22%3E%3CP%3EThose%20are%20the%20new%20terms%20that%20we're%20working%20on.%20%26nbsp%3BSo%20let%20me%20answer%20that%20in%20two%20different%20ways%2C%20%22old%22%20vs.%20%22new%22%20terms%3A%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3ENew%20Windows%2010%20releases%20are%20initially%20considered%20%22Current%20Branch%22%20releases%2C%20to%20be%20used%20for%20piloting.%20%26nbsp%3BAfter%20a%20period%20of%20about%20four%20months%2C%20we'll%20declare%20the%20release%20as%20a%20%22Current%20Branch%20for%20Business%22%20release%2C%20ready%20for%20broad%20deployment.%3C%2FLI%3E%0A%3CLI%3ENew%20Windows%2010%20releases%20in%20the%20Semi-Annual%20Channel%20are%20initially%20to%20be%20used%20for%20pilot%20deployments.%20%26nbsp%3BAfter%20about%20four%20months%2C%20we'll%20declare%20that%20the%20release%20is%20ready%20for%20broad%20deployment.%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3ERegardless%20of%20the%20terms%2C%20the%2018%20months%20is%20for%20the%20release%2C%20e.g.%20Windows%2010%201703%2C%20and%20that%2018%20months%20starts%20from%20the%20date%20that%20it%20was%20released.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Michael Cherry
Occasional Contributor

So the pilot comes on on a March and September timing. So the first will be 1709.

 

So right now the latest CB is 1703. Does it become the last CBB or the first Semi-Annual Channel (Broad)?

 

Is the approximately four months between the release of a Semi-Annual Branch (Pilot) and the Semi-Annual Branch Channel (Broad)? Or are Semi-Annual Channel (Pilots) promoted to Semi-Annual Channel (Broads) on six month boundaries too?

 

On the 18 months support? Is that measured against both channels or the first (Pilot)?

 

As you throttle release (based on hardware), does 18 months come from the date first released for first hardware platform, or when available to all platforms?

 

Thanks

 

14 Replies

Those are the new terms that we're working on.  So let me answer that in two different ways, "old" vs. "new" terms:

 

  • New Windows 10 releases are initially considered "Current Branch" releases, to be used for piloting.  After a period of about four months, we'll declare the release as a "Current Branch for Business" release, ready for broad deployment.
  • New Windows 10 releases in the Semi-Annual Channel are initially to be used for pilot deployments.  After about four months, we'll declare that the release is ready for broad deployment.

Regardless of the terms, the 18 months is for the release, e.g. Windows 10 1703, and that 18 months starts from the date that it was released.

Hi, Michael:

"Regardless of the terms, the 18 months is for the release, e.g. Windows 10 1703, and that 18 months starts from the date that it was released."

By "released", do you mean "released to the Semi-annual (Pilot) Channel"? Or Semi-annual (Broad)? Insider?

So the branches don't transition to channels. Branches end when 1703 ends out as CB.

 

First channel starts with 1709. 18 Months measured from first day as a channel.

That's why we're changing the terminology :)

 

What's important are releases to the Semi-Annual Channel.  Don't focus so much on "Pilot" vs. "Broad" - those are just "states" or "statuses" of a particular release.

So in the case of v1703, announced late March, but released April 11th, support will therefore end on October 11th 2018, or the date that v1809 is released?

Michael,

 

Sorry I don't follow. Pilot and Broad do matter? I want a small trusted number of people on the non-supported preview just to track features and provide feedback. I want a only marginally slightly number of trusted people on Pilot to test with our hardware and software. The major of people will be on Broad. So I have to understand when a Pilot comes out and when it is promoted to a Broad. Finally some number of devices, not running Office may be on the LTSB. Correct?

 

So I miss your point on them not mattering. We need to know the names, the constant changes are problematic. If you want to show consistency then you have to show this more than aspirational it is consistently repeatable.

Highlighted

This is what I'm hearing:

 

  1. 1709 is released in September 2017. It's dubbed "Semi Annual (Pilot)", and the 18 month clock starts ticking immediately.
  2. A few months later (January 2018, if we're matching the Office Pro Plus timeline), 1709 is declared ready for Semi Annual (Broad). The 18 month clock is now at 15 months.
  3. 15 Months later (March 2019), 1709 is no longer supported. There is no 60-day "grace period", as that was removed with implementation of this new servicing schedule.

 

Would that be an accurate life for 1709, under the new model?

Sorry, I meant that "Pilot" and "Broad" don't matter from the perspective of the servicing/support timeline.

Yes, that's pretty much accurate.  We do have to work out the finer points (e.g. if a release happens on the 2nd of the month, does the 18 months mean the last security update will be on the Patch Tuesday before that, or the Patch Tuesday after that).

I think changing the name completely would be more confusing. I like CB and CBB it made sence and it still does. I'm not realy looking forward to having to explain the road map all over again to my peers :(

Hi Michael!

 

Noticed too late that I missed the whole AMA sessions that would have been a very imporant one right now as I need to plan the months and years ahead. Is there any existing blog or presentation that would explain the timeline in a more detailed level forward. I should be able to present the critical timepoints to our Windows 10 migration project where we need to jump from one version to another and all help with timing would be very great.

 

Also a question (that may have been answered during AMA): is Office switching to 3-6 month update cycles to stay in sync with Windows 10 feature updates? We need that info also to plan for things ahead.

Hi Michael, Will this naming convention also be used for ConfigMgr? And as ConfigMgr only has CB versions, will ConfigMgr 1709 (assuming that they will also follow March-September cycle and not the 4-month cycle) be called Semi-Annual Channel "Pilot" too? That may not go down well with customers, running a Pilot version in their production.

@Michael Niehaus, Will the change in terminilogy affect the way configuration.xml is set for ODT?

 

We have ODT configured for two sets of people with

channel="current"

 and

channel="deferred"

After Sep-2017, will the terms need to be changed to something like

channel="Semi-Annual Channel (Pilot)"

?


@Abhimanyu Singh wrote:

@Michael Niehaus, Will the change in terminilogy affect the way configuration.xml is set for ODT?

 

We have ODT configured for two sets of people with

channel="current"

 and

channel="deferred"

After Sep-2017, will the terms need to be changed to something like

channel="Semi-Annual Channel (Pilot)"

?


 @Michael Niehaus - Any clarification on the ODT channel names?

 

Related Conversations
flashing a white screen while open new tab
cntvertex in Discussions on
13 Replies
Tabs and Dark Mode
cjc2112 in Discussions on
22 Replies
Stable version of Edge insider browser
HotCakeX in Discussions on
35 Replies
How to Prevent Teams from Auto-Launch
chenrylee in Microsoft Teams on
28 Replies
PacketMon Components are not loading in WAC 1909
HotCakeX in Windows Admin Center on
2 Replies