Home
%3CLINGO-SUB%20id%3D%22lingo-sub-369767%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%20Update%20for%20Business%20and%20the%20retirement%20of%20SAC-T%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-369767%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSPAN%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F33735%22%20target%3D%22_blank%22%3E%40Oleg%20K%3C%2FA%3E%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3E%26gt%3BI%20guess%2030%20months%20support%20is%20designed%20for%20those%20using%20ConfigMgr%2FWSUS%20to%20distribute%20feature%20updates.%20They%20can%20wait%20longer%20than%20365%20days.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EI%20don't%20know%20so%20curious%20for%20anyone%20to%20comment.%20That%20apart%3A%20ConfigMgr%2FWSUS%20out%20here%20in%20K12%20(some%202.000%20schools)%20probably%20represents%20less%20than%203%20to%205%25%20of%20schools%20using%20it%20not%20necessarily%20meaning%20that%20they%20know%20how%20to%20use%20it%20so%20my%20guess%20based%20on%20my%20daily%20interactions%20is%20that%20probably%201%25%20of%20the%20K12%20uses%20it%20and%20knows%20how%20to%20use%20it.%20That's%20the%20reality%20whether%20we%20like%20that%20or%20not.%20I%20hear%20from%20colleagues%20in%20other%20countries%20much%20the%20same%20story%20in%20general%20with%20of%20course%20the%20usual%20exceptions%20to%20confirm%20the%20rule%3A-)%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-369462%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%20Update%20for%20Business%20and%20the%20retirement%20of%20SAC-T%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-369462%22%20slang%3D%22en-US%22%3E%3CP%3EHaving%20to%20rebuild%20all%20machines%20with%20curren't%20years%2003%20update%20seems%20like%20a%20lot%20of%20work.%20Unless%20you%20already%20do%20this%20every%20summer%20before%20the%20new%20school%20year.%20Then%20yeah%2C%20rebuilding%20it%20with%20current%2003%20every%20summer%20kind%20of%20makes%20it%201%20update%20per%20year.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20guess%2030%20months%20support%20is%20designed%20for%20those%20using%20ConfigMgr%2FWSUS%20to%20distribute%20feature%20updates.%20They%20can%20wait%20longer%20than%20365%20days.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-369452%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%20Update%20for%20Business%20and%20the%20retirement%20of%20SAC-T%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-369452%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F15668%22%20target%3D%22_blank%22%3E%40Adam%20Sova%3C%2FA%3E%26nbsp%3BThank%20you%20for%20your%20explanation%3B%20it%20looks%20indeed%20I've%20been%20misunderstanding%20the%20deferral%20concept%20to%20the%20extent%20that%20I%20thought%20that%20the%20deferral%20period%20applied%20to%20the%20release%20date%20of%20the%20%3CSTRONG%3Einstalled%3C%2FSTRONG%3E%20version%20(a%20new%20version%20will%20not%20be%20installed%20up%20until%20365%20days%20of%20release%20of%20the%20current%20verion)%20instead%20of%20the%20release%20date%20of%20the%20%3CSTRONG%3Eupcoming%3C%2FSTRONG%3E%26nbsp%3Bversion%20(a%20new%20version%20will%20not%20be%20installed%20up%20until%20365%20days%20after%20that%20new%20version%20has%20been%20released)%3C%2FP%3E%3CP%3EYour%20explanation%20is%20the%20first%20that%20I'd%20call%20%22human%20understandable%22%20yet%20the%20problem%20for%20schools%20continues%20(if%20they%20don't%20build%20a%20clean%20image%20every%20summer%20based%20on%20the%2003%20version)%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ETaking%20back%20your%20example%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3ESchool%20did%20a%20clean%201803%20install%20back%20in%20april%20or%20summer%202018%20with%20deferral%20set%20to%20365%20meaning%20that%20the%20next%20version%20(1809)%20will%20not%20be%20installed%20up%20until%20365%20days%20after%201809%20becomes%20available.%20So%20that%20effectively%20gives%20the%20school%20the%20possibility%20to%20use%201803%20for%201%20full%20schoolyear%20(sept%202018-june%202019)%20without%20feature%20upgrades%20happening%20during%20that%20schoolyear%20IF%20they%20build%20new%20images%20every%20summer%20based%20upon%20the%2003%20release.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EIf%20they%20don't%20build%20a%20new%20image%20every%20summer%20and%20just%20continue%20to%20use%20that%201803-please%20correct%20me%20if%20I'm%20wrong-%20then%201809%20will%20be%20installed%20somewhere%20after%20november%2012%202019%20in%20the%20midst%20of%20the%20schoolyear%3B%20not%20acceptable.%20Next%20-if%20they%20continue%20to%20use%20that%201809-%201903%20that%20was%20released%20march%202019%20will%20be%20installed%20march%202020%20again%20in%20the%20midst%20of%20the%20schoolyear.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESo%20the%20next%20best%20thing%20to%20do%20for%20schools%20if%20not%20using%20the%20Enterprise%20LTSB%2FLTSC%20edition%20is%20to%20build%20a%20new%20image%20every%20summer%20using%20the%20then%20current%2003%20version.%26nbsp%3B%20That%20would%20avoid%20feature%20upgrades%20during%20the%20schoolyear.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20can%20now%20understand%20the%2018%20months%20suport%20period%3A%20in%20the%20example%20if%201803%20was%20cleanly%20installed%20march%202018%20it%20could%20be%20used%20up%20until%20september%202019%20and%20that's%2018%20months.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20still%20wonder%20about%20the%2030%20months%20support%20for%20the%2009%20Enterprise%20%26amp%3B%20Education%20(%20see%20%3CA%20href%3D%22https%3A%2F%2Fsupport.microsoft.com%2Fen-in%2Fhelp%2F4462896%2Fupdates-to-servicing-and-support-for-windows-10%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ethis%20article%3C%2FA%3E)%20in%20relation%20to%20the%20365%20days%20deferrral%3B%20any%20idea%20what%20that%20could%20mean%20in%20human%20understandable%20language%20%3F%20An%20example%20where%20a%20customer%20installs%20a%20clean%20Enterprise%201809%20with%20deferral%20set%20to%20365%20(%3F)%20would%20help%20to%20understand!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ELTSB%2FLTSC%20-imho-%20continues%20to%20shine%20because%20it%20should%20not%20be%20taken%20for%20granted%20that%20schools%20have%20the%20resources%20to%20build%20new%20images%20every%20year%20let%20alone%20to%20live%20through%20feature%20upgrade%20cycles%20twice%20a%20year.%20After%20all%20they've%20been%20used%20to%20work%20with%20an%20OS%20for%20say%205%20year's%20in%20a%20row%20with%20all%20previous%20Windows%20versions...%20The%20OS%20is%20just%20a%20platform%20not%20a%20goal%20on%20it's%20own%20for%20most%20user's%20but%20MS%20seems%20to%20think%20different%20here.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-369356%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%20Update%20for%20Business%20and%20the%20retirement%20of%20SAC-T%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-369356%22%20slang%3D%22en-US%22%3E%3CP%3EMy%20god%20it%20just%20posted%20my%20message%20without%20letting%20me%20to%20finish%20it..%3C%2FP%3E%3CP%3EThe%20paragraph%20starts%20with%20%22Once%20your%20organization's%20devices%22%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-369352%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%20Update%20for%20Business%20and%20the%20retirement%20of%20SAC-T%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-369352%22%20slang%3D%22en-US%22%3E%3CP%3EIn%20this%20blog%20post%20their%20refer%20to%20release%20date%20of%20SAC%20as%20a%20starting%20point%20of%20defer%20period.%20As%20every%20SAC%20has%20its%20own%20release%20date%20i%20get%20that%20Windows%2010%20would%20pull%20release%20date%20from%20Windows%20Update%20and%20then%20apply%20defer%20value%20to%20this.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20can't%20provide%20you%20excerpt%20of%20paragraph%20as%20paste%20refuses%20to%20work%20here%20on%20movile.%20It%20boggles%20my%20mind%20that%20we%20have%20to%20use%20this%20utter%20buggy%2C%20ugly%2C%20slow%20platform%20to%20collaborate..%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-369351%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%20Update%20for%20Business%20and%20the%20retirement%20of%20SAC-T%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-369351%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F287710%22%20target%3D%22_blank%22%3E%40Clipper87%3C%2FA%3E%26nbsp%3B%2Cyou%20are%20wrong%2C%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F33735%22%20target%3D%22_blank%22%3E%40Oleg%20K%3C%2FA%3E%26nbsp%3Bhas%20it%20right.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ELook%20at%20this%20example%3A%3C%2FP%3E%3CP%3EWe%20talk%20about%20Win10%20Pro%20here%2C%20we%20have%20365%20days%20feature%20deferral%20set%20(and%20no%20SAC%20deferral%2C%20because%20after%201903%20it%20will%20be%20no%20such%20option%2Fpolicy)%20and%20currently%201803%20installed%2C%20ok%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHere%20are%20(expected)%20release%20dates%20of%20those%20versions%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%201803(currently%20installed)%3A%2030.4.2018%3CBR%20%2F%3E%26nbsp%3B%201809%3A%2013.11.2018%20(%20deferral%20365%20means%2C%20it%20can't%20be%20installed%20before%2012.11.2019%20)%3CBR%20%2F%3E%26nbsp%3B%201903%3A%2004.04.2019%20(for%20example%3B%20deferral%20365%20means%2C%20it%20can't%20be%20installed%20before%2003.04.2020%20))%3CBR%20%2F%3E%26nbsp%3B%201909%3A%2020.10.2019%20(for%20example%3B%20deferral%20365%20means%2C%20it%20can't%20be%20installed%20before%2019.10.2020%20))%3CBR%20%2F%3E%26nbsp%3B%202003%3A%2001.04.2020%20(for%20example%3B%20deferral%20365%20means%2C%20it%20can't%20be%20installed%20before%2030.03.2021%20))%3CBR%20%2F%3E%26nbsp%3B%202009%3A%2010.09.2020%20(for%20example%3B%20deferral%20365%20means%2C%20it%20can't%20be%20installed%20before%2009.09.2021%20))%3C%2FP%3E%3CP%3E%3CBR%20%2F%3ESo%20the%20result%20is%20%3A%3CBR%20%2F%3E-%20every%20half%20year%20(around%20april%20and%20october)%20you%20will%20be%20updated%20to%20%22one%20year%20old%22%20release%20(for%20example%20on%203.4.2020%20you%20wil%20get%201903)%3CBR%20%2F%3E-%20you%20will%20not%20be%20able%20to%20%22skip%22%20versions%20and%20install%20once%20a%20year%20(now%20you%20can%20do%20this%20-%20for%20example%2C%20with%20SAC%20and%20365%20days%20set%20you%20can%20install%201709%20in%20summer%202018%20and%20then-next%20summer-%20when%201809%20is%20out%2Btested%20you%20change%20policy%20to%20no%20SAC%20and%20180%20days%20and%20you%20get%201809%3B%20then%20you%20set%20again%20SAC%20and%20365)%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-369315%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%20Update%20for%20Business%20and%20the%20retirement%20of%20SAC-T%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-369315%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F33735%22%20target%3D%22_blank%22%3E%40Oleg%20K%3C%2FA%3E%26nbsp%3BNope%3A%20if%20you%20install%201903%20in%20april%202019%20%26amp%3B%20set%20deferral%20to%20365%20days%20you%20will%20get%20a%20feature%20update%20as%20of%20March%202020%20(365%20days%20after%201903%20has%20been%20released%20presuming%201903%20will%20be%20released%20in%20March%202019)%20It%20won't%20happen%20immediately%20for%20everyone%20as%20MS%20does%20it%20progressively%20per%20region%20%26amp%3B%20per%20hardware%20config%20they%20feel%20reasonable%20sure%20about.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20did%20not%20day%20it%20counts%20365%20days%20from%20the%20last%20feature%20update%20installed.%20Where%20did%20you%20read%20that%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20365%20days%20deferral%20setting%20basically%20prevents%20from%20getting%202%20feature%20updates%20a%20year%20but%20that's%20not%20what%20real%20world%20customers%20are%20after.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EPresuming%20that%20participants%20in%20this%20thread%20are%20above%20average%20ICT%20administrators%20%26amp%3B%20looking%20at%20the%20confusion%20in%20their%20minds%20I%20can%20only%20conclude%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F79327%22%20target%3D%22_blank%22%3E%40John%20Wilcox%3C%2FA%3E%26nbsp%3Bthat%20MS%20still%20has%20a%20lot%20of%20explanation%20to%20do%20in%20human%20understandable%20language.%20I%20greatly%20depend%20on%20the%20Windows%20platform%20for%20my%20business%20and%20it's%20hard%20to%20see%20K12%20moving%20over%20to%20Chromebooks%20-in%20great%20part-%20because%20of%201)%20the%20MS%20complexity%20%2C%202)%20as%20always%20the%20cost%20and%20read%20this%20well%3A%201)%20comes%20before%202)%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-369290%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%20Update%20for%20Business%20and%20the%20retirement%20of%20SAC-T%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-369290%22%20slang%3D%22en-US%22%3E%3CP%3EI'm%20just%20trying%20to%20clarify%20this%20for%20myself.%20As%20i've%20said%20i%20haven't%20used%20deferral%20policies%20(i'm%20talking%20about%20GPO%20for%20Windows%20Update%20for%20Business).%20From%20what%20i%20have%20read%20in%20this%20blog%20post%20and%20other%20comments%20i%20gathered%20that%20it%20works%20the%20other%20way%20that%20you%20describe.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EYou%20install%201903%20(say%20in%20April)%2C%20your%20GPO%20was%20set%20to%20365%20days%20(not%20important%20when%2C%20could%20be%20even%20before%201903).%20So%20it%20will%20always%20count%20365%20days%20since%20the%20official%20release%20of%20any%20feature%20update%20coming%20in%20the%20future.%20This%20means%20that%201909%20would%20be%20installed%20in%202020%20September%2C%202003%20in%202021%20March%20and%20so%20on.%20Every%20feature%20update%20would%20be%20postponed%20for%20a%20year.%20But%20that%20means%20that%20you%20would%20still%20get%20two%20updates%20twice%20a%20year%20on%20March%20and%20September%2C%20they%20just%20will%20be%20a%20year%20old%20every%20time.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EBut%20you%20say%20that%20it%20counts%20365%20days%20since%20the%20last%20feature%20update%20installed.%20This%20doesn't%20sound%20right%20and%20not%20what%20i%20have%20heard.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EUnless%20you%20mean%20that%20you%20don't%20have%20a%20way%20to%20not%20have%20updates%20installed%20twice%20a%20year%20or%20during%20spring%20or%20fall.%20That%20i%20understand%20and%20i%20always%20advocate%20for%20MS%20to%20stop%20doing%20feature%20releases%20twice%20a%20year%20and%20go%20to%20once%20a%20year%20practice.%20Though%20i%20fear%20they%20might%20start%20doing%20even%20more%20often%20updates%20in%20the%20future.%20If%20it%20was%20just%20once%20a%20year%2C%20say%20in%20March%2C%20then%20you%20would%20set%20it%20to%20180%20days%20and%20every%20update%20would%20be%20installed%20during%20summer.%20But%20when%20there%20are%20two%20updates%20per%20year%20it%20is%20impossible%20to%20have%20one%20policy%20to%20work%20for%20both%20of%20them.%20You%20would%20have%20to%20have%20two%20policies%20and%20switch%20them%20twice%20a%20year.%20One%20for%20the%20spring%20update%20to%20defer%20for%20180%20days%20and%20one%20for%20fall%20update%20to%20defer%20for%20270%20or%20so.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-369283%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%20Update%20for%20Business%20and%20the%20retirement%20of%20SAC-T%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-369283%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F33735%22%20target%3D%22_blank%22%3E%40Oleg%20K%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20think%20you%20are%20not%20reading%20my%20message%20correctly%3A%20a%20customer%20who%20installs%201903%20(presuming%20it's%20available)%20in%20March%202019%20%26amp%3B%20sets%20the%20deferral%20to%20365%20will%20get%202003%20as%20of%20March%202020%20which%20is%20not%20desirable.%20Even%20he'd%20deploy%201903%20in%20july%202019%20with%20deferral%20set%20to%20365%20he'd%20be%20getting%202003%20as%20of...%20March%202020.%20Since%20MS%20release%20typically%20in%20March%2FApril%20%26amp%3B%20Sept%2FOct%20this%20is%20causing%20great%20trouble%20for%20schools.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-369280%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%20Update%20for%20Business%20and%20the%20retirement%20of%20SAC-T%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-369280%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F79327%22%20target%3D%22_blank%22%3E%40John%20Wilcox%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20quote%20(emphasis%20mine)%3A%3C%2FP%3E%3CP%3E%3CEM%3EYour%20targeted%20phase%20(%20%3CSTRONG%3Eif%20%3CU%3Eyou%3C%2FU%3E%20self%20manage%3C%2FSTRONG%3E%20)%20takes%20as%20long%20and%20as%20many%20devices%20%3CSTRONG%3Eas%20%3CU%3Eyou%3C%2FU%3E%20need%3C%2FSTRONG%3E%20to%20make%20your%20full%20deployment%20decision.%26nbsp%3B%3C%2FEM%3E%3C%2FP%3E%3CP%3E%3CEM%3EWith%201803%20is%20was%20250%20million%26nbsp%3B%26nbsp%3B%20and%20is%20documented%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fblogs.windows.com%2Fwindowsexperience%2F2018%2F06%2F14%2Fai-powers-windows-10-april-2018-update-rollout%2F%23FqIAJr2q01PQp6eQ.97%22%20target%3D%22_self%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehere%3C%2FA%3E%26nbsp%3B%3C%2FEM%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSTRONG%3EThis%3C%2FSTRONG%3E%26nbsp%3Bcontinues%20to%20highlight%20the%20problem%20with%20your%20narrative.%20Microsoft%26nbsp%3Breleases%20SAC-T%20to%20250%20million%20devices%2C%20but%20it's%20not%20a%20release%2C%20it%20just%20some%20preliminary%20milestone.%26nbsp%3B%20At%20the%20same%20time%2C%26nbsp%3BHome%20edition%20owners%20don't%20self%20manage%20updates.%20Microsoft%20manages%20updates%20for%20them%2C%20hence%20'you'%20is%20not%20%5Bcompletely%5D%20applicable%20here.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThat's%20why%20I'm%20saying%20that%20SAC-T%20was%20just%20another%20testing%20ring.%20Certainly%2C%20it's%20not%20in%20your%20narrative%20and%20perhaps%2C%20it's%20not%20even%20on%20your%20mind%20(albeit%20it%20should%20be).%20Yet%20this%20is%20the%20reality.%20The%20known%20issues%20sections%20for%20SAC-T%20as%20well%20as%20update%20history%20pages%20for%20subsequent%20CUs%20used%20to%20tell%20and%20continue%20telling%20the%20story%20of%20multiple%20issues%20being%20raised%20immediately%20after%20SAC-T%20(e.g.%201809).%20Thanks%20to%20all%20these%20testers%20who%20you%20pretend%20self%20manage%20updates%20%3A)%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI'm%20sure%20you%20know%20how%20many%20of%20those%20250%20mil%20devices%20getting%201803%20were%20running%20Home%20editions.%20Would%20you%20like%20to%20disclose%20this%20information%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-369279%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%20Update%20for%20Business%20and%20the%20retirement%20of%20SAC-T%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-369279%22%20slang%3D%22en-US%22%3E%3CP%3EWell%2C%20in%20my%20understanding%20it%20should%20work%20like%20that%3A%20if%20you%20set%20it%20to%20365%20days%20then%20in%202020%20March%20you%20would%20get%201903%20version%2C%20not%202003%20as%20release%20date%20for%202003%20would%20be%202020%20march%20and%20it%20would%20be%20deferred%20for%20365%20days%20based%20on%20your%20policy%2C%20so%20it%20would%20be%20installed%20in%202021%20actually.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-369277%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%20Update%20for%20Business%20and%20the%20retirement%20of%20SAC-T%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-369277%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F33735%22%20target%3D%22_blank%22%3E%40Oleg%20K%3C%2FA%3E%26nbsp%3Bexactly%3B%20deferral%20setting%20is%20as%20of%20release%20date%20and%20indeed%20it%20is%20for%20installing%20a%20new%20Windows%20version%20(hence%20the%20name%20feature%20update%20not%20to%20be%20confused%20with%20so%20called%20quality%20updates).%20So%20if%20MS%20releases%201903%20in%20March%202019%20and%20a%20customer%20defers%20the%20next%20feature%20upgrade%20for%20365%20days%20then%20he'll%20get%20version%202003%20in%20%2F%20as%20of%20March%202020%20but%20I'd%20be%20curious%20to%20learn%20about%20the%2018%20%26amp%3B%2030%20months%20support%20explanation%20from%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F79327%22%20target%3D%22_blank%22%3E%40John%20Wilcox%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESomething%20else%20I%20experienced%20on%20one%20of%20my%20own%20systems%20is%20the%20following%3A%20(%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F79327%22%20target%3D%22_blank%22%3E%40John%20Wilcox%3C%2FA%3E%26nbsp%3BI'd%20appreciate%20you%20shedding%20some%20light%20on%20this%20as%20well.)%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20had%20a%201703%20Pro%20system%20with%20deferral%20set%20to%20SAC%20%2B%20365%20days%2C%20then%20it%20got%20a%20feature%20upgrade%20to%201709%20back%20in%20February%202019.%20I%20was%20expecting%20to%20get%201803%20however%20since%201803%20in%20february%202019%20was%20%22ready%20for%20business%20%2F%20SAC%22%20ever%20since%20july%2010th%202018%20%3F%3F%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-369268%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%20Update%20for%20Business%20and%20the%20retirement%20of%20SAC-T%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-369268%22%20slang%3D%22en-US%22%3E%3CP%3EI%20haven't%20used%20deferral%20setting%20before%2C%20but%20i%20thought%20it%20is%20a%20number%20of%20days%20since%20the%20official%20release%2C%20not%20since%20the%20last%20feature%20update%20installed%20on%20your%20system.%20Then%20there%20shouldn't%20be%20a%20problem%20in%20March.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAlso%2C%20deferral%20is%20for%20the%20next%20update%20to%20defer%20(pause)%2C%20not%20a%20setting%20when%20to%20install%20next%20update%20for%20the%20current%20update%20(i%20think).%20And%20group%20policies%20are%20not%20dynamic%2C%20they%20can't%20know%20what%20version%20you%20are%20using%20at%20the%20moment%20and%20stretch%20the%20deferral%20number%20accordingly.%20This%20would%20need%20some%20other%20method%20to%20control%20or%20just%20allow%20any%20number%20in%20that%20policy%20no%20matter%20what%20version%20with%20how%20much%20of%20support%20is%20used.%20But%20i%20think%20MS%20doesn't%20want%20a%20lot%20of%20very%20old%20versions%20in%20the%20wild%2C%20so%20they%20have%20made%20it%20365.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-369264%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%20Update%20for%20Business%20and%20the%20retirement%20of%20SAC-T%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-369264%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F79327%22%20target%3D%22_blank%22%3E%40John%20Wilcox%3C%2FA%3E%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EFrom%20the%20perspective%20of%20K12%20schools%20out%20here%20in%20Belgium%20which%20I%20happen%20to%20deal%20with%20a%20lot%20%2C%20I%20couldn't%20agree%20more%20with%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F11042%22%20target%3D%22_blank%22%3E%40Susan%20Bradley%3C%2FA%3E%20as%20her%20situation%20is%20quite%20comparable.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESchools%20are%20happy%20to%20deploy%20feature%20upgrades%20but%20NOT%20when%20Microsoft%20selects%20to%20do%20so.%20For%20them%20the%20summer%20holiday%20is%20an%20ideal%20period%20for%20example.%20Apart%20from%20that%20-imho-%20Microsoft%20needs%20to%20realize%20that%20-this%20is%20an%20understatement-%20not%20every%20customer%20is%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E1.%20working%20in%20an%20A%2FD%20environment%20but%20rather%20using%20a%20simple%20workgroup%20concept%3C%2FP%3E%3CP%3E2.%20even%20less%20customers%20are%20using%20WSUS%20or%20have%20the%20knowledge%20to%20use%20%2F%20manage%20it%3C%2FP%3E%3CP%3E3.%20even%20less%20are%20using%20deployment%20rings%20(not%20necessarily%20because%20they%20don't%20like%20it%3B%20they%20simply%20don't%20have%20the%20resources)%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIn%20fact%20most%20are%20just%20after%20a%20lean%2C%20mean%20(%3D%20not%20bloated)%20%26amp%3B%20stable%20Windows%20OS%20and%20not%20waiting%20for%20yet%20some%20other%20feature%20they%20most%20probably%20don't%20need.%20Your%20telemetry%20probably%20does%20confirm%20that%20if%20you%20look%20at%20the%20number%20of%20Enterprise%20LTSB%2FLTSC%20deployments%20out%20here%20even%20given%20the%20fact%20that%20it%20is%20still%20a%20widely%20unknown%20version%20for%20most%20-volume%20licensing-%20customers%20(unfortunately).%20Please%20don't%20reply%20that%20LTSB%2FLTSC%20is%20for%20ATM's%20or%20that%20they%20need%20to%20look%20for%20Windows%2010S.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ETo%20add%20to%20the%20confusion%20it%20is%20still%20totally%20unclear%20as%20to%20how%20things%20work%3A%20a%20school%20that%20will%20deploy%20version%201903%20with%20365%20days%20of%20deferral%20(the%20maximum%20available)%20becomes%20a%20sitting%20duck%20as%20of%20march%202020.%20Depending%20on%20how%20fast%20Microsoft%20effectively%20rolls%20out%20version%202003%20chances%20are%20that%20somewhere%20in%20the%20April-June%20time%20frame%20they%20get%20the%20feature%20upgrade%20forced%20upon%20them%20with%20the%20potential%20of%20causing%20all%20kinds%20of%20issues%20(remember%201809%20%3F).%20It%20could%20even%20happen%20while%20students%20are%20taking%20their%20exams%20and%20using%20those%20PC's.%20That's%20just%20not%20acceptable.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ETo%20add%20to%20the%20confusion%20it%20is%20still%20totally%20unclear%20to%20me%20and%20my%20customers%20what%20Microsoft%20means%20with%2018%20months%20of%20support%3B%20If%20a%20version%20is%20supported%20for%2018%20months%20then%20I'd%20expect%20the%20maximum%20deferral%20period%20available%20to%20be%20548%20days%20not%20365%20days.%20I'd%20greatly%20appreciate%20some%20light%20being%20shed%20on%20this.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMoreover%20Microsoft%20has%20announced%20in%20september%202018%20that%20it%20will%20%22support%22%20the%20%2209%22%20autumn%20Enterprise%20%26amp%3B%20Education%20releases%20for%2030%20months%20rather%20than%2018%20months%20for%20all%20other%20versions.%20So%20for%20those%20versions%20I'd%20then%20expect%20a%20maximum%20deferral%20period%20of%20913%20days%20%3F%26nbsp%3BI'd%20greatly%20appreciate%20some%20light%20being%20shed%20on%20this%20as%20well.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20also%20wanted%20to%20express%20-reading%20this%20article%20%3CA%20href%3D%22https%3A%2F%2Fwww.ghacks.net%2F2019%2F03%2F06%2Fwill-microsoft-remove-advanced-update-options-in-windows-10-1903-pro%2F%22%20target%3D%22_self%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fwww.ghacks.net%2F2019%2F03%2F06%2Fwill-microsoft-remove-advanced-update-options-in-windows-10-1903-pro%2F%3C%2FA%3E-%20my%20regret%20that%20Microsoft%20seems%20to%20have%20decided%20to%20remove%20the%20Advanced%20Update%20settings%20(like%20the%20deferral%20setting).%20For%20many%20K12%20customers%20this%20means%20extra%20complexity%20as%20many%20of%20them%20are%20not%20even%20familiar%20with%20local%20GPO's%20or%20messing%20around%20in%20the%20registry.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20local%20education%20volume%20licensing%20program%20out%20here%20is%20called%20MS-KIS%20(Keep%20it%20simple)%20%3B%20at%20this%20stage%20however%20we%20couldn't%20be%20any%20further%20away%20from%20keeping%20things%20simple...%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThank%20you%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-369200%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%20Update%20for%20Business%20and%20the%20retirement%20of%20SAC-T%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-369200%22%20slang%3D%22en-US%22%3E%3CP%3EJohn%2C%26nbsp%3B%3C%2FP%3E%3CP%3EI%20agree%20with%20Susan.%26nbsp%3B%20As%20LAN%20Admin%20in%20a%20financial%20institution%20and%20since%20we%20are%20federally%20regulated%20for%20Safety%20and%20Soundness%2C%20this%20uncertainty%20element%20for%20patches%20is%20really%20bad.%26nbsp%3B%20If%20it%20wasn't%20bad%20enough%20Microsoft's%20updates%20are%20all%20bundled%20together%20in%20to%20one%20massive%20download%20making%20it%20impossible%20to%20troubleshoot%20when%20a%20patch%20breaks%20something%20like%20a%20core%20piece%20of%20software%2C%20but%20now%20we%20won't%20have%20a%20clear%20date%20far%20enough%20in%20advance%20to%20test%3B%20that%20is%20unacceptable!!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAfter%201609%20I%20setup%20a%20IBM%20Tivoli%20server%20on%20site%20to%20help%20make%20updating%20more%20manageable%20in%20our%20own%20timeline%20and%20test%20groups%20so%20we%20can%20mitigate%20issues%20if%20needed.%26nbsp%3B%3C%2FP%3E%3CP%3ESounds%20like%20I%20need%20to%20set%20the%20Update%20Service%20on%20all%20of%20our%20company's%20workstations%20to%20manual%20or%20disable%20until%20Microsoft%20figures%20it%20out.%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAnd%20also%2C%20What%20is%20up%20with%20Xbox%20app%20still%20being%20forced%20on%20Windows%20Pro%3F%3F%3F%26nbsp%3B%20Believe%20it%20our%20not%20Companies%20don't%20let%20their%20employees%20play%20Xbox%20at%20WORK!%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%20%26nbsp%3B%20-You'd%20think%20with%20all%20the%20Telemetry%20data%20you're%20gathering%20from%20Win10%20machines%20this%20point%20would%20be%20clear.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-368527%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%20Update%20for%20Business%20and%20the%20retirement%20of%20SAC-T%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-368527%22%20slang%3D%22en-US%22%3E%3CP%3EBut%20that%20still%20is%20an%20inexact%20date%20in%20time%20-%20take%20for%20example%201903%20which%20will%20come%20out...%E2%80%A6%3F%20%26nbsp%3B%20So%20it's%20always%20a%20date%20in%20time%2Frelease%20info%20that%20I%20have%20to%20be%20aware%20of%20and%20keep%20an%20eye%20on%20the%20deferral%20dates%20I%20have%20set%20to%20ensure%20they%20push%20it%20out%20past%20my%20don't%20you%20dare%20update%20days.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-368526%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%20Update%20for%20Business%20and%20the%20retirement%20of%20SAC-T%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-368526%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Susan%2C%20%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F11042%22%20target%3D%22_blank%22%3E%40Susan%20Bradley%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EYes%2C%20absolutely%2C%20you%20have%20a%20couple%20of%20options%20in%20the%20product%20today%20to%20do%20that.%3C%2FP%3E%0A%3CP%3E1)%20You%20can%20set%20the%20deferral%20value%20to%20a%20number%20of%20days%20from%20release%20that%20will%20move%20the%20update%20beyond%20your%20black%20out%20period%3C%2FP%3E%0A%3CP%3E2)%20You%20can%20activate%20a%20temporary%20pause%20to%20an%20update%2C%20which%20would%20move%20you%20past%20your%20blackout%2C%20but%20not%20change%20the%20deferral%20for%20the%20next%20update.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EWe%20also%20want%20to%20make%20this%20more%20straight%20forward%20so%20that%20you%20could%20%22schedule%22%20black%20our%20periods%20and%20we%20could%20be%20intelligent%20based%20on%20when%20you%20have%20these%20down%20times%20and%20when%20you%20don't%20in%20future%20improvements.%20This%20would%20work%20well%20for%20your%20case%20where%20your%20blackout%20time%20does%20not%20change.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-368503%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%20Update%20for%20Business%20and%20the%20retirement%20of%20SAC-T%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-368503%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Vadim%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F226354%22%20target%3D%22_blank%22%3E%40Vadim%20Sterkin%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThat%20certainly%20is%20not%20what%20I%20would%20want%20you%20to%20take%20away%20from%20the%20guidance.%26nbsp%3B%20We%20update%26nbsp%3B%20millions%20devices%20during%20the%20target%20phase%20before%20moving%20to%20broad%20and%20make%20it%20fully%20available.%20Full%20availability%20is%20the%20final%20%3CEM%3Ephase%20%26nbsp%3B%3C%2FEM%3Eof%20our%20rollout%20process.%20Your%20targeted%20phase%20(%20if%20you%20self%20manage%20)%20takes%20as%20long%20and%20as%20many%20devices%20as%20you%20need%20to%20make%20your%20full%20deployment%20decision.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EW%3CSPAN%20style%3D%22display%3A%20inline%20!important%3B%20float%3A%20none%3B%20background-color%3A%20%23ffffff%3B%20color%3A%20%23333333%3B%20font-family%3A%20inherit%3B%20font-size%3A%2016px%3B%20font-style%3A%20normal%3B%20font-variant%3A%20normal%3B%20font-weight%3A%20300%3B%20letter-spacing%3A%20normal%3B%20line-height%3A%201.7142%3B%20orphans%3A%202%3B%20text-align%3A%20left%3B%20text-decoration%3A%20none%3B%20text-indent%3A%200px%3B%20text-transform%3A%20none%3B%20-webkit-text-stroke-width%3A%200px%3B%20white-space%3A%20normal%3B%20word-spacing%3A%200px%3B%22%3Eith%201803%20is%20was%20250%20million%3C%2FSPAN%3E%20%26nbsp%3B%20and%20is%20documented%20%3CA%20href%3D%22https%3A%2F%2Fblogs.windows.com%2Fwindowsexperience%2F2018%2F06%2F14%2Fai-powers-windows-10-april-2018-update-rollout%2F%23FqIAJr2q01PQp6eQ.97%22%20target%3D%22_self%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehere%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-368457%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%20Update%20for%20Business%20and%20the%20retirement%20of%20SAC-T%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-368457%22%20slang%3D%22en-US%22%3E%3CP%3EIs%20there%20any%20thought%20to%20having%20a%20way%20to%20set%20a%20policy%20that%20says%20%22I%20don't%20want%20release%201903%20until%20a%20specific%20date%22%3F%20%26nbsp%3B%20I'll%20give%20a%20specific%20example.%26nbsp%3B%20I%20work%20for%20a%20tax%20firm%20that%20there%20is%20no%20way%20we%20want%20a%20feature%20release%20to%20be%20installed%20in%20March.%26nbsp%3B%20Right%20now%20I%20have%20SemiAnnual%20chosen%2C%20with%20a%20X%20number%20of%20days%20pushed%20out%20after%20it's%20been%20declared%20SAC.%26nbsp%3B%20In%20the%20new%20era%20I'm%20going%20to%20need%20to%20make%20sure%20my%20deferral%20days%20are%20pushed%20off%20enough.%26nbsp%3B%20Conversely%20I%20often%20plan%20in%20terms%20of%20solid%20maintenance%20windows.%26nbsp%3B%20July%204th%20holiday%20for%20example%20is%20a%20day%20I%20can%20blow%20up%20the%20network%20and%20most%20folks%20don't%20care.%26nbsp%3B%20If%20there%20was%20a%20way%20to%20set%20a%20policy%20that%20says%20%22install%20this%20feature%20release%20on%20this%20day%22%20that%20would%20be%20grand.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-368386%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%20Update%20for%20Business%20and%20the%20retirement%20of%20SAC-T%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-368386%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Christian%2C%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F54057%22%20target%3D%22_blank%22%3E%40Christian%20Zenzano%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ESee%20my%26nbsp%3B%3CSPAN%20class%3D%22DateTime%22%20style%3D%22box-sizing%3A%20border-box%3B%20font-family%3A%20%26amp%3Bquot%3B%22%3E%3CSPAN%20class%3D%22local-date%22%20style%3D%22box-sizing%3A%20border-box%3B%20font-family%3A%20%26amp%3Bquot%3B%20segoeui%26amp%3Bquot%3B%2C%26amp%3Bquot%3Blato%26amp%3Bquot%3B%2C%26amp%3Bquot%3Bhelvetica%20neue%26amp%3Bquot%3B%2Chelvetica%2Carial%2Csans-serif%3B%20white-space%3A%20nowrap%3B%22%3E%E2%80%8E%3CFONT%20size%3D%223%22%3E02-17-2019%3C%2FFONT%3E%3C%2FSPAN%3E%20%3CSPAN%20class%3D%22local-time%22%20style%3D%22box-sizing%3A%20border-box%3B%20font-family%3A%20%26amp%3Bquot%3B%20segoeui%26amp%3Bquot%3B%2C%26amp%3Bquot%3Blato%26amp%3Bquot%3B%2C%26amp%3Bquot%3Bhelvetica%20neue%26amp%3Bquot%3B%2Chelvetica%2Carial%2Csans-serif%3B%20white-space%3A%20nowrap%3B%22%3E%3CFONT%20size%3D%223%22%3E07%3A55%20PM%3C%2FFONT%3E%20%26nbsp%3B%20response%20to%20Vadim%20above.%26nbsp%3B%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22DateTime%22%20style%3D%22box-sizing%3A%20border-box%3B%20font-family%3A%20%26amp%3Bquot%3B%22%3E%3CSPAN%20class%3D%22local-time%22%20style%3D%22box-sizing%3A%20border-box%3B%20font-family%3A%20%26amp%3Bquot%3B%20segoeui%26amp%3Bquot%3B%2C%26amp%3Bquot%3Blato%26amp%3Bquot%3B%2C%26amp%3Bquot%3Bhelvetica%20neue%26amp%3Bquot%3B%2Chelvetica%2Carial%2Csans-serif%3B%20white-space%3A%20nowrap%3B%22%3EWindows%20continues%20to%20share%20the%20same%20servicing%20framework%20as%20Office%2C%20with%20a%20Targeted%20phase%20of%20deployments.%20This%20done%20with%20each%20windows%20release.%20%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22DateTime%22%20style%3D%22box-sizing%3A%20border-box%3B%20font-family%3A%20%26amp%3Bquot%3B%22%3E%3CSPAN%20class%3D%22local-time%22%20style%3D%22box-sizing%3A%20border-box%3B%20font-family%3A%20%26amp%3Bquot%3B%20segoeui%26amp%3Bquot%3B%2C%26amp%3Bquot%3Blato%26amp%3Bquot%3B%2C%26amp%3Bquot%3Bhelvetica%20neue%26amp%3Bquot%3B%2Chelvetica%2Carial%2Csans-serif%3B%20white-space%3A%20nowrap%3B%22%3EThere%20are%20only%20the%202%20SAC%20releases.%20There%20never%20was%20separate%20SAC%20and%20SACT%20releases.%26nbsp%3B%20Our%20guidance%20still%20has%20a%20Targeted%20phase%2C%20that%20is%20SACT.%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22DateTime%22%20style%3D%22box-sizing%3A%20border-box%3B%20font-family%3A%20%26amp%3Bquot%3B%22%3E%3CSPAN%20class%3D%22local-time%22%20style%3D%22box-sizing%3A%20border-box%3B%20font-family%3A%20%26amp%3Bquot%3B%20segoeui%26amp%3Bquot%3B%2C%26amp%3Bquot%3Blato%26amp%3Bquot%3B%2C%26amp%3Bquot%3Bhelvetica%20neue%26amp%3Bquot%3B%2Chelvetica%2Carial%2Csans-serif%3B%20white-space%3A%20nowrap%3B%22%3EThis%20is%20true%20for%20Office%2C%26nbsp%3B%20the%20difference%20is%20in%20the%20update%20deployment%20update.%20With%20Windows%2C%20you%20get%20the%20image%20day%20one%20and%20manage%3CBR%20%2F%3Eyour%20update%20roll%20out%20plan%20and%20schedules%20your%20self%20with%20SCCM%2C%20etc.%20With%20office%2C%20you%20subscribe%20to%20one%20of%20the%203%20channels%2C%20but%20the%20framework%20and%20concepts%20are%20the%20same.%3CBR%20%2F%3E%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CDIV%20class%3D%22lia-menu-navigation-wrapper%20lia-menu-action%20lia-component-message-view-widget-action-menu%20lia-menu-overflow-right%22%20id%3D%22actionMenuDropDown_12%22%20style%3D%22box-sizing%3A%20border-box%3B%20color%3A%20%23333333%3B%20display%3A%20inline-block%3B%20font-family%3A%20%26amp%3Bquot%3B%20segoeui%26amp%3Bquot%3B%2C%26amp%3Bquot%3Blato%26amp%3Bquot%3B%2C%26amp%3Bquot%3Bhelvetica%20neue%26amp%3Bquot%3B%2Chelvetica%2Carial%2Csans-serif%3B%20font-size%3A%2014px%3B%20font-style%3A%20normal%3B%20font-variant%3A%20normal%3B%20font-weight%3A%20300%3B%20letter-spacing%3A%20normal%3B%20orphans%3A%202%3B%20position%3A%20absolute%3B%20right%3A%20-35px%3B%20text-align%3A%20right%3B%20text-decoration%3A%20none%3B%20text-indent%3A%200px%3B%20text-transform%3A%20none%3B%20top%3A%20-35px%3B%20-webkit-text-stroke-width%3A%200px%3B%20white-space%3A%20normal%3B%20word-spacing%3A%200px%3B%22%3E%0A%3CDIV%20class%3D%22lia-menu-navigation%22%20style%3D%22box-sizing%3A%20border-box%3B%20font-family%3A%20%26amp%3Bquot%3B%22%3E%0A%3CDIV%20class%3D%22dropdown-default-item%22%20style%3D%22box-sizing%3A%20border-box%3B%20font-family%3A%20%26amp%3Bquot%3B%22%3E%26nbsp%3B%3C%2FDIV%3E%0A%3C%2FDIV%3E%0A%3C%2FDIV%3E%0A%3CP%3EJW%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-368375%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%20Update%20for%20Business%20and%20the%20retirement%20of%20SAC-T%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-368375%22%20slang%3D%22en-US%22%3E%3CP%3EAnother%20%23SAC-T%20build%20released%20in%20Office%20365%20ProPlus%20yesterday%2C%26nbsp%3B%20again%20adding%20more%20confusion%20to%20how%20removal%20of%20SAC-T%20from%20windows%26nbsp%3B%20is%20in%20alignment%20with%20Office%20365%3F%26nbsp%3B%20Am%20I%20the%20only%20one%20confused%20%3F%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20400px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F88558i39220A66EE2C1843%2Fimage-size%2Fmedium%3Fv%3D1.0%26amp%3Bpx%3D400%22%20alt%3D%22SACT1902.png%22%20title%3D%22SACT1902.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-358672%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%20Update%20for%20Business%20and%20the%20retirement%20of%20SAC-T%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-358672%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F79327%22%20target%3D%22_blank%22%3E%40John%20Wilcox%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIn%20my%20opinion%20this%20is%20a%20step%20backwards.%20%26nbsp%3B%20It%20has%20been%20the%20recommendation%20from%20the%20begging%20to%20move%20to%20a%20continual%20release%20model%20adopting%26nbsp%3B%20with%20the%20adoption%20of%20incremental%20release%20periods.%26nbsp%3B%26nbsp%3B%20This%20has%20been%20a%20model%20that%20has%20worked%20from%20the%20begging%20whether%20it%20is%20named%20CB%20%5C%20CBB%20or%20SAC-T%20%5C%20SAC-B%20%2C%20the%20point%20is%20that%20we%20know%20when%20we%20are%20at%20day%20zero.%26nbsp%3B%20We%20also%20know%20we%20still%20have%20a%20version%20that%20may%20have%20not%20been%20tested%20across%20the%20business%20ecosystem%20and%20that%204%20to%206%20month%20later%20we%20will%20be%20notified%20of%20Business%20ready%20version.%20%26nbsp%3B%20We%20also%20know%20we%20have%20this%20time%20to%20address%20issues%20with%20vendors.%20%26nbsp%3B%3C%2FP%3E%3CP%3EI%20do%20not%20see%20how%20this%20new%20change%20to%20remove%20Sac-T%20is%20being%20made%20to%20align%20with%20Office%20365%20when%20Office%20utilizes%20a%20First%20release%20%5C%20targeted%20channel%20as%20well%20.%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fofficeupdates%2Fupdate-history-office365-proplus-by-date%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%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fofficeupdates%2Fupdate-history-office365-proplus-by-date%3C%2FA%3E%3C%2FP%3E%3CP%3ESeem%20to%20be%20a%20disconnect%20here.%20%26nbsp%3B%3CSPAN%3ESpecially%20if%20you%20view%20the%20image%20that%20illustrates%20the%20release%20history%20for%20Office%20365%20ProPlus%26nbsp%3B%20or%20if%20you%20look%20at%20the%20version%20information%20from%20the%20Office%20aplication%20itself.%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20847px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F84773iE9093526E066352C%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22ProPlusSAC_T.gif%22%20title%3D%22ProPlusSAC_T.gif%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Eimage%20from%20Outlook%20Desktop%20application.%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20529px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F84774iE5E8CECB242E6166%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22ProPlusSAC_T2.gif%22%20title%3D%22ProPlusSAC_T2.gif%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-356161%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%20Update%20for%20Business%20and%20the%20retirement%20of%20SAC-T%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-356161%22%20slang%3D%22en-US%22%3E%3CP%3ELTSC%20(formerly%20called%20LTSB)%20available%20via%20volume%20licensing%20is%20the%20only%20sustainable%20way%20to%20use%20Windows%2010%20for%20schools%2C%20SMB's%20and%20maybe%20even%20larger%20corporates%20but%20very%20few%20people%20know%20about%20it's%20existence%20and%20Microsoft%20put's%20it%20away%20as%20an%20OS%20for%20use%20in%20ATM's%20etc%20which%20is%20ridiculous.%20Most%20people%20just%20want%20a%20clean%20%26amp%3B%20stable%20OS%20without%20all%20the%20crap%20and%20that's%20what%20LTSC%20brings%20you%3A%20no%20Edge%2C%20Cortana%2C%20Store%2C%20Games%20(promoted%20apps).%20LTSC%20also%20is%20faster%20%26amp%3B%20consumes%20less%20battery.%26nbsp%3BThe%20enforcement%20of%20the%20feature%20upgrades%20is%20unacceptable%3B%20Apple%20for%20example%20offers%20a%20new%20OS%20approx%20every%20year%20BUT%20they%20let%20the%20user%20decide%20IF%20%26amp%3B%20WHEN%20to%20install%20it%20AND%20the%20upgrades%20just%20work.%20What%20I'm%20seeing%20here%20in%20our%20market%20is%20schools%20for%20example%20moving%20to%20chromebooks%20except%20for%20those%20applications%20that%20specifically%20require%20the%20Windows%20platform.%20Bravo%20Microsoft!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-356138%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%20Update%20for%20Business%20and%20the%20retirement%20of%20SAC-T%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-356138%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20John%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20quote%26nbsp%3B%3CSPAN%3E%26nbsp%3B%22%3CEM%3ESACT%20referred%20to%20the%20phase%20of%20deployment%20where%20we%20are%20publishing%20only%20to%20%22targeted%22%20devices%2C%20versus%20all%22%3C%2FEM%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3EThis%20implies%20that%20'targeted'%20is%20something%20very%20small%2C%20insignificant%20and%20in%20general%20for%20those%20who%20selected%20it%20themselves%20for%20testing%20purposes%20(and%20therefore%20it's%20their%20fault%20if%20they%20run%20into%20issues%20while%20using%20a%20preliminary%20release).%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EYet%20if%20you%20look%20at%20your%20own%20screenshots%2C%20they%20say%20that%20SAC-T%20is%20%3CEM%3Eready%20for%20most%20people%3C%2FEM%3E.%20Which%20includes%20all%20consumers%20on%20Home%2C%20as%20they%20don't%20have%20an%20option%20to%20defer.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EBut%20thanks%20for%20publicly%20confirming%20that%20SAC-T%20was%20just%20another%20public%20testing%20ring%2C%20like%20fast%2C%20slow%20and%20RP%20%3A)%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-355792%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%20Update%20for%20Business%20and%20the%20retirement%20of%20SAC-T%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-355792%22%20slang%3D%22en-US%22%3E%3CP%3EAnd%20while%20we%20at%20it%2C%20a%20deferral%20policy%20for%20drivers%20would%20be%20nice%20too.%20We%20do%20not%20need%20to%20have%20the%20latest%20drivers%20on%20all%20machines%2C%20we%20want%20to%20roll%20them%20out%20in%20rings%20too.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-354014%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%20Update%20for%20Business%20and%20the%20retirement%20of%20SAC-T%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-354014%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F79327%22%20target%3D%22_blank%22%3E%40John%20Wilcox%3C%2FA%3E%26nbsp%3BMany%20schools%20are%20only%20depending%20on%20Windows%20Update%20for%20Business%20(typically%20in%20workgroup%20configuration%2C%20no%20A%2FD%20etc)%20in%20order%20to%20be%20able%20to%20use%20a%20given%20W10%20version%20for%201%20schoolyear.%20It%20was%20my%20understanding%20that%20using%20the%20spring%20release%20with%20SAC%20%2B%20365%20days%20was%20ideal%3B%20release%20arrives%20march%20%2F%20april%20in%20SAC-T.%20release%20to%20SAC%20happened%20a%20few%20months%20later.%20Add%20365%20days%20after%20SAC%20and%20a%20school%20was%20all%20set.%20Now%20they%20risk%20that%20PC's%20will%20start%20to%20upgrade%20during%20the%20last%20few%20months%20of%20the%20schoolyear%20during%20exams%20etc.%20Totally%20unacceptable.%20Schools%20need%20more%20than%20just%20365%20days%20deferral.%20Using%20the%20fall%20release%20is%20even%20worse.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ECurrently%20the%20only%20thing%20that%20is%20workable%20for%20schools%20is%20using%20LTSC.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-353726%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%20Update%20for%20Business%20and%20the%20retirement%20of%20SAC-T%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-353726%22%20slang%3D%22en-US%22%3E%3CP%3EEdit%3A%20Ignore%20this%3C%2FP%3E%3CP%3EIt%20would%20be%20good%20if%20we%20could%20delete%20our%20comments.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-353723%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%20Update%20for%20Business%20and%20the%20retirement%20of%20SAC-T%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-353723%22%20slang%3D%22en-US%22%3E%3CP%3EBut%20Office%20has%20SAC-T%20and%20SAC%20with%20published%20dates%20four%20months%20apart%20(not%20an%20invisible%2060%20days).%3CBR%20%2F%3E%3CBR%20%2F%3EWhat%20guidance%20will%20Windows%20have%20in%20future%20about%20a%20%22Targeted%20Validation%20Phase%22%20(e.g.%20end%20date)%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-353720%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%20Update%20for%20Business%20and%20the%20retirement%20of%20SAC-T%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-353720%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Bruce%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EHere%20is%20the%20key%20section.%20%26nbsp%3B%26nbsp%3B%3C%2FP%3E%0A%3CH2%20id%3D%22toc-hId-1624538665%22%20style%3D%22box-sizing%3A%20border-box%3B%20color%3A%20%23333333%3B%20font-family%3A%20%26amp%3Bquot%3B%20segoe%20ui%26amp%3Bquot%3B%2Csegoe%2Ctahoma%2Cgeneva%2Csans-serif%3B%20font-size%3A%2018px%3B%20font-style%3A%20normal%3B%20font-variant%3A%20normal%3B%20font-weight%3A%20600%3B%20letter-spacing%3A%20normal%3B%20line-height%3A%201.2%3B%20orphans%3A%202%3B%20text-align%3A%20left%3B%20text-decoration%3A%20none%3B%20text-indent%3A%200px%3B%20text-transform%3A%20none%3B%20-webkit-text-stroke-width%3A%200px%3B%20white-space%3A%20normal%3B%20word-spacing%3A%200px%3B%20margin%3A%2036px%200px%2020px%200px%3B%22%20id%3D%22toc-hId-1676253853%22%20id%3D%22toc-hId-892587042%22%20id%3D%22toc-hId-892587042%22%20id%3D%22toc-hId-892587042%22%20id%3D%22toc-hId-892587042%22%20id%3D%22toc-hId-892587042%22%20id%3D%22toc-hId-892587042%22%20id%3D%22toc-hId-892587042%22%20id%3D%22toc-hId-892587042%22%20id%3D%22toc-hId-892587042%22%20id%3D%22toc-hId-892587042%22%20id%3D%22toc-hId-892587042%22%20id%3D%22toc-hId-892587042%22%20id%3D%22toc-hId-892587042%22%20id%3D%22toc-hId-892587042%22%20id%3D%22toc-hId-892587042%22%20id%3D%22toc-hId-892587042%22%20id%3D%22toc-hId-892587042%22%20id%3D%22toc-hId-892587042%22%20id%3D%22toc-hId-892587042%22%20id%3D%22toc-hId-892587042%22%20id%3D%22toc-hId-1701933668%22%3E%3CFONT%20size%3D%223%22%3E%3CEM%3EWhat%20does%20%E2%80%9Ctargeted%E2%80%9D%20mean%3F%3C%2FEM%3E%3C%2FFONT%3E%3C%2FH2%3E%0A%3CP%20style%3D%22box-sizing%3A%20border-box%3B%20color%3A%20%23333333%3B%20font-family%3A%20%26amp%3Bquot%3B%20segoeui%26amp%3Bquot%3B%2C%26amp%3Bquot%3Blato%26amp%3Bquot%3B%2C%26amp%3Bquot%3Bhelvetica%20neue%26amp%3Bquot%3B%2Chelvetica%2Carial%2Csans-serif%3B%20font-size%3A%2016px%3B%20font-style%3A%20normal%3B%20font-variant%3A%20normal%3B%20font-weight%3A%20300%3B%20letter-spacing%3A%20normal%3B%20orphans%3A%202%3B%20text-align%3A%20left%3B%20text-decoration%3A%20none%3B%20text-indent%3A%200px%3B%20text-transform%3A%20none%3B%20-webkit-text-stroke-width%3A%200px%3B%20white-space%3A%20normal%3B%20word-spacing%3A%200px%3B%20margin%3A%2020px%200px%200px%200px%3B%22%3E%3CFONT%20size%3D%223%22%3E%3CEM%3EIn%20my%20March%202018%20blog%20post%20on%20the%20organizational%20culture%20shift%20of%20%3CA%20style%3D%22background-color%3A%20transparent%3B%20box-sizing%3A%20border-box%3B%20color%3A%20%23146cac%3B%20text-decoration%3A%20underline%3B%22%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FWindows-IT-Pro-Blog%2FMoving-from-project-to-process-digital-transformation-with%2Fba-p%2F175688%22%20target%3D%22_blank%22%20rel%3D%22noopener%22%3Emoving%20Windows%2010%20deployments%20from%20project%20to%20process%3C%2FA%3E%2C%20I%20discussed%20the%20phases%20of%20the%20common%20servicing%20framework%3A%20plan%20%26amp%3B%20prepare%2C%20targeted%20validation%2C%26nbsp%3Band%20broad%20deployment.%3C%2FEM%3E%3C%2FFONT%3E%3C%2FP%3E%0A%3CP%20style%3D%22box-sizing%3A%20border-box%3B%20color%3A%20%23333333%3B%20font-family%3A%20%26amp%3Bquot%3B%20segoeui%26amp%3Bquot%3B%2C%26amp%3Bquot%3Blato%26amp%3Bquot%3B%2C%26amp%3Bquot%3Bhelvetica%20neue%26amp%3Bquot%3B%2Chelvetica%2Carial%2Csans-serif%3B%20font-size%3A%2016px%3B%20font-style%3A%20normal%3B%20font-variant%3A%20normal%3B%20font-weight%3A%20300%3B%20letter-spacing%3A%20normal%3B%20orphans%3A%202%3B%20text-align%3A%20left%3B%20text-decoration%3A%20none%3B%20text-indent%3A%200px%3B%20text-transform%3A%20none%3B%20-webkit-text-stroke-width%3A%200px%3B%20white-space%3A%20normal%3B%20word-spacing%3A%200px%3B%20margin%3A%2020px%200px%200px%200px%3B%22%3E%3CFONT%20size%3D%223%22%3E%3CEM%3ETargeted%2C%20therefore%2C%20refers%20to%20the%20initial%20phase%20of%20a%20release%2C%20the%20phase%20wherein%20your%20IT%20team%20(or%20the%20IT%20team%20here%20at%20Microsoft)%20makes%20the%20release%20available%20only%20to%20specific%2C%20%E2%80%9Ctargeted%E2%80%9D%20devices%20for%20the%20purpose%20of%20validating%20and%20generating%20data%20in%20order%20to%20get%20to%20a%20broad%20deployment%20decision.%3C%2FEM%3E%3C%2FFONT%3E%3C%2FP%3E%0A%3CP%20style%3D%22box-sizing%3A%20border-box%3B%20color%3A%20%23333333%3B%20font-family%3A%20%26amp%3Bquot%3B%20segoeui%26amp%3Bquot%3B%2C%26amp%3Bquot%3Blato%26amp%3Bquot%3B%2C%26amp%3Bquot%3Bhelvetica%20neue%26amp%3Bquot%3B%2Chelvetica%2Carial%2Csans-serif%3B%20font-size%3A%2016px%3B%20font-style%3A%20normal%3B%20font-variant%3A%20normal%3B%20font-weight%3A%20300%3B%20letter-spacing%3A%20normal%3B%20orphans%3A%202%3B%20text-align%3A%20left%3B%20text-decoration%3A%20none%3B%20text-indent%3A%200px%3B%20text-transform%3A%20none%3B%20-webkit-text-stroke-width%3A%200px%3B%20white-space%3A%20normal%3B%20word-spacing%3A%200px%3B%20margin%3A%2020px%200px%200px%200px%3B%22%3E%3CFONT%20size%3D%223%22%3EBoth%20Office%20and%20Windows%20share%20the%20same%20guidance%2C%20with%20a%20Targeted%20Validation%20Phase.%26nbsp%3B%20That%20as%20not%20changed%2C%20even%20for%20Windows.%26nbsp%3B%20The%20confusion%20I%20wrote%20about%20then%20was%20that%20there%20were%26nbsp%3B%20separate%20releases.%20Its%20the%20same%20release%20(SAC)%20that%20starts%20with%20a%20temporary%20Target%20Phase.%3C%2FFONT%3E%3C%2FP%3E%0A%3CP%20style%3D%22box-sizing%3A%20border-box%3B%20color%3A%20%23333333%3B%20font-family%3A%20%26amp%3Bquot%3B%20segoeui%26amp%3Bquot%3B%2C%26amp%3Bquot%3Blato%26amp%3Bquot%3B%2C%26amp%3Bquot%3Bhelvetica%20neue%26amp%3Bquot%3B%2Chelvetica%2Carial%2Csans-serif%3B%20font-size%3A%2016px%3B%20font-style%3A%20normal%3B%20font-variant%3A%20normal%3B%20font-weight%3A%20300%3B%20letter-spacing%3A%20normal%3B%20orphans%3A%202%3B%20text-align%3A%20left%3B%20text-decoration%3A%20none%3B%20text-indent%3A%200px%3B%20text-transform%3A%20none%3B%20-webkit-text-stroke-width%3A%200px%3B%20white-space%3A%20normal%3B%20word-spacing%3A%200px%3B%20margin%3A%2020px%200px%200px%200px%3B%22%3E%3CFONT%20size%3D%223%22%3EOffice%20has%20the%20same%2C%20you%20have%20the%20Target%20Channel%20(%20SACT)%20and%20non%20target%20channel%20(SAC%20)%20both%20have%20the%20same%20features.%3C%2FFONT%3E%3C%2FP%3E%0A%3CP%20style%3D%22box-sizing%3A%20border-box%3B%20color%3A%20%23333333%3B%20font-family%3A%20%26amp%3Bquot%3B%20segoeui%26amp%3Bquot%3B%2C%26amp%3Bquot%3Blato%26amp%3Bquot%3B%2C%26amp%3Bquot%3Bhelvetica%20neue%26amp%3Bquot%3B%2Chelvetica%2Carial%2Csans-serif%3B%20font-size%3A%2016px%3B%20font-style%3A%20normal%3B%20font-variant%3A%20normal%3B%20font-weight%3A%20300%3B%20letter-spacing%3A%20normal%3B%20orphans%3A%202%3B%20text-align%3A%20left%3B%20text-decoration%3A%20none%3B%20text-indent%3A%200px%3B%20text-transform%3A%20none%3B%20-webkit-text-stroke-width%3A%200px%3B%20white-space%3A%20normal%3B%20word-spacing%3A%200px%3B%20margin%3A%2020px%200px%200px%200px%3B%22%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%20style%3D%22box-sizing%3A%20border-box%3B%20color%3A%20%23333333%3B%20font-family%3A%20%26amp%3Bquot%3B%20segoeui%26amp%3Bquot%3B%2C%26amp%3Bquot%3Blato%26amp%3Bquot%3B%2C%26amp%3Bquot%3Bhelvetica%20neue%26amp%3Bquot%3B%2Chelvetica%2Carial%2Csans-serif%3B%20font-size%3A%2016px%3B%20font-style%3A%20normal%3B%20font-variant%3A%20normal%3B%20font-weight%3A%20300%3B%20letter-spacing%3A%20normal%3B%20orphans%3A%202%3B%20text-align%3A%20left%3B%20text-decoration%3A%20none%3B%20text-indent%3A%200px%3B%20text-transform%3A%20none%3B%20-webkit-text-stroke-width%3A%200px%3B%20white-space%3A%20normal%3B%20word-spacing%3A%200px%3B%20margin%3A%2020px%200px%200px%200px%3B%22%3E%3CFONT%20size%3D%223%22%3EJohn%3C%2FFONT%3E%3C%2FP%3E%0A%3CP%20style%3D%22box-sizing%3A%20border-box%3B%20color%3A%20%23333333%3B%20font-family%3A%20%26amp%3Bquot%3B%20segoeui%26amp%3Bquot%3B%2C%26amp%3Bquot%3Blato%26amp%3Bquot%3B%2C%26amp%3Bquot%3Bhelvetica%20neue%26amp%3Bquot%3B%2Chelvetica%2Carial%2Csans-serif%3B%20font-size%3A%2016px%3B%20font-style%3A%20normal%3B%20font-variant%3A%20normal%3B%20font-weight%3A%20300%3B%20letter-spacing%3A%20normal%3B%20orphans%3A%202%3B%20text-align%3A%20left%3B%20text-decoration%3A%20none%3B%20text-indent%3A%200px%3B%20text-transform%3A%20none%3B%20-webkit-text-stroke-width%3A%200px%3B%20white-space%3A%20normal%3B%20word-spacing%3A%200px%3B%20margin%3A%2020px%200px%200px%200px%3B%22%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%20style%3D%22box-sizing%3A%20border-box%3B%20color%3A%20%23333333%3B%20font-family%3A%20%26amp%3Bquot%3B%20segoeui%26amp%3Bquot%3B%2C%26amp%3Bquot%3Blato%26amp%3Bquot%3B%2C%26amp%3Bquot%3Bhelvetica%20neue%26amp%3Bquot%3B%2Chelvetica%2Carial%2Csans-serif%3B%20font-size%3A%2016px%3B%20font-style%3A%20normal%3B%20font-variant%3A%20normal%3B%20font-weight%3A%20300%3B%20letter-spacing%3A%20normal%3B%20orphans%3A%202%3B%20text-align%3A%20left%3B%20text-decoration%3A%20none%3B%20text-indent%3A%200px%3B%20text-transform%3A%20none%3B%20-webkit-text-stroke-width%3A%200px%3B%20white-space%3A%20normal%3B%20word-spacing%3A%200px%3B%20margin%3A%2020px%200px%200px%200px%3B%22%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-353715%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%20Update%20for%20Business%20and%20the%20retirement%20of%20SAC-T%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-353715%22%20slang%3D%22en-US%22%3E%3CP%3EThat%20just%20says%20you%20%22aligned%22%3B%20it%20doesn't%20explain%20why%20Office%20still%20has%20a%20SAC-T%20with%20separate%20dates.%3CBR%20%2F%3E%3CBR%20%2F%3EIt's%20not%20a%20common%20servicing%20model%20if%20SAC-T%20is%20only%20disappearing%20from%20Windows%2C%20but%20not%20Office.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-353676%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%20Update%20for%20Business%20and%20the%20retirement%20of%20SAC-T%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-353676%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Bruce%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ESee%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FWindows-IT-Pro-Blog%2FWindows-10-and-the-disappearing-SAC-T%2Fba-p%2F199747%22%20target%3D%22_self%22%3Ehere%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CFONT%20style%3D%22background-color%3A%20%23ffffff%3B%22%3EOffice%20and%20Windows%20common%20servicing%20model%20is%20covered%20there.%3C%2FFONT%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CFONT%20style%3D%22background-color%3A%20%23ffffff%3B%22%3EJW%3C%2FFONT%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-353066%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%20Update%20for%20Business%20and%20the%20retirement%20of%20SAC-T%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-353066%22%20slang%3D%22en-US%22%3E%3CP%3EAlthough%20i'm%20not%20sure%20how%20it%20works%20exactly.%20Maybe%20it%20can't%20install%20a%20release%20when%20it%20is%20not%20supported%20anymore%2C%20even%20if%20deferred%20setting%20is%20applied%20at%20that%20point%20(otherwise%20it%20would%20install%20say%202003%20(2020.03)%20update%20on%202022.04.xx%20when%20it%20was%20supported%20only%20till%202021.09.xx%2C%20so%20you%20will%20miss%206%20months%20of%20security%20updates%20(although%20you%20would%20get%20a%20TON%20of%20them%20after%20this%20update%20and%20release%20update%20itself%20will%20be%20humongous%20and%20will%20take%20hours%20to%20install%20probably).%20And%20the%20it%20will%20wait%20for%20two%20years%20to%20install%202020.09%2C%20which%20should%20be%20supported%20for%2030%20months%20(Ent%2FEdu).%20So%20it%20will%20install%202020.09%20on%202024.04.xx%20and%20it%20won't%20be%20supported%20already%20either%20at%20that%20point%20(1%20year%20without%20security%20updates%20even).%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-353055%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%20Update%20for%20Business%20and%20the%20retirement%20of%20SAC-T%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-353055%22%20slang%3D%22en-US%22%3E%3CP%3EBut%20spring%20releases%20are%20only%20supported%20for%2018%20months.%20You%20will%20stay%20without%20security%20updates%20for%20a%20while%20in%20such%20case.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-353053%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%20Update%20for%20Business%20and%20the%20retirement%20of%20SAC-T%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-353053%22%20slang%3D%22en-US%22%3E%3CP%3EIt%20is%20not%20enough%20for%20a%20deferred%20date%20of%20365%20days.%3CBR%20%2F%3EFor%20Enterprise%20and%20Education%20environments%2C%20please%20extend%20it%20to%20about%20730%20days.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-352319%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%20Update%20for%20Business%20and%20the%20retirement%20of%20SAC-T%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-352319%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%20%3CFONT%20style%3D%22background-color%3A%20%23ffffff%3B%22%3EVadim%2C%3C%2FFONT%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CFONT%20style%3D%22background-color%3A%20%23ffffff%3B%22%3EWe%20only%20have%202%20releases%20each%20year%2C%20(%20release%20%3D%20new%20features%2Ffunctionality%2FAPIs%20).%20We%20call%20these%20the%20SAC%20releases%2C%20for%20Semi-Annual%20Channel.%20%3C%2FFONT%3E%3C%2FP%3E%0A%3CP%3E%3CFONT%20style%3D%22background-color%3A%20%23ffffff%3B%22%3EThat%20is%20why%20there%20never%20was%20a%20%22SACT%22%20and%20%22SAC%22%20release.%20%26nbsp%3B%26nbsp%3B%20SACT%20referred%20to%20the%20phase%20of%20deployment%20where%20we%20are%20publishing%20only%20to%20%22targeted%22%20devices%2C%20versus%20all%2C%20and%20aligns%20the%20common%20guidance%20shared%20between%20Office%20and%20Windows%20for%20managing%20a%20deployment%20rollout.%20%3C%2FFONT%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CFONT%20style%3D%22background-color%3A%20%23ffffff%3B%22%3EI%20cover%20this%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FWindows-IT-Pro-Blog%2FWindows-10-and-the-disappearing-SAC-T%2Fba-p%2F199747%22%20target%3D%22_self%22%3Ehere%3A%3C%2FA%3E%26nbsp%3B%3C%2FFONT%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CFONT%20style%3D%22background-color%3A%20%23ffffff%3B%22%3EIn%20that%20blog%2C%20you%20will%20also%20find%20links%20to%20the%20shared%20Office%20and%20Windows%20recommended%20servicing%20model.%3C%2FFONT%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThere%20is%20only%20one%20release%20date%20for%20each%20SAC.%20For%20devices%20connected%20to%20the%20update%20service%2C%20using%20WuFB%2C%20we%20begin%20updating%20them%20based%20on%20the%20values%20the%20users%20have%20configured%20their%20devices.%20We%20don't%20have%20separate%20release%20dates%2C%20consumer%20vs%20other.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EFor%20commercial%20customers%20that%20self%20manage%2C%20they%20get%20the%20same%20release%2C%20but%20determine%20when%20and%20how%20it%20will%20get%20published%20to%20their%20users%20via%20their%20management%20tool%20of%20choice%2C%20SCCM%2C%20home%20grown%20or%20other.%3C%2FP%3E%0A%3CP%20style%3D%22box-sizing%3A%20border-box%3B%20color%3A%20%23333333%3B%20font-family%3A%20%26amp%3Bquot%3B%20segoeui%26amp%3Bquot%3B%2C%26amp%3Bquot%3Blato%26amp%3Bquot%3B%2C%26amp%3Bquot%3Bhelvetica%20neue%26amp%3Bquot%3B%2Chelvetica%2Carial%2Csans-serif%3B%20font-size%3A%2016px%3B%20font-style%3A%20normal%3B%20font-variant%3A%20normal%3B%20font-weight%3A%20300%3B%20letter-spacing%3A%20normal%3B%20orphans%3A%202%3B%20text-align%3A%20left%3B%20text-decoration%3A%20none%3B%20text-indent%3A%200px%3B%20text-transform%3A%20none%3B%20-webkit-text-stroke-width%3A%200px%3B%20white-space%3A%20normal%3B%20word-spacing%3A%200px%3B%20margin%3A%200px%3B%22%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-352313%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%20Update%20for%20Business%20and%20the%20retirement%20of%20SAC-T%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-352313%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20ajc196%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EAlready%20are.%20Starting%20with%201807%2C%20we%20have%20been%20publishing%20monthly%20media%20refresh%20for%201803%20and%201807%20every%20month%20to%20MSDN%20and%20VSS.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EJW%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-352310%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%20Update%20for%20Business%20and%20the%20retirement%20of%20SAC-T%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-352310%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Oleg%2C%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIf%20your%20not%20using%20WuFB%20deferral%2C%20then%20this%20has%20never%20and%20will%20not%20going%20forward%20have%20any%20impact%20to%20make%20any%20change%20for%20you.%3C%2FP%3E%0A%3CP%3EJW%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-352279%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%20Update%20for%20Business%20and%20the%20retirement%20of%20SAC-T%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-352279%22%20slang%3D%22en-US%22%3EWill%20refresh%20media%20continue%20to%20be%20released%2C%20or%20will%20that%20also%20be%20a%20one-and-done%20release%20with%20each%20feature%20update%3F%20Since%20Windows%2010%20began%2C%20volume%20ISOs%20and%20WSUS%20KBs%20were%20refreshed%20to%20the%20latest%20build%20number%20and%20re-released%20once%20they%20hit%20CBB%2FSAC.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-352041%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%20Update%20for%20Business%20and%20the%20retirement%20of%20SAC-T%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-352041%22%20slang%3D%22en-US%22%3E%3CP%3ESAC-T%20Policy%20after%201903%3A%3C%2FP%3E%3CP%3E%3CSPAN%3E%26nbsp%3B%20-%26nbsp%3Breadiness%20level%3A%20this%20will%20disappear%20from%20GPs%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3E%26nbsp%3B%20-%20deferral%20period%3A%20this%20will%20stay%20and%20you%20will%20have%20to%20adjust%20it%20to%20meet%20your%20needs%20-%20otherwise%20new%20release%20after%201903%20(first%20will%20be%2019H2)%20will%20be%20installed%20as%20soon%20as%20it%20is%20RTM%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-343174%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%20Update%20for%20Business%20and%20the%20retirement%20of%20SAC-T%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-343174%22%20slang%3D%22en-US%22%3E%3CP%3EI%20haven't%20used%20WU%20for%20Business%20policies%2C%20but%20from%20this%20blog%20i%20gathered%20that%20SAC-T%20won't%20be%20used%20anymore%20(after%201903)%2C%20so%20having%20SAC-T%20policy%20won't%20have%20any%20effect%20after%20the%201903%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-343129%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%20Update%20for%20Business%20and%20the%20retirement%20of%20SAC-T%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-343129%22%20slang%3D%22en-US%22%3E%3CDIV%20class%3D%22lia-message-author-with-avatar%22%3E%3CSPAN%20class%3D%22UserName%20lia-user-name%20lia-user-rank-New-Contributor%20lia-component-message-view-widget-author-username%22%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F226354%22%20target%3D%22_self%22%3E%3CSPAN%20class%3D%22%22%3EVadim%20Sterkin%20%3A%3C%2FSPAN%3E%3C%2FA%3E%3C%2FSPAN%3E%3C%2FDIV%3E%3CDIV%20class%3D%22lia-message-author-with-avatar%22%3E%26nbsp%3B%3C%2FDIV%3E%3CP%3E%3CSPAN%3E-%20Yes%2C%20they%26nbsp%3B%26nbsp%3Bwould%20have%20released%201809%20to%20SAC%20on%26nbsp%3B11%2F13%2F2018%20...%20(b%3C%2FSPAN%3E%3CSPAN%3Eut%20only%20if%20you%20have%20no%20deferrals%20in%20place)%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3ELook%2C%20we%20have%20in%20our%20GPs%20this%20for%20all%20our%20PCs%3A%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3E-%26nbsp%3Breadiness%20level%3A%20SAC%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3E-%20deferral%20period%3A%20180%20days%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3ESo%20our%20PCs%20now%20update%20to%20new%20version%206%20months%20after%20its%20SAC%20declared%20date%20...%20so%20this%20is%20cca%208-10%20months%20after%20SAC-T%20date.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3ESo%20what%20I%20will%20do%20right%20now%20to%20be%20prepared%20for%20the%20new%20change%20(and%20to%20be%20good%20to%20forget%20about%20it%20%3A)%20is%20this%3A%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3E-%20change%20GPs%20to%20this%3A%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3E%26nbsp%3B%20-%26nbsp%3Breadiness%20level%3A%20SAC-T%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3E%26nbsp%3B%20-%20deferral%20period%3A%20300%20days%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EAnd%20that's%20it%20-%20I%20can%20forget%20about%20all%20this%20(with%20hope%2C%20Microsoft%20will%20be%20able%20to%20stabilize%20each%20version%20after%20300%20days%20%3A)%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-341146%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%20Update%20for%20Business%20and%20the%20retirement%20of%20SAC-T%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-341146%22%20slang%3D%22en-US%22%3E%3CP%3E%26nbsp%3BAny%20plans%20on%20adding%20additional%20time%20for%20the%20defferal%20policy%3F%20We%20could%20set%20up%20the%20months%20of%20support%20but%20only%20365%20days%20defferal...%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-341126%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%20Update%20for%20Business%20and%20the%20retirement%20of%20SAC-T%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-341126%22%20slang%3D%22en-US%22%3E%3CBLOCKQUOTE%3E%3CP%3E%3CSPAN%3Ethere%20was%20never%20actually%20a%26nbsp%3BSemi-Annual%20Channel%20(Targeted)%2C%20or%20SAC-T%2C%20release%3B%20rather%2C%20SAC-T%20merely%20reflected%20a%20milestone%20for%20the%20semi-annual%20release%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3E...%3C%2FSPAN%3E%3C%2FP%3E%3CP%3EAs%20I%20said%20above%2C%20with%20version%201903%2C%20we%20will%20cease%20to%20publish%20both%20SAC%20and%20SAC-T%20dates.%20Each%20release%20will%20have%20a%20single%20SAC%20release%20date%3C%2FP%3E%3CHR%20%2F%3E%3C%2FBLOCKQUOTE%3E%3CP%3EWhen%20you%20write%20all%20this%2C%20you%20totally%20pretend%20like%20the%20consumers%20don't%20exist%20(this%20is%20typical%20for%20your%20posts%20in%20general).%20There%20was%20a%20SAC-T%20all%20right%2C%20and%20it%20was%20the%20date%20when%20the%20new%20version%20would%20start%20rolling%20out%20to%20the%20consumers.%20Now%20you%20suddenly%20never%20had%20SAC-T%20and%20would%20stop%20publishing%20its%20date.%20So%20what%20do%20you%20call%20the%20date%20on%20which%20you%20start%20pushing%20the%20new%20version%20to%20Home%20editions%20(sans%20Insider%20rings)%3F%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAlso%20(and%20this%20is%20the%20main%20question%20you%20failed%20to%20address)%2C%20%3CSTRONG%3Eare%20you%20going%20to%20start%20pushing%20new%20releases%20to%20WUfB%20and%20consumers%20on%20the%20same%20date%3F%3C%2FSTRONG%3E%20It's%20not%20clear%20whether%20SAC%20takes%20the%20SAC-T%20place%20as%20the%20%22official%20release%22%20date%20(i.e.%20when%20anybody%20can%20download%20it).%20For%20example%2C%201809%20was%20released%20to%20SAC-T%20on%2011%2F13%2F2018%20while%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows%2Fwindows-10%2Frelease-information%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ethere's%20no%20SAC%20release%20date%20at%20this%20time%3C%2FA%3E.%26nbsp%3BIf%20the%20change%20were%20in%20place%20now%2C%20would%20you%20have%20released%201809%20to%20SAC%20on%26nbsp%3B11%2F13%2F2018%3F%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-340076%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%20Update%20for%20Business%20and%20the%20retirement%20of%20SAC-T%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-340076%22%20slang%3D%22en-US%22%3EHow%20is%20this%20aligned%20with%20Office%2C%20which%20has%20SAC-T%20and%20SAC%20and%20Monthly%20feature%20update%20release%20channels%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-340066%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%20Update%20for%20Business%20and%20the%20retirement%20of%20SAC-T%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-340066%22%20slang%3D%22en-US%22%3E%3CP%3EWhile%20the%20naming%20of%20the%20CBB%2FSacT%20was%20confusing%2C%20the%20fact%20that%20all%20businesses%20still%20want%20a%20date%20that%20we%20can%20deem%20that%20we're%20past%20the%20beta%20testing%20phase%20of%20these%20releases%20is%20still%20needed.%3C%2FP%3E%0A%3CP%3EI%20STILL%20have%20not%20received%201809%20on%20my%20home%20Laptop%20due%20to%20icloud%20software%20being%20on%20there%20and%20thusly%20it's%20held%20off%20until%20mid%20Feb.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EWe%20still%20need%20a%20time%20in%20the%20sand%20that%20we%20all%20trust%20your%20releases.%26nbsp%3B%20We%20don't.%26nbsp%3B%20Work%20on%20that.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EAnd%20may%20I%20say%20this%20just%20makes%20it%20more%20confusing%2C%20not%20less.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-340058%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%20Update%20for%20Business%20and%20the%20retirement%20of%20SAC-T%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-340058%22%20slang%3D%22en-US%22%3E%3CP%3EThis%20is%20horrible%20and%20an%20ongoing%20insult%20to%20your%20customers%20given%20that%20you%20are%20unable%20to%20release%20a%20single%20stable%20feature%20release%20of%20Windows%2010.%20When%20will%20you%20-%20Microsoft%20-%20release%20stable%20software%3F%20And%20you%20can%20say%2C%20in%20marketing-speak%2C%20that%20there%20%22never%20was%20really%20a%20difference%20between%20SAC-T%20and%20SAC%22%20but%20the%20very%20fact%20it%20was%20enshrined%20in%20the%20software%20catches%20you%20out.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-339906%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%20Update%20for%20Business%20and%20the%20retirement%20of%20SAC-T%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-339906%22%20slang%3D%22en-US%22%3E%3CP%3E%22If%20you%20use%20System%20Center%20Configuration%20Manager%2C%20Windows%20Server%20Update%20Services%20(WSUS)%2C%20or%20other%20management%20tools%2C%20there%20will%20now%20only%20be%20one%20feature%20update%20published%20to%20WSUS%2C%20and%20this%20will%20occur%20at%20the%20time%20of%20release.%22%20I%20didn't%20get%20that%20part.%20We%20were%20already%20getting%20just%20one%20release%20in%20WSUS.%20I%20don't%20recall%20seeing%20SAC-T%20releases.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-643227%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%20Update%20for%20Business%20and%20the%20retirement%20of%20SAC-T%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-643227%22%20slang%3D%22en-US%22%3E%3CP%3EHi%3C%2FP%3E%3CP%3EIf%20my%20device%20is%20in%20SAC%2C%20and%20have%201803.%20And%20device%20has%20Intune%20policy%20with%26nbsp%3B%2070%20days%20deferral%20for%20feature%20update.%20To%20which%20version%20device%20will%20be%20updated%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%2F%2FAlexander%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-644346%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%20Update%20for%20Business%20and%20the%20retirement%20of%20SAC-T%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-644346%22%20slang%3D%22en-US%22%3E%3CP%3EGood%20Morning%20Alexander%2C%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EWhen%20your%20managing%20a%20device%20updates%20with%20WuFB%2C%20(%20in%20your%20case%20via%20Intune%20)%2C%20you%20will%20get%20an%20update%2C%20when%20there%20is%20a%20new%20version%20that%20meets%20your%20updates%20criteria%2C%20which%20you%20have%20said%20is%2070%20day%20deferral.%20There%20will%20only%20be%20one%20release%20at%20a%20time%20when%20your%20criteria%20is%20met%2C%20and%20it%20will%20always%20be%20the%20next%20chorological%20release%20from%20the%20one%20you%20are%20on%2C%20so%20you'll%20next%20get%201809.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EJW%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-644405%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%20Update%20for%20Business%20and%20the%20retirement%20of%20SAC-T%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-644405%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F79327%22%20target%3D%22_blank%22%3E%40John%20Wilcox%3C%2FA%3E%26nbsp%3BAre%20the%20dates%20listed%20here%20confirmed%20dates%20for%20Enterprise%20release%20of%20Feature%20updates%3F%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows%2Frelease-information%2F%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%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows%2Frelease-information%2F%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20have%20180%20days%20in%20SAC-T%20configured%2C%20and%20I%20still%20have%20devices%20in%201803.%20If%20I%20go%20by%20the%20date%20of%20Nov%2013%2C%202018%20(1809)%20%2B%20180%20days%20I%20end%20up%20with%20May%2012%2C%202019%2C%20however%20I%20still%20I%20have%20loads%20of%20devices%20at%201803.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EYou%20also%20list%20May%2021%2C%202019%20for%201903%2C%20I%20have%20SAC-T%20configured%20for%20some%20test%20devices%20with%200%20day%20delay%2C%20still%20no%201903.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIt's%20super%20hard%20to%20determine%20exactly%20what%20updates%20i'll%20be%20getting%20with%20configured%20deferrals%20if%20I%20don't%20have%20an%20EXACT%20date%20that%20the%20deferrals%20are%20counting%20up%20from.%20You%20should%20really%20release%20some%20sort%20of%20enterprise%20calculator%20where%20I%20can%20plug%20in%20deferral%20times%20and%20it%20will%20clearly%20show%20myself%20what%20patches%20my%20machines%20should%20be%20getting.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-644496%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%20Update%20for%20Business%20and%20the%20retirement%20of%20SAC-T%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-644496%22%20slang%3D%22en-US%22%3E%3CP%3EYes%2C%20it%20was%20hard%20to%20determine%2C%20thus%20the%20reason%20we%20made%20the%20changes%20to%20simplify%20that%20are%20the%20topic%20of%20the%20blog%20above.%20Now%20everything%20can%20be%20calculated%20off%20the%20one%20release%20date.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EFrom%20your%20scenario%20descriptions%2C%20I%20believe%20your%20still%20on%201803%2C%20(%201809%20no%20longer%20has%20SAC-T%20as%20a%20branch%20option)%20%2C%20so%20you%20will%20not%20be%20updated%20to%201903%2C%20but%20to%201809.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EFor%20the%20%22loads%20of%20SAC-T%22%20devices%20still%20on%201803%2C%20please%20check%20the%20update%20status%3F%20Have%20they%20downloaded%20the%20update%2C%20but%20waiting%20for%20the%20user%20to%20initiate%20the%20update%2C%20or%20reboot%20the%20device%3F%20The%20device%20won't%20move%20forward%20until%20the%20reboot%2C%20which%20the%20user%20can%20control%2C%20unless%20you%20enforce%20that.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EJW%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-644625%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%20Update%20for%20Business%20and%20the%20retirement%20of%20SAC-T%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-644625%22%20slang%3D%22en-US%22%3E%3CP%3EI%20saw%201903%20in%20WSUS%20the%20day%201903%20was%20announced%20(a%20few%20days%20ago).%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-644528%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%20Update%20for%20Business%20and%20the%20retirement%20of%20SAC-T%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-644528%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F79327%22%20target%3D%22_blank%22%3E%40John%20Wilcox%3C%2FA%3E%26nbsp%3Bso%20are%20you%20saying%20if%20I%20have%201809%20devices%20configured%20with%20SAC-T%200%20day%20delay%20they%20won't%20get%201903%20at%20all%3F%20Are%20you%20saying%20I%20have%20to%20force%20my%20device%20down%20to%20SAC%20to%20get%201903%3F%20I%20just%20forced%20down%20to%20SAC%20%2F%200%20day%20delay%20for%20my%20test%20group%2C%20searched%20for%20updates%2C%20still%20no%201903%2C%20most%20likely%20because%20your%20adding%20a%2060%20day%20delay%20to%20SAC%20as%20a%20default.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20blog%20above%20says%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CUL%3E%3CLI%3EWindows%20Update%20for%20Business%20customers%20who%20have%20configured%20a%20deferral%26nbsp%3Bbased%20on%20the%20SAC-T%20branch-readiness%20level%20(remember%2C%20this%20really%20is%20the%20actual%20release%20date)%2C%20devices%20will%20be%20offered%20the%20update%20once%20the%20configured%20number%20of%20deferral%20days%20have%20passed.%20Thus%2C%20no%20change%20from%20previous%20releases.%3C%2FLI%3E%3C%2FUL%3E%3CP%3ESo%2C%20should%20I%20not%20be%20receiving%201903%20on%20SAC-T%20with%200%20day%20delay%20right%20now%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-661643%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%20Update%20for%20Business%20and%20the%20retirement%20of%20SAC-T%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-661643%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F79327%22%20target%3D%22_blank%22%20rel%3D%22noopener%22%3E%40John%20Wilcox%3C%2FA%3E%20it%20may%20make%20sense%20to%20also%20communicate%20the%20availability%20of%20new%20feature%20updates%20can%20vary%20based%20on%20Microsoft's%20%22limited%20release%22%20and%20hardware%20support.%20I%20was%20using%20an%20Inspiron%209380%20%2Fw%20WUB%200%20day%20delay%2C%20and%20still%20no%201903.%20Moved%20to%20a%20Surface%20Laptop%202%2C%20same%20WUB%200%20day%20delay%20policies%2C%20and%20I%20got%201903%20immediately.%20This%20can%20make%20things%20frustrating%20when%20calculating%20the%20servicing%20delay's%2C%20as%20we%20essentially%20are%20unable%20to%20control%20a%20proper%20initial%20release%20and%20testing%20based%20on%20the%20published%20dates%20if%20the%20updates%20are%20only%20made%20available%20to%20select%20hardware%20automatically.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-661656%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%20Update%20for%20Business%20and%20the%20retirement%20of%20SAC-T%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-661656%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Chris%2C%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EMissing%20some%20details%2C%20so%20let%20me%20give%20you%20most%20likely%20things%20to%20look%20at.%3C%2FP%3E%0A%3CP%3E1)%20Inspiron%26nbsp%3B%20%2C%20which%20branch%20readiness%20config%20did%20you%20have%2C%20SAC%20or%20SAC-T.%26nbsp%3B%20If%20SAC%2C%20then%20remember%2C%20we%20are%20adding%20%2B60%20as%20a%20one%20time%20event%2C%20thus%20it%20will%20be%2060%20days%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E2)%20What%20did%20you%20configure%20for%20the%20Surface%20specifically%2C%20or%20did%20you%20mean%20its%20just%20default%3F%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E3)%20If%20a%20device%20is%20default%2C%20(%20new%20device%20old%20device%20never%20changed%2C%20or%20has%20been%20restored)%20it%20is%20not%20the%20same%20as%20a%20deferral%20of%20%220%22.%20Instead%2C%20it%20is%20managed%20via%20the%20WU%20intelligent%20role%20out%20process%2C%20which%20is%20non-deterministic%20by%20device%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E4)%20If%20the%20device%20has%20a%20compat%20block%2C%20ie%20there%20is%20a%20known%20conflict%20not%20yet%20resolved%2C%20we%20will%20not%20update%20the%20device%20into%20the%20bad%20state%2C%20even%20at%20the%20deferral%20period.%26nbsp%3B%20You%20can%20see%20the%20known%20and%20tracked%20issues%2Fcompat%20blocks%20on%20the%20release%20history%20page%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-661662%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%20Update%20for%20Business%20and%20the%20retirement%20of%20SAC-T%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-661662%22%20slang%3D%22en-US%22%3E%3CP%3ESAC-T%200%20Day%20delay%20policy%2C%20Modern%20Desktop%20managed%20through%20Intune.%20Both%20devices%20were%20under%20the%20same%20management%20%2F%20policies%20SAC-T%200%20day%20delay.%20I%20have%20quite%20a%20few%20not%20receiving%20it%2C%20Surface%20Laptop%202%20received%20it%20immediately.%20I'll%20assume%20it's%20a%20blocking%20issue%20on%20the%20other%20devices%20that's%20going%20through%20resolution%20as%20we%20speak%2C%20thanks.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-677447%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%20Update%20for%20Business%20and%20the%20retirement%20of%20SAC-T%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-677447%22%20slang%3D%22en-US%22%3EIf%20I'm%20on%20Windows%2010%20Enterprise%201803%20and%20on%20SAC%20with%200%20days%20deferred.%20When%20will%20I%20get%201809%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-720450%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%20Update%20for%20Business%20and%20the%20retirement%20of%20SAC-T%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-720450%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F79327%22%20target%3D%22_blank%22%3E%40John%20Wilcox%3C%2FA%3E%26nbsp%3B%2C%20currently%20the%20maximum%20deferral%20period%20for%20Feature%20Updates%20is%20365%20days.%20For%20Windows%2010%20Enterprise%20can%20this%20be%20extended%20to%20the%20full%20length%20of%20the%20supported%20lifespan%2C%20so%20two%20years%3F%26nbsp%3B%20While%20my%20organization%20hopes%20to%20get%20to%20an%20annual%20upgrade%20cadence%2C%20we're%20not%20there%20yet%20(still%20on%201703%2C%20moving%20to%201809%20by%20the%20fall)%2C%20and%20limiting%20us%20to%20only%20half%20the%20supported%20period%20forces%20us%20to%20block%20connection%20to%20Microsoft%20update%20servers%20and%20deploy%20updates%20via%20other%20channels.%26nbsp%3B%20Thank%20you!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-731323%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%20Update%20for%20Business%20and%20the%20retirement%20of%20SAC-T%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-731323%22%20slang%3D%22en-US%22%3E%3CP%3EHello%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20have%20now%202x%20policies%20set%20via%20Intune%20Software%20Update%20Rings%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E1st%20SAC%20with%20deferral%20%3D%20120%20days%20%3D%26gt%3B%20targeted%20to%20company%20devices%20%26amp%3B%20excluding%20SAC-T%20devices%3B%3C%2FP%3E%3CP%3E2nd%20SAC-T%20with%20deferral%20%3D%207%20days%20-%26gt%3B%20targeted%20to%20specific%20group%20with%20devices%20%26amp%3B%20excluding%20SAC%20devices%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ENow%20devices%20in%202nd%20policy%20updated%20to%201903%2C%3C%2FP%3E%3CP%3EDo%20we%20need%20to%20change%20policy%20and%20create%20Intune%20Software%20Update%20Rings%20only%20for%20SAC%2C%20so%20we%20will%20have%3A%3C%2FP%3E%3CP%3E1st%20SAC%20with%20deferral%20%3D%2060%20days%20%3D%26gt%3B%20targeted%20to%20company%20devices%20%26amp%3B%20excluding%20SAC-T%20devices%3B%20(changing%20here%20to%2060%20days%2C%20as%20deferral%20will%20have%20another%2060%20from%20service)%3C%2FP%3E%3CP%3E2nd%20SAC%20with%20deferral%20%3D%207%20days%20-%26gt%3B%20targeted%20to%20specific%20group%20with%20devices%20%26amp%3B%20excluding%20SAC%20devices%3B%3C%2FP%3E%3CP%3EOr%20we%20can%20continue%20keep%20using%20SAC-T%20via%20Intune%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-749617%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%20Update%20for%20Business%20and%20the%20retirement%20of%20SAC-T%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-749617%22%20slang%3D%22en-US%22%3E%3CP%3EGOOD%20RIDDANCE%20-%20the%20targeted%20version%20was%20the%20unstable%20one%20with%20sufficiently%20tested%20updates%20and%20features.%20After%20years%20of%20Targeted%20unstable%20retail%20updates%20screwing%20up%20millions%20of%20computers%20you%20finally%20accepted%20the%20fact%20that%20you%20cant%20rush%20feature%20without%20proper%20research%20and%20testing%20time%20-%20especially%20in%20business%20environment.%20From%20experience%20I%20also%20highly%20recommend%20a%207%20day%20deferral%20of%20feature%20updates%20on%20top%20of%20that%20to%20avoid%20any%20last%20minute%20or%20post%20release%20screw%20ups%20and%20fixes.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-339523%22%20slang%3D%22en-US%22%3EWindows%20Update%20for%20Business%20and%20the%20retirement%20of%20SAC-T%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-339523%22%20slang%3D%22en-US%22%3E%3CP%20style%3D%22margin-top%3A%2020px%3B%22%3E%3CSTRONG%3EUpdate%207%2F15%2F2019%3A%3C%2FSTRONG%3EAs%20a%20reminder%20to%20customers%20on%20Windows%2010%2C%20version%201809%20using%20Windows%20Update%20for%20Business%20with%20a%20Branch%20Readiness%20Level%20set%20to%20Semi-Annual%20Channel%20and%20a%20default%200-day%20deferral%2C%20your%2060-day%20one-time%20built-in%20deferral%20period%20will%20end%20on%20Tuesday%2C%20July%2023%2C%202019%20and%20your%20devices%20will%20begin%20updating%20to%20Windows%2010%2C%20version%201903.%3C%2FP%3E%0A%3CP%3EUpdate%202%2F28%2F2019%3A%20This%20change%20does%20not%20affect%20SAC-T%20for%20Office%20365%20ProPlus%20customers.%20See%20below%20for%20details.%3C%2FP%3E%0A%3CHR%20%2F%3E%0A%3CP%20style%3D%22margin-top%3A%2020px%3B%22%3EIn%20my%20post%20last%20May%20on%26nbsp%3B%3CSPAN%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FWindows-IT-Pro-Blog%2FWindows-10-and-the-disappearing-SAC-T%2Fba-p%2F199747%22%20target%3D%22_blank%22%20rel%3D%22noopener%22%3EWindows%2010%20and%20the%20%E2%80%9Cdisappearing%E2%80%9D%20SAC-T%3C%2FA%3E%3C%2FSPAN%3E%2C%3CSTRONG%3E%26nbsp%3B%3C%2FSTRONG%3EI%20explained%20how%20we%20simplified%20and%20aligned%20our%20Windows%20servicing%20terminology%20with%20Office%2C%20reflecting%20that%20there%20are%20two%20Semi-Annual%20Channel%20(SAC)%20releases%20each%20year.%26nbsp%3BI%20also%20explained%20that%20with%20Windows%2C%20there%20was%20never%20actually%20a%26nbsp%3BSemi-Annual%20Channel%20(Targeted)%2C%20or%20SAC-T%2C%20release%3B%20rather%2C%20SAC-T%20merely%20reflected%20a%20milestone%20for%20the%20semi-annual%20release.%20Unless%20you%20were%20using%20Windows%20Update%20for%20Business%2C%20the%20SAC%20and%20SAC-T%20designations%20had%20no%20impact%20on%20when%20your%20devices%20would%20be%20updated.%20At%20the%20time%2C%20we%20had%20not%20yet%20completed%20the%20work%20necessary%20to%20deliver%20the%20changes%20needed%20for%20Windows%20Update%20for%20Business%20to%20reflect%20the%20alignment%20with%20Office%20so%20we%20continued%20to%20show%20dates%20for%20both%20the%20SAC%20and%20SAC-T%20milestones%20on%20the%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows%2Fwindows-10%2Frelease-information%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%22%3EWindows%2010%20release%20information%3C%2FA%3E%20page.%3C%2FP%3E%0A%3CP%20style%3D%22margin-top%3A%2020px%3B%22%3EWe%20have%20now%20completed%20that%20work.%20Beginning%20with%20Windows%2010%2C%20version%201903%20(the%20next%20feature%20update%20for%20Windows%2010)%2C%20the%20Windows%2010%20release%20information%20page%20will%20no%20longer%20list%20SAC-T%20information%20for%20version%201903%20and%20future%20feature%20updates.%20Instead%2C%20you%20will%20find%20a%20single%20entry%20for%20each%20new%20SAC%20release.%20In%20addition%2C%20if%20you%20are%20using%20Windows%20Update%20for%20Business%2C%20you%20will%20see%20new%20UI%20and%20behavior%20to%20reflect%20that%20there%20is%20only%20one%20release%20date%20for%20each%20SAC%20release.%20If%20you%20use%20System%20Center%20Configuration%20Manager%2C%20Windows%20Server%20Update%20Services%20(WSUS)%2C%20or%20other%20management%20tools%2C%20there%20will%20now%20only%20be%20one%20feature%20update%20published%20to%20WSUS%2C%20and%20this%20will%20occur%20at%20the%20time%20of%20release.%26nbsp%3B(%3CEM%3ENote%3A%20This%20change%20does%20not%20impact%20the%20availability%20of%20SAC-T%20for%20Office%20365%20ProPlus.%20The%20SAC-T%20channel%20will%20continue%20to%20be%20an%20option%20for%20Office%20365%20ProPlus%20customers.%20For%20more%20information%2C%20see%26nbsp%3B%3CU%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%3EOverview%20of%20update%20for%20channels%20for%20Office%20365%3C%2FA%3E%3C%2FU%3E.%3C%2FEM%3E)%3C%2FP%3E%0A%3CP%20style%3D%22margin-top%3A%2020px%3B%22%3EWith%20this%20upcoming%20change%2C%20Windows%20Update%20for%20Business%20customers%20may%20have%20a%20few%20questions%20and%20I%E2%80%99ll%20try%20to%20address%20those%20now.%3CSTRONG%3E%20To%20restate%20what%20I%20said%20above%2C%20unless%20you%20are%20using%20Windows%20Update%20for%20Business%2C%20the%20changes%20discussed%20below%20have%20no%20impact%20on%20when%20your%20devices%20get%20updated.%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CH4%20style%3D%22margin-top%3A%2036px%3B%20margin-bottom%3A%2020px%3B%20font-family%3A%20'Segoe%20UI'%2C%20Segoe%2C%20Tahoma%2C%20Geneva%2C%20sans-serif%3B%20font-weight%3A%20600%3B%20font-size%3A%2015px%3B%20color%3A%20%23333333%3B%22%20id%3D%22toc-hId-1308906658%22%20id%3D%22toc-hId--1243250303%22%3EWith%20the%20release%20of%20Windows%2010%2C%20version%201903%2C%20how%20will%20my%20Windows%20Update%20for%20Business%20configuration%20and%20execution%20reflect%20the%20removal%20of%20SAC-T%3F%3C%2FH4%3E%0A%3CP%20style%3D%22margin-top%3A%2020px%3B%22%3EFor%20releases%20prior%20to%20version%201903%2C%20Windows%20Update%20for%20Business%20customers%20had%20two%20settings%20they%20could%20utilize%20to%20designate%20when%20feature%20updates%20should%20be%20installed%20on%20their%20devices.%20The%20first%20was%20the%20branch%20readiness%20level%20(SAC%20or%20SAC-T)%2C%20and%20the%20second%20was%20the%20deferral%20period%2C%20which%20specified%20the%20number%20of%20days%20after%20the%20branch%20readiness%20level-based%20date%20before%20an%20update%20was%20offered%20to%20a%20device.%3C%2FP%3E%0A%3CP%20style%3D%22margin-top%3A%2020px%3B%22%3EOnce%20your%20organization%E2%80%99s%20devices%20have%20been%20updated%20to%20Windows%2010%2C%20version%201903%2C%20the%20configuration%20of%20Windows%20Update%20for%20Business%20will%20be%20simpler%2C%20enabling%20you%20to%20choose%20a%20single%20deferral%20value%20based%20solely%20on%20the%20SAC%20release%20date.%26nbsp%3BThat%20means%2C%20if%20you%20are%20trying%20to%20set%20up%20validation%20flights%20in%20your%20environment%20using%20Windows%20Update%20for%20Business%2C%20or%20stage%20updates%20in%20waves%2C%20you%20will%20do%20so%20from%20a%20common%20release%20start%20date%2C%20which%20should%20simplify%20the%20deployment%20process%20overall.%3C%2FP%3E%0A%3CP%20style%3D%22margin-top%3A%2020px%3B%22%3EI%20want%20to%20clarify%3B%20with%20these%20changes%2C%20%3CEM%3Ewe%20will%20not%20change%20your%20deferral%20value%3C%2FEM%3E.%20Instead%2C%20it%20will%20remain%20as%20it%20was%20configured%20following%20the%20update%20to%20version%201903.%20In%20addition%2C%20while%20all%20Windows%20Update%20for%20Business%20device%20deferrals%20will%20now%20be%20based%20on%20the%20release%20date%20(you%20will%20no%20longer%20have%20to%20configure%20this)%2C%20you%20will%20continue%20to%20have%20the%20option%20to%26nbsp%3Benroll%20devices%20in%20the%20Windows%20Insider%20Program%20and%20choose%20a%20pre-release%20ring%2C%20such%20as%20Slow%2C%20Fast%2C%20or%20Release%20Preview.%3C%2FP%3E%0A%3CP%20style%3D%22margin-top%3A%2020px%3B%22%3EThe%20image%20below%20shows%20the%20Settings%20panel%20as%20it%20looks%20today%20with%20Windows%2010%2C%20version%201809.%3C%2FP%3E%0A%3CP%20style%3D%22margin-top%3A%2020px%3B%22%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20400px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F75188i8A4F8365D47FFD14%2Fimage-size%2Fmedium%3Fv%3D1.0%26amp%3Bpx%3D400%22%20alt%3D%22wufb-branch-readiness-1809.png%22%20title%3D%22wufb-branch-readiness-1809.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%20style%3D%22margin-top%3A%2020px%3B%22%3EWhen%20version%201903%20is%20released%2C%20it%20will%20look%20like%20this%3A%3C%2FP%3E%0A%3CP%20style%3D%22margin-top%3A%2020px%3B%22%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20400px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F75189i3726B177745E012D%2Fimage-size%2Fmedium%3Fv%3D1.0%26amp%3Bpx%3D400%22%20alt%3D%22wufb-branch-readiness-1903.png%22%20title%3D%22wufb-branch-readiness-1903.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%20style%3D%22margin-top%3A%2020px%3B%22%3EAs%20you%20can%20see%2C%20it%20shows%20only%20pause%20and%20deferral%20settings%3B%20Semi-Annual%20Channel%20(Targeted)%20is%20no%20longer%20presented%20as%20an%20option.%20Again%2C%20this%20change%20will%20only%20be%20seen%20once%20you%20have%20deployed%20Windows%2010%2C%20version%201903%20and%20will%20only%20impact%20future%20feature%20updates%20after%20version%201903.%20Devices%20enrolled%20in%20the%20Windows%20Insider%20Program%3B%20however%2C%20can%20already%20see%20these%20changes.%3C%2FP%3E%0A%3CH4%20style%3D%22margin-top%3A%2036px%3B%20margin-bottom%3A%2020px%3B%20font-family%3A%20'Segoe%20UI'%2C%20Segoe%2C%20Tahoma%2C%20Geneva%2C%20sans-serif%3B%20font-weight%3A%20600%3B%20font-size%3A%2015px%3B%20color%3A%20%23333333%3B%22%20id%3D%22toc-hId--1243250303%22%20id%3D%22toc-hId-499560032%22%3EHow%20is%20Microsoft%20going%20to%20handle%20the%20transition%20to%20Windows%2010%2C%20version%201903%20for%20customers%20who%20have%20their%20branch%20readiness%20level%20configured%20for%20SAC%3F%3C%2FH4%3E%0A%3CP%20style%3D%22margin-top%3A%2020px%3B%22%3EAs%20I%20said%20above%2C%20with%20version%201903%2C%20we%20will%20cease%20to%20publish%20both%20SAC%20and%20SAC-T%20dates.%20Each%20release%20will%20have%20a%20single%20SAC%20release%20date%20so%20we%20will%20handle%20this%20one-time%20transition%20in%20the%20following%20manner%3A%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%20style%3D%22margin-bottom%3A%208px%3B%20margin-top%3A%2020px%3B%22%3EWindows%20Update%20for%20Business%20customers%20who%20have%20configured%20a%20deferral%26nbsp%3Bbased%20on%20the%20SAC-T%20branch-readiness%20level%20(remember%2C%20this%20really%20is%20the%20actual%20release%20date)%2C%20devices%20will%20be%20offered%20the%20update%20once%20the%20configured%20number%20of%20deferral%20days%20have%20passed.%20Thus%2C%20no%20change%20from%20previous%20releases.%3C%2FLI%3E%0A%3CLI%20style%3D%22margin-bottom%3A%208px%3B%22%3EFor%20devices%20that%20have%20been%20configured%20with%20a%20branch%20readiness%20of%20SAC%2C%20for%20the%20upgrade%20to%20version%201903%20only%2C%20we%20will%20add%20an%20additional%2060%20days%26nbsp%3Bto%20the%20configured%20deferral.%20This%20will%20simulate%20the%20delay%20previously%20experienced%20when%20Microsoft%20declared%20the%20SAC%20milestone.%20For%20example%2C%20if%20your%20device%20is%20currently%20configured%20to%20defer%20updates%2030%20days%20from%20the%20SAC%20release%20date%2C%20for%20the%20upgrade%20to%20version%201903%20(and%20this%20time%20only)%2C%20we%20would%20append%20a%2060-day%20delay%20to%20that%20configured%2030-day%20deferral%E2%80%93meaning%20that%20the%20device%20would%20be%20upgraded%2090%20days%20(60%2B30)%20after%20version%201903%20is%20released.%20(Note%20that%20the%20additional%2060%20days%20will%20be%20handled%20on%20our%20service%20side%2C%20and%20will%20not%20be%20reflected%20in%20your%20device%20configuration.)%3C%2FLI%3E%0A%3CLI%20style%3D%22margin-bottom%3A%208px%3B%22%3EFor%20subsequent%20feature%20updates%20after%20version%201903%2C%20your%20Windows%20Update%20for%20Business%20configuration%20deferral%20value%20will%20be%20whatever%20it%20was%20before%20version%201903%3B%20we%20are%20not%20modifying%20that%20value.%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%20style%3D%22margin-top%3A%2020px%3B%22%3EFor%20future%20upgrades%20beyond%20Windows%2010%2C%20version%201903%2C%20to%20establish%20an%20additional%20delay%20and%20recreate%20your%20deployments%20rings%20on%20the%20schedule%20you%20want%2C%20you%20will%20need%20to%20update%20your%20deferral%20value.%20Using%20the%20same%20example%20above%2C%20you%20would%20change%20the%20deferral%20value%20from%2030%20to%2090%20days.%20Or%2C%20if%20you%20want%20to%20create%20a%20three-ring%20deployment%20model%2C%20you%20could%20have%20three%20groups%20of%20devices%2C%20designated%20simply%20with%20deferral%20values%20from%20the%20single%20release%20date%2C%20perhaps%2030%2C%2060%2C%20and%2090%20days.%3C%2FP%3E%0A%3CP%20style%3D%22margin-top%3A%2020px%3B%22%3EIf%20you%E2%80%99re%20interested%20in%20learning%20more%2C%20or%20would%20like%20to%20see%20how%20you%20can%20use%20tools%20like%20Configuration%20Manager%2C%20WSUS%2C%20or%20Windows%20Update%20for%20Business%20to%20manage%20updates%2C%20see%20the%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows%2Fdeployment%2Fupdate%2Fwaas-quick-start%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%22%3EQuick%20guide%20to%20Windows%20as%20a%20service%3C%2FA%3E.%20To%20learn%20more%20about%20Windows%20as%20a%20service%2C%20check%20out%20the%20Windows%20as%20a%20service%20gateway%20on%20Docs.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-339523%22%20slang%3D%22en-US%22%3E%3CP%3ELearn%20how%20branch%20readiness%20level%20options%20will%20be%20simplified%20customers%20starting%20with%20Windows%2010%2C%20version%201903.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20400px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F75187i48B878B16F42072D%2Fimage-size%2Fmedium%3Fv%3D1.0%26amp%3Bpx%3D400%22%20alt%3D%22wufb-branch-readiness-1903.png%22%20title%3D%22wufb-branch-readiness-1903.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-TEASER%3E%3CLINGO-LABS%20id%3D%22lingo-labs-339523%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EServicing%20and%20updates%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Microsoft

