<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Windows-Server-2016 on When Software Attacks!</title><link>https://rikhepworth.com/tags/windows-server-2016/</link><description>Recent content in Windows-Server-2016 on When Software Attacks!</description><generator>Hugo -- gohugo.io</generator><language>en_GB</language><copyright>&amp;copy; Rik Hepworth</copyright><lastBuildDate>Fri, 24 Aug 2018 00:00:00 +0000</lastBuildDate><atom:link href="https://rikhepworth.com/tags/windows-server-2016/index.xml" rel="self" type="application/rss+xml"/><item><title>Configure Server 2016 ADFS and WAP with custom ports using Powershell</title><link>https://rikhepworth.com/posts/configure-server-2016-adfs-and-wap-with-custom-ports-using-powershell/</link><pubDate>Fri, 24 Aug 2018 00:00:00 +0000</pubDate><guid>https://rikhepworth.com/posts/configure-server-2016-adfs-and-wap-with-custom-ports-using-powershell/</guid><description>&lt;p&gt;A pull request for Chris Gardner&amp;rsquo;s WebApplicationProxyDSC is now inbound after a frustrating week of trying to automate the configuration of ADFS and WAP on a Server 2016 lab.&lt;/p&gt;
&lt;p&gt;With Server 2016, the PowerShell commands to configure the ADFS and WAP servers include switches to specify a non-default port. I need to do this because the servers are behind a NetNat on a server hosting several labs, so port 443 is not available to me and I must use a different port.&lt;/p&gt;</description></item></channel></rss>