{"id":657,"date":"2020-02-07T23:44:44","date_gmt":"2020-02-08T04:44:44","guid":{"rendered":"http:\/\/itblog.ldlnet.net\/?p=657"},"modified":"2020-02-07T23:50:37","modified_gmt":"2020-02-08T04:50:37","slug":"adding-windows-capability-to-server-core-to-add-features-needed-for-application-compatibility","status":"publish","type":"post","link":"https:\/\/itblog.ldlnet.net\/index.php\/2020\/02\/07\/adding-windows-capability-to-server-core-to-add-features-needed-for-application-compatibility\/","title":{"rendered":"Adding Windows Capability to Server Core to add features needed for Application Compatibility"},"content":{"rendered":"\n

I’ve been working on installing Windows Server 2019 Core into my network to be able to look at new features for Windows Administration and learning how Server Core works. I was able to install a virtual machine with Server Core and get it activated. I then wanted to place my custom PowerShell script for loading PowerShell into the Server Core Environment.<\/p>\n\n\n\n

So, I added the Server Core Server to the Windows Admin Center and copied my custom scripts for PowerShell into the proper directory:<\/p>\n\n\n\n

\"Windows
Windows Admin Center<\/figcaption><\/figure>\n\n\n\n

I then logged on remotely to the server and started PowerShell. When I did that, I got this error with the script load:<\/p>\n\n\n\n

\"Error
Error that IE First Run has not been completed<\/figcaption><\/figure>\n\n\n\n

At first, I tried using the -UseBasicParsing as a switch to see if that would repair the issue in the script. It did not because, IE is not installed by default on the default installation of Server Core. That is so there is less of a footprint that can be attacked by a hacker. I needed this installed though so that the Invoke-WebRequest cmdlet would load my script parameters properly.<\/p>\n\n\n\n

I started looking for answers to how to install IE onto the Server Core box and found the following article<\/a><\/em><\/strong>. I had to run the Add-WindowsCapability cmdlet on the server to install the optional components. When I did, I received an error:<\/p>\n\n\n\n

\"Error
Error when adding the Windows Capability<\/figcaption><\/figure>\n\n\n\n

So I found out that there is a block that WSUS does keeping the cmdlet from going to the online source to download the software package and producing this error. After researching, I found this article<\/a><\/em><\/strong>. I setup a Group Policy to make sure this setting is propagated to my Server Core machine. I also setup in the same policy the ability to turn off the First-Run for IE so that you do not get that message and have to open IE to “set it up”<\/p>\n\n\n\n

\"Group
Group Policy Setting with Path to Templates Specified<\/figcaption><\/figure>\n\n\n\n

I then ran a gpupdate \/force on the Server and was able to download the components for IE and App Compatibility.<\/p>\n\n\n\n

\"Successful
Successful Installation of Windows Capability<\/figcaption><\/figure>\n\n\n\n

I then rebooted the server and now my PowerShell loads successfully:<\/p>\n\n\n\n

\"Successful
Successful PowerShell Load<\/figcaption><\/figure>\n\n\n\n

I learned a few different new things here and was able to get Server Core working more the way that I like it. I will keep posting updates when I run into issues with this type of installation. I would definitely give the Windows Admin Center a try as it has more robust features than Server Manager has, especially for Server 2019 and Server Core.<\/p>\n\n\n\n

CONQUER THE UNCOMFORTABLE TO GROW!
POSITIVE ATTITUDE ABIDES!<\/h2>\n\n\n\n

REFERENCES:<\/em><\/strong>
RSAT Tools Installation Error 0x800f0954 \u2013 Windows 10 1809<\/a><\/strong>
Server Core App Compatibility Feature on Demand (FOD)<\/a><\/strong>
\u201cSet Up Internet Explorer 11\u201d Bypass with GPO or Registry<\/a><\/strong><\/p>\n","protected":false},"excerpt":{"rendered":"

I’ve been working on installing Windows Server 2019 Core into my network to be able to look at new features for Windows<\/p>\n

Read More<\/a><\/p>\n","protected":false},"author":1,"featured_media":159,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[195,2,3,16],"tags":[227,15,8,20,228,226,120,224],"class_list":["post-657","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-azure","category-general","category-powershell","category-windows","tag-add-windowscapability","tag-cmdlet","tag-powershell","tag-windows","tag-windows-server-admin","tag-windows-server-core","tag-windows-updates","tag-wsus","odd"],"_links":{"self":[{"href":"https:\/\/itblog.ldlnet.net\/index.php\/wp-json\/wp\/v2\/posts\/657","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/itblog.ldlnet.net\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/itblog.ldlnet.net\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/itblog.ldlnet.net\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/itblog.ldlnet.net\/index.php\/wp-json\/wp\/v2\/comments?post=657"}],"version-history":[{"count":7,"href":"https:\/\/itblog.ldlnet.net\/index.php\/wp-json\/wp\/v2\/posts\/657\/revisions"}],"predecessor-version":[{"id":671,"href":"https:\/\/itblog.ldlnet.net\/index.php\/wp-json\/wp\/v2\/posts\/657\/revisions\/671"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/itblog.ldlnet.net\/index.php\/wp-json\/wp\/v2\/media\/159"}],"wp:attachment":[{"href":"https:\/\/itblog.ldlnet.net\/index.php\/wp-json\/wp\/v2\/media?parent=657"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/itblog.ldlnet.net\/index.php\/wp-json\/wp\/v2\/categories?post=657"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/itblog.ldlnet.net\/index.php\/wp-json\/wp\/v2\/tags?post=657"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}