This message was deleted.
# _generals
Slackbot
10/17/2019, 12:36 PMThis message was deleted.
r
Rody Kossen
10/17/2019, 12:41 PMo
Owen Reynolds
10/17/2019, 2:49 PMThanks for your reply, I had tried that yesterday, but will attempt again. Can you confirm once done that any new users that login see both languages? as below?
Owen Reynolds
10/17/2019, 2:50 PMMy issue, is that any language added is just for the logged in user, new users only see the language from the base OS: Either En-US or Fr-Fr
l
Leee Jeffries
10/17/2019, 4:49 PMThis is great article by Dennis Span https://dennisspan.com/managing-windows-languages-and-language-packs/
👍 1
Leee Jeffries
10/17/2019, 4:49 PMTells you how to manage and roll out the lot
d
Dennis
10/17/2019, 9:24 PMYou can build your own WIM image or ISO with OSDBuilder and integrate language packs. It’s worth trying. https://osdbuilder.osdeploy.com/
It a great and powerful powershell module.
👍 2
o
Owen Reynolds
10/17/2019, 10:05 PMI got it working ! Not via DISM, will share details via blog post this week
Owen Reynolds
10/20/2019, 8:09 PMThe issue I was having, was partial language pack downloads due to a forced GPO that was pushing the following: HKLM:\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU\UseWUServer=1
once set to zero, I was able to download the required bits via regular Windows update. The local WSUS didn't have what I needed to support En-Us/Fr-CA languages. Thank you to everyone who responded.
Owen