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

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 Client Certificate (PKI) Value is None

SCCM Client Certificate (PKI) Value is None Stopping WMI service Stopping CCMExec SC Delete any sccm services (ccmexec, smstsmgr, cmecservice, ccmsetup) Delete C:\windows\ccm, C:\windows\ccmsetup, C:\windows\ccmcache, C:\Windows\SMSCFG.ini Go into regedit and remove: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\CCM HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\CCMSetup HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS Then restart WMI, and reinstall the client. You shouldn't need a reboot to complete this. Once this has been done the client will install and pick up the cert. https://www.windows-noob.com/forums/topic/12644-sccm-2012-client-certificate-pki-value-is-none/

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