The GoTo Community is currently experiencing some technical issues affecting new posts and comments. We are actively working with our service provider and apologize for the frustration.

Forum Discussion

Chris42's avatar
Chris42
Active Contributor
4 years ago
Solved

Windows Defender Firewall issue

Hello, Remote users are getting a Windows Defender Firewall prompt about the Rescue applet when I start a connection.  Hoping you can guide me to a fix.   Here are the details... Users have an AD...
Problem
  • Chris42's avatar
    Chris42
    4 years ago

    OK, so then the firewalls I create in Endpoint should have distinct names, in case I deploy different CC builds to the same machine.

    And that probably should be distinct profiles, too, with all the rules for one CC instance per policy, not combining all the firewall variants in one big profile.

     

    So that's the setup, to sum up for other users:

    1, Create the CC, wrap it in an intunewin package, configure its deployment.

    2, Create a configuration profile for Endpoint Protection that sets a firewall rule for the particular CC install location.

    3, attach both to the user group that gets this CC.

    All done, nice and easy.

Chris42's avatar
Chris42
Active Contributor
4 years ago

Hello.  Sorry for the delay, holidays and such and I thought I had this fixed but... well...

So I downloaded Calling Card as you suggested, and deployed it thru InTune.   Calling Card does indeed look like the right plan here.

 

Users are now getting a firewall error from that.  Note the different program folder than the earlier screenshot.

 

This is occurring after they click Connect on the calling card and I accept the session on my side.

What's weird is it only happens once.  If the user clicks Cancel, we close the session, and the user starts a new connection there's no prompt that time.  Even weirder is that since it's a cancel, I'm not finding any LogMeIn related firewall permissions created as a result of this, so I'm back to wondering what entries should be created ahead of time.

 

Of course what would be ideal would be never getting this even the once.  And I can't be sure it won't all happen again if I change out to a new copy of Calling Card - like if someone wants to change our corporate branding.

Thanks

 

AshC's avatar
AshC
Retired GoTo Contributor
4 years ago

The most likely cause for the installation path change would be using InTune to deploy the software instead of an MSI or regular install through LMI.   Is it possible to manually allow 'callingcard.exe' into the new path determined? 

  • Chris42's avatar
    Chris42
    Active Contributor
    4 years ago

    It is deployed with a standard MSI.  I just wrap the MSI into a .InTuneWin package for distribution, it should be running the MSI on the target machine same as if it was downloaded there.  Is there something in the calling card configuration that I missed that would set up the firewall?

    Or what's more likely is that it's running the MSI out of the administrator login, not out of the user login elevated, and the installer's firewall rules only apply to the current user.  If I was to put calling card on a machine direct with the MSI and admin permission, would the firewall problem repeat for a newly created local user account?

     

    Either way, I can deploy a firewall rule, 

     

    The question I have is the \ejwsyp\ portion of the file path.

    Is that a constant for the calling card app?

    or is that something particular to the calling card MSI that I configured for our company?

     

    Thanks