Update 7/15/2019: As a reminder to customers on Windows 10, version 1809 using Windows Update for Business with a Branch Readiness Level set to Semi-Annual Channel and a default 0-day deferral, your 60-day one-time built-in deferral period will end on Tuesday, July 23, 2019 and your devices will begin updating to Windows 10, version 1903.

Update 2/28/2019: This change does not affect SAC-T for Office 365 ProPlus customers. See below for details.


In my post last May on Windows 10 and the “disappearing” SAC-T, I explained how we simplified and aligned our Windows servicing terminology with Office, reflecting that there are two Semi-Annual Channel (SAC) releases each year. I also explained that with Windows, there was never actually a Semi-Annual Channel (Targeted), or SAC-T, release; rather, SAC-T merely reflected a milestone for the semi-annual release. Unless you were using Windows Update for Business, the SAC and SAC-T designations had no impact on when your devices would be updated. At the time, we had not yet completed the work necessary to deliver the changes needed for Windows Update for Business to reflect the alignment with Office so we continued to show dates for both the SAC and SAC-T milestones on the Windows 10 release information page.

We have now completed that work. Beginning with Windows 10, version 1903 (the next feature update for Windows 10), the Windows 10 release information page will no longer list SAC-T information for version 1903 and future feature updates. Instead, you will find a single entry for each new SAC release. In addition, if you are using Windows Update for Business, you will see new UI and behavior to reflect that there is only one release date for each SAC release. If you use System Center Configuration Manager, Windows Server Update Services (WSUS), or other management tools, there will now only be one feature update published to WSUS, and this will occur at the time of release. (Note: This change does not impact the availability of SAC-T for Office 365 ProPlus. The SAC-T channel will continue to be an option for Office 365 ProPlus customers. For more information, see Overview of update for channels for Office 365.)

