[prev in list] [next in list] [prev in thread] [next in thread] 

List:       patchmanagement
Subject:    RE: [patchmanagement] Rollback Plan
From:       "Job Cacka" <job () ccbox ! com>
Date:       2019-02-20 16:26:44
Message-ID: 00a601d4c939$11d6ddc0$35849940$ () ccbox ! com
[Download RAW message or body]

"And of course... waiting."

This is probably the single most valuable piece of advice for any organization that \
cannot handle the feedback requirements that Win 10 imposes. Just wait until Woody \
says, "it is ok to patch"

Job

-----Original Message-----
From: Susan E Bradley [mailto:sb@askwoody.com] 
Sent: Tuesday, February 19, 2019 5:22 PM
To: Patch Management Mailing List
Subject: Re: [patchmanagement] Rollback Plan

Ultimate control freak/small firm:  client workstation backup to roll it 
back to a point in time

Larger firm:  Autopilot/standard desktops/roll out a new image when 
there are issues.

And of course... waiting.  Many a patch problem never hits your desktops 
if you don't install on day one and instead wait at least a week.


On 2/19/2019 4:31 PM, Job Cacka wrote:
> Yes, and it works best if you have people that will use the updated OS daily, \
> tinker with the OS and its settings and then report any problems or changes. \
> Without that in-depth feedback you will always be reacting to the problems as they \
> arise in your organization. 
> Win 10 KB documentation is atrocious and cannot be relied upon. The update failure \
> rate over the last couple of years is high. If 1809 is any indication of future \
> results then only detailed testing can ensure a seamless transition. 
> Good design would dictate the OS gets out of the way and allows the user to run the \
> software that is needed to do their job. Often updates and upgrades get in the way \
> of day-to-day work, or they make changes that assume a usage that doesn't exist, or \
> they create insurmountable challenges that require administrator intervention. 
> Job
> 
> -----Original Message-----
> From: Mark Browning [mailto:MSBrowning@winstonind.com]
> Sent: Tuesday, February 19, 2019 12:17 PM
> To: Patch Management Mailing List
> Subject: [patchmanagement] Rollback Plan
> 
> We're trying to finally implement a good update schedule, but right now we're still \
> looking for a good rollback strategy. Unfortunately we do not have a real dev/test \
> environment. Has anyone faced the same problems? 
> Mark Browning, Senior Support Analyst
> Winston Industries, LLC | 502.495.5454 | msbrowning@winstonind.com
> 
> 
> 
> ---
> PatchManagement.org is hosted by Shavlik
> 
> The content on the email list is intended for assisting administrators.  If you \
> would like to use any of this content in a blog or media publication, please \
> contact the owners of the list for approval. 
> To unsubscribe send a blank email to leave-patchmanagement@patchmanagement.org
> If you are unable to unsubscribe via this email address, please email
> owner-patchmanagement@patchmanagement.org
> 



---
PatchManagement.org is hosted by Shavlik

The content on the email list is intended for assisting administrators.  If you would \
like to use any of this content in a blog or media publication, please contact the \
owners of the list for approval.

To unsubscribe send a blank email to leave-patchmanagement@patchmanagement.org
If you are unable to unsubscribe via this email address, please email
owner-patchmanagement@patchmanagement.org


---
PatchManagement.org is hosted by Shavlik

The content on the email list is intended for assisting administrators.  If you would \
like to use any of this content in a blog or media publication, please contact the \
owners of the list for approval.

To unsubscribe send a blank email to leave-patchmanagement@patchmanagement.org
If you are unable to unsubscribe via this email address, please email
owner-patchmanagement@patchmanagement.org


[prev in list] [next in list] [prev in thread] [next in thread]