Probax Scout - FAQ

The bellow article aims to answer some of the common concerns and questions revolving around Probax Scout. Refer to this article if you have any queries regarding Scout's instillation and/or usage.

Please email support@probax.io with any further queries you may have regarding Probax Scout, and let us know the questions you would like to see answered in this artcle.

Do I need to white list Scout for it to work fully?

Yes. Please whitelist Scout and all associated properties of Scout in all Anti-malware/virus and Firewall settings. After installation of Scout, you'll be able to identify this to be the issue if Scout has not checked in for some time. We recommend whitelisting the following:

Folders:
C:\Program Files (x86)\Probax Scout\
Files:
C:\Program Files (x86)\Probax Scout\Probax-Scout-Watchdog.exe
C:\Program Files (x86)\Probax Scout\Probax-Scout-Controller.exe
C:\Program Files (x86)\Probax Scout\Probax-Scout.exe
Services:
Probax Scout Watchdog
Probax Scout
Domains:
api.probax.com.au

Can I install Scout on a 32-bit operating system?

Given Scout is designed for 64-bit operating systems, unfortunately, the application will not be able to run properly on a 32-bit operating system. For users wanting to use Veeam Agent for their 32-bit operating systems, we recommend installing Veeam Agent manually and creating a copy job for this. Visit our Knowledge-Base article here for more information. 
https://kb.probax.io/how-to-manually-deploy-veeam-agent-for-windows

Do I need to add Local Authentication details in the Windows Credentials Manager?

In most cases, no, the local authentication can be left in Scout's configuration, with Scout being able to handle this itself. If you are finding that Scout is not authenticating or working properly, some customers have seen success in adding these details into the Windows Credentials Manager as a troubleshooting step.