I made a search in this forum before posting, as I didn't find a similar posting of what I want to find out. In SCCM 2007, when deploying a site server, SCCM 2007 does not verify whether the site code has already been used. My question is what is the impact if two servers having the same site coode are within the site?Valuable skills are not learned, learned skills aren't valuable.

Hello - No, It won't verify. You should not use same site code it's not supported scenario and the site can't get connected to the hierarchy.Anoop C Nair - This posting is provided "AS IS" with no warranties or guarantees, and confers no rights. |Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Is it that the only impact is - the site can't get connected to the hierarchy. Yes, I know should not use the same site code and is not supported, but I want to know what happen if same situation occurs, what are the problems that we shall see?Valuable skills are not learned, learned skills aren't valuable.

You can't predict the behaviour. You won't be able communicate with other sites and if it's secondary server you won't be able configure etc......Anoop C Nair - This posting is provided "AS IS" with no warranties or guarantees, and confers no rights. |Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Don't even try it ... you will get unpredicted results. Assignment is one thing that will not work. Content location (IOW locating package sources on DPs), upload of data (status messages, inventory etc) are also affected.Torsten Meringer | http://www.mssccmfaq.de

Never tried it as I don't see the need in why you want to do this. So the real question is why the same site code? I guess you will see issue with registering the ConfigMgr attributes in the System Management container as it contains generic names like SMS-Site-P00 (where P00 is the site code) and not specific to the site server name. I always see the site code as just a number and don't really care what it is as long as it is unique. The site name I use to identify the location or the purpose of the site. You are way for flexible with site names.Follow me through my blog and Twitter!

Agree with Torsten. Take a look at below technet article on Configuration Manager Site Naming and Re-Using Site Codes : Site codes should never be used more than once in a Configuration Manager 2007 hierarchy for active sites. If you have uninstalled a site that was publishing site data to Active Directory Domain Services in preparation for installing a new Configuration Manager 2007 site with the same site code more Via http://technet.microsoft.com/en-us/library/bb633287.aspx //Eswar Koneti @ www.eskonr.com

The problem lies in the fact that SCCM 2007 doesn't verify if the site code has already been in use. There is thus a chance that an administrator may unknowingly re-use a site code.Valuable skills are not learned, learned skills aren't valuable.

You can provide feedback to Microsoft using connect.microsoft.com if you think that this is an issue.Torsten Meringer | http://www.mssccmfaq.de

There is thus a chance that an administrator may unknowingly re-use a site code. Valuable skills are not learned, learned skills aren't valuable. Then you should replace the administrator.Follow me through my blog and Twitter!

I concur with Jannes. There's a chance the administrator might shutdown the system and reload the OS on a whim. There are entirely too many things to check for -- software always makes assumptions, it has to.Jason | http://myitforum.com/cs2/blogs/jsandys | Twitter @JasonSandys