If you're running SCCM 2012 script it. "Overly Simple Instructions"
1. Copy the package source files to your new server (keep the same folder structure) 2. Using the PowerShell cmdlets update each package with the new location I had to do this for our OSD related packages. My script enumerated all of the packages and checked the current source location. If the source server was the one that we were retiring my script would update the package with the new source location. In our environment the source for our packages are scattered across a couple of servers depending on what the packages are for. (i.e. all OSD packages are on our image development server). This way your package IDs remain the same and you don't have to go through the trouble of recreating everything from scratch. Mike From: [email protected] [mailto:[email protected]] On Behalf Of John Aubrey Sent: Tuesday, May 19, 2015 12:42 PM To: [email protected] Subject: [mssms] Migrating App Shares We currently have everything on one box, all SCCM rolls and the shares for the various stuff in SCCM (images, packages, drivers, apps..). My goal is to move the share folder with all the SCCM stuff to a different server. Is there an easy way of doing this, or is the best method delete everything and reimport it? I'm trying to break apart SCCM and the DP role + shares onto a different servers. --John ********************************************************** Electronic Mail is not secure, may not be read every day, and should not be used for urgent or sensitive issues