With this upcoming change, Windows Update for Business customers may have a few questions and I’ll try to address those now. To restate what I said above, unless you are using Windows Update for Business, the changes discussed below have no impact on when your devices get updated.

With the release of Windows 10, version 1903, how will my Windows Update for Business configuration and execution reflect the removal of SAC-T?

For releases prior to version 1903, Windows Update for Business customers had two settings they could utilize to designate when feature updates should be installed on their devices. The first was the branch readiness level (SAC or SAC-T), and the second was the deferral period, which specified the number of days after the branch readiness level-based date before an update was offered to a device.

Once your organization’s devices have been updated to Windows 10, version 1903, the configuration of Windows Update for Business will be simpler, enabling you to choose a single deferral value based solely on the SAC release date. That means, if you are trying to set up validation flights in your environment using Windows Update for Business, or stage updates in waves, you will do so from a common release start date, which should simplify the deployment process overall.

I want to clarify; with these changes, we will not change your deferral value. Instead, it will remain as it was configured following the update to version 1903. In addition, while all Windows Update for Business device deferrals will now be based on the release date (you will no longer have to configure this), you will continue to have the option to enroll devices in the Windows Insider Program and choose a pre-release ring, such as Slow, Fast, or Release Preview.

The image below shows the Settings panel as it looks today with Windows 10, version 1809.

