Skip to main content

Google Earth Pro 7.1.5

This process is based on Windows 7 64-bit and Google Earth Pro 7.1.5.

https://docs.google.com/viewer?a=v&pid=forums&srcid=MDIyODIxNTE2ODcxMjA5NzI3MzABMTAzNTYwMTU0MzgyMzg3MDQ4ODABTGg1Y3RUR3VxS2tKATAuMQFnb29nbGVwcm9kdWN0Zm9ydW1zLmNvbQF2Mg

•Download and install GEP on a computer such as a test computer. Make note of the time when you start the install. We need it to help identify the MSI file.
•Go to C:\Windows\Installer\ and locate the MSI file with the date and time stamp matching the time you performed the install. The MSI file should be approximately 30 MB. Note: ..\Installer\ is a hidden folder. If you don't see it in C:\Windows it is because you are browsing and "Hide protected operating system files" is enabled. Type the full path into Windows Explorer or turn off "Hide protected..."
•Copy the MSI from C:\Windows\Installer\ to a network share that you will use for deployment. Rename the MSI to something logical such as GoogleEarthProWin.msi
•Launch GEP after installation on the test computer and complete the license registration window. Because GEP is now free you do not have to do the online registration process as was done when you had to buy a license. Instead, just enter a legitimate email address in the Username field and "GEPFREE" in the License Key field. Click "Log In" when done.
 Recommended if you want a good deployment:
 - Enable automatic login
 - Enable for all users...
•Close GEP
•Open Registry Editor (regedit.exe) and navigate to:
 HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Google\Google Earth Pro
 For 32-bit Windows then: HKEY_LOCAL_MACHINE\Software\Google\Google Earth Pro
•Optional but recommended. Why? Because users will be users. Add the following reg keys and values to the same key path as above:
 Hide the "Deactivate" option from the GEP Help menu:
 - Right click on the Google Earth Pro folder and click on New > DWORD Value
 - Rename the entry to "DisableDeactivation"
 - Right click on the entry and choose Modify...
 - Set the "Value data" to 1.
 Hide the Username and License Key from the GEP Help>About menu info:
 - Right click on the Google Earth Pro folder and click on New > DWORD Value
 - Rename the entry to "hideUserData"
 - Right click on the entry and choose Modify...
 - Set the "Value data" to 1.
•Launch GEP and verify that your registry keys are working. You should not be able to Deactivate GEP from the Help menu and you should not be able to see the Username nor License Key from the Help>About Google Earth window.
•Go back to Registry Editor and the location HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Google\
 (For 32-bit Windows then: HKEY_LOCAL_MACHINE\Software\Google\)
•Right click on the Google Earth Pro folder and choose Export. Save the registry file to the same network share location as the MSI for deployment. Give it a logical name so you don't wonder what the heck it is in the future.
•Below are commands to silently install Google Earth Pro and the registry file. Use your favorite deployment method from here. I personally like PDQ Deploy. Depending on your deployment method you may or may not need to add paths to the msi file and reg file in the commands below.
Silent install: msiexec.exe /i "GoogleEarthProWin.msi" ALLUSERS=1 /qn /norestart /log install.log
Silent Registry file install: regedit.exe /s "GoogleEarthPro715.reg"

Resources:
ITninja: http://www.itninja.com/software/google/earth-pro/7-pro
  
Google Maps and Earth Help Forum: "Unattended Install of Google Earth Pro" - March 18, 2015:
https://productforums.google.com/forum/?utm_medium=email&utm_source=footer#!msg/maps/NhT3W2ZameI/-47sGr53vvQJ

Comments

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