• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 65
  • Last Modified:

2 SCCM Primary Servers in same domain

Hi All,

I am currently in the process of creating a new sccm server (current branch). This is to replace our old SCCM 2007 environment.

The reason i am not doing a side by side upgrade is due to our plan to upgrade all pc's to windows 10.

Our 2007 SCCM is live for our w7 pc's. I do not require any of the information to be migrated e.g. packages, OS images etc. i would like to set up a new sccm current branch environment and set this up with windows 10 images and packages and test deployment building just windows 10 computers / packages.

I am aware that both site codes need to be unique, i am just a little confused when it comes to boundaries. Our 2007 environment boundaries are set by IP subnet. When i configure the new SCCM current branch will i have problems if i set the same IP subnet boundaries?

The end goal is to have W10 clients going to the new SCCM current branch and then phase out the 2007 SCCM as pc's are replaced with W10. Once all W7 clients are upgraded i can decommission the 2007 SCCM.

Apologies if any of the above does not make sense i am rather new to SCCM.

Many Thanks
0
WycombeAbbey
Asked:
WycombeAbbey
  • 4
  • 3
1 Solution
 
Nagendra Pratap SinghDesktop Applications SpecialistCommented:
Overlapping boundaries are allowed for content.


https://www.petervanderwoude.nl/post/overlapping-boundaries-and-configmgr-2012/

https://technet.microsoft.com/en-us/library/gg712679.aspx

But make sure that you do not use GPO etc to assign sitecode etc because you should be moving few clients every hour to the new SCCM. Also disable auto client push or logon/WSUS based installs.


What you are trying to do is perfectly fine and fairly straightforward. If the environment is not large then you should be able to do it in 3 stages in a week itself. You can even push 2012 client using 2007.
0
 
Mike TLeading EngineerCommented:
Hi,

I have to question the reasoning. Why do want to double everything up so you have two environments, two sets of hardware, licensing etc. to "keep W7 separate from W10"? I don't see any value there. You can easily upgrade in place and then manage your W7 clients with Current Branch technology which is far better than 2007 AND get the option to start deploying W10 whenever you like. You will not have any worries about boundaries, pushing clients etc. I found the same links as Nagendra posted above, and yes, you *can* do it, without caveats, but I really question why bother. It sounds like an expense you can avoid for no real gain.

If there's something obvious I am missing here, please say!
Note, if your current 2007 is messy and you want a clean start, then I would say clean it up then upgrade. Looking after 1 CM environment is tough. Looking after two, simultaneously is a challenge I would avoid.

Mike
0
 
WycombeAbbeyAuthor Commented:
Our 2007 environment is well out of date hardware and software wise and somewhat of a mess.

The reason i would like to setup a completely new environment is because we do not need any of the client information or packages as these are for W7, the new environment will be setup in readiness for our w10 roll out. I can still do a migration if this makes more sense but i wouldn't want to bring across much if any packages / collections etc.

The new setup would be fresh and only for w10, that way we could leave the existing sccm setup in place until we have fully upgraded to win10 at which point we could decommission the old 2007 sccm.

I am a rookie in sccm terms and have been left to pick an old messy system which will need upgrading very soon so we can move over to w10.

any further advise would be greatly received.

Thanks
0
Cloud Class® Course: MCSA MCSE Windows Server 2012

This course teaches how to install and configure Windows Server 2012 R2.  It is the first step on your path to becoming a Microsoft Certified Solutions Expert (MCSE).

 
Mike TLeading EngineerCommented:
Hi,

Thanks for the explanation. The best advice I can give is for you to research the best way to install CM. If you just do a Next, next Finish install then you're really going to suffer further down the road. The tips are:

1) use on-box SQL - remote SQL is just complicating things and gains nothing
2) Choose the fastest storage you can afford - SQL hits your hardware hard; it needs IOPS so fast disks will give great performance. SSDs or equivalent would make it rocket
3) Add more "spindles" not just disks/partitions. You need several disks and each one needs to be a separate physcial disk. Don't just buy a big disk and split it into volumes. TempDB needs the fastest disk so at the very least make that a separate disk.
4) PRe-create your DBs with a script. This aligns the DBs with sectors and reduces fragmentation later
5) Do plan to SQL maintenance and do it regularly. There's a good script out there for it!
6) Plan your collections well and don't EVER deploy anything to ALL SYSTEMS. That's the way to needing a CV/resume. Don't just sit there and add collections willy-nilly after the install.
7) Finally, use Scopes and Roles to protect the system using RBAC. Have one full admin to install it and after that only use System Operator role and delegate other roles as required. I would even require training proof before letting anyone on it. It's a dangerous tool in the wrong hands!

I hope that all makes sense. Read lots from the MVPs and experts and look up what I've mentioned. There are some great blog out there and too many to list, but you just have to stitch them together for what you want :).

Mike
1
 
WycombeAbbeyAuthor Commented:
Thanks Mike,

In terms of hardware, we have a brand new server with various disks, all 15K disks. SQL is also installed on the same server.

Thanks for the information and pointers!

Thanks

Daniel
0
 
Mike TLeading EngineerCommented:
Hi - sounds like you are off to a good start. Put no_sms_on_drive.sms on ALL drives except the ONE you want, before installing CM (just a blank file with that name). This file stops CM writing its files to each disk you have. Because it will.

Mike
0
 
WycombeAbbeyAuthor Commented:
Thanks for the tip, would you advise putting the no_sms_on_drive.sms on the OS Drive?
0
 
Mike TLeading EngineerCommented:
Always!
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Cloud Class® Course: SQL Server Core 2016

This course will introduce you to SQL Server Core 2016, as well as teach you about SSMS, data tools, installation, server configuration, using Management Studio, and writing and executing queries.

  • 4
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now