Correct. But, the latest update is actually an msu and available in the WSUS 
catalog which is a bit different than previous WUA updates so it can be 
delivered via the normal update process.

J

From: [email protected] [mailto:[email protected]] On 
Behalf Of Marcum, John
Sent: Thursday, June 4, 2015 12:11 PM
To: [email protected]
Subject: RE: [mssms] Windows update KB 
https://support.microsoft.com/en-us/kb/3050265

But it ONLY updates itself from WSUS if you have windows updates enabled on the 
machines which we know will cause unexpected reboots so there’s a big catch 22 
there.




From: [email protected]<mailto:[email protected]> 
[mailto:[email protected]] On Behalf Of Jason Sandys
Sent: Thursday, June 4, 2015 11:45 AM
To: [email protected]<mailto:[email protected]>
Subject: RE: [mssms] Windows update KB 
https://support.microsoft.com/en-us/kb/3050265

The WUA was explicitly designed to update itself from WSUS or Windows Update 
though and has done so successfully on every Windows installation since Windows 
2000 SP4 that communicates with WSUS or Windows Update. If this were an issue, 
the Windows Update ecosystem would have had issues long, long ago.

J

From: [email protected]<mailto:[email protected]> 
[mailto:[email protected]] On Behalf Of Daniel Ratliff
Sent: Thursday, June 4, 2015 4:05 AM
To: '[email protected]'; '[email protected]'
Subject: RE: [mssms] Windows update KB 
https://support.microsoft.com/en-us/kb/3050265

I'm betting he's referring to the fact that you are updating the WUA using the. 
..WUA. I would agree that's not great, except that this update doesn't install 
until you reboot, so it should be fine in my opinion.

Kind of like updating the Configmgr client with ConfigMgr, depending on how you 
do it out may not work well.

-----Original Message-----
From: Freddy Grande 
[[email protected]<mailto:[email protected]>]
Sent: Thursday, June 04, 2015 12:09 AM Eastern Standard Time
To: [email protected]<mailto:[email protected]>
Subject: RE: [mssms] Windows update KB 
https://support.microsoft.com/en-us/kb/3050265
I feel like you’re leaving us hanging.
Why shouldn’t this update be deployed through WSUS?

Freddy

From: [email protected]<mailto:[email protected]> 
[mailto:[email protected]] On Behalf Of Jason Wallace
Sent: Wednesday, 3 June 2015 10:08 PM
To: [email protected]<mailto:[email protected]>
Subject: RE: [mssms] Windows update KB 
https://support.microsoft.com/en-us/kb/3050265

Yes

This is marked as an optional update but really should be higher.

Also while it can be deployed via WSUS there are reasons why it should be 
deployed via software distribution

From:[email protected]<mailto:[email protected]> 
[mailto:[email protected]] On Behalf Of Roland Janus
Sent: 03 June 2015 13:03
To: [email protected]<mailto:[email protected]>
Subject: [mssms] Windows update KB 
https://support.microsoft.com/en-us/kb/3050265

That looks like finally some help on the memory issue with the wsus agent

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

-R





The information transmitted is intended only for the person or entity to which 
it is addressed
and may contain CONFIDENTIAL material. If you receive this material/information 
in error,
please contact the sender and delete or destroy the material/information.


________________________________

Confidentiality Notice: This e-mail is from a law firm and may be protected by 
the attorney-client or work product privileges. If you have received this 
message in error, please notify the sender by replying to this e-mail and then 
delete it from your computer.


Reply via email to