Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - Andrew Jimenez

Pages: 1 ... 4 5 6 7 8 [9]

We're not currently tracking this issue, but will set up a Windows 10 2004 system in our lab and see if we can reproduce. We'll keep you updated on what we find.

Turning out to be trickier than expected... We'll keep investigating!

Thnx a bunch for your trouble!
Btw, why not switch to detection by file version? Chrome on a x64 system always gets installed to "C:\Program Files (x86)\Google\Chrome\Application", and on a x86 system to "C:\Program Files\Google\Chrome\Application", right?

You would think so, but that isn't always the case. We do use file version, but rely on the path provided by that registry value to get the Google Chrome path. Literally the only difference between the Google Chrome and Beta installer is where they are installed, which is why we haven't been able to differentiate between the two.

An alternative for you for now could be to set a CI or Group Policy to set the reg key "SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\chrome.exe\Path" to the path where Google Chrome <non-beta> is installed such as
Code: [Select]
C:\Program Files (x86)\Google\Chrome\Application

Turning out to be trickier than expected... We'll keep investigating!

We're looking at this now. I think we found a good alternate path to look for that wont pull the beta.

I think the native ConfigMgr App Export/Import are going to be your best bet here. If you export with content it should be a relatively pain-free process, so long as the signing certificates are trusted in the offline environment.

We are investigating this as an install method. Please see Thanks!

Pages: 1 ... 4 5 6 7 8 [9]