KB2919355 not required on some systems, difficult to deploy


ok 8.1/2012 r2 update (kb2919355) is kinda driving me crazy. 

here's example, 4 identical 2012 r2 servers, have same updates installed including prereqs kb2919442, 2 of them see need need run 2919355, 2 of them not.  includes through wsus/sccm , windows update.

another scenario, 10 identical windows 8.1 computers, have same updates prereqs , should ready 8.1 update, same thing happens, of them want run update, of them not.  few days goes by, no changes made on ones where 2919355 not required or not availbe, of sudden out of blue 1 or 2 of them decide, "hey i'm ready run 2919355 now!" install update sccm/wsus.  , keep in mind, isn't problem sccm/wsus infrastructure, on systems displaying these symptoms if go out windows updates update still isn't published affected systems, until of sudden have available randomly. 

i know can install manually, (http://www.microsoft.com/en-us/download/details.aspx?id=42334 ) but that's not big of when have many systems update , expect able use wsus infrastructure out there.  plus if have system can't wait on, , need install update on now, install manually you're staring @ like 6 updates install in specific order, pain, , you're asking yourself, "if able install via windows update, picking 6 of these , installing them in proper order itself?"  "do need reboot after every 1 of these, 6 reboots on production server!?". 

i hope isn't future of windows updates, if had several hundred/thousand 8.1 clients out there right , had rush deploy update a intesive task that wasn't necessary in past.  please tell me microsoft making easier system admins keep flagship products date in future.  it's hard me justify management need stay @ latest os when crazy stuff happens , used easy in past, time consuming project.

thanks!

i dont strange in case small updates have fast download on client pc-s and on night installed on of clients.

some of clients are self-rebooted but some of them waiting reboot, etc

kb2919355 huge windows update , nead time download because have runing bits service on wsus server , replica servers. this is perhaps logical explanation.

also servers may have same system and everything else when is the last time some of them reset, how many people are logged on of them, what their function on infrastructure?

this me some of issues that affect time updates download , installations on server , client pc-s.

sorry english.

 





Windows Server  >  WSUS



Comments

Popular posts from this blog

CRL Revocation always failed

Failed to query the results of bpa xpath

0x300000d errors in Microsoft Remote Desktop client