Help! - Deploying Google Earth as a GPO

[jzepeda]

Hello,

I understand that there are posts similar to this one open already, but none answer what my questions is.
This is my scenario,

I need to install the newest version of Google Earth (Free Version) on several student computers. I tried developing a MSI package using WinInstall LE, but no luck. I've deployed other programs through AD as a GPO, but usually the MSI packages are already built for me. Anyone know where I could find a MSI package for the latest version of Google Earth? If not, a good free program to create MSI packages? Thanks very much in advance.

[AngryTechnician]

1. Go to Google Earth - Advanced setup
2. Pick your version
3. Untick 'Allow Google Earth to automatically install recommended updates.' (Optional, but recommended IMO)
4. Click 'Agree and Download' and save the .exe file that you are offered.
5. Extract the contents of the .exe using 7-Zip (other package extractors probably do it but I always use this one
6. The MSI is in the extracted files, ready to deploy.

[willv28]

1. Go to Google Earth - Advanced setup
2. Pick your version
3. Untick 'Allow Google Earth to automatically install recommended updates.' (Optional, but recommended IMO)
4. Click 'Agree and Download' and save the .exe file that you are offered.
5. Extract the contents of the .exe using 7-Zip (other package extractors probably do it but I always use this one
6. The MSI is in the extracted files, ready to deploy.

We're not interested in updating yet. But are there similar issues in the MSI that there were in the 5.0 edition? Numerous people I know had to edit the MSI with a transform to make it work.

[jzepeda]

I will try your solution using 7-Zip. Thank you! I will reply again once I have tested to see how it worked out.

[AngryTechnician]

But are there similar issues in the MSI that there were in the 5.0 edition? Numerous people I know had to edit the MSI with a transform to make it work.

No issues whatsoever that I encountered. The only transform I used was one to move the shortcuts to a different folder on the Start Menu than the default, purely for cosmetic reasons.

[jzepeda]

Hi AngryTechnician,

First. Thank You! for your quick reply. I tried your suggested solution for two programs that I need to deploy, Google Earth 5.0 and Google Sketch-up. Your solution worked flawlessly for Sketch-up, but not for Google.

The error I am getting is when selecting the package under the group policy object and it states,

'Add operation failed. Unable to extract deployment information from the package. Run validation on the package to ensure that the package is correct.'

Any help is appreciated. Thanks in advance.

[Michael]

You can download the Google Earth 5.1 MSI here from my website

[jzepeda]

You can download the Google Earth 5.1 MSI here from my website

Thank You! Very very much! This is kind of what I was looking for. Unfortunately, the same issue still persists. any ideas on what could be wrong?

[gerardsweeney]

jzepeda...

This part is lifted from:

appdeploy.com]packages]detail.asp?id=1482

(replace the ] with /)


(I can't post URLs)


by AngryTechnician

To deploy the .msi package using Group Policy, a minor modification is needed. If you attempt to deploy the original .msi, you may receive the error message "Unable to extract deployment information from the package. Run validation on the package to ensure that the package is correct."

This appears to be because of erroneous data in the Languages field in the .msi Summary Information. I had to open the .msi in Orca, go to the "View" > "Summary Information menu", and edit the Languages field so that it only contained 1033 (the language ID for US English). Only then would it successfully deploy.


Alternatively, I use:

msiexec /i "Google Earth.msi" TRANSFORMS="1033.mst" - don't know if that's applicable to GPO (we don't use that).

Any help?

Gerard

[jzepeda]

Gerard,

Thank You so very very much! Your strategy worked! I was able to add the package to the GPO and deploy it successfully. Thank You again! and thanks to everyone who replied to this post with your suggestions!

Happy Holidays!

[stms958]

If anyone still having problem with this, you can find full instructions here:
mysysadmintips.com[index.php[active-directory[4
(Replace [ with /)

[Michael]

I've also made an MSI you can deploy for Google Earth 6.0 here

[kbauer]

Here's what I did to deploy the latest version:

Download the latest version of Google Earth from Here: dl.google.com/earth/client/advanced/current/googleearthwin.exe
Open the Exe with 7-zip and extract the following files and folders:
LocalAppData
program files
1033.mst
Google Earth.msi
Setup.ini

Edit google earth.msi with orca
(I made the following changes, so it would be installed for All Users, suppress the Google toolbar, won't launch after install and auto-accept the EULA.)

Transform -> new transform
Select Property from the sidebar, add a row titled ALLUSERS with a value of 1
INSTALLTOOLBARNOW 0
ISCHECKFORPRODUCTUPDATES 0
LAUNCHPROGRAM 0
AgreeToLicense Yes
generate & save the transform
Transform -> close transform
view -> summary information
Delete everything except for 1033 in the Languages field (1033 is english)
save and exit

then push the MSI & MST using your weapon of choice.

[OverWorked]

jzepeda...


by AngryTechnician

To deploy the .msi package using Group Policy, a minor modification is needed. If you attempt to deploy the original .msi, you may receive the error message "Unable to extract deployment information from the package. Run validation on the package to ensure that the package is correct."

This appears to be because of erroneous data in the Languages field in the .msi Summary Information. I had to open the .msi in Orca, go to the "View" > "Summary Information menu", and edit the Languages field so that it only contained 1033 (the language ID for US English). Only then would it successfully deploy.


Gerard

Just to update, I found that this fix works with Google Earth 6.2.

[gerardsweeney]

Just to update, I found that this fix works with Google Earth 6.2.

If I get a chance, I'll also have a go at seeing if specifying 1033.mst still works.

Regards,
Gerard