![]()
Now you will see this import will create the Configuration Item AND the Baseline. Select the Fix Chrome shell command path 圆4.cab and click Open. Open the MECM console and go to \Assets and Compliance\Overview\Compliance Settings\Configuration ItemsĬlick on Import Configuration Data in the ribbon. Place the extracted Fix Chrome shell command path 圆4.cab on a location so that you can import it in your MECM console. I exported the Configuration Item and the Configuration Baseline so you can import them in you MECM console.ĭownload the Fix Chrome shell command path 圆4.zip and extract it. With a Configuration Baseline we can deploy a Configuration Item or more than one if you want to a collection and remediate the value if needed. I created a Configuration Item (type Application) in the MECM console in this CI I specified a Discovery script and a Remediation Script (Powershell). The CI can detect if the value of the regkey has got the correct value and if the correct value is not detected the CI knows what the correct value should be. A configuration Item is a collection of settings, values, and criteria that defines what is compared, checked, or evaluated on a target system. In order to fix this regkey I created a Configuration Item in the MECM console and deployed it to all devices. “C:\Program Files (x86)\Google\Chrome\Application\chrome.exe” –single-argument %1īecause of this URL’s didn’t open anymore. “C:\Program Files\Google\Chrome\Application\chrome.exe” –single-argument %1 HKEY_CLASSES_ROOT\CHromeHTML\shell\open\command The biggest problem was that in some cases the following rekey Nothing happened when opening a URL from Outlook or trying to start a VPN authentication webpage in order to use the vpn software. I had to change some shortcuts created with a group policy in order to start certain URL’s with Chrome every time (Even if Chrome isn’t the default browser).īut a bigger issue was that some users who had Chrome as their default browser couldn’t open URL’s anymore. Manually created shortcuts to Chrome.exe didn’t work anymore of course because chrome.exe was now in a different folder (Program Files), users would have to change or delete them and create new ones. ![]() #Uninstall google chrome enterprise upgradeAfter the upgrade users started mentioning the issues below. 111 圆4 with MECM and superseded and uninstalled the old version. ![]() Sadly I didn’t read the release notes of 85 but i did of 86 (not reading anything about program files), so I deployed the Chrome version. Existing installations won’t be impacted. #Uninstall google chrome enterprise windowsNew installations of 64-bit Chrome will be installed in “%ProgramFiles%” on Windows instead of “%ProgramFiles(x86)%”. However when Google announced Chrome version 85 they mentioned in the release notes that from version 85 they would change the installation directory (finally):Ĭhrome 64-bit on Windows will be installed in “Program Files” instead of “Program Files (x86)” Because al lot of versions of Chrome 圆4 kept installing the sources in Program Files x86. ![]() This was an issue that was reported but apparently Google didn’t see it as something to fix right away. #Uninstall google chrome enterprise installThe fist thing worth mentioning is that Google Chrome 圆4 installed the sources in Program Files x86 NOT in Program Files where 64 bits programs should install their sources. In this post I will explain what happened and how you can fix the issues if your would run into them. Some shortcuts that we created to open a specific URL with Chrome by default even if the default browsers wasn’t Chrome didn’t work anymore. ![]() Users that had set Chrome as their default browser before the upgrade could not open URL’s anymore. If ($RESULT.I recently updated Google Chrome Enterprise version. $INSTALLED = Get-ItemProperty HKLM:\Software\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\* | Select-Object DisplayName, UninstallString $INSTALLED = Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | Select-Object DisplayName, UninstallString Another possibility would be a powershell script or maybe even better convert this one to a proactive remediation script! Hi, normally the option you have chosen, should work. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |