Docker – Issues installing Windows Identity Foundation (WIF) on Docker Server Core 2016

dockerwindows-server-2016windows-server-core

When I run the following command:

Enable-WindowsOptionalFeature -Feature -Online Windows-Identity-Foundation

on a container based on windowsservercore, I get the following error:

Enable-WindowsOptionalFeature : Feature name Windows-Identity-Foundation is unknown.

This command works on the same version of Windows 2016 Enterprise MSDN distribution. I'm assuming this is a feature decided to not include in WindowsServerCore. Does anyone know of a way to install it? All of the WIF 3.5 downloads either fail due to a certificate issue or says its not for this version of Windows.

Is it that they decided not to include the feature in WindowsServerCore? Looking for insight and/or solutions please. My need is to be able to use WIF on 2016 Server Core, but using Enterprise is likely to be a licensing concern (creating docker images should not require the consumer to use Enterprise Windows, right?)

Best Answer

Please check if that KB help, not the same symptom as you have, but the explication explain your issue;

To install Windows Foundation in Windows Core, you must apply the Minimal Server Interface. The Minimal Server Interface binaries are not present in Windows Core installation. To obtain these binaries, you must use the Features on Demand component or an alternative installation source.

You can also install (and uninstall) features remotely from Windows Server Manager on a remote installation of Windows 8 or Windows 2012. For information about how to do this, see the "More Information" section.

Reference: You can't install Windows Identity Foundation in Windows Core

How to fix reference: Configuring the Minimal Server Interface

Related Solutions

How to install dotNet Framework 3.51 on Windows Server 2012 core

You can use Powershell to show the available Windows Features:

Import-Module ServerManager
Get-WindowsFeature | out-file C:\WindowsFeatures.txt -width 300

Because the data is a long and wide it is better to pipe it into a file and review it there.

it shows that '.NET Framework 3.5 Features' are available, but '.NET Framework 3.5 (includes .NET 2.0 and 3.0)' has been removed.

However, the files are still on the DVD, you can use:

dism /online /enable-feature /featurename:NetFX3 /source:D:\sources\sxs /all /LimitAccess

or the PowerShell 'Add-WindowsFeature' commandlet to install it:

Add-WindowsFeature –name NET-Framework-Core -source D:\sources\sxs

Edit: On Server 2012 R2 with Update 1 installed (KB2919355) this doesn't work if you are using the original DVD/ISO. You need a DVD or ISO which includes that update. For new installations, install .NET 3.5 before you apply KB2919355.

Powershell – Is it possible to get a windows-version from a powershell command on Windows Server 2016 Nano

You could try the following, I've not got a nano server to try it out on. Drop the select if it gets you something else and see if what you want is stored under a different property in Server 2016 Nano

Get-CIMInstance -ClassName Win32_OperatingSystem -Property * | select caption

When tested on a real Nano instance the -session parameter was not needed, but if you need it at some future date, here's the variant with -session:

$cuser = "Your username"
$cservername = "Your Servername"
$csession = New-CimSession –Credential $cuser –ComputerName $cservername
Get-CIMInstance –session $csession -ClassName Win32_OperatingSystem -Property * | select caption

Best Answer

Related Solutions

How to install dotNet Framework 3.51 on Windows Server 2012 core

Powershell – Is it possible to get a windows-version from a powershell command on Windows Server 2016 Nano

Related Topic