-
タイトル
Quest® Defender Administration Console Hotfix (Update_5.7.0.4330) Readme and Download -
説明
This hotfix may receive additional testing. If you are not severely affected by the issues that this hotfix addresses, it is recommended that you install the next full release of Defender that includes this hotfix.
For complete product information, refer to the Defender 5.7 product documentation.
Files Updated
This hotfix is a complete rebuild and repackaging of the Defender Administration Console component. As the hotfix is cumulative, please see the "Resolution" section for the complete list of Resolved Issues.
-
対策
Please download the hotfix called, Defender 5.7 Defender Administration Console Hotfix (Update_5.7.0.4330) for solution SOL115596 by Clicking Here.
Resolved Issues
The following is a list of issues resolved in this hotfix.
Resolved Issues
Defect ID
Support for Digipass 301-CV and Nano tokens.
Note: Defender Security Server 5.7.0.4328 is required for this feature.
0004809
Resolved an issue which could cause the Admin Console to generate .dmp files for handled as well as unhandled exceptions.
0005326
Resolved an issue related to the license DN which could result in the user license count being incorrect when managing multiple Defender environments using the same Admin Console.
0005957
To install this hotfix:
An upgrade of the Defender Administration Console is required.1. Copy the 'DefenderADE MMC Installer.exe' and the included Visual C++ redistributables to the same folder on the required server or workstation.
2. Run 'DefenderADE MMC Installer.exe'.
3. If prompted that a Microsoft Visual C++ Redistributable Package is required, select OK to continue. The package will be installed and the Console installation will continue as normal.
Note: If the correct or a later version of the Visual C++ redistributable is already installed then this prompt will not be seen.
We recommend that if you are upgrading the Defender Administration Console, the Defender Security Server is also upgraded to the most recent available version.
To determine if this hotfix is installed:1. Open Active Directory Users & Computers.
2. Select the Defender OU.
3. On the menu tool bar select 'Defender'.
4. Select 'About...' to display the 'About Defender 5.7' dialog.
5. The version number is displayed at the top of the dialog and should read 'Version 5.7.0.4330'.
To remove this hotfix:The Defender Administration Console component will need to be un-installed, and a previous version installed. Please contact Quest support for assistance if required.
Previous Hotfixes
The following enhancements and issues were resolved in hotfix 5.7.0.4265.
Resolved Issues
Defect ID
Fixed an issue where the Defender COM Interface could fail after programming a token.
0004176
Fixed an issue within the Console 'About' dialog where the GrIDsure token allocation on the 'Token Summary' tab could be displayed as a symbol rather than a number until the count was complete.
0004406
Fixed an issue that could prevent the 'Send Email' option from being available after completing the token programming wizard.
0004428
Correctly removed the * symbol from a token when it is being displayed in a temporary DN state but the token assignment has been updated.
0004598
Modified the token programming wizard to allow the iToken to be programmed using Defender SNK, AES & 3DES modes as well as OATH Compliant.
0004677
Included additional RADIUS payload options to allow for the selection of User attributes to be returned in the payload.
Defender Security Server 5.7.0.4265 is required for this feature.0004748
The following enhancements and issues were resolved in hotfix 5.7.0.4199.Resolved Issues
Defect ID
Provided a configurable performance enhancement for large installations such that Defender will always use the AD server that ADUC is connected to when reading / writing data that requires linked attributes e.g. user and token data.
This is implemented by creating a new registry DWORD as detailed below:
x64 - HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\PassGo Technologies\Defender\Defender AD MMC\ADSIx86 - HKEY_LOCAL_MACHINE\SOFTWARE\PassGo Technologies\Defender\Defender AD MMC\ADSI
Value: DWORD - Allow serverless bind
Leave the value set to 0 to implement this feature.
Or by using the new Group Policy administrative template (DefenderBindingGroupPolicy.adm) provided with this hotfix.0004239
0004269
0004270
Included an enhancement to the Token activation email, sent by the console, such that it can now be sent in either HTML or plain text. This is implemented using the updated Defender Administrative template (DefenderGroupPolicy.adm) provided with this hotfix.
When sending the email in HTML format an option to automatically activate soft tokens on Android and iPhone devices is included.0004276
Included a new option on the 'Mobile Provider' tab of a token policy providing additional configuration options for SMS tokens.
Defender Security Server hotfix 5.7.0.4199 is required to support this feature.0004371
Included a modification to allow for temporary helpdesk token responses to be assigned to tokens where the AD linked attribute has not yet been created (the token serial number will have an asterisk when in this condition). This condition can occur when AD replication has not completed.
0004219
Improved the process for locating a Global Catalog server so that newly created objects are immediately visible in search dialogs e.g. when creating a new token Policy and assigning this to an Access Node.
0004418
The following enhancements and issues were resolved in hotfix 5.7.0.4090.Resolved Issues
Defect ID
Fixed an issue related to token programming where under certain circumstances an application failed error could occur
0004045
Optimizations to improve the performance of the console during token programming or when viewing licensing information.
0004099
Modified the Token properties dialog to allow the same token to be assigned to more than one user.
0004108
Improved the installation process to address an issue that could result in the installation process appearing to stop responding
0004203
Modified the 'Select Token Mode' dialog for iTokens to only allow OATH compliant tokens to be programmed.
0004204
-
添付ファイル