awesome ask. makes sense.
Impossible to use Windows 10 Servicing when multi-language is used (and this is the case outside US ;-)
That's why I must use Task Sequence to :
1) Switch in US (Default OS language)
2) Run upgrade
3) install New multi language version
4) Install some others stuffs
That's why it could be a really good idea if we could run a TS before & after the Windows 10 Servicing .... or intregrate on it all this functions.
Updated by bobmn for sangeev/OSD
This is actually the most problematic issue we have during the differents scenarios we could encounter with inplace upgrade & MUI.
we have a TS to upgrade Windows 8.1 To Win 10 CB and another to upgrade Win 8.1 To LTSB.
Our 8.1 is be default in EN-US and we apply 3 languages (MUI).
During the inplace upgrade process, I should manage some steps inside the task sequence in a way to switch the 8.1 OS language in EN-US if I want my TS to work well.
I must have multiple reboot (registry change & Powershell script) to be sure that this os Language switch is ok.
During this phase & reboot, the winlogon is accessible and even if I have customized the background wallpaper (with a big warning for users which say, STOP your computer is under upgrade) ... this is not a really nice process.
And I have the same problem with an inplace upgrade for two Windows 10 versions.
This could be really nice if this switch could be managed directly by a "by design" step in Task Sequence.
149 votesstarted · AdminMark Silvey - ConfigMgr Product Team (Admin, System Center Configuration Manager) responded
First iteration is available in 1901 technical preview.