<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Package-Conversion-Manager - Tag - byteben</title><link>https://byteben.com/tags/package-conversion-manager/</link><description>Package-Conversion-Manager - 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>Wed, 30 Jan 2019 00:00:00 +0000</lastBuildDate><atom:link href="https://byteben.com/tags/package-conversion-manager/" rel="self" type="application/rss+xml"/><item><title>Converting legacy packages into applications with SCCM 1810 Package Conversion Manager</title><link>https://byteben.com/bb/converting-legacy-packages-into-applications-with-sccm-1810-package-conversion-manager/</link><pubDate>Wed, 30 Jan 2019 00:00:00 +0000</pubDate><author>ben@byteben.com (Ben Whitmore)</author><guid>https://byteben.com/bb/converting-legacy-packages-into-applications-with-sccm-1810-package-conversion-manager/</guid><description><![CDATA[<h3 id="background">Background</h3>
<p>Since SCCM 2012 Microsoft have been steering us towards using &ldquo;applications&rdquo; to install apps over the traditional &ldquo;packages&rdquo; method. Applications give us additional benefits over packages like detection methods, dependencies and requirement rules . An example might be:-</p>]]></description></item></channel></rss>