![ems 8860 update firmware ems 8860 update firmware](https://cdn.shopify.com/s/files/1/0068/3288/1779/products/789d8f0039c830bc804b868a9f75f624_16280f9d-192e-482c-a915-bd0319fdf7d2_600x600.jpg)
Simply running the command lines from the post referenced above on a Windows Server 2012 R2 machine, will not be sufficient for this type of operation, due to the version of DISM.exe available in the operating system does not support newer Windows PE images (from Windows ADK 10 and above). However, it’s recommended to utilize a version of DISM.exe that supports managing the boot image in question. It also provides the capability to update the package source meaning that it refreshes the boot image on the Distribution Points.
![ems 8860 update firmware ems 8860 update firmware](https://www.altaro.com/hyper-v/wp-content/uploads/2016/07/070616_1221_Workingwith1.png)
But instead of providing you with a solution that consists of running a set of command lines (see this post for a great example of just that), I’ve created a simple PowerShell script that takes the PackageID of a boot image, the keyboard layouts you want to set (it supports an string array of multiple layouts) and the mount path as parameter inputs wrapping it all into a single script.
![ems 8860 update firmware ems 8860 update firmware](https://video.informer.com/frames/f224211119957018.frame.jpg)
In fact, it’s a simple operation of mounting the boot image wim file, running a command line with DISM.exe and then dismount and commit the changes. Making this kind of change to the boot image (in fact the Windows PE image) is not a complex task to be honest. Generally, there’s no need to change this if you’re a shop that do zero-touch deployments, but whenever you introduce a frontend of some kind, and require the user to input data it’s convenient if the keyboard layout is set to what the user expects. The reason for this is quite simple, technicians or end users that are supposed to use the frontend should not be required to be familiar with the default keyboard layout of en-US. While developing the ConfigMgr OSD FrontEnd, a good chunk of customers where I’ve helped them to implement the solution, has asked me to also change keyboard layout (input locale) for their boot images as well.