-
Title
TPAM Required Operating System Patch Prerequisites for TPAM Version 2.5.920 - Hotfix OSPatch_3106991 -
Description
This hotfix includes the changes outlined in the following sections. One Identity may generate additional hotfixes for future releases of the product.
This patch applies several Microsoft patches. Additional maintenance is included as prerequisites for upgrading to the TPAM 2.5.920 release preparing for TLS 1.2 support including SP3 for SQL Server. This patch is required before applying the 2.5.920 upgrade. The minimum version required for installing this hotfix is 2.5.913.NOTE: This is an OS Patch and it is not possible to remove it.
-
Resolution
Please download the hotfix, TPAM Hotfix OSPatch_3106991 for KB 250954, by clicking here.
Resolved issues
The following is a list of issues resolved in this hotfix.
Issues resolved in hotfix 10021:Resolved Issue Issue ID Microsoft KB3106991 - Hotfix rollup 3106991 for the .NET framework 2.0 SP2 in Windows Server 2008 R2. 10021 Microsoft KB3081320 - Security update for Schnannel to address spoofing. 10021 Microsoft KB2979597 - SQL Server 2008 R2 Service Pack 3. 10021 Microsoft KB3144114 - TLS 1.2 support for Microsoft SQL Server. 10021
Applicability of this hotfix
Products affected by this hotfix:Product Name Version TPAM 2.5.913 - 2.5.919
Installing this hotfix
To install the hotfix:
1. Take a backup of the TPAM appliance.
2. Copy the supplied .zip file to your local computer.
3. Log in to the TPAM /admin interface.
4. Put TPAM at a Run level of Maintenance.
5. Reboot the TPAM appliance.
6. After TPAM reboots, log back in to the admin interface and select Maint | Apply a Patch from the menu.
7. Click the Select File button.
8. Click the Browse button. Select the patch file that you saved locally.
9. Click the Upload button.
10. Type the key provided on the download page in the in the Key box.
11. Type /genkey in the Options box.
12. By default, if applying a patch to a primary member of a cluster, the replicas in the cluster will be listed and highlighted in the Target Replicas list. If any of the replicas are deselected, the patch will not be applied to it, unless it is directly applied by logging on to the replica or applying to the replica through the CLI/API.
IMPORTANT: Since the patch is replicated to the replicas sequentially, for an environment with many replicas, it may be worth applying the patch to the replicas individually through the CLI. When done through the CLI the patch will be applied simultaneously, instead of in sequence.
13. Click the Apply Patch button.
14. After the patch has applied to the primary and all the replicas, reboot the primary and all the replicas.
15. Put the TPAM primary back at a Run Level of Operational.
Verifying successful installation
To determine if this hotfix is installed:
1. Click the Patch Log tab.
2. To set the log refresh interval, select Refresh Results every X seconds.
3. Once the hotfix has been applied there will be a message in the patch log stating “Patch successfully applied to system”.
Removing this hotfix
To remove this hotfix:
It is not possible to revert this hotfix. -
Change Request
10021 -
Attachments