We help IT Professionals succeed at work.

SMS 2003 and SCCM 2007 side to side migration Issues

Hi Experts,

We currently have and SMS 2003 running on a Windows 2003 Ent., Physical server, recently we deploy a SCCM 2007 SP2 on a Windows 2008 R2 (Hyper-V -  VM), we decided to extend the AD Schema after the SCCM installation and before extending the schema we configure everything but the boundaries.  After extending the schema made the SMS 2003 a child site, and keep the SCCM as Primary site, we have gone through the process of migrating SMS 2003 to SCCM 2007, I am able to see from the parent site the child site (which is the SMS 2003), but from the SCCM 2007 in the Addresses options under Site Settings, but I can see the primary site from the Child but it has an XXX – (Unknown) where XXX is the site name, we have followed the Flowchart provided by Microsoft, but we are stuck in the “Use an existing client installation method at the SMS 2003 site to upgrade and reassign clients to the new Configuration Manager site”

I have even executed “Preinst.exe /Syncchild XXX, I was able to see the child without the Unknown part (XXX – This is the name of the Child), but I can still see from the child the Unknown name.
I am attaching a screenshot of what I have, I can see the child from the parent, but I cannot see anything under the child, such as collection, packages, etc.
Watch Question

Have you configured the Computer Accounts in the local Groups SMS_SiteToSiteConnection_ZHL ?
Is the SCCM Site Server Computer Account in the local Administrators on the Secondary Site Server?
have you configured a secure key exchange? If no you have to exchange the key files.
Check out the Logs on both Servers



Thanks for replying, computer accounts have been configured in both servers ( Computer Accounts in the local Groups SMS_SiteToSiteConnection_ZHL) and SCCM computer account is on the local Administrator group in the SMS server.

I have not configured the secure key exchange, do not know how to do that, any ideas?

If you extended the AD and published the SCCM Site into it you can use the Secure Key Exchange method. When adding a Site Server to a SCCM Site they need to exchange the Keys for making sure it's a secure parent, or child server.http://technet.microsoft.com/en-us/library/bb633269.aspx
If you have enabled that option you your don't want to use it, then you need the preinst.exe to export the Keys and exchange them.
Please post the post both Servers logfiles if it does not work



Something that I need to mention is that the SMS 2003 is in a fully production environment, and when I deployed SCCM 2007 was in parallel, I ran the prerequisite checker and the only warning was the schema extension which I did after SCCM was installed, once I finished the install, I proceed to configure the following:

Client Agents (All of them)
Discovery Methods (All of them)
Client Installation Methods
DID NOT CONFIGURE the BOUDARIES: however, I am seeing the same boundaries from the parent site the same as the child site, but did not configured yet, in other words did not touch it, but apparently they showed up.

Completed the following:

So under Site Name > Site Settings > Site systems > Select the SCCM Server > Right click "ConfigMgr distribution point" > Properties > Tick "Allow clients to transfer content from this distribution point using BITS, HTTP and HTTPS) > Apply OK.


Go to the properties of "Configmgr management point" > Tick "Allow devices to use this management point" > Apply > OK

I have not use the wizard under Site System to deploy Management Point or Distribution Point, and like I mentioned before I am able to see from the parent site the child site with his full name, but from the child I can see the parent with the (Unknown).


I would like to know once that I complete the exchange key process as you stated above, IF this resolved my problem, should I be able to see my Collections and Packages from the Parent Site (SCCM) or Do I have to do this using another method?

Thanks in advanced for your help.  Look forward to hear from you.
Check that the SCCM Site is listed under the System Management Container in AD.
As long as you do not define any Boundaries your good to go

It seems that both Site Servers no not communicate correct. For this reason you cannot this the objects from your Secondary Site. The Site Settings of your SCCM Site do not matter at this moment. I don't know if the missing Key exchange is the reason. If yes then the replication of the objects should work.
You have made the SCCM Site as parent Site of your SMS Site?
Post a Screenshot of the Boundaries showing up on the SCCM Server.
Are the Addresses configured properly in both ways?
Logs, Logs, Logs :)

Also check out this guide:



I have made the SCCM my parent site of my SMS site, I'll place a screenshot of my boundaries of my SCCM server, the addresses are properly configured on both servers, such as:

SMS -> Addresses -> SCCM server
SCCM -> Addresses -> SMS server

I followed the link that you posted, and this is a little confusing in the following steps:

Do you need to migrate custom collections or software distribution objects to the new SCCM 2007 site? If so upgrade the SMS 2003 site to configuration manager using the in-place upgrade method.
 Since I had some collections and packages I wanted to migrate, I had to upgrade my existing SMS2003 to SCCM.
Detach the upgraded site from the hierachy and attach the new 2007 as a child site of it.

Note (Upgraded site=SMS2003 that you just upgraded and the New 2007 is the SCCM2007 that you first implimented)
SO, what I am understading is that in order to migrate custom collections or software distribution objects, I need to perform a in-place upgrade method on the SMS 2003 to SCCM 2007, but Could you explain this part to me:

"Note (Upgraded site=SMS2003 that you just upgraded and the New 2007 is the SCCM2007 that you first implimented)"

That's the part that is confusing, if you could detail this part, I'll have a better understanding of what I am doing.


The expert were negligent and none of the answers were accurate.


No more comments on this.

Explore More ContentExplore courses, solutions, and other research materials related to this topic.