Running WSUS 3.2.7600.274 and Windows 10 clients

-

we're running wsus 3.2.7600.274/server 2008r2. number of client pcs in enterprise running windows 10 has increased small group of 8 pcs, though majority still running windows 7 pro. i've been holding out upgrading our wsus server until server 2016 questioning if it's best server 2012r2/wsus 4 sooner rather later anniversary update in pipeline. 

if upgrade wsus 3 4 , allow upgrades push out clients cause our win7 machines upgraded win10? make sense upgrade wsus 3 4 , not push out upgrades? not have upgrades checked in classification list. if advise benefits/pitfalls of upgrading wsus 3 4 in environment increasing number of win10 clients appreciate it.

thanks 

hank vare

hi techrep,

>just clarify, wsus 3/server 2008r2 still push security updates out win10 clients? 

just few.

i quote statement technet blog below:

"our story how support new servicing model in existing tools continue improve in subsequent releases through additional features support key scenarios.  during time, wsus 3.0 sp2 remain in old servicing model.  technically, can provide minimal windows 10 update support (i.e., sync , distribute security updates), experience less ideal."\

detailed information:

https://blogs.technet.microsoft.com/wsus/2016/01/22/for-those-on-wsus-3-0-sp2-or-sbs-2011/

and statement in kb3159706(which needs installed on wsus 4.0)

"you must install update on wsus server intended sync , distribute windows 10 upgrades (and feature updates) released after may 1, 2016."

detailed information:

https://support.microsoft.com/en-us/kb/3159706

so, it's better upgrade wsus 4.0 , install kb3095113 , kb3159706(with manual steps) in order newest updates , support win10.

best regards,

anne

please remember mark replies answers if , unmark them if provide no help. if have feedback technet support, contact tnmff@microsoft.com.



Windows Server  >  WSUS



Comments

Post a Comment

Popular posts from this blog

DCOM received error "2147746132" from...

-
hi everybody, i have dc (my windows essentials 2012 server) , windows 2012 server in network.  the windows server 2012 inside domain. on server, got "non stopping" error says in event logs : ===> dcom received error "2147746132" fromd computer xxxx(my dc computer) while server trying activation : {6df8cb71-153b-4c66-8fc4-e59301b8011b} it never stops, got 11000+ new events :s i found : http://support.microsoft.com/kb/971153/fr i'm not sure should ? does got idea ? matthieu. hi, please try solution mentioned in below link: http://www.eventid.net/display-eventid-10006-source-dcom-eventno-272-phase-1.htm regards, cicely Windows Server  >  Windows Server 2012 General ...
Read more

DFSR RPC replication errors 5014 1726 with large files over VPN

-
i have similar issue ryan in reply http://social.technet.microsoft.com/forums/en-gb/winserverfiles/thread/6d49fd71-2236-4fcb-9763-bf1c03459ee8 cited below. start additional thread here because other 1 related windows server 2003 (r2) , i'm (as ryan) on windows 2008 r2 x64. here first of post ryan: i've got same problem on 2008 r2 dfsr server.  the spoke server has 2x intel 1 gigb on-board nics in active/standby teamed configuration. the hub server (running on vmware using 10gbit vmnet3 nic driver) logs dfsr event 5014 every 2-15mins (usually around 5mins). the spoke server not log event. replication running slowly. initial sync/replication. had re-configure replication folder because of lost dfsr database on spoke server.  could teamed nic on spoke causing error on host? a note: last time did initial sync on folder processed @ 30k files , hour. time it's doing few hundred and hour. another note: hub server has several replication groups , conne...
Read more

ADFS 3.0 Event ID 4625 | An Error occurred During Logon | Status: 0xC000035B

-
we're getting these random errors on our adfs security logs, how can track down generating them? an account failed log on. subject: security id: null sid account name: - account domain: - logon id: 0x0 logon type: 3 account logon failed: security id: null sid account name: account domain: failure information: failure reason: an error occured during logon. status: 0xc000035b sub status: 0x0 process information: caller process id: 0x0 caller process name: - network information: workstation name: - source network address: - source port: - detailed authentication information: logon process: kerberos authentication package: kerberos transited services: - package name (ntlm only): - key length: 0 event generated when logon request fails. generated on computer access attempted. subject fields indicate account on local system requested logon. commonly service such server service, or local process such ...
Read more