Forum Discussion

john81's avatar
john81
New Member
8 years ago

Group policy is blocking the installer from running in app data ( due to security) Help!

We cant run go to assist since yesterday, no changes our side, could it be that the installer location has changed to users/appdata ?
  • GlennD's avatar
    GlennD
    GoTo Manager
    8 years ago

    Hi John,

    We haven't changed the install location, can you provide some more detail about how you are installing and what is happening exactly?

     

    • 516-Andrew's avatar
      516-Andrew
      New Contributor
      7 years ago

      I got this from my SysAdmin, am working on figuring it out myself now. Happened again. Did it in June, also. Fixed by our IT Service Dept then. Thought I'd share. I'm thinking it mat occur when my browser - or something - updated itself. Windows? Reg-Edit, here I come...

       

      From my IT guys:

       

      Here is the error:

       

      Access to C:\Users\ <myuserID> \AppData\Local\GoTo Opener\GoTo Opener.exe has been restricted by your Administrator by location with policy rule {A512C122-DDC5-4C5D-882E-04165674DD67} placed on path C:\Users\ <myUserID>\AppData\Local\*\*.exe.

       

      Never seen this before but this is a Windows issue.  Need to figure out where this policy is and remove it.

  • John A1's avatar
    John A1
    New Member
    8 years ago
    I am seeing the same thing.  used to work OK now users cannot launch the app
  • AshC's avatar
    AshC
    Retired GoTo Contributor
    8 years ago

    Hi John,
    Can you provide some more detail about how you are installing and what is happening exactly?

  • John A1's avatar
    John A1
    New Member
    8 years ago
    most of my customers have GPO in place to block items running from the users Appdata folder and other user folders, look up cryptoblocker prevention. goto assist has worked in the past but not any more.  I send the user a link via email and they click on it and now they get a popup stating that this was blocked by a group policy.  also tried going to the fastsupport web site.  same issue.
  • AshC's avatar
    AshC
    Retired GoTo Contributor
    8 years ago

    While I'm not aware of any change in Remote Support installation policy (we installed to the Appdata folder prior to the merger), we have adjusted some of the install paths and folders for the Unattended due to legal requirements.  The new path for the GoToOpener is '\Software\LogMeInInc\GoTo Opener'.

    Alternatively, you might try the MSI instead, if a selected user base does not have the correct permissions:  https://support.logmeininc.com/gotoassist-remote-support/help/what-is-the-multi-user-launcher-opener-msi-g2ars850002

     

  • John A1's avatar
    John A1
    New Member
    8 years ago

    it not the unattended install have not tried that..  just sent them a link.  they click on the link and the app is blocked.  after looking at more posts other are having the same issue.

    my only work around is to use another a different application.

    please fix this 


  • Derrick Pullen1's avatar
    Derrick Pullen1
    New Member
    8 years ago
    We have the same issue in our organization. Same goes with gotomeeting and gotowebinar. Please fix!
  • Derrick Pullen1's avatar
    Derrick Pullen1
    New Member
    8 years ago

    Here is the error: 

    GoTo Opener encountered an error:

    Installer launch error 2001, Method "createprocess" returned Win32 error [1260]. This program is blocked by group policy. For more information, contact your system administrator.

    Error occurred at , endpointtools.cpp:134

    Failed to start GoToAssist.

    Please restart the download or contact Global Customer Support at

  • AshC's avatar
    AshC
    Retired GoTo Contributor
    8 years ago

    Hi Derrick,
    Were you able to grant access to the path '\Software\LogMeInInc\GoTo Opener' ?

    When the launcher downloads an installer for GoToAssist it first creates the executable as an empty file, then populates it with the data afterwards. Some firewall/proxies will block this request and substitute a common error message instead, but this is not delivered to the end user and instead into the .exe that was created. This causes the .exe to fail with the error when run by the Launcher.

    See if you can also whitelist the following URL *.getgocdn.com in the firewall or proxy.