Release it now, fix it later. That's how things seem to work now.
From: [email protected] [mailto:[email protected]] On Behalf Of Jerousek, Jeff Sent: Wednesday, February 10, 2016 12:45 PM To: [email protected] Subject: [mssms] RE: Removing Windows 10 Apps I agree, but all of Microsoft is undergoing a paradigm shift to an agile development process. It feels like some teams haven't quite switched over yet, like the ADK WinPE that hasn't been fixed for 4-5 months at a time. The Business Store, and Business Update teams. (Maybe they haven't been assembled yet.) While others are just throwing as much out there as they can without testing like the Universal Apps. Half of the documented settings for start the screen .xml either aren't implemented or have changed. The GPOs not even being able to control the new features at first. Running LTSB doesn't make sense either because it really isn't meant for everyday user devices. It's been very frustrating. We had the Threshold 1 OSD ready and then had to change practically everything when Threshold 2 was released. Thanks, Jeff Jerousek From: [email protected] <mailto:[email protected]> [mailto:[email protected]] On Behalf Of Marcum, John Sent: Wednesday, February 10, 2016 11:28 AM To: [email protected] <mailto:[email protected]> Subject: [mssms] RE: Removing Windows 10 Apps Right. They should just yank those consumer apps out of Win10 enterprise but allow them to be installed if someone wants them. (which nobody will) I don't even care if they leave the crap in Pro but it can't be in Enterprise. From: [email protected] <mailto:[email protected]> [mailto:[email protected]] On Behalf Of Schwan, Phil Sent: Wednesday, February 10, 2016 11:23 AM To: [email protected] <mailto:[email protected]> Subject: [mssms] RE: Removing Windows 10 Apps This definitely a logistical issue and a bit of a step backwards. OSD in the more distant past required a lot of chicken wire and duct tape (ie, scripts and specialized processes) to get everything looking the way you wanted for an enterprise deployment. The trend through the last several releases has been towards more control and easier customization through standardized tools and settings. However, with this new "WaaS" model we essentially have to do in-place upgrades on at least a semi-annual basis. I can understand to an extent not supporting the logistics of trying to incorporate a customized WIM file into the standard upgrade engine..but in lieu of having the changes Enterprises want baked into the core OS itself there should be better facilitation of a standardized "runtime" method for making the changes at deployment time. Whether that's through an unattend.xml-style customization method, or tighter integration of Provisioning Packages into the in place upgrade scenario.there has to be a better way than forcing the install of something we're just going to turn around and uninstall. "Do this, then undo it" makes no sense. Given the way things have progressed prior to Windows 10, the "just make the changes post-deployment" position runs completely counter to the entire enterprise systems management paradigm we've been given for the last decade plus. That's akin to saying with Windows 7 we should deploy the Win7 media directly from Microsoft and then use scripts and GPOs to make all of our changes post-deployment. It's horribly inefficient. -Phil _________________________________________________________________ Phil Schwan | Technical Architect, Enterprise Windows Services Microsoft VTSP ([email protected] <mailto:[email protected]> ) Project Leadership Associates | 2000 Town Center, Suite 1900, Southfield, MI 48075 Lync: 312.756.1626 Mobile: 419.262.5133 <http://www.projectleadership.net/> www.projectleadership.net <http://www.linkedin.com/in/philschwan> <https://twitter.com/philschwan> <http://myitforum.com/myitforumwp/author/philschwan> Lead with Strategy. Leverage Technology. Deliver Results. From: [email protected] <mailto:[email protected]> [mailto:[email protected]] On Behalf Of Marcum, John Sent: Wednesday, February 10, 2016 8:31 AM To: [email protected] <mailto:[email protected]> Subject: [mssms] RE: Removing Windows 10 Apps I'm curious how many people think it's acceptable to have to remove a bunch of junk from their OS's after each branch update? Maybe Rod could put up a poll? I for one find it unacceptable and for that reason I'm still think LTSB is the way to go. Why in the world would MS want us to load any of these on our corporate PC's? "Microsoft.BingFinance","Microsoft.BingNews","Microsoft.XboxApp","Microsoft. SkypeApp","Microsoft.MicrosoftSolitaireCollection","Microsoft.BingSports","M icrosoft.ZuneMusic","Microsoft.ZuneVideo","Microsoft.Windows.Photos","Micros oft.People","Microsoft.MicrosoftOfficeHub" "microsoft.windowscommunicationsapps","Microsoft.Getstarted","Microsoft.3DBu ilder","9E2F88E3.Twitter","king.com.CandyCrushSodaSaga", From: [email protected] <mailto:[email protected]> [mailto:[email protected]] On Behalf Of Aaron Czechowski Sent: Tuesday, February 9, 2016 11:08 PM To: [email protected] <mailto:[email protected]> Subject: [mssms] RE: Removing Windows 10 Apps >From https://technet.microsoft.com/en-us/library/mt627919.aspx First bullet: Upgrades the operating system on computers that currently run Windows 7, Windows 8, or Windows 8.1. You can also do build-to-build upgrades of Windows 10. For example, you can upgrade Windows 10 RTM to Windows 10, version 1511. :) From: [email protected] <mailto:[email protected]> [mailto:[email protected]] On Behalf Of Michael Niehaus Sent: Tuesday, February 9, 2016 4:00 PM To: [email protected] <mailto:[email protected]> Subject: [mssms] RE: Removing Windows 10 Apps You don't have to use servicing plans, you can continue to use task sequences with Windows 10 media. But the servicing plans have more features, so that's the preferred route. Thanks, -Michael From: [email protected] <mailto:[email protected]> [mailto:[email protected]] On Behalf Of John Aubrey Sent: Tuesday, February 9, 2016 5:57 AM To: [email protected] <mailto:[email protected]> Subject: [mssms] RE: Removing Windows 10 Apps I was under the impression this would work for Win 7 to Win 10 upgrades, but not the serving from 10 to 10. I thought you had to use the Windows 10 Servicing Plans. From: [email protected] <mailto:[email protected]> [mailto:[email protected]] On Behalf Of Jerousek, Jeff Sent: Tuesday, February 9, 2016 8:53 AM To: [email protected] <mailto:[email protected]> Subject: [mssms] RE: Removing Windows 10 Apps With an upgrade Task Sequence. https://blogs.technet.microsoft.com/configmgrteam/2015/06/16/revised-content -for-the-windows-10-in-place-upgrade-via-task-sequence-for-configuration-man ager/ <https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fblogs.tech net.microsoft.com%2fconfigmgrteam%2f2015%2f06%2f16%2frevised-content-for-the -windows-10-in-place-upgrade-via-task-sequence-for-configuration-manager%2f& data=01%7c01%7caaron.czechowski%40microsoft.com%7c8eac9fc663694f776d4a08d331 ad55b5%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=omZyExPKk97WELSoehYA45V7 NDnNsNqUAXNWjb4YvSs%3d> Thanks, Jeff Jerousek From: [email protected] <mailto:[email protected]> [mailto:[email protected]] On Behalf Of John Aubrey Sent: Tuesday, February 9, 2016 7:24 AM To: [email protected] <mailto:[email protected]> Subject: [mssms] RE: Removing Windows 10 Apps How do you run a custom task sequence to remove them after Windows 10 has been updated to the new release and make sure it runs before someone logs on? From: [email protected] <mailto:[email protected]> [mailto:[email protected]] On Behalf Of Jerousek, Jeff Sent: Monday, February 8, 2016 5:36 PM To: [email protected] <mailto:[email protected]> Subject: [mssms] RE: Removing Windows 10 Apps We use a Task Sequence to run the upgrade and we remove these: "'Microsoft.BingFinance','Microsoft.BingWeather', 'Microsoft.WindowsPhone', 'Microsoft.Getstarted', 'Microsoft.MicrosoftSolitaireCollection', 'Microsoft.Office.Sway', 'Microsoft.People', 'Microsoft.SkypeApp', 'microsoft.windowscommunicationsapps', 'Microsoft.WindowsPhone', 'Microsoft.XboxApp', 'Microsoft.BingSports', 'Microsoft.Appconnector', 'Microsoft.MicrosoftOfficeHub', 'Microsoft.3DBuilder', 'Microsoft.CommsPhone','Microsoft.Office.OneNote','Microsoft.ConnectivitySto re', 'Microsoft.Messaging'" If you remove them and set a custom start menu you will not see any shortcuts, some built in shortcuts to the apps will say the app is missing would you like to use a different program to run it, etc. Thanks, Jeff Jerousek From: [email protected] <mailto:[email protected]> [mailto:[email protected]] On Behalf Of John Aubrey Sent: Monday, February 8, 2016 2:53 PM To: [email protected] <mailto:[email protected]> Subject: [mssms] RE: Removing Windows 10 Apps Here is my list: "Microsoft.BingFinance","Microsoft.BingNews","Microsoft.XboxApp","Microsoft. SkypeApp","Microsoft.MicrosoftSolitaireCollection","Microsoft.BingSports","M icrosoft.ZuneMusic","Microsoft.ZuneVideo","Microsoft.Windows.Photos","Micros oft.People","Microsoft.MicrosoftOfficeHub","Microsoft.WindowsMaps","microsof t.windowscommunicationsapps","Microsoft.Getstarted","Microsoft.3DBuilder","9 E2F88E3.Twitter","king.com.CandyCrushSodaSaga","Microsoft.WindowsPhone", "Microsoft.Messaging","Microsoft.WindowsStore", "Microsoft.CommsPhone", "Microsoft.MicrosoftOfficeHub", "Microsoft.Office.Sway", "Microsoft.ConnectivityStore" I use the same script you have listed below. It works sometimes for the current logged on user, but pretty much perfect for people that first sign in after this is ran. When Windows 10 gets serviced up to the new build, all those apps come back. You can't use a task sequence to do the upgrade from what I have read. It would be nice to have an option to run a custom "clean up" script that removes and modifies the new Windows install after the upgrade but before people can log back on. There might be settings or hooks that need readded to Windows once it is upgraded. I haven't gotten to that point yet in my deployments. I know Cisco anyconnect has caused issues in the past with Windows 10 upgrades. Currently there isn't a way to have that uninstall before the OS upgrade starts and drop it back down on the PC once it's done. From: [email protected] <mailto:[email protected]> [mailto:[email protected]] On Behalf Of Merenda, Kenneth Sent: Monday, February 8, 2016 3:28 PM To: [email protected] <mailto:[email protected]> Subject: [mssms] Removing Windows 10 Apps In the past, my company has been very traditional on how software is installed, so with Windows 8.1 we disabled the store and removed almost every modern app. Culture is changing though, and now along with a move to Office 365, we're being challenged to deliver a more consumer-like experience, but still exclude things that would only serve as a distraction from business. That said, I was wondering which Windows 10 apps you all remove? I've included my list below, but I've found it isn't working well. Although the apps get removed, I still find start menu shortcuts for them, often with the icon missing. Here is what I run to get rid of the apps. I'd love to hear everyone's feedback, and any suggestions for improvement. # Define the apps to be removed $appsToRemove = "Microsoft.WindowsPhone","Microsoft.MicrosoftOfficeHub","Microsoft.People"," Microsoft.MicrosoftSolitaireCollection","Microsoft.BingFinance","Microsoft.B ingNews","Microsoft.BingSports","Microsoft.BingWeather","Microsoft.SkypeApp" ,"microsoft.windowscommunicationsapps","Microsoft.XboxApp","Microsoft.ZuneMu sic","Microsoft.ZuneVideo" # Loop through the app list and remove each app foreach ($app in $appsToRemove) { # Uninstall app for the current user Get-AppxPackage | Where-Object -Property "Name" -eq $app | Remove-AppxPackage # Remove app from the OS Get-AppxProvisionedPackage -Online | Where-Object -Property "DisplayName" -EQ $app | Remove-AppxProvisionedPackage -Online } ------ Kenneth Merenda _____ 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.
