Search the Community

Hi, I need your advice about migrated sccm2007 AD entries(SMS-MP-SiteCode-SiteServerName, SMS-SLP-SiteCode-SiteServerName and sccm2007 sitecode) that still exists in system management container, sccm 2012 client installation on some machines failing because they are still contacting with old sccm2007 MP and assigned to sccm2007 site code "Name: 'MP.x.x.x.com' HTTPS: 'N' ForestTrust: 'N' LocationServices 4/25/2016 1:38:12 PM 3780 (0x0EC4)" log file attached. we are using GPO for site assignment. please help to answer following Qs: - is deleting migrated sccm2007 AD entries from system management container, will help on sccm2012 client installation? - what is best practice to delete sccm2007 MP and site code from system management container? thanks in advance. LocationServices.txt

I currently have SCCM2012R2 installed on Windows Server 2008R2 and a SQL Server 2008R2 instance installed on a separate Windows Server 2008R2. I would like to Install a new SCCM 2012R2 on a new Windows Server 2012R2 that will also run a SQL server 2012 instance on the same server and have a new site code. I'm not too worried about the current data that I have in the current SCCM 2012R2 Server. I can set up all the automatic deployment roles and all my OSD task sequences all over again that is not the problem. What I wanted to know is what is the best way of pointing all my current clients to the new SCCM 2012R2 Server that will have the new site code? Group Policy? I will be going from SCCM 2012R2 to SCCM 2012R2 so the current client on all workstations will be the same version as the new Server with the new site code. What are best practices when attempting this? Has anybody done this yet?

We have building out our new SCCM 2012, we had it in our R&D and everything was wonderful, the person I have been working with to do the install seemed to know what she was doing, very cautious. BUT, when she did the install in production she used the same site code, even though I had told her to use a new one, actually the same as we had used in the R&D We had not planned to do a migration, we planned to start from scratch and push out the new client as well as re add all our software and OS images, the old 2007 had a crash a few months back and has been limping along so we thought this was a better way to go. So, what factors are going to come to play as we are not ready to make the switch yet? Wish we could change the Site Code, be so much easier. Thanks for any advice, comments. Derek