Configuring SQL Reporting Services user permission for Configuration Manager 2007

Using SQL Reporting Services is really a “blast”. If you want to use the reporting feature with Configuration Manager 2007 R2 (and you do!), you need to configure a few accounts, groups and configure permissions. In this post I assume that SQL Reporting Services is installed and configured.

Accounts to be created

• Execution Account (Configured in the SQL Reporting Services manager)
  • The EA is used by SRS to execute reports used for subscribtions. The account should be a low privilige account that has:
    • Read access to all reports
  • Open a browser and type SQLReportingSername/Reports
  • Click Properties
  • Click New Role Assignment
  • Fill in the domain\account name and select the Browser role
    
  • Click OK to finish the configuration
• Dataset Authentication Account (configured in the Config Mgr. console)
  • A SQL login and db_datareader user mapping to the Configuration Manager database.
  • To assign the correct permission to the account open SQL Studio Management.
  • Select Security, Logins
    
    
  • Right click Login and select New User
    
    
  • Click Search and add the domain account. Select the SMS_Sitecode as the default database and click OK
    
    
  • Right click the new Login name and select Properties.
  • Select User mapping. Select the SMS_sitecode database and map the user to the DB_datareader.
    
    
  • Click OK and close SQL
  • Open the Configuration Manager console.
  • Navigate to Computer Management, Reporting, Reporting Services, Servername.
  • Right click the reporting services server and select Properties.
  • In Data source settings type the database servername (and instance if needed) and the name of the SMS_sitecode database.
    
    
  • Select Data Source Authentication and select Credentials stored securely in the report server. Fill in the data source authentication account like domain\account. Select Use as windows credentials when connecting to the data source.
    
    
  • Click OK 

The same account can be used as both Execution and Data source authentication. The permissions in this example also enables the account to be used for subscription purposes.

Groups to be created

• Reporting Viewers
  • Members who have read access to the reports. Add the group to the SQL Reporting Services Browser role as described earlier in the post..
• Reporting Administrators
• Members who can publish reports, create subscriptions etc. Select all the roles in the New role assignment.

Easy setup of SRS with SCCM R2

SQL Reporting Services Reporting

The SQL Server Reporting services product is a reporting platform that provides advanced reporting functionality currently not available in the existing Config Manager reporting solution. Building the Config Manager reporting solution on this platform enables advanced reporting scenarios for the Config Manager administrator and enables future extensions and improvements to further enhance the Config Manager product from a reporting perspective.
Config Manager 2007 R2 with SQL Reporting Services Integration enables rich reporting and advanced information gathering and delivery for current and future configuration management releases, by providing rich reports highlighting the strengths of the product to executive level audiences and enable the Config Manager administrator to perform their job more effectively.
SQL Reporting Services Integration is being added as a reporting solution for Configuration Manager 2007 R2 to accomplish the following goals:

• Provide best in class reporting capability by integrating SQL Reporting Services, with the leading change and configuration management product: SCCM 2007
• Enable Ad-hoc reporting - Make it easy for both SCCM administrators, and non administrators to find the information they need to make the right decisions for their business
• Integrate core SRS functionality without requiring significant changes to the Configuration Manager product
• Assist customers by migrating both existing reports and customer generated custom reports to the SRS solution
• Integrate Reporting Services side by side with the existing Configuration Manager reporting solution, so customers can slowly migrate to the SRS solution
• Implement a new Reporting Services Point that can be added as a site role to an existing or new SCCM Site System that has SQL Reporting Services already installed
• Support alternative databases as the reporting database, such as a replicated or backup database
• Provide ability to convert out of the box classic SCCM reports and to convert customer- generated reports to SQL Server reports.
• Allow custom report creation via a report authoring wizard.
• Enable report browsing and viewing via the SRS Report Viewer.
• Take advantage of rendering in all supported SRS formats, report caching, and subscriptions.

Planning for SQL Reporting Services

The following considerations should be taken into account when configuring the Configuration Manager 2007 R2 SQL Reporting Services feature.

Performance

Location of SQL Reporting Services Installation - Configuration Manager 2007 R2 supports locating the SQL reporting server on the site server or a remote computer. However, for performance reasons, you should locate the SQL reporting server and the reporting services point on a remote site system.

