/build/static/layout/Breadcrumb_cap_w.png

GoogleEarth Pro 7.3.1.4505

Can someone please advise how to disable start tips for GoogleEarth Pro 7.3.1.4505 via a registry hack.

I have already tried following however it has not been successful;

Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Google\Google Earth Pro]
"enableTips"="false"


0 Comments   [ + ] Show comments

Answers (3)

Posted by: Maidens 6 years ago
Third Degree Blue Belt
0

[HKEY_CURRENT_USER\Software\Google\Google Earth Pro]

enableTips="false"



Comments:
  • Thanks but I need this done for all the users , not just the current user. - Vickyw 6 years ago
    • So target the 32-bit part of the registry, not the 64-bit part. - anonymous_9363 6 years ago
Posted by: Maidens 6 years ago
Third Degree Blue Belt
0

Either by

- Using Packaging techniques and creating an MST file. MST contains the CU registry settings and any additional changes. If the base MSI  has  an  advertised shortcut, then set entry as keypath to trigger self heal. Otherwise Active Setup might be required.

- Using Active Directory Group Policy.

- Script deployment

You don't indicate what deployment tool your organisation uses. Some deployment tools have the ability to create deployments/scripts and run as the "logged on user" or "current user" as opposed to system account. Obviously in order for this to work the users need to have permissons to the registry.



Comments:
  • Hi There Thanks a lot. My organisation uses SCCM for deployment.

    I opened up the msi file using Orca however could not find any table/entry related to "Start Tips".

    Can you please provide further advise?

    Thanks - Vickyw 6 years ago
  • Hi There Thanks a lot. My organisation uses SCCM for deployment.

    I opened up the msi file using Orca however could not find any table/entry related to "Start Tips".

    Can you please provide further advise?

    Thanks - Vickyw 6 years ago
Posted by: Maidens 6 years ago
Third Degree Blue Belt
0

Yeah the “enable Tips”entry doesn’t exist within the MSI, thus why you need to create a new transform (MST) which contains the entry. (Never directly change the vendor MSI, always create a transform file)

Unless your familiar with Orca and know your way around the tables it can be a bit daunting. However adding HKCU entries has been covered here before –

http://www.itninja.com/question/how-do-i-add-hkcu-values-in-msi-file-using-orca

Alternatively, your organisation uses SCCM. As previously indicated, if the users have permissions to the registry. Why not create a package, which runs a script to apply the CU registry settings, Run mode set to“Run with user’s rights”

Good Luck!

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