/build/static/layout/Breadcrumb_cap_w.png

Blog Posts tagged with Google Chrome

Ask a question

Hyperlinks Won't Open After Chrome Browser Is Uninstalled

We have had several users request support for hyperlinks not working from Office programs. They click on a link in an email and they get an error message: "This operation has been cancelled due to restrictions in effect on this computer. Please contact your system administrator."

After quite a bit of investigation we determined this was caused by Chrome web browser being uninstalled while it is still set as the default web browser.

The short answer: While logged in as the user, with Office programs closed, install Chrome. Then set the default browser to Internet Explorer, uninstall Chrome, and reboot.

 

What bothers me about this scenario is the user doesn't need to have privleges to install Chrome. I have tested this with a basic user account on Windows 7 32 bit. The user is not able to install or uninstall programs. (Tested using Dymo Label Software v8 and Adobe Acrobat Reader X) However, browsing to https://www.google.com/chrome/browser/ and clicking on the Download button will allow Chrome to install.

View comments (3)

How to extract information from the Chrome preferences file and collect them with a K1000 Custom Inventory Rule

If you already had a look inside the Chrome folders on your Windows machine for sure you noticed that Chrome saves the preferences in a file under 

 %USERPROFILE%\AppData\Local\Google\Chrome\User Data\Default .

The file that contains the preferences is called Preferences and it is in JSON format.

The best approach to extract the information that we need from that file and collect them with a Custom Inventory Rule is 

  1. run a script that looks for the Preferences file for all the users of the device
  2. interpreters the Preferences file that is in the JSON format and dumps the information in a unique text file
  3. collect the file content with a Custom Inventory Rule

To interpreter the file we can use the PowerShell cmdlet ConvertFrom-Json that was introduced in PowerShell 3.0.

The following example extracts the default page(s) from the Preferences file found in all the users profiles and dumps the result in the file C:\Chromato.txt

 <# 
 .SYNOPSIS
This script extracts the default page from the Chrome preferences file for all the user of the computer.
 .DESCRIPTION
 This script extracts the default page from the Chrome preferences for all the user of the device using the 
 ConvertFrom-Json cmdlet introduced in PowerShell 3.0
 AUTHOR:      Marco S. Zuppone for DELL KACE
 .NOTES       
  You will need PowerShell 3.0 or better
 WARNING: This script is given AS IS. Use it at your own risk! Revise it carefully before to use it.
#>
Remove-Item c:\Chromato.txt
Get-ChildItem c:\users| 
where {$_.PsIsContainer} |
foreach {
$PrefFileName = $_.FullName+'\AppData\Local\Google\Chrome\User Data\Default\Preferences'
try {
$ch = ConvertFrom-Json -InputObject (Get-Content $PrefFileName -raw)
echo "-----------------" | Out-File -filepath c:\Chromato.txt -Append
Out-File -filepath c:\Chromato.txt -Append -InputObject ("User: "+$_.FullName)
Out-File -filepath c:\Chromato.txt -Append -InputObject $ch.session.startup_urls
echo "-----------------" | Out-File -filepath c:\Chromato.txt -Append
    }
    catch {"File not there or not parsable at "+$PrefFileName}
}  

You can easily modify the script above to exact the information that you want from the file: the object $ch contains all of them.

The custom inventory rule is the following:

ShellCommandTextReturn(cmd /c type c:\Chromato.txt)

You can execute periodically the PowerShell script on the devices from you want to obtain the Chrome settings information.

Remember to invoke it using PowerShell.exe -ExecutionPolicy Unrestricted  or otherwise to sign the script with a trusted certificate.

If you want to know more about how to sign a PowerShell script you can have a look to this article http://www.msz.it/how-to-sign-a-powershell-script/

Be the first to comment

Google Chrome – Class not Registered – really FIXED

I have spent a serious amount of time researching how to fix Google Chrome’s “Class not registered” error.

Many responses move toward deleting the registry keys

-HKLM\Software\Classes\Chrome

-HKLM\Software\Classes\ChromeHTML\open\command\DelegateExecute

Or the same path under HKCR.  With my testing in our Corp environment, I found the HKLM did not exist. On some Win8 machines deleting the HKCR did not fix our problem.  Not sure of the reason, some machines deleting the HKCR fixed it.  Maybe that machine only had one user on it.  I don’t get the opportunity to talk to most users about their computer problems.

Other “FIXED” meant creating a shortcut right from the chrome.exe file, but pinning that to the user task bar meant it broke again.  This solution doesn’t work in the Corp environment either.

Other “FIXED” have said just run it as Admin.  Two points, one it won’t fly in a Corp environment where the users are just users, and two, the people who worked out to run it as admin might have ran regedit as admin and hit the HKCR keys, so they fixed it for only admin.

From the information I have read, the HKCR is a concatenation of the HKLM and HKCU and so this can be different to each user logging in to that computer.  Fixing the Classes Root for one person won’t for another.

I did a bit of deeper investigation into shortcuts and worked out each user under HKEY_USERS\S-1-5-21-[SID] has their own shortcut and classes table.

The fix for the "Class not registered" error is to fix it for each existing user.

EDIT: I managed to get the time to write the script up for fixing Chrome

Option Explicit
Const HKU = &H80000003
Dim strValue,oReg, Value, subValue, wmi, wshshell, strFullPath
Dim Key1, key2, key3
Dim strValueName1
Set oReg=GetObject("winmgmts:{impersonationLevel=impersonate}!\\.\root\default:StdRegProv")
Set wmi = GetObject("winmgmts:\\.\root\cimv2")
Set WshShell = WScript.CreateObject("WScript.Shell")
Set subValue = wmi.ExecQuery("Select SID from Win32_UserProfile where SID like 'S-1-5-21%'")
strValueName1 = "DelegateExecute"
Key1 = "\Software\Classes\Chrome\.exe\shell\open\command"
Key2 = "\Software\Classes\Chrome\.exe\shell\opennewwindow\command\"
Key3 = "\Software\Classes\ChromeHTML\shell\open\command\"
ParseReg key1,strValueName1
ParseReg key2,strValueName1
ParseReg key3,strValueName1
Sub ParseReg(key,strValueName)
For Each Value In subValue
oReg.GetStringValue HKU,Value.SID & key,strValueName,strValue
If strValue <> "" Then
Wscript.Echo HKU & Value.SID & key & strValueName 
  oreg.deletevalue HKU, Value.SID & key,strValueName
End If
Next
End Sub


View comments (1)

Virtual Google Chrome and Local o365 issues - Solution

After publishing Google Chrome App-V package in windows 7, logging into portal.office.com and opening a word or excel document and trying to edit it with locally installed Office 0365 fails. When checked with procmon, we can see that Google Chrome virtual package is able to see the local o365 package and tries to open it but the winword.exe process closes soon with exit code 1.

word.png

As in last blog,  I have detailed about the same issue happening with Appv-d Mozilla Firefox package and local o365.The solutions are still the same for the current scenario too. 

Solution 1:

Create the AllowJitvInAppvVirtualizedProcess registry key as shown below to fix this known issue.


jitv.png




Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ClickToRun\OverRide]
"AllowJitvInAppvVirtualizedProcess"=dword:00000001

If it doesn't work try in wow6432Node registry.


Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\ClickToRun\OverRide]
"AllowJitvInAppvVirtualizedProcess"=dword:00000001


Solution 2:

If Solution 1 doesn't work , try with the latest App-V 5.1 Hot Fix. Always make sure to use the latest App-V 5.1 Hot Fix. (A minimum of Hot Fix 4 is required for this issue to be resolved.)

You can download the latest Hot Fix here: KB4018510

Tested the same scenario in Windows 10 1607, only the AllowJitvInAppvVirtualizedProcess registry key is required.

NOTE: Fixes that are delivered to the “out-of-box” versions of App-V and UE-V are first delivered for the “in-box” versions of App-V and UE-V in the monthly Windows 10 cumulative updates.Since updates are provided to windows 10 in-box App-V client first, it will not require the installation of the latest Hot-Fix.

From Windows 10 1703, this AllowJitvInAppvVirtualizedProcess registry key will be automatically added when any of the Office product starts.
Be the first to comment
Showing 6 - 9 of 9 results

Top Contributors

Talk About Remote Control