Security

Unattended Report Processing Account - If you intend to allow report subscriptions, you must configure an execution account to allow these to run unattended. This account must be a Windows user account. If you configure this account with a password expiry date, or if you change its information in Active Directory, you must also update this information in Reporting Services. You should set read-only permissions to reports for this account.
Credentials Options when Configuring the Connection to the Configuration Manager Database - Use the option, Credentials are not required in the Report Server Properties: Data Source Authentication Tab for testing purposes only. This setting is not recommended for a production environment.

Best Practices for SQL Reporting Services

Optimize SQL Reporting Services Queries - Optimize your report queries. Usually, the bulk of report execution time is spent executing queries and retrieving results. If you are using SQL Server, tools such as Query Analyzer and Profiler can help you optimize queries.
Report Subscription Scheduling - Whenever possible, schedule report subscription processing to run outside of normal office hours. This will reduce load on the reporting server and improve availability for ad-hoc report requests.

Prerequisites for SQL Reporting Services

SQL Reporting Services in Configuration Manager 2007 R2 has external dependencies and dependencies within the product.
The following table describes the external dependencies for SQL Reporting Services running in Configuration Manager 2007.

Dependency	More Information
A SQL Reporting Services reporting server must be installed and configured in the site hierarchy.	Before you can use SQL Reporting Services integration in Configuration Manager 2007 R2, you must configure reporting services on a SQL Server installation in your network. For more information about installing and configuring SQL Reporting Services, visit the SQL Reporting Services Web site at http://go.microsoft.com/fwlink/?LinkId=111840.
SQL Reporting Services requires Internet Information Services (IIS) 6.0 or later for the Reporting Services Web Site.	For more information about installing Internet Information Services, see your Windows Server documentation. Note Computers running Windows Server 2008 require further configuration of Internet Information Services to operate as sccmshortname site systems.

The following table describes the dependencies within Configuration Manager 2007 for running SQL Reporting Services.

Dependency	More Information
The site server must be running Configuration Manager 2007 R2.	SQL Reporting Services requires Configuration Manager 2007 R2.
Reporting services point site system role.	The reporting services point site system role must be configured before you can use SQL Reporting Services.

Configuring Microsoft SQL Server for SQL Reporting Services

Before you can use SQL Reporting Services integration in Configuration Manager 2007 R2, you must configure reporting services on a SQL Server installation in your network. The following steps will allow you to install the SRS Component of SQL:
1. From the installation media you used to install SQL Server 2005, run setup.exe to launch the SQL Server Setup Wizard.
2. Accept the end user license agreement, then click Next.
3. Review the Installing Prerequisites page, and click Next.
4. After SQL Server setup performs a configuration check, the Welcome page of the SQL Server Installation Wizard is displayed. Click Next.
5. Review the results of the system configuration check to identify any problems that may prevent the configuration of SQL Server from completing successfully. Click Next.

Note:

If you receive an Edition Change Check warning message, you must reapply any previously applied SQL Server Service Packs after you have finished configuring the software.

6. On the Registration Information page, enter your name, company name and product key, then click Next.
7. On the Components to Install page, make sure that Reporting Services is selected, then click Next.
8. On the Instance Name page, specify a name for the instance of SQL Server you are upgrading. If you are upgrading the default instance of SQL Server, select the Default instance check box, then click Next.
9. On the Service Account page, specify the account details that the reporting services service will use to log in. Check the Reporting Services check box to start the reporting services service after setup completes. Click Next to continue.
10. On the Report Server Installation Options page, verify that the option Install but do not configure the server is selected, then click Next.
11. On the Error and Usage Report Settings page, select whether you want to inform Microsoft of any error and usage data for SQL Server, then click Next.
12. On the Ready to Install page, review the information shown, then click Install.
13. After installation is complete, click Next.
14. On the Completing Microsoft SQL Server 2005 Setup page, review any information shown, and click Finish to close the wizard.
15. If you need to reapply the Service Pack, please do so at this time before moving on to the next section.

Configuring SQL Reporting Services in SQL Server 2005

