Kyle Peterson Posted May 31, 2019 Share Posted May 31, 2019 We force install a few chrome extensions via gpo and are also using the roaming profile setting for chrome. The weird part is when launching chrome via the desktop/start menu the extensions do not install, so I thought this was maybe related to upm. It gets weirder when launching chrome.exe via powershell the extensions install right away and work as intended. (windows 10 1903 and xendesktop 1903) Has anyone else ran into this? I have excluded chrome from syncing with upm completely so the profile should be rebuilt from scratch each login. Link to comment
Kyle Peterson Posted May 31, 2019 Author Share Posted May 31, 2019 Turns out with VDA 1903 and windows 10 1903 the appdata/local/temp folder is not created on login. Chrome uses this for installing extensions. Opening powershell creates this folder which is why it was working that way. Kind of interesting. Link to comment
Question
Kyle Peterson
We force install a few chrome extensions via gpo and are also using the roaming profile setting for chrome.
The weird part is when launching chrome via the desktop/start menu the extensions do not install, so I thought this was maybe related to upm.
It gets weirder when launching chrome.exe via powershell the extensions install right away and work as intended. (windows 10 1903 and xendesktop 1903)
Has anyone else ran into this? I have excluded chrome from syncing with upm completely so the profile should be rebuilt from scratch each login.
Link to comment
1 answer to this question
Recommended Posts
Archived
This topic is now archived and is closed to further replies.