SCOM2007: Audit Collection Services (ACS) Reports Installation and Configuration

One question we seem to get around here a lot concerns the installation of ACS.  You put in the CD, you install Audit Collection Services and do everything the deployment guide tells you, but then in the console you can't find your Audit Reports.  What's the deal?  Well, there are a few more steps you'll need to be sure to complete in order to get these working and I've listed them below:

1. Create a "C:\TOOLS\AUDIT REPORTS\ACS" folder on the server that is hosting Audit Reporting.  In the next steps we'll refer to this server as <WhateverYourAuditReportingServerNameIs>. 

2. Copy uploadauditreports.cmd, the Models and Reports folders from the System Center
Operations Manager 2007 CD (located at ReportModels\ACS\) into the folder you just created.

3. Copy the reportingconfig.exe from the SCOM 2007 CD (under the Support Tools folder) to the same folder you created in step #1.

4. On the server, open a CMD prompt, change to the "c:\tools\audit reports\acs" directory and run the following command:

UploadAuditReports “" "<WhateverYourAuditReportingServerNameIs>"
“http://<WhateverYourAuditReportingServerNameIs>/reportserver" “c:\tools\audit reports\acs"

Click OK on any dialog you receive.  This creates a new data source called Db Audit, uploads the reporting models Audit.smdl and Audit5.smdl and uploads all reports in the ACS\REPORTS directory.

5. Open Internet Explorer and enter the following in the address bar:


This opens the SQL Reporting Services’ Home page.

6. Click Audit Reports

7. Click Show Details (located in the upper right part of the screen).

8. Click on the Db Audit data source.

9. In the Connection string box, verify the text that starts with "data source =" reads:

data source=" "<WhateverYourAuditReportingServerNameIs>;initial
catalog=OperationsManagerAC;Integrated Security=SSPI

10. Under the Connect Using section, change from "Credentials are not required" to
"Windows Integrated Security" and click Apply.

11. On the top of the page, click Audit Reports to get back to the audit report

12. To test, log on and off of a couple of machines that you enabled audit collection on.  Then, back on the Operations Manager server, open http://<WhateverYourAuditReportingServerNameIs>/reports and under Audit Reports, click the Usage - User Logon report. This report displays logon activity of the specified user in the specified time period on computers that have audit collection enabled.

- J.C. Hornbeck

Comments (3)

  1. Anonymous says:

    thank you

  2. Anonymous says:

    Hello, I am having a problem with the installation of Audit.smdl and Audit5.smdl, each and every time I try to install Audit Reports on my reporting server.

    In our test environment we have 6 virtual servers dedicated to SCOM 2007 pilot work. We have configured the first 4 as 1 RMS, 2 Secondary Management Servers and 1 dedicated SQL database for OperationsManager DB. 5th server has Windows Server 2003 Standard Edition with SP2 as operating system and SQL Server 2005 Enterprise with SP2 installed. We have configured this server as a Management Server, than installed ACS database and ACS server role. The 6th server is the reporting server and holds the OperationsManagerDW, ReportServer and ReportServerTempDB databases. I follow the exact same steps as you refer to: Copy UploadAuditReports.cmd and ReportingConfig.exe files and also the inside of acs folder into a directory named as c:acs on the reporting server. Than I open the command window and write exactly as


    It runs and then throws two warnings saying that

    Warning(s) loading file Audit.smdl

    Warning(s) loading file Audit5.smdl

    The audit reports come and yes they work, however these audit reports do not have any description below where I should be viewing the Report details:

    It simply says

    Description Unavailable

    for each and every audit reports. Besides I cannot open the Audit_Report_Template and Audit5_Report_Template.

    Since there is just the OperationsManagerAC database on the ACSSERVER, I don’t know if it matters using the /instance part for this installation, anyways I tried writing as


    The result is the same, I get the exact same warnings for audit.smdl and audit5.smdl, no matter.

    Please, give me an idea about this problem, these warnings really bother me a lot.

Skip to main content