I love patches. :)
--
There are 10 kinds of people in the world...
those who understand binary and those who don't.
-----Original Message-----
From: [email protected] [mailto:[email protected]] On
Behalf Of Susan Bradley
Sent: Monday, November 16, 2015 1:46 PM
To: [email protected]
Subject: Re: [NTSysADM] RE: Outlook patch issue?
Revision 100 was the first release - the faulty one.
Don't ask me what 201/202 are - just know that 200 is the one you want.
On 11/16/2015 10:38 AM, Melvin Backus wrote:
> Based on the revision numbers that would not appear to be the case. Revision
> 200 is the active one and revision 201 / 202 are declined. Since the
> declined instance has 2 different revisions and the associated dates, what's
> the best way to determine what version of the patch is actually being
> deployed?
>
> --
> There are 10 kinds of people in the world...
> those who understand binary and those who don't.
>
>
> -----Original Message-----
> From: [email protected]
> [mailto:[email protected]] On Behalf Of Susan Bradley
> Sent: Monday, November 16, 2015 12:44 PM
> To: [email protected]
> Subject: Re: [NTSysADM] RE: Outlook patch issue?
>
> WSUS has already declined the expired updates. When the new update comes in,
> it expires the older one automatically.
>
>
>
> On 11/16/2015 9:04 AM, Melvin Backus wrote:
>> I'm seeing multiple instances of this patch now in WSUS. When I
>> check the revision status there is currently a revision 200, which
>> got approved and installed. There is also a 2^nd with revisions 201
>> and
>> 202 which is flagged as declined. Since we do security updates as
>> auto approved, what would flag those for declined?
>>
>> All that said, I'm seeing the best process for actually applying the
>> updated version of the patch as to flag the original for removal,
>> then approve the newer one. Am I missing anything there?
>>
>> --
>> There are 10 kinds of people in the world...
>> those who understand binary and those who don't.
>>
>> *From:* [email protected]
>> [mailto:[email protected]] *On Behalf Of *Kennedy, Jim
>> *Sent:* Friday, November 13, 2015 9:29 AM
>> *To:* [email protected]
>> *Subject:* [NTSysADM] RE: Outlook patch issue?
>>
>> 3097877 is the problem child this month. It was killing Outlook and
>> was revised Thursday morning. Not killing outlook anymore but still
>> killing touchscreens on Win 7.
>>
>> *From:*[email protected]
>> <mailto:[email protected]>
>> [mailto:[email protected]] *On Behalf Of *Melvin Backus
>> *Sent:* Friday, November 13, 2015 9:22 AM
>> *To:* [email protected]
>> <mailto:[email protected]>
>> *Subject:* [NTSysADM] Outlook patch issue?
>>
>> Anyone seeing any issues with KB3101535 for Outlook?
>>
>> We've seen some folks suddenly start having issues with Outlook not
>> starting up and removing that patch seems to be the solution to the
>> issue. Still investigating, but I figured here was a good place to
>> pose the question.
>>
>> Thanks
>>
>> --------------------
>> Melvin Backus | Sr. Systems Engineer | Byers Engineering Company |
>> 404.497.1565
>>
>> Service Desk | 404-497-1599 | http://servicedesk.byers.com
>>
>> --
>> There are 10 kinds of people in the world...
>> those who understand binary and those who don't.
>>
>
>
>
>
>
