My Technet

In the third part of this post we have covered the following components.

• Installed the SCOM Reporting on DB Server
• Installed the SCOM 2007 R2 MS role on MS Server

In this part, we will be:

• Installing ACS collector on MS Server and create the ACS Database
• Uploading ACS Reports on DB Server

Installing ACS collector on MS Server and create the ACS Database

• Double click SetupOM.exe from SCOM R2 media to launch the SCOM R2 setup.
• Click Install Audit Collection Server under Install to start the installation process.

• On the Welcome page, click Next.
• On the End User License Agreement (EULA) page, accept the agreement, and then click Next.
• Click Create a new database on Database Installation Options and click Next.

• Leave the value of Data Source name default and click next on the Data Source page.

• On the Database page, select Remote database server and type the DB server name in the machine name field, leave the database server instance name blank and Database name also default. Click Next.

• Specify the location of Database files on the Database Creation Options page. Click Next.

Note: Make sure that you have enough space on the drive where you are going to save ACS database as it consumes a lot of space (after you have enabled ACS forwarders on the agents) unless you have applied good filtering. ACS filtering is the process s of filtering the unnecessary events collected by the ACS server. Unfortunately, it is outside the scope of this post.

• On the Event Retention schedule, you can accept the default values of change it as per the requirements. Click Next.

• On the ACS stored Timestamp Format page, select Local option, and then click Next.

• On the Summary page, review the installation options, and then click Next.
• During the installation, you will be prompted for a SQL Server Login. Accept the default and click OK.

• Click Finish to complete the installation.
• On the SQL Server, open the SQL Server Management Studio tool, open the Databases folder, and confirm the presence of the OperationsManagerAC database.
• On the ACS management server, open Server Manager tool, expand the Configuration container and select Services, and confirm that the Operations Manager Audit Collection Service is present, that it is started, and that the Startup Type is set to Automatic.

Uploading ACS Reports on DB Server

• Logon to DB server with the credentials of ScomAdmin1.
• Open SQL Management Studio and verify that ScomAdmin1 is the DB owner of ACS database.

• Create a temporary folder, such as E:\AcsReporting.
• On your SCOM R2 installation media, go to \ReportModels\acs and copy all directory contents to the temporary installation folder.
• Open a Command Prompt window by using the Run as Administrator option, and then change directories to the temporary acs folder. Run the following command.

UploadAuditReports “<AuditDBServer\Instance>” “<Reporting Server URL>” “<path of the copied acs folder>”

Note: Remove the quotes before running the command or you will get an error.

• Open Internet Explorer and enter the following address to view the SQL Reporting Services Home page. http://DBServerName/Reports.
• Click Audit Reports in the body of the page .

• And then click Show Details in the upper right part of the page.

• Click the Db Audit data source.

• In the Connect Using section, select Windows Integrated Security and click Apply (If not already there).

That concludes the fourth part and also the SCOM deployment post series. Once this basic setup is ready you can proceed with the Agent deployment, Import the Management Packs and start monitoring.

Obviously, there is a lot of other configurations stuff which can be done. Anyways, if you need more information you can leave a comment, I will try to help. Thanks!

Happy Monitoring!

Tags: acs collector, acs reporting, scom audit collector

You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.

1. My Technet » Blog Archive » Deploying SCOM 2007 R2 – Part3 Says:
   April 4th, 2010 at 5:55 pm

   [...] concludes Third part of SCOM 2007 R2 deployment series. In the next part, we will look at the following [...]

2. banki Says:
   March 3rd, 2011 at 10:14 pm

   Hello, I also have got mine own blog and I really want to write on it what I found on yours. You wrote interesting things and I want to use your words on my blog. Is that OK?? Thanks.

3. Vineet Says:
   March 4th, 2011 at 1:41 pm

   You can but have to put a reference to my blog….

4. Tor Says:
   July 5th, 2011 at 6:46 pm

   Hi
   I’m planning to install 2 MS servers to connect all scom agents instead of connecting all clients to RMS server. but still did not find a way to do so. can you tell me how to accomplish this..?
   Thanks
   Tor

5. Vineet Says:
   July 6th, 2011 at 11:47 am

   Hi,

   Have you looked at following documentation?

   http://technet.microsoft.com/en-us/library/bb432140.aspx

   Thanks,
   Vineet

6. Tor Says:
   July 6th, 2011 at 1:57 pm

   Thanks Vineet

7. Cheap Web Hosting Providers Says:
   August 1st, 2011 at 1:55 pm

   I appreciate, cause I found exactly what I was looking for. You’ve ended my 4 day long hunt! God Bless you man. Have a great day. ByeThe Best Web Hosting

Name (required)

Mail (will not be published) (required)

Website