Customers should verify all Profiles after updating to V8.6 before deploying Profile changes to endpoint devices The SecureDoc Profile settings for Number of Failed Logins at Windows has been decoupled from failed authentication attempts at Pre-Boot. and NetBIOS name a1trucks), then this advisory is not applicable to your environment.

If your prefix and NETBIOS name match (e.g. If your Domain ID and NETBIOS name differ in this way, you are recommended to remain on SecureDoc 8.5 SR2 or earlier until WinMagic has resolved this issue. These issues can include the creation of duplicate user records, as well as the failure to synchronize the users password or correctly cache the user’s credentials on the device. This can cause issues due to the SecureDoc database having synchronized the user from AD using the Domain Name Prefix “a1trucks”. trucksamerica), the user information provided to SecureDoc by the windows client is based on the NETBIOS name (e.g. prefix is a1trucks) is different from the NETBIOS name (e.g. a weekend or holiday) in order to permit ADSync the maximum possible time to complete the update.Ĭustomers who have configured their Domain NETBIOS name to be different from their AD Domain name prefix should not upgrade to V8.6 or V8.6HF1 until we have a resolution for domain name resolution issues encountered with this configuration.ĭetails/example: Where Domain Name Prefix (e.g. By performing a full sync immediately, it will ensure that existing AD User Records are updated efficiently before those records can become locked or busy due to SDConnex activity.įor those customers with huge Active Directories, the ideal upgrade planning would include planning to upgrade SES during a period of relatively low user activity (e.g. This is required due to changes in how User information that is retrieved from Active Directory is stored in the SES Database. For more information on this limitation please see previous release note v8.2SR1 Īfter upgrading SES to V8.6 and BEFORE starting SDConnex, customers that use ADSync MUST start and run a Full Sync using ADSync's Full Sync option, BEFORE starting SDConnex.

Prior to upgrading from v8.2SR1 to v8.2SR2 or later versions, please refer to KB article KB000001727 to follow the steps to ensure your client machine has Win7 with KB3033929. Please visit Knowledge Base Article 1760 for more information. As of this release, customers will no longer see this feature available for macOS configuration settings. On JWinMagic customers and partners were notified that the SecureDoc pre-boot authentication feature for macOS – known as SecureDoc On Top (SDOT) for FileVault 2 – would be deprecated in SecureDoc 8.2 SR1.

What is opal viewer lite