wufb-branch-readiness-1809.png

When version 1903 is released, it will look like this:

wufb-branch-readiness-1903.png

As you can see, it shows only pause and deferral settings; Semi-Annual Channel (Targeted) is no longer presented as an option. Again, this change will only be seen once you have deployed Windows 10, version 1903 and will only impact future feature updates after version 1903. Devices enrolled in the Windows Insider Program; however, can already see these changes.

How is Microsoft going to handle the transition to Windows 10, version 1903 for customers who have their branch readiness level configured for SAC?

As I said above, with version 1903, we will cease to publish both SAC and SAC-T dates. Each release will have a single SAC release date so we will handle this one-time transition in the following manner:

  • Windows Update for Business customers who have configured a deferral based on the SAC-T branch-readiness level (remember, this really is the actual release date), devices will be offered the update once the configured number of deferral days have passed. Thus, no change from previous releases.
  • For devices that have been configured with a branch readiness of SAC, for the upgrade to version 1903 only, we will add an additional 60 days to the configured deferral. This will simulate the delay previously experienced when Microsoft declared the SAC milestone. For example, if your device is currently configured to defer updates 30 days from the SAC release date, for the upgrade to version 1903 (and this time only), we would append a 60-day delay to that configured 30-day deferral–meaning that the device would be upgraded 90 days (60+30) after version 1903 is released. (Note that the additional 60 days will be handled on our service side, and will not be reflected in your device configuration.)
  • For subsequent feature updates after version 1903, your Windows Update for Business configuration deferral value will be whatever it was before version 1903; we are not modifying that value.