1. From the Windows Start menu, navigate to Microsoft SQL Server 2005 / Configuration Tools, then click Reporting Services Configuration.
2. In the Report Server Installation Instance Selection dialog box, specify the name of the server hosting SQL Reporting Services, select the database instance from the drop-down menu, and then click Connect.
3. In Reporting Services Configuration Manager, click Server Status. Verify that Service Status is set to Running. If it is not, click Start, and then click Apply.
4. Click Report Server Virtual Directory, and then click New to specify a new virtual directory.
5. In the Create a New Virtual Directory dialog box, select Default Web Site from the Website drop-down list, and specify the name you want to call the virtual directory created by Reporting Services (or use the default ReportServer), then click OK.
6. Ensure that Apply default settings is selected, then click Apply.
7. Click Report Manager Virtual Directory, and then click New to specify a new virtual directory.
8. In the Create a New Virtual Directory dialog box, select Default Web Site from the Website drop-down list, and specify the name you want to call the Report Manager virtual directory created by Reporting Services (or use the default Reports), and then click OK.
9. Ensure that Apply default settings is selected, then click Apply.
10. Click Web Service Identity. If you do not want to change the defaults in this section, click Apply.
11. Click Database Setup, select a server from the Server name drop-down list, and then click Connect.
12. In the SQL Server Connection Dialog dialog box, specify the SQL Server name and connection details for the Reporting Services server, then click OK.
13. On the Database Connection page of Configure Report Server, click New.
14. In the SQL Server Connection Dialog dialog box, specify a name for the new Reporting Services database (or use the default, ReportServer), then click OK.
15. Click Apply to complete configuration of the new database.
16. Click Email Settings. Specify the following information:

Note:

If you do not want to use report subscriptions, you do not need to complete this step.

Sender Address: Specifies the email address that will appear as the sender address of any email sent from SQL Reporting Services. The account specified must have sufficient permissions to send email from the specified SMTP server.
Current Delivery Method: Specifies that the delivery method used to send emails will be via. SMTP server. This is the only delivery method you can configure through reporting services configuration. For details about configuring other delivery methods, see the SQL Reporting Services documentation.
SMTP Server: Specify the name of the SMTP server to use when sending reports. This can be a local or remote server.
17. Click Apply.
18. Click Execution Account. Specify the domain\username and password of a Windows user account that will be used to run unattended reports, for example those used by subscriptions. Click Apply.

Note:

If you do not want to use report subscriptions, you do not need to complete this step.

19. Click Apply, and then click OK.
20. Click Exit to close Reporting Services Configuration Manager.

Creating a Reporting Services Point for SQL Reporting Services

Before you can use SQL Reporting Services in Configuration Manager 2007, you must configure a reporting services point. The reporting services point is a site system role that must be configured on a server running Microsoft SQL Server with the Reporting Services component installed.
Use the following procedure to create a reporting services point on a Configuration Manager 2007 site system computer.
1. In the Configuration Manager console, navigate to System Center Configuration Manager / Site Database / Site Management / - / Site Settings / Site Systems.
2. Determine whether to create a new site system or add the reporting services point site role to an existing site system, and then follow the associated step.
To create a new site system and add the reporting services point role:
Right-click Site Systems, click New, and then click Server.
On the General page of the New Site Role Wizard, specify the name of the server that will be used to host the reporting services point.
To add the reporting services point role to an existing site system:
□ Right-click the site system name, and click New Roles.
3. On the General page of the New Site Role Wizard, configure the general settings for this site system, then click Next. Click Next.
4. On the System Role Selection page of the wizard, select Reporting Services point, then click Next.
5. On the Reporting Services Point page, specify the folder that will be created on the report server to contain the SQL Reporting Services reports used in Configuration Manager and then click Next.

Note:

The folder will not be created on the report server until you create reports or copy reports into SQL Reporting Services.

6. Review the information shown on the Summary page, then click Next.
7. Click Close to exit the wizard.

Configuring Properties for the Reporting Services Point

Before you can begin to generate reports in the Configuration Manager 2007 R2 console using SQL Reporting Services, you must configure properties for the reporting services point.
Use the following procedure to configure the reporting services point.
1. In the Configuration Manager console, navigate to System Center Configuration Manager / Site Database / Computer Management / Reporting / Reporting Services, and expand the node.
2. Right-click the reporting services point server you want to configure, then click Properties.
3. On the General tab of the Report Server Properties dialog box, review information about the currently selected report server.

Note:

Information about the report folder will only be shown after you have created a new report or copied existing reports to this report server.

4. On the Data Source Settings tab of the Report Server Properties dialog box, specify the Configuration Manager 2007 database server and database name to be used as the data source for SQL Reporting Services reports. Click the test button to verify that you have correct data entered.
5. On the Data Source Authentication tab of the Report Server Properties dialog box, specify the credentials used to access reports on the report server.
6. On the Data Source Security tab of the Report Server Properties dialog box, specify permissions for the users who have access to the data source specified in the Data Source Settings tab.
7. On the Security tab of the Report Server Properties dialog box, specify the users who have access to the selected report server.
8. Click OK to close the Report Server Properties dialog box.

Copying standard Configuration Manager reports to Reporting Services

In Configuration Manager 2007 R2, standard reports can be copied to a folder on a Reporting Services server by using the Copy Reports to Reporting Services Wizard. Use the following procedure to copy existing Configuration Manager reports to Reporting Services.
Use the following steps to copy standard Configuration Manager reports to Reporting Services.
1. In the Configuration Manager console, navigate to System Center Configuration Manager / Site Database / Computer Management / Reporting / Reporting Services Reporting.
2. Right-click the Reporting Services server that the standard reports will be copied to, then click Copy Reports to Reporting Services.
3. On the Data Source Settings page of the Copy Reports Wizard, specify the Configuration Manager 2007 database server and database name from which to copy the reports.
4. Click Next.
5. On the Data Source Authentication page of the Copy Reports Wizard, choose the authentication method required to run the copied reports on the reporting point server.
6. Click Next.
7. On the Select Reports page of the Copy Reports Wizard, select the reports you want to copy to the reporting services point. Select Overwrite existing reports if you want to overwrite any reports that already exist on the reporting services point.
8. Click Next.
9. On the Security page of the Copy Reports Wizard, specify which users can access the copied reports and the roles they must belong to. For more information about the options on this page, see Report Server Properties: Security Tab.
10. Click Next.
11. On the Summary page of the Copy Reports Wizard, review the reports that will be created, and then click Next.
12. After the reports are copied, click Next.
13. On the Confirmation page of the Copy Reports Wizard, review the information, and then click Close to exit the wizard.

Note:

If a report fails to import, it will be indicated by a red cross. Double-click the entry to open the Details dialog box, which lists details of the error in copying the report.

SCOM 2007 - How To Raise Alerts Using WMI Event Rule (and get the desired variable in alert description)

I post this after one of my customers requirement. He asked me to create a rule that raises an alert if a service in automatic startup mode is stopped.Here is how i did:

• Go to the Authoring pane and create a new rule.

• Select Alert Generating Rules -> Event Based -> WMI Event (Alert). Store the new rule in a specific Management Pack (not Default one).
   

• Give a name to your rule and select Windows Server as rule target.

• Enter root\cimv2 for the WMI Namespace and the following query: select * from __InstanceOperationEvent within 60 where TargetInstance isa 'Win32_Service' and TargetInstance.StartMode = 'Auto' and TargetInstance.State = 'Stopped'. This query will catch wmi events raised each time a windows service in automatic startup mode enters the stopped state. Enter 60 seconds as the Poll Interval. More info about such WMI queries here

• Leave the default setings for the alert configuration for the moment.

 

•  As a test let's stop the Automatic Updates service on the RMS. We can see alert is raised but nothing in this alert tells us which service has stopped.

 

•  To see which parameters can be inserted in the alert we have to look inside the alert in the database. Open SQL Management Studio, open the OperationsManager database and open the dbo.Alert table. Find our alert using the TimeRaised column and copy the content of the Context field.

 

•  Paste that content into a XML editor. By expanding the XML tree we can see that the caption of the stopped service is there inside tags EventData -> DataItem -> Collection Name="TargetInstance" -> Property Name="Caption".

 

• To get this value inside our alert description, open the rule we created and open the alert properties. By doing some logic comparison with the built-in parameters available for alert description I established that the following text would return our service's caption: $Data/EventData/DataItem/Collection[@Name="TargetInstance"]/Property[@Name="Caption"]$.

• A much efficient alert is now raised.

 

Solution: The ACS forwarder in Operations Manager 2007 may frequently log connection and disconnection events

Here's an issue I came across recently that I thought would be worth a mention here on our blog.  The issue is one where the ACS forwarder service shows frequent connections and disconnections on Windows XP POS computers but it could happen on any ACS Forwarder if the accounts being used or the permissions are configured incorrectly.  But first a little background:
The ACS Forwarder is a separate service (AdtAgent.exe) called the Operations Manager Audit Forwarding Service.  It is deployed automatically with the Operations Manager 2007 agent but must be explicitly enabled to initiate security log collection. The Operations Manager Audit Forwarding Service listens to the local Windows Event Log service and processes security events, in near real-time, then forwards the events to a central collector. During failover and connectivity outages the local Security log acts as the Forwarding Service queue.
After you install the ACS Collector and database you can then remotely enable this ACS Forwarding Service on agents through the Operations Manager 2007 console by running the Enable Audit Collection task.  By default the ACS Forwarding service runs using the Network Service Account, but since in Windows XP POS it does not have read permission on the security event log you may see frequent connection and disconnection events logged in the Operations Manager event log on the ACS Collector server:


Log Name: Operations Manager
Source: AdtServer
Date:
Event ID: 4628
Task Category: None
Level: Information
Keywords: Classic
User: NETWORK SERVICE
Computer:
Description: An Audit Forwarder connected.
Name: <>
Address: <>
Port: 266
DbId: 2
Value: 1
Log Name: Operations Manager
Source: AdtServer
Date:
Event ID: 4629
Task Category: None
Level: Warning
Keywords: Classic
User: NETWORK SERVICE
Computer: <>
Description: An Audit Forwarder disconnected.
Name: <>
DbId: 2
Value: 1
Reason: Forwarder initiated disconnect or connection broken.
Log Name: Operations Manager
Source: AdtServer
Date:
Event ID: 4628
Task Category: None
Level: Information
Keywords: Classic
User: NETWORK SERVICE
Computer: <>
Description: An Audit Forwarder connected.
Name: <>
Address: <>
Port: 2314
DbId: 2
Value: 1
For detailed troubleshooting you can enable debugging for the ACS Forwarder and gather more information. To enable verbose logging on a local Forwarder, create a new registry value and restart the AdtAgent service as shown below.  Just remember to turn off debugging when completed.
1. Browse to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\AdtAgent\Parameters
2. Create DWORD value = TraceFlags and set it to a decimal value of 524420.
3. Restart AdtAgent service.
4. Review log, C:\Windows\Temp\AdtAgent.log.  You'll probably see something similar to this:
[20100420 143003,721][Error  ]EventLogReader::Open(0x1520): 0x00000522
[20100420 143003,721][Error  ]OpenReaders(): EventReader::Open(Security) returned 0x00000522.
[20100420 143003,721][Warning]AgentRun(): Transmit() returned 0x00000522
[20100420 143003,721][Info   ]AgentRun(): Disconnecting after Transmit() returned 0x00000522.
Error Number 0x00000522 resolves to "A required privilege is not held by the client"
5. Turn off debugging when done by removing above created DWORD and restarting the AdtAgent service.
Resolution
There are two resolutions to fix this issue.
1. Grant Read permission on the security event log for the Network Service account.  For information on this see the following Knowledge Base article:
KB323076 - How to set event log security locally or by using Group Policy in Windows Server 2003
or
2. Change the “Log on As” value for the ACS Forwarding service from “Network Service” to “Local System”.
Hope this helps,

OpsMgr 2007 : How to Generate alerts based on generic CSV log file

Here's a small document I put up together to outline how to generate alerts out of the CSV file. Apparently the steps are outlined below and for convenience I have also attached the PDF with screen shots attached.

