Select Page

[:de]Windows Server 2016 Standard: Kompatibilitätscheck überspringen[:en]Windows Server 2016 Standard: Skipping Compatibility Check[:]

by | Nov 21, 2016 | Administration | 9 comments

This entry has been published on 2016-11-21 and may be out of date.

Last Updated on 2016-11-21.

[:en]Issue

Trying to install an in-place upgrade for Windows  2008 R2 -> 2012 R2 -> 2016 Server, it might come to a compatibility check issue which you cannot skip or accept by default.

With version 2016, some features like Unix Identity management features were removed. In some cases Windows Setup sees those components as installed even if they are not.

Solution

First make sure you run the DISM / ServerManagerCmd commands to uninstall the Unix identity features.

Then if you are absolutely sure they are not enabled any more and the compatibility check fails again, copy your Windows Server 2016 setup ISO/DVD content to a place where you have write permissions, e.g. your local HDD.

Edit sources\compliance.ini: Remove or comment the line which contains “IDMUUpgradeComplianceCheck”.

Save it and restart setup.[:]

9 Comments

  1. Seth
    Seth on 2019-02-03 at 04:13

    Thanks, appreciate this post. The DISM removal didn’t work. This command as Admin launching powershell did though: Remove-WindowsFeature RSAT-NIS

    • cathy
      cathy on 2021-07-31 at 19:18

      THANK YOU!!! I don’t know what I would do if people didn’t comment when they find a simple answer!! (M$ is no help at all! )

  2. Seth
    Seth on 2019-02-03 at 04:14

    Just this command works: Remove-WindowsFeature RSAT-NIS using powershell as admin.

  4. Selensch
    Selensch on 2019-10-25 at 11:05

    copy the dvd to a Folder and delete the line RdsUpgCheck.dll,IDMUUpgradeComplianceCheck
    from the file from “\sources\compliance.ini”

  5. gogoti
    gogoti on 2020-05-21 at 19:03

    copy the dvd to a Folder and delete the line RdsUpgCheck.dll,IDMUUpgradeComplianceCheck
    from the file from “\sources\compliance.ini”

    This worked!!!

  6. Roger
    Roger on 2020-06-03 at 07:02

    Seth’s comment helped me! Thanks

  7. steve
    steve on 2021-04-22 at 19:31

    Seth’s comment also worked for me.

Submit a Comment