Gotomeeting app for windows 10
![gotomeeting app for windows 10 gotomeeting app for windows 10](http://cdn.windowsreport.com/wp-content/uploads/2014/05/precision-touchpads-not-working-windows-8.1.jpg)
#Gotomeeting app for windows 10 update
I eventually had to stop banging my head against the desk and gave up and just whitelisted the path "%USERPROFILE%\AppData\Local\GoToMeeting\*\g2m.dll" and now it works again.Īnyway, I thought I'd post this update as a note to myself and to see if anyone else has been having an issue and if you found a reason why, I checked all the files that were in the Gotomeeting folder in the user's profile and they were all digitally signed with the same certificate that I used for my cert rule. I was getting the same error in my original post about 0x0000361. G2Minstaller.exe runs, the problem is it could not load the DLLs it needed (I have SRP restricting DLLs as well). Perhaps because the meeting organizer is using a slightly different version? I'm not quite sure, but the user would get prompted to run GoTo Opener.exe which would run fine using the cert rules I previously established, but when it tried to launch G2Minstaller.exe from the user's AppData profile, it would crash.
#Gotomeeting app for windows 10 install
I've been using the certificate rules which worked well and have even taken to using Ninite to install GoToMeeting and do updates so the program is actually in the Program Files directory.īut, recently I've had users trying to join webinars and GoToMeeting insists on installing again. I'm not sure why, but I recently started having trouble with GoToMeeting/GoToWebinar again. I cleared the additional checks since it sounds to me according the the MS policy explanations that this is where the biggest performance hit is from. There are settings under the SRP called "Trusted Publishers" that if you define you can clear the "Additional Checks" for verifying the certificate is not revoked and that the timestamp is not revoked.
![gotomeeting app for windows 10 gotomeeting app for windows 10](https://comparecamp.com/media/uploads/2020/07/gotowebinar-dashboard.png)
Upon reading the explanations in the GPO settings, my understanding is this impact happens when you launch a signed EXE because Windows has to check a CRL for the validity of the certificate. Now, you've probably seen the warning about impacting system performance with certificate rules. You need to set another policy, this one under Computer Configuration > Windows Settings > Security Settings > Local Policies > Security Options > and enable System settings: Use Certificate Rules on Windows Executables Now the tricky part is, just because you have turned the cert enforcement on in the SRP, that does not automatically make Windows pay attention to the certs.If you do not have your SRP configured to enforce certificate rules, you will get a warning asking you if you want to enable them. Create a new certificate rule and use the cert you just exported.Open up the Certificates MMC and export the cert you just installed and place it somewhere you have access to when editing your GPO.Right click the exe, go to digital signatures, view certificate, then install (I just place it into my Personal certificate store). Can you share how you set up your certificate rule? I can't remember what I did (it was a while ago now) but I couldn't get that to work,