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

List:       patchmanagement
Subject:    RE: [patchmanagement] Windows 10 1607: Keeping apps from coming back when deploying the feature upda
From:       "Job Cacka" <job () ccbox ! com>
Date:       2016-08-26 18:36:57
Message-ID: 08a901d1ffc8$d32b7e00$79827a00$ () ccbox ! com
[Download RAW message or body]

" To be honest, this is one of the main things holding us back from even rolling out \
a pilot group." +1

From the article:
"We're aware that's less than desirable, since you removed those apps for a reason, \
and we're working on solving this particular issue in a future feature update."

And once that update has been proven (n+1) we will consider that issue remediated. \
Re-configuring an OS every 4-6 months is impossible in our organization not less than \
desirable. 


" Also remember that some apps aren't in-box but are instead installed from the \
Windows Store when a user signs on for the first time."

This is a marketing/initial configuration mistake on MS part. "On by default", and \
"auto-download without owner permission" still fails security tests after all these \
years.

" ..., and keep in mind that some of the policies related to this aren't supported in \
Windows 10 Pro version 1607 and later"

Whenever I read about this, I wonder how long it will take to see a lawsuit about \
these "bait-and-switch" tactics. 

Job



-----Original Message-----
From: Matthew Houston [mailto:Matthew.Houston@camden.nsw.gov.au] 
Sent: Tuesday, August 23, 2016 4:43 PM
To: Patch Management Mailing List
Subject: RE: [patchmanagement] Windows 10 1607: Keeping apps from coming back when \
deploying the feature update

To be honest, this is one of the main things holding us back from even rolling out a \
pilot group.

I installed two workstations in IT with Windows 10, spent the time crafting all the \
GPO's, removing all the garbage during the SCCM tasksequence etc.

But I'll never use the servicing model until all of this garbage gets sorted out. I \
don't have the time to go through an entire 'OS level' testing procedure every time a \
new CB or CBB is released. Nor do I have time to create dozens of configuration items \
to check if these garbage items have been reinstalled and remove them. I just don't.

The alternative is a full rebuild (which is not completely off the table) but that \
brings its own problems along with it.

Until they can get to the point of having a consistent OS experience through the \
servicing process it's on the shelf for us.

Matthew Houston
Information Systems Support Specialist 

-----Original Message-----
From: Susan Bradley [mailto:sbradcpa@pacbell.net]
Sent: Wednesday, 24 August 2016 5:38 AM
To: Patch Management Mailing List
Subject: [patchmanagement] Windows 10 1607: Keeping apps from coming back when \
deploying the feature update

Windows 10 1607: Keeping apps from coming back when deploying the feature update – \
Michael Niehaus' Windows and Office deployment ramblings: \
https://blogs.technet.microsoft.com/mniehaus/2016/08/23/windows-10-1607-keeping-apps-from-coming-back-when-deploying-the-feature-update/



So how many of you are using wsus to deploy 1607 versus how many are looking at more \
of a deployment-ish method to roll out 1607?

[my personal opinion that "We're getting your desktop ready" isn't what I consider \
appropriate for WSUS installs.  This is feeling more like CBB's need to be handled \
more like deployments and less like updates.

As always thank you greatly to Michael Neihaus for having solutions and workarounds \
for our needs.


---
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]