wanderer Posted May 18, 2012 Report post Posted May 18, 2012 Hi, First, thanks for your excellent guides, the only way I got 2007 working. Just looking for some advice. We are using the AD site as the boundary for our existing 2007 SCCM. When I install 2012 in the same AD is it safe to add our new server in the "Delegate Control" bit of the Systems Management OU container - so both servers would have control? I'd use a different site name for the new server but I'm worried about one of our 2007 clients picking up the wrong site code. Our clients are in the build and we use Heartbeat discovery. I was thinking for 2012 making the boundary a test IP address range until I've migrated everything across. Or would it be safe to use the AD site here too? I don't know to what extent 2007 clients could see a 2012 server and vice versa. Has anyone already done this? Cheers, Stephen Quote Share this post Link to post Share on other sites More sharing options...
jkabaseball Posted May 21, 2012 Report post Posted May 21, 2012 What I did was move my 2007 server to use IP Range instead of AD Site boundry. I grabbed a chunk of IP address and added that boundry to CM 2012 and use that to test. All the rest of the IP Range is in the boundry for CM 2007. On the CM 2007 I added the IP ranges and then deleted the AD Site so I had a few seconds of overlap in case a client was trying to check in. I wanted to make sure that there was some kind of boundry when it went to check in that it would fall into that boundry. Quote Share this post Link to post Share on other sites More sharing options...
wanderer Posted May 25, 2012 Report post Posted May 25, 2012 Thanks jkabaseball, I'll give it a try, Quote Share this post Link to post Share on other sites More sharing options...
