-
Home
- Blog
A couple of days ago, I posted a blog post detailing how to add language packs to MDT using PowerShell. In today's blog post I am going to build up on that and showcase how I use PowerShell to automatically generate a tasksequence specific CustomSettings_%TaskSequenceID%.ini containing the rules required to create a simple and dynamic deployment process. This includes configuring commonly used rules and also injecting language pack GUIDs.
As you’ve probably surmised by my blog posts and my Twitter ramblings, I like to push OSD to its limits. Besides keeping my deployments running smoothly, my vigilance sometimes helps me spot potential problems before they actually become an issue for my customers. The case opened wide when I started testing a pre-release Windows 10 1703 Insider Build based MDT task sequence. During the specialize phase, my VMs would run into a blue-ish screen stating that "Something went wrong".
In order to deploy Windows 10 with Microsoft Deployment Toolkit in a multi language environment successfully, you probably have to work with language packs. In today’s blog I will discuss the approach that I use to import language packs and features on demand packages in Microsoft Deployment Toolkit using PowerShell.
Microsoft Cuts Features from Windows 10 Pro... Again
Written by Anton Romanyuk
I would never usually be as presumptuous as to suppose that I knew exactly what my thousands tens of readers wanted to hear me talk about this week, but this is clearly a special occasion. Only one thing has been on everyone's mind since Microsoft quietly updated the list of features that are being removed and/or deprecated in the Windows 10 1709 update, and only that thing would be expected to be the subject of an almost-weekly almost-amusing blog post.
More...
Join me at Experts Live Europe on 23 August – 25 August in Berlin, Germany, where experts from around the world present discussion panels, ask-the-experts sessions and breakout sessions and cover the latest products, technologies and solutions from Microsoft. The conference will be held at Berlin Congress Center (bcc). If you aren’t familiar with it, the bcc is a great venue in a historic city that is located in the heart of Europe and the entire Germany’s road network convenes here, along with two airports and train station connected to the venue. The bcc enjoys a central location, hotels and shopping areas are close.
Microsoft is Changing the Windows 10 Servicing Model ... Again
Written by Anton Romanyuk
I have an embarrassment of riches regarding what to talk about this week, but instead, and apologies in advance for sounding like a record stuck in a groove, I am going to talk about Windows as a Service.
More specifically, about the changes to the branches. Microsoft is moving Windows 10 to the same servicing as Windows Server which means that they are transitioning from the Current Branch (CB) and Current Branch for Business (CBB) model of Windows releases to a twice-yearly release cadence called the Semi-Annual Channel. The release cadence will align to Windows Server and Office which means you can expect the updates to arrive in in March and in September, each of which with an 18-month servicing timeline. The Creators Update marks the first of the Semi-Annual Channel releases. Additionally, Microsoft is renaming the Long Term Servicing Branch (LTSB) to the Long-Term Servicing Channel (LTSC).
Of late, several customers I work with started deploying Windows 10 clients using an English base image and applying language packs in the process. They ran into a little snag involving localizing UWP apps.
In order to deploy and service Windows 10 successfully, you need to carefully consider how you apply language packs. In today’s blog post I will discuss the approach that I use to deploy and service Windows 10 in a multi language environment using Microsoft MDT and one base Windows 10 image.