<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>SCCM on John Billekens | Notes from the field</title><link>https://blog.j81.nl/tags/sccm/</link><description>Recent content in SCCM on John Billekens | Notes from the field</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>© 2026 John Billekens</copyright><lastBuildDate>Sat, 23 May 2020 21:44:57 +0000</lastBuildDate><atom:link href="https://blog.j81.nl/tags/sccm/index.xml" rel="self" type="application/rss+xml"/><item><title>Provisioning Target Device Unattended Deployment</title><link>https://blog.j81.nl/posts/provisioning-target-device-unattended-deployment/</link><pubDate>Sat, 05 Mar 2016 18:57:44 +0000</pubDate><guid>https://blog.j81.nl/posts/provisioning-target-device-unattended-deployment/</guid><description>&lt;p&gt;When deployoing the Citrix PVS Target Device software with for example SCCM or RES ONE Automation, this fails. As it turns out &amp;ldquo;CFsDep2.sys&amp;rdquo; is missing from the System32\Drivers directory. This is because during the (unattended) installation of the Target Device software the installation of &amp;ldquo;CFsDep2&amp;rdquo; fails. When you install the software by hand, everything is works as it should. This can be solved to run the following command after the installation of the Target Device Software.&lt;/p&gt;</description></item></channel></rss>