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.
Welcome / Willkommen
[EN] Welcome to my blog mainly focusing on Microsoft Windows client infrastructures. I've created this blog to share some of my knowledge with the community. I've personally benifit from so many great bloggers on the web that I just feel it's time to give something back.
[GER] Dieser Blog ist überwiegend auf Microsoft Windows Client Infrastrukturen spezialisiert, wie Sie in großen Unternehmen zum Einsatz kommen. Da ich selber größtenteils von Bloggern aus aller Welt profitiert habe, möchte ich mit diesem Blog meine Erfahrungen und Wissen an die Community zurückgeben. Die Themen sind in den meisten fällen auf Enterprise-Strukturen angepasst. Die Community ist überwiegend englischsprachig unterwegs, weshalb hier auch alle Themen auf Englisch behandelt werden.
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:
As we all know Windows PE is a very lightweight operating system containing only the neccesarry components for operating system installation. Operating Systems are usually installed by 1st Level Support that is not familar with the SCCM environment and sometimes they are really restricted in their administrative rights. Therefore it can be usefull to extend the Windows Boot Image.
In this example I’ll show you how to integrate Double Commander, a File Explorer alternative, in your Boot Image. Feel free to add other software products or custom scripts to your environment.
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.
During a Build and Capture Task Sequence I ran into the following error “Machine does not meet OSD capture requirements. Capture cannot continue.”