Windows 1703 pro and Windows Update for Business

Superfly said:

Yup.. if offered why not? ...

MS may have changed the forced updates that's all.. the "for Business" may change to something else for non-Business users.

Thanks Superfly for your help,

i'll wait a bit before marking as solved, you seems to be taking a guess more than
actually knoing for sure if my license is actually entitled to use such feature;
forgive my skepticism but there are so many windows 10 versions/updates that
i'm honestly very confused.

If there is someone else that knows how the "Current Branch for Business"
entitlement/availability works i kindly ask to step in or provide a microsoft
doc/link to verify.

Thanks again, Roy.

The choice between CB and CBB offered in Creators Update for Pro was available in previous versions too, it's just that Microsoft didn't make it clear what was going on. It was called 'Defer feature updates' in 1607, but it had exactly the same effect, it switched you to the CBB so that feature updates (ie. an upgrade to the next version) would be deferred unit that version was on CBB. Now they explicitly spell out how 'defer feature updates' works, that's all.

Microsoft said:

When Microsoft officially releases a feature update for Windows 10, it is made available to any PC not configured to defer feature updates so that those devices can immediately install it.

Overview of Windows as a service

Oh, and we'll all have to learn some new names shortly...

Going forward, these are the new terms we will be using:+

• Semi-Annual Channel - We will be referreing to Current Branch (CB) as "Semi-Annual Channel (Targeted)", while Current Branch for Business (CBB) will simply be referred to as "Semi-Annual Channel".
• Long-Term Servicing Channel - The Long-Term Servicing Branch (LTSB) will be referred to as Long-Term Servicing Channel (LTSC).

https://docs.microsoft.com/en-us/win...naming-changes

roy111 said:

If there is someone else that knows how the "Current Branch for Business"
entitlement/availability works i kindly ask to step in or provide a microsoft
doc/link to verify..

As far as I can figure CBB doesn't exist - they have renamed it yet again.

This quote is from MS dated 2017-7-27 so who know what everything will be called next month but hopefully it may help some.

Semi-Annual Channel - We will be referreing to Current Branch (CB) as "Semi-Annual Channel (Targeted)", while Current Branch for Business (CBB) will simply be referred to as "Semi-Annual Channel".
Long-Term Servicing Channel - The Long-Term Servicing Branch (LTSB) will be referred to as Long-Term Servicing Channel (LTSC).

Overview of Windows as a service (Windows 10) | Microsoft Docs

lx07 said:

As far as I can figure CBB doesn't exist - they have renamed it yet again.

Quite right, I was updating my post while you posted that :)

Thanks Bree, is 1703 in CBB already?

in the meantime i readed again this Microsoft page about update policy:

Configure Windows Update for Business (Windows 10) | Microsoft Docs



i'll try to test a new system as above

roy111 said:

Thanks Bree, is 1703 in CBB already?

Previously MS have announced when a version is made CBB, but that too seems to have change with the 'renaming'. I would assume that versions will automatically move from "Semi-Annual Channel (Targeted)" to "Semi-Annual Channel" as each next version is about to be released. With 1709 just around the corner that would certain seem to be the case for 1703, judging by the number of recent threads on these boards complaining about a forced upgrade from 1607 to 1703 despite having 'defer feature updates' turned on.

Bree said:

...
With 1709 just around the corner that would certain seem to be the case for 1703, judging by the number of recent threads on these boards complaining about a forced upgrade from 1607 to 1703 despite having 'defer feature updates' turned on.

Yest things are starting to make sense, this can indeed have been the cause of the update to 1703 i experienced,
maybe because i did not set any GPolicy key to increase the defer period

DeferFeatureUpdatesPeriodinDays=180

if what the document i linked is correct (i read 2017-7-27)

i assume my system will not be upgraded to 1703 for 180 days
let say 1703 hit the Long-Term Servicing Channel (CBB) 1st of july
system should stay put to 1607 180 days from 1st july so roughly till dec 2017.

Superfly said:

Well.. skepticism forgiven... but uhmm, told you so (and I didn't even Google...LOL)

yes, but your expression in your avatar isn't too reassuring :)