SecureDoc v6.2 SR2 Release Notes

Reference

Improved disk operation times.

The disk operation times which could take more than 2 seconds have been improved.

Bug: The "Other..." icon will still be available in the OSX login screen after deploying SDMacFV.

SD-5766

SD-6346

Bug: 9401 Bootlogon error has been resolved.

The issue when restarting and opening the Control Center, which ends up crashing has been resolved.

Bug: Boot slot numbers will not be accepted to authenticate.

When selecting "Force user to input User ID at Login" in the Boot Configuration in Profile, Boot slot numbers will no longer be accepted.

The issue with sw/hw encryption which caused the password to not be converted to TPM protected has been resolved.

Issues with the SDPin session to close have been fixed.

SD-6197

SD-6555

Bug: The error 0x7819 Unable to find a computer with the unique identifier in the database has been resolved.

After upgrading the issues of seeing duplicate devices on the SES console has been fixed.

Bug: Removable Media (RMO) with passwords from older clients will be detected.

Bug: The caluculations for free space on RMO have been corrected.

Note: There is a limitation of FAT and FAT32 file systems which do not support more than 4GB files.

Bug: The challenge response length for the users have been fixed.

Issues with X-mode being reset to 0 have been resolved.

Bug: The SDConnex service will stop/restart properly.

Issues with the SDConnex Service not stopping and having to use a "force stop" have been fixed.

When upgrading from 6.1 SR1 the SD service will not terminate unexpectedly.

Bug: The Lenovo M93P and M83 devices now receive an IP address at Boot Logon.

Improvement: When doing an upgrade from 6.1 SR1 if FFE is enabled, a prompt for a patch install will be shown.

Bug: The "Winmagic Windows Logon" will not display when SSO and Permanent Autoboot are selected.

Bug: A notification is shown when communication with the server is succesful.

Reference

SES administrator configures AES-NI usability in the profile via “Allow use of ASE-NI if supported by CPU” setting in General Options => Advanced section.

This setting is applied to all client components. At the same time the user can locally modify this setting in the Boot Logon via “Global YMode” highest bit to handle possible hardware problems at pre-boot.

This produces the following limitations for enterprise users:

• The AES-NI setting received with the profile is not shown in the SDCC. This setting can be verified in SecureDoc.ini file as the value of "UseOf_AES-NI" attribute.
• Changes of AES-NI made manually at pre-boot are not visible in the SDCC either.
• AES-NI setting cannot be modified from the SDCC
• Each time a new profile comes from SES the local AES-NI setting is overwritten. User will need to restore the overwritten local setting manually.

SD-5824

SD-6577

SSO does not work after self-help recovery Challenge Response while CP and SSO is enabled. This occurs when the SecureDoc account has not performed Single Sign On with the Windows account.

In SDWEB, only Windows profiles can be assigned to MAC Devices.

The option "Disable user's access to computer if no communication with server for more than xx days" currently does not work.

SDCC displays a different Y-mode value than set in the pre-boot.

If the user changes (AES-NI preboot) bit at preboot, it will be overwritten when SES sends a new profile, or when the user changes the boot configuration in SDCC.