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

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...

KB5025885: How to manage the Windows Boot Manager revocations for Secure Boot changes associated with CVE-2023-24932

This article outlines the protection against the publicly disclosed Secure Boot security feature bypass involving the BlackLotus UEFI bootkit (CVE-2023-24932). It includes steps to enable the necessary mitigations and provides guidance on creating bootable media. I will provide: - An overview of the CVE issue. - Pre-requisite actions within ADK. - Detection and remediation scripts for CVE-2023-24932. - Instructions for creating a WinPE Boot.wim file to support systems that have undergone remediation. - A breakdown of the files changed and how to boot WinPE to support systems before remediation. 1. Secure Boot Security Feature Bypass Vulnerability CVE-2023-24932 see MSRC CVE-2023-24932 is a security vulnerability involving the BlackLotus UEFI bootkit, which allows attackers to bypass Secure Boot protections. This vulnerability enables the execution of malicious code at the UEFI level, potentially leading to persistent and evasive threats. Mitigations for this issue include updates to th...

Java 7 update 21 (1.7.0_21) Enterprise Repackaged Security Medium Deployment with SCCM

------------------------------------------------------------------------------------------------- Java 7 update 45 Enterprise deployment complete walk through http://www.syswow64.co.uk/2013/10/java-7-update-45-enterprise-deployment.html -------------------------------------------------------------------------------------------------- The issue on many blogs and articles is around creating the 'deployment.config' and 'deployment.properties' files for an enterprise deployment.  In my case i wanted to set the security level to 'Medium', but everytime I open the Java control panel it was set to the default HIGH setting. Solution 1 Create the following directory path 'C:\Windows\sun\java\deployment' 2 Create a file called 'deployment.config' in this directory and open with Notepad. Copy the two line below #################### deployment.system.config = file\:\\C\:\\WINDOWS\\Sun\\Java\\Deployment\\deployment.properties deployment.system...