How to Resolve Identity Management for UNIX Upgrade Blocks on Windows Server
Introduction
Upgrading Windows Server from 2008 R2 to 2012 R2 or 2012 R2 to 2019 often encounters a roadblock due to the presence of Identity Management for UNIX (IDMU). This guide provides step-by-step instructions to fix the issue, including removing IDMU components and editing the compliance.ini
file to bypass upgrade checks.
Step 1: Remove Identity Management for UNIX Components
The first step is to disable and remove IDMU features using PowerShell.
Instructions:
- Open PowerShell as Administrator.
Execute the appropriate command based on what needs to be removed:
- Remove all Identity Management for UNIX components:
1
Dism.exe /online /disable-feature /featurename:adminui
- Remove only Server for NIS:
1
Dism.exe /online /disable-feature /featurename:nis
- Remove only Password Synchronization:
1
Dism.exe /online /disable-feature /featurename:psync
- Remove all Identity Management for UNIX components:
- Restart the server to apply the changes.
Use the/quiet
parameter to restart automatically:1
Dism.exe /online /disable-feature /featurename:adminui /quiet
Step 2: Edit
compliance.ini
to Bypass Compatibility ChecksIf the upgrade still fails after removing Identity Management for UNIX (IDMU), you may need to bypass the upgrade compliance check.
Instructions:
- Copy the Windows Server setup ISO/DVD contents to a writable location, such as your local drive.
- Navigate to the following file within the copied setup content:
1
sources\compliance.ini
- Open the file using a text editor (e.g., Notepad).
- Locate the line containing:
1
IDMUUpgradeComplianceCheck
- Comment out the line by adding a # at the beginning or delete the line entirely:
1
# IDMUUpgradeComplianceCheck
- Save the file and retry the upgrade process.
This post is licensed under CC BY 4.0 by the author.