• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 298
  • Last Modified:

SMS 2003 to SCCM

I am in the middle of upgrading SMS 2003 to SCCM and I'm stuck.

Once you set a server to be a child of a parent site, does it automatically create the package directory and copy all of the packages over to the new server?

It's already replicated the Collections, Advertisements and Package information (and padlocked them on the child), so I know it's doing 'something', I just don't know if it's done ALL of what it needs to do (before I install SCCM on the new server).
1 Solution
This is a cool article for a side by site migration.

If all packages, advertisements and collections are replicated you could remove the relationship between the sites. All the objects will remain on your new site.
But: The package path is the same as it was on the old site. You have to change that manually, or with the help on a script
Use the Copy Packages Wizard native to SCCM 2007:


Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Train for your Pen Testing Engineer Certification

Enroll today in this bundle of courses to gain experience in the logistics of pen testing, Linux fundamentals, vulnerability assessments, detecting live systems, and more! This series, valued at $3,000, is free for Premium members, Team Accounts, and Qualified Experts.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now