For future upgrades beyond Windows 10, version 1903, to establish an additional delay and recreate your deployments rings on the schedule you want, you will need to update your deferral value. Using the same example above, you would change the deferral value from 30 to 90 days. Or, if you want to create a three-ring deployment model, you could have three groups of devices, designated simply with deferral values from the single release date, perhaps 30, 60, and 90 days.

If you’re interested in learning more, or would like to see how you can use tools like Configuration Manager, WSUS, or Windows Update for Business to manage updates, see the Quick guide to Windows as a service. To learn more about Windows as a service, check out the Windows as a service gateway on Docs.

60 Comments
Microsoft

Yes, it was hard to determine, thus the reason we made the changes to simplify that are the topic of the blog above. Now everything can be calculated off the one release date.

 

From your scenario descriptions, I believe your still on 1803, ( 1809 no longer has SAC-T as a branch option) , so you will not be updated to 1903, but to 1809.

 

For the "loads of SAC-T" devices still on 1803, please check the update status? Have they downloaded the update, but waiting for the user to initiate the update, or reboot the device? The device won't move forward until the reboot, which the user can control, unless you enforce that.

 

JW

New Contributor

@John Wilcox so are you saying if I have 1809 devices configured with SAC-T 0 day delay they won't get 1903 at all? Are you saying I have to force my device down to SAC to get 1903? I just forced down to SAC / 0 day delay for my test group, searched for updates, still no 1903, most likely because your adding a 60 day delay to SAC as a default.

 

