<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Packagesource on Anything About IT</title><link>https://www.verboon.info/tags/packagesource/</link><description>Recent content in Packagesource on Anything About IT</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 13 May 2013 20:08:57 +0000</lastBuildDate><atom:link href="https://www.verboon.info/tags/packagesource/index.xml" rel="self" type="application/rss+xml"/><item><title>How to change the SCCM 2012 Package Source Path with PowerShell</title><link>https://www.verboon.info/2013/05/how-to-change-the-sccm-2012-package-source-path-with-powershell/</link><pubDate>Mon, 13 May 2013 20:08:57 +0000</pubDate><guid>https://www.verboon.info/2013/05/how-to-change-the-sccm-2012-package-source-path-with-powershell/</guid><description>&lt;p&gt;Let’s assume you’ve just created a larger number of packages within SCCM 2012 and then you’re asked to move the package sources to a different location. I guess no-one on earth would want to visit each package and update the data source manually, So I wrote 2 scripts that automate this task. It could actually be done with one script, but when it comes to changing such things I prefer to validate things.&lt;/p&gt;</description></item></channel></rss>