Desining SCOM for Multiple location Mainly for ACS purpose
Hi, I have a project that will use SCOM to monitor windows server in multiple locations with single forest.Locations are further classified below : 1 Primary Site( P1 ) 2 Secondary Site ( S1 , S2 ) 300 Branch Sites Link between P1 - S1 = 10 MBPS Link between P1 - S2 = 10 MBPS Each Secondary Sites has 150 Branch Sites connected to it with a 64 kbps link. Each Branch site has a Domain Controller. we need to design ACS infrastructure to collect security logs from all branch domain controllers and store them in a single database located at the primary site. Kindly help me out with the design Regards Syed
March 29th, 2011 8:07am

Now you have to keep in mind the following stuff : A collector is in fact a Management server with the ACS functionality and Microsoft recommends to have all the MS on the same site that the OpsDB/DWDB. You need to have one DB per collector, so if you want to have only one db, you don't have any solution, you have to use only one collector. Now, a group of collectors could use the same reporting server, so why to you want to have only one DB ? FYI, MS provided a DB size calculator http://blogs.technet.com/b/momteam/archive/2008/07/02/audit-collection-acs-database-and-disk-sizing-calculator-for-opsmgr-2007.aspx What do you plan as data retention ? How many DC ? How many servers ? a collector server could manages 150 DC OR 3000 members servers OR 15 000 Workstations. Currently, how is your design ? Are you using gateway server for the remote sites ?Christopher Keyaert - My OpsMgr / SCOM & Opalis blog : http://www.vnext.be
Free Windows Admin Tool Kit Click here and download it now
March 29th, 2011 10:07am

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

Other recent topics Other recent topics