The blog above says 

 

  • Windows Update for Business customers who have configured a deferral based on the SAC-T branch-readiness level (remember, this really is the actual release date), devices will be offered the update once the configured number of deferral days have passed. Thus, no change from previous releases.

So, should I not be receiving 1903 on SAC-T with 0 day delay right now?

Super Contributor

I saw 1903 in WSUS the day 1903 was announced (a few days ago).

New Contributor

@John Wilcox it may make sense to also communicate the availability of new feature updates can vary based on Microsoft's "limited release" and hardware support. I was using an Inspiron 9380 /w WUB 0 day delay, and still no 1903. Moved to a Surface Laptop 2, same WUB 0 day delay policies, and I got 1903 immediately. This can make things frustrating when calculating the servicing delay's, as we essentially are unable to control a proper initial release and testing based on the published dates if the updates are only made available to select hardware automatically.

Microsoft

Hi Chris,

 

Missing some details, so let me give you most likely things to look at.

1) Inspiron  , which branch readiness config did you have, SAC or SAC-T.  If SAC, then remember, we are adding +60 as a one time event, thus it will be 60 days

 

2) What did you configure for the Surface specifically, or did you mean its just default?

 

3) If a device is default, ( new device old device never changed, or has been restored) it is not the same as a deferral of "0". Instead, it is managed via the WU intelligent role out process, which is non-deterministic by device

 

