Return
-
Title
One Identity Defender 6.2 Hotfix for Solution 338802 - Resolved issues for Defender Security Server, Defender Desktop Login and Defender Group Policy component -
Description
This hotfix is intended to provide a fix for the issue listed in the Resolved Issues and is meant only for Defender Security Server, Defender Desktop Login and Defender Group Policy component. It also includes the changes as listed in the following sections. One Identity may generate additional hotfixes for future releases of the product.This hotfix addresses a functionality issue. The minimum version required for installing this hotfix is 6.2.0. This Hotfix is specifically designed to be applied on the site and in the environment documented in this KB 338802 to resolve the issue described in Resolved Issues section. -
Resolution
Please download the hotfix, Defender 6.2 Hotfix for Solution 338802 HERE
Resolved Issues
The following is a list of issues are resolved in this hotfix.
Resolved issue Issue ID New improvised experience for both offline and online DDL login: Improved value parameters for online login besides inclusion of GINA settings (to hide/show passcode field).
Default timeout for Push notification approval/deny has been updated to28 seconds from 30 seconds.
311103 DDL users when logging in with RDP, get "The password stored by Defender isno longer valid" error if the password is already saved289778 Buffer overrun in the Defender authentication when PIN is enabled for thetokens299171 Removal of extra hexadecimal buffer traces that strain the memory print 301066 The VPN users get successful response upon triggering the PN in client 301901 RDP crash issue because of Empty DNS name in DSS logs in parent child ADtrusts hierarchy302085 The users get incorrect password message on UI when they try to login to Windows 10/Server 2016/Server 2019 DDL client after the screen is locked303990 Upgrade safety version of strcpy, strcat in certain cases to avoid bufferoverrun305009 DSS service crashes with Application Error on DSServADE.exe 311257
Products affected by this hotfix.Product Name Platform Version One Identity Defender 6.2 How to install this hotfix
To install the hotfix - For Defender Security Server:
1. On the computer that has the previous version of Defender Security Server and Administration Console 6.2.0.198 installed, run the Defender_x64.msi file. In the Defender distribution package, you can find the Defender_x64.msi file in the Setup folder.
2. Complete the Defender Setup Wizard. When stepping through the wizard, make sure to select the Defender Security Server and Defender Administration Console features for installation.
To install the Hotfix - For Desktop Login:
1. On the computer that has the previous version of Defender Desktop Login 6.2.0.198 installed, run the DefenderDesktopLogin_x64.msi file. In the Defender distribution package, you can find the DefenderDesktopLogin_x64.msi file in the Setup folder.
2. Complete the Defender Setup Wizard. Restart the computer.
To install the update for Desktop Login Group Policy:1. On the computer that has the previous version of Defender Desktop Login Group Policy 6.2.0.198 installed, run the DefenderDesktopLoginGroupPolicy_x64.msi file. In the Defender distribution package, you can find the DefenderDesktopLoginGroupPolicy_x64.msi file in the Setup folder.
2. Complete the Defender Setup Wizard.
Verifying successful completionTo determine if this hotfix is installed:
1. Open the list of installed programs and updates (appwiz.cpl).
2. Check the list of installed programs - Defender 6.2.1 should be mentioned.
To remove this hotfix
1. On the computer running Defender, open the list of installed programs and updates (appwiz.cpl).
2. Select Defender 6.2.1 in the list, and then click Uninstall.
3. On the computer running Defender Desktop Login, open the list of installed programs and updates (appwiz.cpl).
4. Select Defender Desktop Login 6.2.1 in the list, and then click Uninstall.
IMPORTANT:Uninstallation of hotfix 6.2.1 will also result in complete removal of Defender from your environment. You would have to reinstall the earlier version of 6.2 to go back to that version. -
Attachments