Ranger and Webroot Spy Sweeper

Question

Is Spy Sweeper v2.1 compatible with Ranger?

Symptoms

N/A

N/A

Cause

Previous versions of Spy Sweeper have not been fully compatible with Network Ranger. The spy shield interfered with the Ranger logon process causing the user logon to fail.

Resolution

We have been in contact with Webroot and have learned that they have resolved the conflict between Spy Sweeper and Ranger in the latest version v2.1. They have added the ability to exclude particular applications from the spy shield scanner.

Response from Webroot.

In 2.1; You can add an exclusion to the SIS shield by making a registry key.

This is something new to 2.1.

NOTE: This is different than adding it to the spy installation shield list as that list blocks more apps. The registry key would go in the SpySweeper registry hive and would be a string value. The name of the key would be "sis".
The value of the key would be whatever the program is that you are seeing the SIS shield block. For example, if it was blocking abc.txt, that would be the value you would enter in. After adding this value to the registry, then turn the shield on and see if the program will open correctly. If you wanted to enter multiple programs, they would be separated with a /. For example, abc.txt/def.txt/geh.txt and so on.

Following Webroot's instruction we have created a registry fragment that will configure the Spy Sweeper settings on the client to ignore the Ranger files. After merging the registry changes we were able to successfully test the Spy Sweeper software alongside the Ranger client.

Instructions

If you have already installed Spy Sweeper and disabled the spy shield then skip to the Registry Fix.

If you are about to install the software, configure the server installation to disable the client's spy shield scanner as per the KB article.

Registry Fix

Download the registry fragment and merge the registry changes into each client that is running the Spy Sweeper software.

Then using the servers Spy Sweeper installation re-configure the client to enable the Spy Shield. The client will then incorporate the server configuration change and the registry merge activating the full features of Spy Sweeper.

Testing

After incorporating the changes try logging on a Ranger client.