The “Windows Settings” will replace the “Control Panel” in future Windows releases. Until version 1703 there were no possibilities to modify the standard view of the “Windows Settings”. Since Windows 10 1703 it is possible to modify the Windows settings menu similar to control panel settings.
I was asked to install a KMS Server for Office 2010/2016, Windows Client (7/10) and Windows Server (2008/2012/2016). The intention was to replace all KMS servers that were build up in the last 10 years by a KMS server hosted on Windows Server 2016. I’ve started to install the KMS Keys for clients and servers as I’ve already explained for Server 2012 R2 in “Windows 10 / Office 2016 – KMS Activation“. For Office 2016 I’ve just had to install “Microsoft Office 2016 Volume License Pack” and the activation was working fine. In the last step I’ve tried to install “Microsoft Office 2010 KMS Host License Pack” that is necessary for Office 2010 KMS activation but I haven’t recognized that this package isn’t available for Server 2016.
Nevertheless I’ve downloaded the Package and tried to install it on Windows Server 2016. As exspected I’ve received a error message.
I’ve noticed that the installation data is stored in “C:\Program Files (x86)\MSECache\OfficeKMS”. The installation is started by a vbs script that could be easily edited. After editing the script the installation worked fine. Here is how to do it:
I’ve tried so many different ways to deploy Windows 10 clients in different languages and there was only one way working for me, I like to share with you. Our aim was to deploy Windows 10 clients in 28 different languages, so our itention was to deploy these clients in English and to deploy the language packs afterwards. We didn’t want a client with 27 language packs installed that must be maintained with every Windows 10 Feature Update. But we got a lot of Problems with the Windows 10 UI that sometimes didn’t changed the language as exspected or the time and date formats were set comletelly wrong. The only way I figured out was to deploy language packs by the following order.
- Install the language pack during the OS installation using the dism command dism.exe /norestart /online /add-package /packagepath:.\lp.cab
- Restart the computer
- Run a script executing the following command C:\Windows\System32\control.exe intl.cpl /f:"configuartion.xml"
- Restart the computer
Step 3 is neccessary to set the installed language pack as activated and to install the corresponding “Input Preferences”.
Create Package – “MS W10 1703 LanguagePack de-DE”
Lets start with building a deployment package including the german languagepack *.cab file, a PowerShell script for setup and *.xml file that is needed for configuration.
A lot of company applications are actually using the Java Runtime Environment (JRE) and a lot of them are integrated in the Internet Explorer using local adresses. When you open these kind of applications you will receive an error message that the application can not be trusted eventhough you provided your own root certificates by group policies. One big problem of the JRE is that it completelly ignores the Windows certificate stores. Instead of using the windows certificate store it uses its own implementation.
Java certificates are stored in a file called cacerts located at C:\Program Files (x86)\Java\jre1.x.x_xxx\lib\security\ You can open javacpl.exe to get a graphical overview about the content:
Even if you start installing a Windows 10 Enterprise (SAC) operating system there is still a bunch of applications installed you really don’t need in an enterprise environment. There are two ways of getting rid of these. First thing you can do is to disable the “Microsoft Consumer Experiences” (Application Set) that are automatically installed during the system deployment. That is the easiest way to get rid of apps like “Candy Crush” or “Xing”.
To get rid of the rest of applications like “Weather” & “Xbox” there is only one way to do that. You need to build a PowerShell script that is executed during your OS deployment. Eventhough the removing commands for appx packages are supported by Microsoft some applications are still not removed from the user interface completelly. I recommend to run the script during the OS deployment to avoid these kind of problems. If you start removing appx packages after the first user login sometimes the app will be removed completelly but the icon will stay in the start menu as long as you delete the user profile.
1. Hide Applications by Group Policy Settings
- Open/Create a new group policy object in the “Group Policy Management Editor”
- Navigate to Computer Configuration > Administrative Templates > Windows Components > Cloud Content
- Click on “Turn off Microsoft consumer experience“
- Switch the status of the policy to enabled.
Sometimes it’s good to know which updates are installed on your client. Of course you can choose the regular way via the GUI elements of Windows but than you have no possibilities to export your result for filtering or reporting.
There are different ways to achieve that
- Option 1 – CMD WMI querry
- Option 2 – PowerShell
- Option 3 – DISM
Required Windows Server Updates
The following update is required for Windows 10 activation:
- Windows Server 2012 R2 / KB3173424 – https://support.microsoft.com/kb/3173424
- Windows Server 2012 / KB3173426 – https://support.microsoft.com/kb/3173426
The following update is required for Office 2016 activation:
- Microsoft Office 2016 Volume License Pack – https://www.microsoft.com/en-us/download/details.aspx?id=49164&751be11f-ede8-5a0c-058c-2ee190a24fa6
Activation by Command Line
Type the following command to integrate your volume license key to the KMS server.
Microsoft (R) Windows Script Host Version 5.8
Copyright (C) Microsoft Corporation. All rights reserved.
If the key isn’t accepted by the server you will receive the error 0xC004F015.