Hi There, This is more of a confirmation for me. I have an existing SCCM 2007 R2 SP2 environment with 1400 devices. This is running of one server, as the DP, MP etc. I have configured a new SCCM 2007 SP2 R3 Server with all the same roles, plus the new ones. This server is going to replace the existing one. I have configured the new one to have the same site code as the existing one, and at the moment it has only my ip address as a boundary. What i want to know is how do i remove the old server and have the clients report to the new server, i beleive it is... A: Add boundries to new server B: Shut down old server C: Update some active directory field (i beleive it is this "Systems Management Server cannot delete the object "cn=SMS-SLP-NHL-OLDSERVERNAME" in Active Directory.") Is there anything else i need to do? as even installing the new client with /mp:NEWSERVERNAME still connects it to the old server (and i am within the boundary)

Clients will not automatically report to a new hierarchy: http://blogs.technet.com/b/configmgrteam/archive/2009/04/09/reassigning-a-configuration-manager-client-across-hierarchies.aspx. Using the same site code for the new hiearchy is asking for issues. How will you know if a client is assigned to the new or old site? The client will also be confused and I'm pretty sure that is unsupported. Also, there are more objects in AD than just the one to delete. You should also have one for the MP.Jason | http://myitforum.com/cs2/blogs/jsandys | http://blogs.catapultsystems.com/jsandys/default.aspx | Twitter @JasonSandys

is schema extended? is it in the same domain? i too am having this issuse and ran a simple script the only thing i did differently is not using same site code. try this: 1. make a batch file with the following setup string ccmsetup.exe /mp:server.domain.local SMSSITECODE=wtf SMSMP=server.domain.local SMSSLP=server.domain.local CMALLOWSILENTREBOOT=0 FSP=server.domain.local resetkeyinformation=true 2. try it one a few clients and see if they report in. 3. kill the boundary on the old server. 4. turn off client installation. 5. do a manual approve in the new server instead of automatic When in doubt...let Google help you out!

RE: How will you know if a client is assigned to the new or old site? In the client CCM console in control panel it says the site server name. Also the clients report as not having a client installed to the new MP. I know its not really supported using the same site code but basically im removing the old one and replacing the client installs with this one... Even if i have to use the old server to remove all the clients, then uninstall the SCCM components to remove the entries from AD. Just looking for some guidance

My question would be why don't you do a back and restore. Use ConfigMgr to back up the site server. Bring the new server up with the same name/IP settings then restore. As long as the logic is the same you should be fine and all the clients will be happy. http://www.sccm-tools.com http://sms-hints-tricks.blogspot.com

Would that work though? wont all the settings point to the name of server #2 when restored as opposed to the renamed #1 If that will work i have no issue doing that what so ever, what i don't want to do is import all the old ____ from the original server, bad packages, drivers, poor system layout/config.

If you did a backup restore then it would look exactly as you had it, same server name, gliches, packages etc. I was assuming you would create the new server with the same DNS name and IPaddress. If you want to avoid all that then yes give the server a new name, new site code and rebuild everything from scratch. http://www.sccm-tools.com http://sms-hints-tricks.blogspot.com

Thats my issue, i have the server setup perfectly with a new name new IP address etc. etc. The only issue was using the same site code. Is there no way to remove the existing server and migrate clients to the new one without a full rebuild? I dont mind how hard/tedious, as long as i dont need to rebuild.

i would do as i told you: make a batch file with the following setup string ccmsetup.exe /mp:server.domain.local SMSSITECODE=wtf SMSMP=server.domain.local SMSSLP=server.domain.local CMALLOWSILENTREBOOT=0 FSP=server.domain.local resetkeyinformation=true 2. try it one a few clients and see if they report in. either as an advertisement or manually 3. kill the boundary on the old server. 4. turn off client installation. 5. do a manual approve in the new server instead of automaticWhen in doubt...let Google help you out!

Thank you, i will mark that as the answer as im now told i cannot make the change till after Xmas due to change freeze. Thanks for your help

If you can’t make change until after Christmas, when rethink your decision to use the same site code! You are begging for trouble. You have 3 MVP telling you not to do it! Are really going to manually approve 1400 device? http://www.enhansoft.com/