Why is kb3000850 not marked as an Update Rollup

-

i've discovered update rollup windows 8.1 , server 2012r2. it's kb3000850 released last november. reason missed because wsus lists update, not update rollup. have update view 8.1 set security, critical , update rollups, not general updates.

why not listed rollup? if had shown @ correct time have included in tablet rollout. might swamp wireless connections of tablets such huge update, i'm reluctant it.

i've discovered update rollup windows 8.1 , server 2012r2. it's kb3000850 released last november. reason missed because wsus lists update, not update rollup. have update view 8.1 set security, critical , update rollups, not general updates.

why not listed rollup? if had shown @ correct time have included in tablet rollout. might swamp wireless connections of tablets such huge update, i'm reluctant it.


i took quick @ "monthly" 8.1 "updates", , other november 2014 release, seem "critical" , not "rollup" @ all. @ guess, you've been seeing these in view, not because have selected "update rollup", because have selected "critical".

so, in way, going happen @ time, because there's no guarantee there going "critical" aspect update classification.

msft rather vague/ambiguous use of term "rollup" , "cumulative" across different products (e.g. windows vs. office).

[and vivian's reply regarding "service pack updating new features", that's weird - sps windows don't that, excepting xpsp2, extra-special case..]

don
(please take moment "vote helpful" and/or "mark answer", applicable.
helps community, keeps forums tidy, , recognises useful contributions. thanks!)



Windows Server  >  WSUS



Comments

Post a Comment

Popular posts from this blog

WIMMount (HSM) causing cluster storage to go redirected (2012r2 DC)

-
looking options resolve error , prevent in future. thanks help. hardware: 2 node dell hv cluster running2012r2 dc 8 nic/ea in multiplex mode 4x hyper-v 4x hosts storage: 2x synology nas, accessed through iscsi hosts , cluster relevant logs: log name:      microsoft-windows-failoverclustering/diagnostic source:        microsoft-windows-failoverclustering date:          event id:      2050 task category: none level:         warning keywords:       user:          system computer:      l description: [dcm] filter wimmount found @ unsafe altitude 180700 log name:      system source:        microsoft-windows-failoverclustering date:         event id:      5125 task category: cluster shared volume level:         warning keywords:       user:          system computer: description: cluster shared volume 'volume1' ('cluster disk 1') has identified 1 or more active filter drivers on device stack interfere csv operatio
Read more

Failed to delete the test record dcdiag-test-record in zone test.com

-
ps c:\users\administrator.test> dcdiag /test:dns directory server diagnosis performing initial setup:    trying find home server...    home server = dc02    * identified ad forest.    done gathering initial info. doing initial required tests    testing server: default-first-site-name\dc02       starting test: connectivity          ......................... dc02 passed test connectivity doing primary tests    testing server: default-first-site-name\dc02       starting test: dns          dns tests running , not hung. please wait few minutes...          ......................... dc02 passed test dns    running partition tests on : forestdnszones    running partition tests on : domaindnszones    running partition tests on : schema    running partition tests on : configuration    running partition tests on : test    running enterprise tests on : test.com       starting test: dns          test results domain
Read more

Azure MFA with Azure AD and RDS

-
i have setup following lab in azure , need help. a server (domain controller) , remote desktop services. and server multi factor authentication server. i have setup following one http://www.rdsgurus.com/uncategorized/step-by-step-using-windows-server-2012-r2-rd-gateway-with-azure-multifactor-authentication/ and when im connecting got following error. the user "domain\username", on client computer "xxx.xxx.xxx.xxx", did not meet connection authorization policy requirements , therefore not authorized access rd gateway server. authentication method used was: "ntlm" , connection protocol used: "rpc-http". following error occurred: "23003". also on security log i've got following authentication details: connection request policy name: ts gateway authorization policy network policy name: - authentication provider: radius proxy authentication server: test.test.local authentication type: - eap t
Read more