MDT has pre-defined variables for languages, and it updates the unattend.xml file. Since I could not find any pre-defined variables for language settings, I was left needed a method to change the variables in the unattend.xml file with the actual values. This function updated the unattend.xml file with the computer name, time zone, and domain join information. Writing configuration information to c:\windows\panther\unattend\unattend.xmlįollowing Adam Gross’s mantra, I reviewed the running processes. Getting namespace “Microsoft-Windows-International-Core” for architecture “amd64” Getting namespace “Microsoft-Windows-Shell-Setup” for architecture “amd64” Getting namespace “Microsoft-Windows-Deployment” for architecture “amd64” Loading existing answer file “c:\windows\panther\unattend\unattend.xml” ![]() During the “Apply Operating System” step the smsts.log files shows the following steps: Normally, I create variables for the major language settings: System Locale, User Locale, UI Language, and Input Locale. Thought about what was different, and then realized it was the “Gather” step. ![]() Now I have done this many time from work, but what I was doing differently today, was not using MDT - just installing the OS and language pack from native Config Manager task sequence. I wanted to do a simple task sequence with a language pack. I performed an interesting experiment in my lab today.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |