![]() ![]() The most recent version as to date is 1511. Language Packs are available for each Current Branch release of Windows 10. ![]() You do not have to re-create your Task Sequence since the client.xml file have not been updated. NOTE! If you’re using MDT 2013 U1 (even the re-released version), you should install Update 2 and update your deployment share, since Update 2 contains fixes to a bug regarding Language Packs in Windows 10. ![]() I will also cover some bits of what’s going on under the hood regarding how MDT is applying the Language Pack, since it’s not really documented well. In this post, I’ll show you how to add Language Packs in your Windows 10 reference image by using MDT 2013 Update 2. They all may do the trick, but since MDT has built-in support for adding Language Packs to the reference image, I always tend to use that. I’ve seen many examples of using for instance dism.exe, lpksetup.exe and other methods. Dealing with Language Packs in MDT, essentially adding them to your reference image, is a process that’s not very well documented. Over the years, I’ve worked with customers that have the need for adding Language Packs into their deployment process. ![]() Next up is how to add Language Packs to your reference image. These past few days, I’ve shared some scripts and tricks on how you can create a Windows 10 reference image. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |