All “ms-settings” commands for Windows 10 v1709

Ok ok, Windows 10 v1803 is out for some time, but lots of enterprises still use v1709 or at least are on the deployment phase with this version.

One of the most awkward thing I’ve found on GPOs for Windows 10 it’s the way to hide or disable Windows Settings icons, like I’ve explained on a previous post (FrontSlash Blog - Win10 - GPOs - Hiding pages in Settings app)

But…well…not much to do here.

Because Microsoft implements new features twice a year, also with these new features the Settings app get new icons.
To save you the trouble to search all of them, here’s a nice post from Winaero with ALL the “ms-settings” you can use in your GPO:
Winaero - ms-settings Commans in Windows 10 Fall Creators Update

Win10 – What’s new for IT Pros in Windows 10 v1709 (Fall Creators Update)

Here’s a nice video from Microsoft about the new features of Windows 10 v1709 (Fall Creators Update) with focus on things that IT Pros need to know:

What's New in Windows 10, version 1709 for IT Pros

GPOs – Administrative Templates for Windows 10 v1709 (Fall Creators Update) Release

Well…this week of course is completely full of Windows 10 v1709 (Fall Creators Update) downloads!

So here are the new group policy administrative templates (.admx) for the new Windows 10 release:
Microsoft - Administrative Templates (.admx) for Windows 10 Fall Creators Update (1709)

Win10 Deploy – v1709 (Fall Creators Update) – You’ll Need to Change Your “RemoveApps” Script!

This new paradigm of Windows as a Service (Waas) really makes SysAdmins to change the way they work and also adapt really really quick.

Following the release of Windows 10 v1709 (Fall Creators Update), and if like me you use a Powershell script to remove provisioned apps during image deployment or golden image creation, you’ll notice…a lot of broken things on you script.

This happens because of changes on the apps version…so…or you create a more complex script that just looks for the beginning of the application string or you adapt your script to this new release.

So…you try to install you golden image with Microsoft Deployment Toolkit (MDT) and you get the following error when finishing:

Now…don’t close this Window right yet. Instead, follow this steps:

1. Open a Powershell prompt
2. Execute the following command: Get-AppxPackage –Online > C:\Apps.txt
3. This will create a file called Apps.txt on you C: drive with all the installed/provisioned apps. It will be something similar to this:
   
4. Now you just need to copy/paste the updated “PackageName” to your script and everything works fine again.

Just a quick note to remember that for example Microsoft 3DBuilder app was removed from Windows 10 v1709 so you may completely remove that line from your script.

Remote Server Administration Tools for Windows 10 v1709 (Fall Creators Update) Released

And again…following the wave of releases for Windows 10 v1709 (Fall Creators Update), Microsoft launched a new Remote Server Administration Tools (RSAT).

Just be aware of this additional information in the download website about some issues you may encounter with this version:

Go ahead and download the new RSAT here:
Microsoft - Remote Server Administration Tools for Windows 10

GPOs Settings Reference Spreadsheet Updates for Windows 10 v1709 (Fall Creators Update)

Following Windows 10 v1709 (Fall Creators Update) release, Microsoft updated their reference documents of Group Policy Settings.

These spreadsheets list the policy settings for computer and user configurations that are included in the Administrative template files delivered with the Windows operating systems specified. You can configure these policy settings when you edit Group Policy Objects.

Go ahead and download it here:
Microsoft Group Policy Settings Reference for Windows and Windows Server

Windows 10 v1709 (Fall Creators Update) - Features that are removed or deprecated in Windows 10 Fall Creators Update

Like any other major release, or like it’s called nowadays, feature update, of Windows 10 there are some features that get removed or deprecated.

For Windows 10 v1709 (Fall Creators Update) here’s the list of features that changed:
Microsoft Support - Features that are removed or deprecated in Windows 10 Fall Creators Update

Windows 10 1709 (Fall Creators Update) Changes to Media (ISO) on VLSC – ATTENTION!!

Microsoft Windows 10 1709 (a.k.a. Fall Creators Update a.k.a. FCU) was launched today.

Like on my previous post, you can download the installation media (ISO) from the usual relevant distribution channels: the Volume Licensing Service Center (VLSC), Windows Update for Business, Windows Server Update Services and Visual Studio Subscriptions (MSDN).

Now…for the ISOs that you download from VLSC or MSDN, you need to be aware on some changes.

Instead of separated media packages for each SKU (WIndows 10 Pro; Windows 10 Enterprise; Windows 10 Education), the Windows 10 v1709 that you download, will include in the ISO a single WIM file with all this version.

So, when using this ISO in tools such as Microsoft Deployment Toolkit (MDT) or Microsoft System Center Configuration Manager (SCCM) make sure you select the appropriate image index in you task sequence.

Here’s the index table for your reference and…save you some time:

Image Name	Index
Windows 10 Education	1
Windows 10 Education N	2
Windows 10 Enterprise	3
Windows 10 Enterprise N	4
Windows 10 Pro	5
Windows 10 Pro N	6

Windows 10 Enterprise 1709 (Fall Creators Update) Now Available on MVLSC

It’s now available for download the new Microsoft Windows 10 Enterprise v1709 (a.k.a. Fall Creators Update a.k.a. FCU) through Microsoft Volume Licensing Service Center (MVLSC).

So go ahead to MVLSC website and download it today:
Microsoft Volume Licensing Service Center

Windows 10 Fall Creators Update – Improved Formatting for Windows Update Log

I must say…finally!

For those that needed to get Windows Update log using powershell with the cmd-let “Get-WindowsUpdateLog” there was a really annoying issue to read this “compiled log”.

Basically what happened was that after you run the cmd-let, and you opened the log file you’ll noticed that the formatting was completely a mess typically because the symbols weren’t there. That was usually a temporary situation, waiting for the symbols to be uploaded to a server and indexed.

Well….but if, for example, you were troubleshooting a machine that need to be out of the network? Than you’ll never get the correct formatting for the log file unless you copied it to a connect machine.

Now, with Windows 10 Fall Creators Update (v1710) or if you’re a Windows Insider with at least v1709, this issue was completely “fixed".
This means that running “Get-WindowsUpdateLog” you’ll automatically format the log file, without the need to have any network connection.

Here’s an example on how the log file looks with automatic formatting even without network: