Link to home
Start Free TrialLog in
Avatar of Aamer-
Aamer-

asked on

SCCM deployment

We are a group of companies. The management has recently decided to consolidate the management and monitoring of our company and two other sister companies. There will be not trust between the parent company and the two sister companies. The sister locations are located in two cities. I am asked to look into the design of SCCM and SCOM. High availability is required in every component possible. Must use a central sql server for all databases.  This is what I think I should suggest

In the Parent company
1.      Install SQL Cluster (Active/active) to host the databases for SCOM and SCCM
2.      Install a single site server with MP and DP roles
3.      Install and additional site system with MP and DP for HA
4.      Install sql reporting on the site server and create the database on the cluster
5.      Single primary site
In the sister companies
Two locations in each company

Company A

Site1: two sccm site systems with MP and DP roles in untrusted forest
Site 2: two sccm site systems with MP and DP roles in untrusted forest

Company B

Site1: two sccm site systems with MP and DP roles in untrusted forest
Site 2: two sccm site systems with MP and DP roles in untrusted forest
Add multiple forests to sccm site

System discovery of all computers in all three forests.

I am not sure of the SQL A/A clustering. Consoles need to be installed in each site so that admins can use remote tools and sw deployment to their respective clients.
Any suggestions appreciated

for SCOM I will install two Management servers  in the parent company and two gateway servers in each location. i.e total of 8 gateway servers in two companies with two sites
Avatar of Leon Taljaard
Leon Taljaard
Flag of South Africa image

Hi,

Here are a few links that will point you in the right direction and also guide you on what you have suggested above. Let me know if you would like additional information or need confirmation on more of the above.

Planning for High Availability with Configuration Manager

System Center 2012 R2 High Availability : Operations Manager

SCOM 2012 R2 Data Access Service (DAS) High Availability – Part 1: Configure A Static IP

Thanks
Leon
Avatar of Aamer-
Aamer-

ASKER

well I wanted to know if I am thinking in the right direction. I arrived at this design after reading and reviewing the docs referred by you
Hi,

Your design looks OK but you have missed out how many seats you need to serve. It will have a bearing on the number of DPs you need. You also missed link bandwidth. Don't leave it at default otherwise it will saturate. CM 2012 has excellent bandwidth tuning options. Size the DP caps according to the bandwidth your network team say, otherwise they may come looking for you...

Have at least two MPs. If you have many clients and/or lots of complex reporting to do you can offload the SQL reporting to any old box. The console itself is lightweight and you can go crazy with it installing on workstations. It just needs authorisation. Speaking of which lock down permissions hard using the role based access scopes. Give read-only to anyone who has only minor needs to access it. I would go further and require training or certification to even touch the console. Accidents happen. With three companies joining forces it's even more crucial.

Making CM highly available is more than just sticking the DB on a cluster though. If you Primary goes down your SQL might well still be up and "HA" but so what. There's no MP to do anything.
It makes it hard to justify splitting SQL off the primary server to me. You need both halves. Separating the two just complicates everything with firewalls, network etc. I prefer having SQL on-box personally.

Either way, you probably need to think about having a hot standby Primary. An MVP I know recommended being a boy scout and being prepared with a server ready built, patched and with all the ISOs and pre-reqs present but not installed for the day when something goes bang. Then it's just a case of installing CM and pointing to the DB.

You can of course script most if not all the install.

Mike
Avatar of Aamer-

ASKER

I am planning to install two Management points and two distribution points in in each location.
Yes that's fine, but you still don't say how *many* machines you have per site. There's a limit per DP of 4000 clients.
Avatar of Aamer-

ASKER

not more than 1000 clients per location
ASKER CERTIFIED SOLUTION
Avatar of Mike Taylor
Mike Taylor
Flag of United Kingdom of Great Britain and Northern Ireland image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial