SecuriKey Knowledge Base

The SecuriKey Knowledge Base contains technical information regarding the use of SecuriKey Professional, SecuriKey Pro Multi-User, and SecuriKey Enterprise. Additional FAQ information about SecuriKey is available in the SecuriKey Q&A center.

Support for Mac OS X Leopard
Applies to SKP, SKPMU

SecuriKey v2.1 is required for use with Mac OS X Leopard. Earlier versions of SecuriKey do not support the many changes in Leopard and will hang Leopard on boot. If you wish to protect your Leopard Mac, you must obtain the upgrade to SecuriKey v2.1. If you have hung a Mac running Leopard by installing an older version of SecuriKey, please contact SecuriKey support for step-by-step information on the recovery process.

Resizing the SecuriKey Encrypted Volume with Mac OS X Leopard on Intel Macs
Applies to SKP, SKPMU

There is a known problem with the ability to resize the SecuriKey Encrypted Volume. This problem exists specifically on Intel-based Macs running Mac OS X Leopard. Macs running OS X Tiger and PPC-based Macs running Leopard are not affected by this problem. On Leopard/Intel Macs, attempts to resize a SecuriKey Encrypted Volume will fail with error number -5341. This is due to a bug in the Leopard file system on Intel-based Macs. Apple is aware of the problem and is working on a fix. In the interim, it is possible to protect more than 1GB of data on a Leopard/Intel Mac by using multiple SecuriKey Encrypted Volumes.

Support of Windows Hibernation/Sleep/Standby Mode
Applies to SKP, SKPMU, SKE

SecuriKey integrates with Windows power management including Hibernation, Sleep and Standby modes. Windows must be configured to require authentication from returning from these power management modes in order for SecuriKey to protect the resume operations with two factor authentication. 

To enable this Windows authentication process, launch Power Options from the Windows Control Panel. Once the Power Options applet has loaded, click on the Advanced tab. Enable the "Prompt for password when the computer resumes from standby" option. 

 

Adding a USB Hub
Applies to Windows editions of SKP, SKPMU, SKE

To add a USB Hub to a Windows system that is already protected by SecuriKey, there are a few steps to follow. This same process can be used to enable SecuriKey on any built-in USB ports that were not configured during installation. The process is:

1. Disable SecuriKey

2. Reboot the system

3. Attach SecuriKey to each available USB port. The found new hardware wizard will load the SecuriKey drivers each time for each new port. 

4. Re-enable SecuriKey

5. Reboot. The new ports will now recognize and work with the SecuriKey token.

 

Intel Mac Support
Applies to Mac editions of SKP, SKPMU

Both SecuriKey Professional and SecuriKey Professional Multi-User include support for Mac OS X on both PowerPC and Intel chips. Intel Mac support was introduced in SecuriKey Professional v1.50. Previous versions of SecuriKey Professional do not support the Intel Mac, and will hang the Mac on boot. If you have hung an Intel Mac by installing an older version of SecuriKey, please contact SecuriKey support for step-by-step information on the recovery process.

 

Registering user tokens with SecuriKey Pro Multi-User
Applies to SKPMU

Once you have configured the SecuriKey Administrator and configured the individual user token and profile, you need to register the user token. This must be done with the special SecuriKey Professional Multi-User Registration Tool, included on the SecuriKey Professional Multi-User CD. The user token that you have just added will be Token #2 (or greater, if you have added more than one user).

Be sure to select the token number that corresponds to the token you have just configured on the second screen of the Multi-User Registration Tool. Then, be sure to use a unique identifier in the Token ID Code field during the registration process to identify this token within the SecuriKey Registration Database. This can be any unique information that makes sense to you, such as "Bob's Token" or "ABC Co. 1234" 

In general, you will not ever need to register Token #1 using the SecuriKey Professional Multi-User Registration Tool. This is because Token #1, the SecuriKey Administrators Token, will most likely have been already registered during the SecuriKey software installation process. 

 

Error installing the SecuriKey Enterprise Server Extensions
Applies to SKE

The SecuriKey Enterprise Server Extensions provide deep integration into Active Directory. The Server Extensions include extensions to the Active Directory Schema. The SecuriKey Enterprise Server Extensions must be installed on the Active Directory Schema Master Server for your network. In order to install the Server Extensions, you must be logged in to the Schema Master Server as a Domain Administrator with both domain administrative rights and schema update rights. Errors received during the installation of the Server Extensions generally are the result of attempting to install the Extensions to a server other than the Schema Master Server or attempting to install the Extensions without the proper domain admin and schema update rights.

 

Error accessing computer after policy driven password update
Applies to SKE

In some circumstances, after the user updates his password because of a policy-driven password update request, SecuriKey will not allow logon using the new password. This is a known problem with SecuriKey Enterprise Client v2.21. There are two workaround options. The first option is to connect the laptop to the network and perform a live LAN logon to the Active Directory and SecuriKey Server. This resets the user settings and allows the user to proceed with his new password. The second workaround is to use a special SecuriKey User Rest Tool. This is useful if users are still experiencing trouble after performing the live LAN-based logon. This tool is available from SecuriKey Support.