4) If the device has a compat block, ie there is a known conflict not yet resolved, we will not update the device into the bad state, even at the deferral period.  You can see the known and tracked issues/compat blocks on the release history page

New Contributor

SAC-T 0 Day delay policy, Modern Desktop managed through Intune. Both devices were under the same management / policies SAC-T 0 day delay. I have quite a few not receiving it, Surface Laptop 2 received it immediately. I'll assume it's a blocking issue on the other devices that's going through resolution as we speak, thanks.

Occasional Visitor
If I'm on Windows 10 Enterprise 1803 and on SAC with 0 days deferred. When will I get 1809?
Occasional Visitor

@John Wilcox , currently the maximum deferral period for Feature Updates is 365 days. For Windows 10 Enterprise can this be extended to the full length of the supported lifespan, so two years?  While my organization hopes to get to an annual upgrade cadence, we're not there yet (still on 1703, moving to 1809 by the fall), and limiting us to only half the supported period forces us to block connection to Microsoft update servers and deploy updates via other channels.  Thank you!

New Contributor

Hello,

 

We have now 2x policies set via Intune Software Update Rings:

 

1st SAC with deferral = 120 days => targeted to company devices & excluding SAC-T devices;

2nd SAC-T with deferral = 7 days -> targeted to specific group with devices & excluding SAC devices;

 

Now devices in 2nd policy updated to 1903,

Do we need to change policy and create Intune Software Update Rings only for SAC, so we will have:

1st SAC with deferral = 60 days => targeted to company devices & excluding SAC-T devices; (changing here to 60 days, as deferral will have another 60 from service)

2nd SAC with deferral = 7 days -> targeted to specific group with devices & excluding SAC devices;

Or we can continue keep using SAC-T via Intune?

Occasional Visitor

GOOD RIDDANCE - the targeted version was the unstable one with sufficiently tested updates and features. After years of Targeted unstable retail updates screwing up millions of computers you finally accepted the fact that you cant rush feature without proper research and testing time - especially in business environment. From experience I also highly recommend a 7 day deferral of feature updates on top of that to avoid any last minute or post release screw ups and fixes.