Traveler and Samsung Galaxy fingerprint lock
paul | Friday, 15 January 2016 | Traveler | samsung

One of the cool features of new smartphone are that some of them have integrated fingerprint sensors which can be used to secure the device. I have a Samsung Galaxy S5 handset and this allows you to easily unlock the screen by swiping the home button.

Unfortunately this unlocking method does not work with Traveler when a require device password policy is set. It results in the error message "Error: Sync is disable because of a device security poicy violation".

I have logged a PMR with IBM SUpport and here is their response:

We have the following statement from development regarding the fingerprint scan:
"The reason for this is that Traveler supports the Android Operating system, not specific phones.   The Android OS does not provide apis relating to figerprint s canners, which is why the fingerprint security is categorized as "unrestricted".     
When we initially tested this support, we found that even when "unrestricted" was  specified, the Android OS was still reporting the device as non-compliant when the fingerprint scanner was enabled.       
After a lengthy correspondence with Samsung on t his issue, we found that they require that we set the minimum password length to 0 in our calls to the Android OS.  We modified our code to set the minimum password length to 0 when the setting was "unrestricted" and at that point, the Samsung device reported compliant with the fingerprint scanner was enabled.     
Traveler will not have a specific setting for fingerprint or any other biometric u ntil the Android OS provides explicit support for it. The device passcode settings  are direct passthrough to the Operating System. "         
Samsung modified the api (few months ago) and Marshmallow Android offers new APIs to let authenticate users by using their fingerprint
In light of this we created Enhancement request for them to be added (this is internal, so you won't be able to open it but I'm posting it so it's present in the text of the PMR and others would be able to see it):                                                                                

Hopefully a new version will be release soon to provide the functionality.

Display Comments...
Error when install new Kace client 6.4.180
paul | Thursday, 14 January 2016 | Kace | Client

When installing the new Kace client (6.4.180) it fails with the error "The older version of Dell KACE Agent cannot be removed. Contact your technical support group."

It seems that the previous client (6.3.314) has not uninstalling properly. This can be fixed by manually deleting a registry key using the command below:

reg delete HKEY_CLASSES_ROOT\Installer\Products\44140F99099025F43AD5BA2A095E7531 /f

Then install the Kace Agent MSI. If upgrading from another version of the Kace agent (not 6.3.314) then you may need to use regedit and search the key HKEY_CLASSES_ROOT\Installer\Products for the right identifier to delete.

Display Comments...
Adding a local network PAC file for Websense
paul | Friday, 04 December 2015 | Websense | PAC

1. Create a Forward Lookup Zone for "" on your internal DNS server.

2. Add a DNS address record, as above, pointing to the IP address of an internal web server where you are going to host the PAC file.

3. Add a web site to your internal web server which serves pages for host header "".

4. Download the PAC file from "".

5. Modify the PAC file, if required, and then upload the PAC file to your new internal web site's root folder.

6. Edit site (example in IIS 7) and add a binding for port 8082 and hostname name "".

7. Add a MIME Type to the site for ".pac" files - mime type should be "application/x-ns-proxy-autoconfig".

8. Restart the web site.

9. Restart your web browser and it should download the PAC file from your internal webserver if your primary DNS is set to your internal DNS server.

Also when your machine is not connected to your internal network it will use another DNS server so will then download the PAC file directly from Websense's servers.

Display Comments...
Notes client error: Invalid NSF version
paul | Thursday, 03 December 2015 | Notes | NSF

When opening database the Notes client displays the error message "Invalid NSF version".

Client cannot understand the ODS (file format). Upgrade client to latest release.

Display Comments...
PRTG Administration Tool error Access violation at address
paul | Thursday, 05 November 2015 | PRTG | error

After installing a PRTG Remote Probe when you run the PRTG Administration Tool on the machine to configure the remote probe it displays the error message - PRTG Network Monitor - PRTG Administration Tool Access violation at address 0040A65C in module 'PRTG Administration.exe'. Read of address 010100F9 - as below.

PRTG Error

This is due to the communication between the Admin Tool and the Probe service being blocked by a firewall. Adding an exception for the port (default 23560 TCP) then allowed access without any error messages.

Display Comments...
Page 1 of 59 (296 Articles) << 1 2 3 4 5  Next >>