Step 1: Go to  Authoring TAB , right click on "RULES" and Select "Create New Rules"

Step 2: Expand Alert Generating Rules expand Event Based

Step 3: Select Generic CSV Text Log (Alert)

Step 4: Enter the rule name, Description. Click select to pick a target class.

Step 5: For testing purpose choose "Windows Computer"

Step 6: Enter the Directory path where log resides for ex " c:\logs "

Step 7: In the pattern you could include log pattern for ex ( FileDDMMYYY.log )

             file*.log to represent all log files

Step 8: You can specify the separator in the CSV ex , ; /

Step 9: Considering you might have multiple values separated by comma(or any other separator)

the next steps is to specify a condition generally Params/Param[1] would indicate first column in CSV file of the active row.

for purpose of this example proved Params/Param[1] matchregularexpression test

Step 10: Provide matching  alert priority/severity

 There are some special variables that you can use to print in alert description

===========================================================

Log file Directory :               $Data/EventData/DataItem/LogFileDirectory$

Log file name:                       $Data/EventData/DataItem/LogFileName$

Column Data:                       $Data/EventData/DataItem/Params/Param[1]$

===========================================================

In case you decide to use a monitor

====================================================

Log file Directory :             $Data/Context/LogFileDirectory$

Log file name:                         $Data/Context/LogFileName$

Column Data:                          $Data/Context/Params/Param[1]$

Ex test,abcd,efgh is the line

$Data/Context/Params/Param[1]$ should contain test

$Data/Context/Params/Param[2]$ should contain abcd and so on

====================================================

Download the document in the PDF format

How to create a computer group for VMware servers or Hyper-V servers

