If you do not have an Active Directory, you can use the 'group name' reg key available in the Safeconsole install folderwebappsres Edit the file "group name.reg" By default it is designed to put all users in a group "non domain users". You can change ...

This means that the drive cannot locate a SafeConsole server to connect to, either because there is no SafeConsole present or that the deployment configuration is wrong. If you don't have SafeConsole, go to SafeConsole.com and register for a free trial ...

By running SafeConsole cloud you will not have to install any software locally on your systems. You can find out more and try it on http://www.blockmastersecurity.com/safeconsole-trial [http://www.blockmastersecurity.com/safeconsole-trial] Requirements...

Applies only to SafeConsole on-premise. The 403 error indicates that your computer's IP is blocked in the Trusted Zone IP address filter. This could be due to * An IP address filter which contains zeroes (0) instead of blank fields in the configura...

For inbound connections to SafeConsole port 443 with https is used as default although this port is configurable to any port. To allow devices to connect back to SafeConsole (in order to use features such as remote kill or collect logs over the Internet...

_Applies only to SafeConsole on-premise._ SafeConsole will only show users that has registered a SafeConsoleReady flash drive or ShieldShare client and claimed it as theirs. If no clients have been deployed, SafeConsole will show only the OU structure o...

_Applies only to SafeConsole on-premise._ The problem manifests itself in SafeConsole 4.2 or earlier as a user name and password prompt that pops up again after a correct user name and password has been supplied The reason you get prompted repeatedly ...

_Applies only to SafeConsole on-premise._ AFFECTS: SAFECONSOLEREADY DEVICES 4.1 AND 4.2 THE PROBLEM When using a CA issued SSL certificate from an intermediate CA, SafeConsoleReady devices will not be able to verify the trust of the certificate on ce...

This problem has been identified as having to do with the passwords on the certificates (old/new) not matching which affects other setting in SafeConsole 4.2 or earlier. If you have a backup of the old safeconsole.ini it is quick to implement this fix. ...

If a device password has been forgotten there are three options available. * Try to remember the password, the hint that is displayed when an incorrect password is entered maybe will help you. You have 20 attempts or less before the device initializes...

The SafeConsole manual contains information on how to deploy your devices to connect to the server. I problems still arise please confirm the following steps on the machine where the device is attempting to connect: * Check that the registry key fo...

_Applies only to SafeConsole on-premise._ The Trusted Zone uses the IP-filter settings from the SafeConsole configuration. Unfortunately it is only possible to setup one IP-address range from the SafeConsole Configurator. By manually editing XML files y...

SafeConsoleReady Devices require a reg key and certificate to be present on initialization to connect to SafeConsol.e The certificate and reg key of the SafeConsole can be pushed to the user accounts using a GPO. Once these materials are at the ma...

_Applies only to SafeConsole on-premise._ THE PROBLEM The SafeConsole SSL-certificate has expired, this due to the use of a public CA certificate or an internal CA with short expire time. If the certificate has expired, new SafeConsoleReady Devices wil...

_Applies only to SafeConsole on-premise._ _How to prepare and move an existing SafeConsole server to a new server location._ STEP 1 – SETUP THE NEW SERVER MACHINE AND INSTALL THE NEW SAFECONSOLE Install the SafeConsole server software on the n...

In some cases systems are not able to receive both the SafeConsole registry key and certificate at the same time. For instance where this happen attempt instead to push the SafeConsole certificate in a separate GPO by following these steps: * Cr...

A bug in SafeConsole (4.2.0-4.6.6) caused devices to become disabled under certain circumstances. The bug presented itself if SafeConsole was configured to: * automatically disable devices in Device State Management * and the administrator select...

One option is to update the device to a later device software which features improved proxy support. The other option is to create a rule in the firewall that should be configured so that all calls over https (port 443) to the cloud server address are a...

_Applies only to SafeConsole on-premise._ To reset the password when the message 'failed to reset the password' appears and the correct code has been used, please follow these steps: 1. Open consoledb.script in the 'db' folder in the SafeConsole insta...

_Applies only to SafeConsole on-premise._ PROBLEM DESCRIPTION If I try to open the console via a web browser the page times out. I have tried from the server itself and from a remote client. The Safeconsole service is running and I have restarted the s...

_Applies only to SafeConsole on-premise. BlockMaster handles this process for SafeConsole Cloud._ Since SafeConsole is not required for devices to function, it is not considered critical and failover is not built into the product. Preparing for and perf...

_Applies only to SafeConsole on-premise._ If you are unable to see or use the 'Install License' button in the license view, it is possible to still easily install the SafeConsole license manually. The 'Install License' button should of course be visib...

The document goes through some of the errors that can be seen when analysing the catalina.log from SafeConsole, available in the logs folder of the install directory. EXAMPLE - CONNECTIVY ISSUE SEVERE: Safedownloader: Failed to download index java.net...

HTTP STATUS 403 - ACCESS TO THE SPECIFIED RESOURCE () HAS BEEN FORBIDDEN. Possible reasons: * The machine trying to access SafeConsole is not inside the range of IP addresses allowed in the SafeConsole Configurator "IP Filter" * RESOLUTION: ADJUST...

This problem indicates that the address mentioned in the warning message does not resolve to a valid domain controller. There are fallback mechanisms within SafeConsole that may counteract this problem and still make it work, so you may want to try to p...