<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Dsc on When Software Attacks!</title><link>https://rikhepworth.com/tags/dsc/</link><description>Recent content in Dsc 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/dsc/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><item><title>Setting Enroll Permissions on ADCS Certificate Template using DSC</title><link>https://rikhepworth.com/posts/setting-enroll-permissions-on-adcs-certificate-template-using-dsc/</link><pubDate>Thu, 02 Mar 2017 00:00:00 +0000</pubDate><guid>https://rikhepworth.com/posts/setting-enroll-permissions-on-adcs-certificate-template-using-dsc/</guid><description>&lt;p&gt;As part of the work I have been doing around generating and managing &lt;a href="https://rikhepworth.com/post/2017/03/2017-03-02-define-once-deploy-everywhere-sort-of" &gt;lab environments using Lability&lt;/a&gt; and DSC, one of the things I needed to do was change the permissions on a certificate template within a DSC configuration. Previously, when deploying to Azure, I used the &lt;a href="https://rikhepworth.com/post/2015/08/2015-08-30-complex-azure-template-odyssey-part-two-domain-controller" &gt;PSPKI PowerShell modules within code executed by the Custom Script extension&lt;/a&gt;. I was very focused on sticking with DSC this time, which ruled out PSPKI. Whilst there is a DSC module available to configure Certificate Services itself, this does not extend to managing Certificate Templates.&lt;/p&gt;</description></item></channel></rss>