<div>
Use the Copy Packages Wizard native to SCCM 2007:<br />
<br />
<a href="http://technet.microsoft.com/en-us/library/bb632698.aspx" rel="ugc nofollow">http://technet.microsoft.com/en-us/library/bb632698.aspx</a><br />
<br />

</div>


Use the Copy Packages Wizard native to SCCM 2007:

http://technet.microsoft.com/en-us/library/bb632698.aspx [http://technet.microsoft.com/en-us/library/bb632698.aspx]



<div>
<div class="content wysiwyg-content">
I am in the middle of upgrading SMS 2003 to SCCM and I'm stuck.<br />
<br />
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?<br />
<br />
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).
</div>
</div>


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).

SMS 2003 to SCCM

Windows Server 2003 was based on Windows XP and was released in four editions: Web, Standard, Enterprise and Datacenter. It also had derivative versions for clusters, storage and Microsoft’s Small Business Server. Important upgrades included integrating Internet Information Services (IIS), improvements to Active Directory (AD) and Group Policy (GP), and the migration to Automated System Recovery (ASR).