Forum Discussion

Chris42's avatar
Chris42
Active Contributor
3 years ago

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
    3 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.

Elian1's avatar
Elian1
New Contributor

I was having same issue and still finding the solution please share the answer if you got thanks in advance.

AshC's avatar
AshC
Retired GoTo Contributor
3 years ago

When a Rescue7 administrator generates a Calling Card installer for a channel by the Admin Center, the CC is assigned a Referral ID, like "ejwsyp". This is a unique ID in Rescue7 and the install path will contain the referral ID every time the CC is installed or deployed by a Tech. The referral ID is used to differentiate company's Calling Cards from each other, it is stored in the current Windows user's registry, together with the company ID, and the channel ID.


The binaries may be the same in folders with paths of different referral ID-s.  The Windows pop-up with the security prompt every time a CC first runs under a user on each PC -- even for lower admin users.

  • Chris42's avatar
    Chris42
    Active Contributor
    3 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.