Design suggestion
Hi,We are installing Configuration Manager in 2 sites with 700 computers in each site. Our concern is to minimize the downtime as much as possible. We are confused if we install 2 primary sites instead of a primary and a secondary. (if one site fails, how the clients will be assigned to the other site?)Is it necessary in such scenario to separate the database and cluster it?We are installing Operations Manager as well on a different server, but we are planning to co-locate it's database with the Configuration Manager's database. Any knowledge or experience for such a case?All suggestions are highly appreciated.Systems Engineer
March 8th, 2010 12:21pm

Hi,You can co-host the OpsMgr and ConfigMgr DB on the same server. But you might want to check your SLA's against it, reason is that if the server is down you loose two important products to manage your environment.You can install two sites and if one fails you change the boundary of the failed server to the other server. Clients will than roam to the new server.Follow me through my blog and Twitter!
Free Windows Admin Tool Kit Click here and download it now
March 8th, 2010 12:30pm

Hi, Will you use SQL reporting service for your SCCM(R2)? Keep in mind that OpsMgr Reporting CANNOT exist on the same server as ConfigMgr. The reason is the OpsMgr replace the security of SRS with it own version and ConfigMgr does not integrate with it.
March 8th, 2010 12:37pm

Thank you JannesSystems Engineer
Free Windows Admin Tool Kit Click here and download it now
March 11th, 2010 12:20pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics