Skip to main content

Google Earth Pro Repackaged for SCCM with license key

Tags: install google earth pro with license key

Google Earth Pro can be downloaded here http://www.google.com/earth/download/gep/agree.html

Select Version 7.0 and un-tick “allow Google Earth to install Recommended Updates Automatically”.  Most Enterprise software is highly controlled and making sure versions are consistent and understood is essential.

 

GoogleEarthProWin.exe can be installed silently with the following switch.

GoogleEarthProWin.exe /S /v/qn /V"/qn ALLUSERS=1"

 

Or you can extract the exe to get at the MSI using a tool like 7zip.  The switch here is: msiexec /i "Google Earth Pro.msi" /qn

 

The issue that most SCCM Admins face is how to deploy Google Earth Pro with the license details included in the package.

 

In my example I will use InstallShield to create an MST file to transform the MSI file.

 

Once you have installed GEP you will be prompted for the username and password credentials.  Input them, and click “Auto login”.

 (Please be careful when modifying the registry, i accept no responsibility)

Open Regedit and navigate to top level path representing your current user hive. i.e HKEY_Users\S-1-5-21-########

 

Right Click:  Software/Google/Google Earth Pro and export reg key ( i.e. C:\temp\gep\gep.reg)

Change the key path to HKLM and remove all entries except for, as below:

 

[HKEY_LOCAL_MACHINE\SOFTWARE\Google\Google Earth Pro]

"AData"=hex:

"HideUserData"=dword:00000001

"Passport"="Insert Password"

"Username"="Insert Username"

"DisableDeactivation"=dword:00000001

 

This is all that is required to for any user to open Google Earth Pro without being prompted for credentials.

Now open Installshield and create a new MST project.

Click on System Configuration\Registry\

Right click on HKLM and select Import Reg file… Select the Reg created above.

Save the project to make the MST file (GoogleEarthPro7.0.mst)

Now using the MSI extracted earlier you can transform the MSI with the following command line.

 

msiexec /i "Google Earth Pro.msi" TRANSFORMS=GoogleEarthPro7.0.mst /l*v C:\temp\Logs\GoogleEarthPro7.0.log /qn

Comments

  1. I have the latest googleearthprosetup.exe and am trying to deploy it in SCCM2007. What is the command line I would need to do it silently?

    ReplyDelete
  2. I have the latest googleearthprosetup.exe and am trying to deploy it in SCCM2007. What is the command line I would need to do it silently?

    ReplyDelete
    Replies
    1. You can install the exe and then review the C:\Windows\Installer folder for the MSI. To find the MSI sort by date and review the MSI details. The MSI name will look random i.e. 3f617e.msi
      msiexec /i 3f617e.msi /qn

      Delete
    2. You can install the exe and then review the C:\Windows\Installer folder for the MSI. To find the MSI sort by date and review the MSI details. The MSI name will look random i.e. 3f617e.msi
      msiexec /i 3f617e.msi /qn

      Delete

Post a Comment

Popular posts from this blog

SCCM Unknown computer not able to see Task Sequences after installing Current Branch 1702

Soon after installing SCCM CB 1702 we were unable to see Task Sequences deployed to the unknown collection. This issue was identified as a random system taking the GUID of the 'x64 Unknown Computer (x64 Unknown Computer)' record. As a result it was now a known GUID; as we were only deploying Task Sequences to the Unknown collection none were made available. 'x64 Unknown Computer (x64 Unknown Computer)' record 'x86 Unknown Computer (x86 Unknown Computer)' record To get the GUID of your unknown systems open SQL management studio and run the following command: --Sql Command to list the name and GUID for UnknownSystems record data select ItemKey, Name0,SMS_Unique_Identifier0 from UnknownSystem_DISC Using the returned GUID (SMS_Unique_Identifier0) we can find the hostname that has been assigned the 'x64 Unknown Computer (x64 Unknown Computer)' GUID by running the query below. --x64 Unknown Computers select Name0,SMS_Unique_Identifier0,Decommissioned0 from Sys...

Windows 7 Offline files will not go Online when connected to network

Issue Several laptop users move between networks, domain, home, etc and when they attempt to access DFS shares explorer status is working offline.  The issue only resolves it self after a reboot. Connecting directly to the share works and i am able to ping network resources.  This behavior occurs for VPN users as well. Possible Causes "slow-link mode". In win7 (with default settings) a client will enter slow-link mode if the latency to the server is above 80ms. In slow-link mode all writes are made to the local cache and a background sync only happens every 6 hours.  Depending on your connection the default slow link detection speed is 64,000 bps On client computers running Windows 7 or Windows Server 2008 R2, a shared folder automatically transitions to the slow-link mode if the round-trip latency of the network is greater than 80 milliseconds, or as configured by the "Configure slow-link mode" policy. After transitioning a folder to the slow-link mode, Offline Fil...

SCCM Software Update - Job error 0x80004005 Failed to Add Update Source for WUAgent

SCCM Software Updates - Failed to Add Update Source for WUAgent  Today I have been looking at a range of servers (Server 2008 /R2 2012 /R2) that were failing to communicate with the Software Update Point (SUP) in SCCM and retrieve deployment policy. The UpdateDeployment.log was reporting the Job error 0x80004005 Job error (0x80004005) received for assignment ({af7a48e6-d550-4070-dd9b-ecc234567584}) action UpdatesDeploymentAgent 12/6/2017 10:32:27 AM 2096 (0x0830) The WUAHandler.log  was reporting "Unable to read existing WUA Group Policy object" and "Failed to Add Update Source for WUAgent " Unable to read existing WUA Group Policy object. Error = 0x80004005. WUAHandler 12/6/2017 3:41:00 AM 2828 (0x0B0C) Failed to Add Update Source for WUAgent of type (2) and id ({3AAB6A76-CE2D-4E8A-9F11-123AE69612A1}). Error = 0x80004005. WUAHandler 12/6/2017 11:03:31 AM 2276 (0x08E4) Until the agent can report back to the SUP, SCCM will not be able to summarize Software Update sta...