<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Pki - Tag - byteben</title><link>https://byteben.com/tags/pki/</link><description>Pki - Tag - byteben</description><generator>Hugo -- gohugo.io</generator><language>en</language><managingEditor>ben@byteben.com (Ben Whitmore)</managingEditor><webMaster>ben@byteben.com (Ben Whitmore)</webMaster><lastBuildDate>Tue, 24 Jul 2018 00:00:00 +0000</lastBuildDate><atom:link href="https://byteben.com/tags/pki/" rel="self" type="application/rss+xml"/><item><title>Signing PowerShell Scripts for an SCCM App Detection Method</title><link>https://byteben.com/bb/signing-powershell-scripts-for-an-sccm-app-detection-method/</link><pubDate>Tue, 24 Jul 2018 00:00:00 +0000</pubDate><author>ben@byteben.com (Ben Whitmore)</author><guid>https://byteben.com/bb/signing-powershell-scripts-for-an-sccm-app-detection-method/</guid><description><![CDATA[<p>In this blog post we will look at signing the PowerShell scripts we use in the &ldquo;App Detection Method&rdquo; when distributing apps with ConfigMgr. The PowerShell Execution Policy can be modified in Client Settings to allow ConfigMgr to execute unsigned scripts. If your environment needs to be a bit tighter with script execution and you dont want to open up the Execution Policy, here is how you can sign the scripts using your own PKI infrastructure.</p>]]></description></item></channel></rss>