Sizing of System Center 2016

I'm beginning the installation of system Center 2016 in my environment

Environment :
3 Sites :
Site A: Primary site
 - consists of about 100 users
 - three ESXi Host servers
- about 40 Windows Virtual servers.
Site B: DR site
 - consists of 4 users
 - Consists of three ESXi hosts ( basically used to host the DR environment )
Site C: Remote site
 - Consists of 20 users
- Two domain controllers and file and print server
- Users connect back to Site A to work

I'm having a difficult time sizing my environment for System Center. I'm trying to use a minimal amount of servers for the System Center environment,  we are in a constant struggle to reduce the amount of servers. Too many servers end up being a support problem, maintenance is difficult and refreshing that many servers every few years to install a new OS is an ongoing issue,  Basically all of our servers are 2012 R2 and later, about a 50/50 split with 2012R2 and 2016.

I currently installed System Center 2016 Configuration Manager on  a Windows server 2016 and SQL Server 2014 on that same Server.

I'm now looking to install Operations Manager and was hoping Operations Manager Databases could use the same SQL server as Configuration Manager.  Is that OK ?

I guess my overall question is how would the experts install System Center in an Environment like mine, with the client requesting minimal amount of servers
How many Servers ? and which components on each server.

Also If I install on as few servers as possible and have performance problems, Can I then move or reinstall components onto individual servers ?  If this is possible are there any components that once they are installed , I would not be able to separate pieces out ?

Let me know if anything need clarification

Thank you for you advice
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Ganesh Kumar ASr Infrastructure SpecialistCommented:
I assume you have the System Center Family pack which comprises of many products like Configuration Manager, Operation Manager, Orchestrator, Virtual Machine Manager, Data Protection Manager, System Center Service Manager. Let me put this though, i am not expertise on the Orchestrator and Service Manager but giving you some thought about the basics. Configuration Manager is good for managing servers and workstations if it is configured properly and SCOM is good for monitoring the Windows servers too. But if you want to automate the deployments, reduce the workloads then try to learn and use VMM and Orchestrator even Service manager. Orchestrator does everything for you if you setup proper work flow and VMM can do automatic VM deployment and monitor (similar like VCenter), but i vote for Vcenter it is better.

Have CMS server in HO and DP in the secondary and remote sites for SCCM. For monitoring servers use SCOM. Here is a short insight on the configurations.

SCCM server should be separate not mingled with any other System center products but can be same server having SQL though not recommended but based on the sizing of your environment single vm with 8 core vcpu, 24 / 32 GB ram, 200 GB for OS and 200 GB for Content Library will be sufficient. SSRS is required for reporting so you can install it on another server with light usage.

For SCOM minimum 2 vms are required, one for SCOM with all role and SSRS on another server with DW warehouse database. Configuration can be 4 core vcpu, 16 GB ram and 150 GB HDD would be enough. SSRS can be with 2 core, 6 GB ram and 100 GB disk space is enough.
EkuskowskiAuthor Commented:
Yes,  I own all the components of system Center. At this time monitoring of Servers and workstations using SCCM and SCOM is what I am looking to do.  Then I think I would like to start using for deployments and updates.

You say you vote for Vcenter, could you elaborate on that topic.  What can vCenter do that is also being handled by System Center - is it just monitoring ? or do you mean deployment, at this time I have a couple of Templates that I use to deploy servers in VCenter.

OK So I'll keep my SCCM  by itself with its own SQL database , and match your specs.
I'll install SCOM on a separate server meeting your specs
I'll also spin up another server for another SQL server with SSRS and SCOM Data Warehouse.

After I have this running and when I'm ready to add additional components for deployment and such , will they all need separate servers?
Like VMM , Orchestarto and Service manager ?

Thanks again for all your suggestions
Ganesh Kumar ASr Infrastructure SpecialistCommented:
Glad you have complete system Center product family.

SCOM is for monitoring of Servers not for workstations.

SCCM is for patch management or software deployment tool for workstations and servers.

Since you have ESXi host, i suggested native management tool (vcenter), If you have Hyper-v based then i would have recommended the VMM.  Moreover vCenter is just for managing your VM's. What you are doing for template in VCenter is perfectly okay.

SCCM with SQL on single server and if additional site have DP depends on the PC count and bandwidth you have got for the second site.

Remember SCOM is monitoring tool only for windows servers and network devices.

Having SQL server with SSRS and SCOM Data Warehouse each on separate server is sufficient enough.

Yes you need additional server for Orchestrator, VMM and Service manager if you have or planned to do with VMM. Service manager is for ticketing system and with more feature. Orchestrator is for managing the complete virtualization environment to orchestrate. I would suggest to take some training on the System Center products thoroughly so that you can yield good benefit from the product.

Important Note: VMM also supports ESXi host, may be you can try.
Learn Ruby Fundamentals

This course will introduce you to Ruby, as well as teach you about classes, methods, variables, data structures, loops, enumerable methods, and finishing touches.

Mike TLeading EngineerCommented:

I'd just like to add my comments:

how would the experts install System Center in an Environment like mine, with the client requesting minimal amount of servers
For so few clients (PCs or servers) you don't need much hardware-wise

SCCM    RAM      DISK                                                              NIC
              8GB       OS:120   DATA:200    WSUS:200                2 x 1GB

              16GB     OS:120   DATA: 300

The reason for the disk sizes is just growth. Experience of shoving your OS on a 60GB disk ended badly. Disk is cheap. Go for more now and avoid issues later.

With regards SQL, I would go "on box" for both CM and OM. You can however use the same SQL install for ALL System Center products, you just have to create a new instance for each product. Note CM and OM are big SQL users. Orchestra is very, very light-weight and will only use about 100MB. It does NOT need another server at all.

How many Servers ? and which components on each server.
You can get away with CM x1 and OM x1.  e.g.   WOS2016 + CM2016 + SQL2014 = Server1,  WOS2016 + OM2016 (pointing to Server1) = Server2
On Server1 add all roles for CM: MP + DP + FSP + SUP (+WSUS) + Reporting.
At each site you can install a DP (Distribution Point) on anything, from a PC to a server. It's just a small role that needs enough disk space. Any PC with a 500GB disk is enough, but if the OS is W7 or W10 you will hit the network connection limit of concurrent connections (20 I think?). Server OSes remove that limit. For very small sites you may find a DP on a PC might be fine. If it doesn't cope you can pop it into your File and Print server instead. You don't need a new server for this role but you need a DP at every physical site ideally to avoid network costs.

Also If I install on as few servers as possible and have performance problems, Can I then move or reinstall components onto individual servers ?  If this is possible are there any components that once they are installed.
If you have performance issues, then yes move roles off the CM box, but then you DO need another server. The key role to move off is Reporting (SSRS) which needs it's own instance or even own SQL install. This is just to protect the main CM box from dodgy reports the spike the CPU. It happens especially when learning reporting.

Finally SCOM 2012 can definitely monitor PCs and servers fine. There are more management packs for server roles, but there are MPacks for all OSes, including Windows 7.

I will qualify all the above setup by saying I have set this system up with similar hardware and just 2 servers that did CM and OM on PCs and servers. (up to 100 each).


Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Mike TLeading EngineerCommented:
I forgot - this article covers your question and has 2 good case studies
EkuskowskiAuthor Commented:
In the next few days I will actually begin the installation.
To start off I am going to follow Mikes design and see if two servers will suffice in my environment.
I appreciate all your advice
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
System Center Operations Manager (SCOM)

From novice to tech pro — start learning today.