While tuning an Operations Manager environment that is heavily virtualized on VMware, we started receiving alerts that the “Total Percentage Interrupt Time is too high” on several of the virtualized servers. During discussions with the local virtualization SMEs, they indicated that this metric is handled differently in a virtual versus physical server configuration (see http://www.vmware.com/pdf/vmware_timekeeping.pdf and http://searchservervirtualization.techtarget.com/tip/0,289483,sid94_gci1373898,00.html) for details. To properly tune this environment we decided to create two groups:

• One for VMware servers
• One for Hyper-V servers

The intent was to then create overrides (or disable alerts) as we identified what needs to be handled differently on the virtual systems. 

Hyper-V Server Group

This process was very simple for the Hyper-V servers, as there is an existing attribute (Virtual Machine) that indicates if the server is virtual in Hyper-V. The steps to create this group from the Operations Manager console: Navigate to the Authoring space -> Groups, right-click and create a new group. We named ours Hyper-V virtual, and when we specified the dynamic members we defined them to where Windows Computer / Virtual Machine equals True.

Next, we checked the members of the group (right-click, view group members) to verify the group was working.

VMware Server Group

For VMware, we needed to create an attribute that would identify systems virtualized with VMware, and then use the attribute to populate the group membership. From the Operations Manager console -> Authoring space –> Management Pack Objects –> Attributes, we right-clicked and created a new attribute. We labeled the attribute as VMware tools, provided a description, defined it to a target of Windows Computer (which set it to Windows Computer_Extended) based upon a registry key, and stored it in a custom MP (not the default MP shown in the screenshot below).

Next we defined the registry setting as a key for the HKLM\System\CurrentControlSet\Services\VMTools if it exists, and to run daily (86400 seconds).

After adding this attribute, we used the Monitoring / Discovered Inventory view (which started as blank, but it soon added records as they were discovered; as shown in this next screenshot.

To complete the process we created a new computer group (Operations Manager console –> Authoring space -> Groups, right-click and create a new group) called VMware Virtual based upon the new attribute created in the Windows Computer_Extended class.
 
The end-result was two different computer groups that now represent the two different virtualization technologies available in this environment. These can be used as part of overrides to set different thresholds for alerts such as the “Total Percentage Interrupt Time is too high” alert discussed in the beginning of this posting.
 
Note: After this was posted, Pete Zerger pointed out the Virtual Machine Discovery MP for Operations Manager 2007 (http://www.systemcentercentral.com/PackCatalog/PackCatalogDetails/tabid/145/IndexID/12572/Default.aspx), which extends existing discovery of virtual machines to include VMware guests. This is a much cleaner solution than discussed above. Pete wrote this to make it easy to override hardware MPs so they leave VMs alone.

ConfigMgr 2007 Inboxes To Monitor

ConfigMgr 2007 inboxes with a backlog of files to be processed generally indicates a problem is occurring. As a result your infrastructure may suffer and may become problematic. Listed here is a list of the ConfigMgr 2007 inboxes that should be checked on a regular basis to ensure that your site(s) function as expected.

Auth\Dataldr.Box
A backlog of files can indicate problems accessing the site database.

Auth\Dataldr.Box\Process
A backlog of files can indicate problems accessing the site database.

Auth\Ddm.box\Bad_DDRs
A backlog of files can indicate a network corruption problem or a problem with the DDM

Auth\Sinv.Box
A backlog of files can indicate that the Software Inventory Processor cannot connect to the site database or that too many files were received.

Auth\Sinv.Box\Orphans
A backlog of files can indicate problems with specific clients, with management points, or with the network that could cause data corruption.

Compsumm.Box
A backlog of files can indicate that the Component Status Summarizer cannot process the volume of messages.

Dataldr.Box
A backlog of files can indicate problems accessing the Systems Management Server (SMS) database

Dataldr.Box\Badmifs
A backlog of files can indicate a bad custom MIF file or that a client computer cannot transfer the file correctly.

Ddm.Box
A backlog of files can indicate a bad DDR is preventing other DDR’s to process.

Ddm.Box\Bad_DDRs
A backlog of files can indicate a network corruption problem or a problem with the DDM

OfferSum.Box
A backlog of files can indicate a performance problem that is caused by a large number of messages.

Policypv.Box
A backlog of files in the policypv.box folder indicates that the policy provider component is not running.

Replmgr.Box\Ready
A backlog of files can indicate that the Scheduler is backlogged or is already processing files of the same priority

Schedule.Box
A backlog of files can indicate that the Sender cannot connect to or cannot transfer data to another site.

Schedule.Box\Outboxes
A backlog of .srq files indicates that the sender cannot process the number of jobs scheduled for that sender or that the sender cannot connect to or transfer data to another site.

Schedule.Box\Tosend
A backlog of files can indicate that many send requests are not completed or that the Scheduler has not yet deleted the files.

Sinv.Box
A backlog of files can indicate that the Software Inventory Processor cannot connect to the site database or that too many files were received.

Sinv.Box\BadSinv
A backlog of files can indicate problems with specific clients, with management points, or with the network, causing data corruption.

SiteStat.Box
A backlog of files can indicate a performance problem. Examine status messages for the Site System Status Summarizer for possible problems.

Statmgr.Box\Futureq
A backlog of files can indicate that some site systems' clocks are not synchronized with the site server.

Statmgr.Box\Queue
A backlog of files can indicate a problem with the Status Manager or that the component is trying to process too many messages.

Statmgr.Box\Retry
A backlog of files can indicate problems with the connection to the computer that is running SQL Server.

Statmgr.Box\Statmsgs
A backlog of files can indicate a problem with the Status Manager or that the Status Manager is trying to process too many messages

Swmproc.Box
A backlog of .sum and .sur files can indicate that the Software Metering Processor component cannot connect to the SMS database.

Additional Information:

Inbox Folders in Configuration Manager 2007
http://technet.micro...y/bb892790.aspx

Count Files In All The SMS inboxes And Send To Excel
http://myitforum.com/cs2/blogs/dhite/archi...7/23/22467.aspx

VBS Script To Count Objects In A Specified SMS Or ConfigMgr Inbox
http://myitforum.com/cs2/blogs/dhite/archi...gmgr-inbox.aspx

VBS Script To Count Objects In A Specified SMS Or ConfigMgr Inbox From A List Of Servers
http://myitforum.com/cs2/blogs/dhite/archi...of-servers.aspx

VBS Script To Count Objects In Specified SMS Site Server Inbox
http://myitforum.com/cs2/blogs/dhite/archi...rver-inbox.aspx