Topic last updated—November 2007

You can monitor inbox folders on a Microsoft System Center Configuration Manager 2007 site to help troubleshoot problems with different components. This article lists some of the Configuration Manager 2007 inbox folders.

You should periodically examine the Configuration Manager 2007 inbox folders for a backlog of files that wait to be processed. The inbox folders temporarily store files before they are processed to the site database or transferred to another site or site component. A backlog of files can indicate that a component is not running or is experiencing a problem. For example, when the Microsoft SQL Server database runs out of space, a backlog of files occurs until the files are processed to the site database.

Inbox Folders

\Auth

This folder and its subfolders are used by Configuration Manager 2007 sites, management points, and clients. Configuration Manager 2007 uses these folders to temporarily store hardware, software, and discovery data records (.ddr files).
\Auth\dataldr.box

This folder stores .mif files that represent hardware inventory data for Configuration Manager 2007 client computers. This folder also stores IDMIF files for custom architectures. A backlog of files can indicate problems accessing the site database. Examine the status messages for the Inventory Data Loader for possible problems. You can also examine the Dataldr.log file for errors or additional information.
\Auth\dataldr.box\process

This folder stores .mif files that are in process. A backlog of files can indicate problems accessing the site database. Examine the status messages for the Inventory Data Loader for possible problems. You can also examine the Dataldr.log file for errors or additional information.
\Auth\ddm.box

This folder temporarily stores .ddr files after a client or server agent generates a discovery record. Examine the status messages for the Discovery Data Manager (DDM) for possible problems. You can also examine the Ddm.log file for errors or additional information.
\Auth\ddm.box\BAD_DDRS

This folder stores .ddr files that are corrupted. A backlog of files can indicate a network corruption problem or a problem with the DDM. Configuration Manager 2007 automatically deletes .ddr files that are older than 25 hours. Examine the status messages for the Discover Data Manager component for possible problems. You can also examine the Ddm.log file for errors or additional information.
\Auth\sinv.box

This folder stores client software inventory files (.sic and .sid files) that are copied from the management point. A backlog of files can indicate that the Software Inventory Processor cannot connect to the site database or that too many files were received. Examine the status messages for the Software Inventory Processor for possible problems. You can also examine the Sinvproc.log file for errors or additional information.
\Auth\sinv.box\Orphans

This folder stores hardware and software inventory that cannot be processed. Inventory files that are moved to this folder are retried later. A backlog of files can indicate problems with specific clients, with management points, or with the network that could cause data corruption. Examine status messages for the Software Inventory Processor for possible problems. You can also examine the Sinvproc.log file for errors or additional information.
\Auth\statesys.box

This folder stores information related to state messages. For more information about state message backlogs, see Troubleshooting State Message Backlogs.
\Compsumm.box

This folder contains component status summary messages from child sites. A backlog of files can indicate that the Component Status Summarizer cannot process the volume of messages. Examine status messages for the Component Status Summarizer for possible problems. You can also examine the Compsumm.log file for errors or additional information.
\Dataldr.box

This folder stores .mif files that represent hardware inventory data for Configuration Manager 2007 client computers. This folder also stores IDMIF files for custom architectures. A backlog of files can indicate problems accessing the Systems Management Server (SMS) database. Examine status messages for the Inventory Data Loader for possible problems. You can also examine the Dataldr.log file for errors or additional information.
\Dataldr.box\Badmifs

This folder stores corrupted .mif files for hardware inventory or custom IDMIF files. A backlog of files can indicate a bad custom MIF file or that a client computer cannot transfer the file correctly. Configuration Manager 2007 automatically deletes all files in the \Badmifs folder that are older than 14 days. Examine status messages for the Inventory Data Loader for possible problems. You can also examine the Dataldr.log file for errors or additional information.
\Ddm.box

This folder temporarily stores discovery data records (.ddr files) after a client or server agent generates a discovery record. Examine status messages for the Discovery Data Manager (DDM) for possible problems. You can also examine the Ddm.log file for errors or additional information.
\Ddm.box\BAD_DDRS

This folder stores .ddr files that are corrupted. A backlog of files can indicate a network corruption problem or a problem with the DDM. Configuration Manager 2007 automatically deletes .ddr files that are older than 25 hours. Examine status messages for the DDM for possible problems. You can also examine the Ddm.log file for errors or additional information.
\Despoolr.box\Receive

This folder stores the data that is received from a child site or a parent site. Typically, files are processed and moved as soon as Configuration Manager 2007 receives the instruction file (.ins file). Examine status messages for the Despooler for possible problems. You can also examine the Despool.log file for errors or additional information.
\Inventry.box

This folder temporarily stores hardware inventory files from management points after clients transfer their hardware inventory to the management point. The Inventory Processor converts the .nhm file to a binary .mif file and then moves the file to the \Dataldr.box folder. Examine status messages for the Inventory Processor for possible problems. You can also examine the Invproc.log file for errors or additional information.
\OfferSum.box

This folder receives summarization messages (.sum files) for advertisements from child sites and processes the files to the site database. A backlog of files can indicate a performance problem that is caused by a large number of messages. Examine status messages for the Offer Status Summarizer for possible problems. You can also examine the Offersum.log file for errors or additional information.
\policypv.box

This folder temporarily stores policy changes for the Configuration Manager 2007 components. Whenever the policy of Configuration Manager 2007 components change, a notification file appears in this inbox, causing the policy provider to regenerate the policies. A backlog of files in the policypv.box folder indicates that the policy provider component is not running. The policy provider component might not be able to read the site control file, or the component cannot write to the database. You can examine the Policypv.log in the \Logs folder on the site server for errors or additional information.
\Replmgr.box\Incoming

This folder receives files from the SMS despooler after processing files from other SMS sites. The SMS Replication Manager determines whether the file is transaction-oriented and then verifies that the serial numbers are correct. If the file is not transaction-oriented, no additional verification is performed. The Replication Manager transfers the file to the recipient component for final processing. Examine status messages for the Replication Manager for possible problems. You can also examine the Replmgr.log file for errors or additional information.
\Replmgr.box\Outbound

This folder temporarily stores files that are destined for another site. This folder also contains three outbox subfolders that correspond to the priority of the files. For example, this folder can contain \High, \Low, and \Normal folders. When the Replication Manager detects files in one of the outbound directories, the Replication Manager waits for additional files before moving the files to the \Process subfolder and then to the \Ready subfolder. Examine status messages for the Replication Manager for possible problems. You can also examine the Replmgr.log file for errors or additional information.
\Replmgr.box\Ready

This folder stores files that are compressed for transmission to remote sites. The files are moved to the Scheduler for transmission. A backlog of files can indicate that the Scheduler is backlogged or is already processing files of the same priority. In this scenario, the Scheduler has to wait for the transmission to complete. Examine status messages for the Replication Manager for possible problems. You can also examine the Replmgr.log file for errors or additional information.
\Schedule.box

This folder stores mini-job files (.job files) that were created by the Replication Manager. The Scheduler turns the .job files into Sender jobs. A backlog of files can indicate that the Sender cannot connect to or cannot transfer data to another site. A backlog can also indicate that the Scheduler cannot process the mini-job files because files are missing from the \Schedule.box\Uid folder. Examine status messages for the Scheduler for possible problems. You can also examine the Sched.log file for errors or additional information.
\Schedule.box\Outboxes

This folder contains the outbox folders for each installed sender. In the sender's outbox folder, you can find send request files (.srq files) or send request status files (.srs files). 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. Examine status messages for the Scheduler for possible problems. You can also examine the Sched.log file for errors or additional information. Also examine the sender log file (Sender.log) for any errors when it tries to communicate to the remote site.
\Schedule.box\Requests

This folder stores the initial send request files before the Scheduler transfers the files to a sender. This folder also stores send request files that are returned when the sender cannot connect to the target site. Examine status messages for the Scheduler for possible problems. You can also examine the Sched.log file for errors or additional information. Also examine the sender log file (Sender.log) for any errors when it tries to communicate to the remote site.
\Schedule.box\Tosend

This folder stores package and instruction files before they are transferred to another site. Package and instruction files start with .p00 and .i00 file name extensions, and the file name extensions increment numerically. The files are removed after the sender has copied the files to the remote site. A backlog of files can indicate that many send requests are not completed or that the Scheduler has not yet deleted the files. Examine status messages for the Scheduler for possible problems. You can also examine the Sched.log file for errors or additional information. Also examine the sender log file (Sender.log) for any errors when it tries to communicate to the remote site.
\Sinv.box

This folder stores client software inventory files (.sic and .sid files) that are copied from the management point. A backlog of files can indicate that the Software Inventory Processor cannot connect to the site database or that too many files were received. Examine status messages for the Software Inventory Processor for possible problems. You can also examine the Sinvproc.log file for errors or additional information.
\Sinv.box\BadSinv

This folder stores corrupted software inventory files. A backlog of files can indicate problems with specific clients, with management points, or with the network, causing data corruption. Make sure that there is not a backlog of zero-byte files in this folder. If zero-byte files exist, manually delete them. Examine status messages for the Software Inventory Processor for possible problems. You can also examine the Sinvproc.log file for errors or additional information.
\SiteStat.Box

This folder receives summarization messages (.sum files) for site system status from child sites before the files are processed to the SMS site database. A backlog of files can indicate a performance problem. Examine status messages for the Site System Status Summarizer for possible problems. You can also examine the Sitestat.log file for errors or additional information.
\Statmgr.box\Futureq

This folder stores status messages (.svf files) from remote systems (clients or site systems) if the date and time of the message is in the future compared to the site server's clock. The Status Manager does not process these messages until the computer clock matches the date and time when the status message was created. The date and time when the status message was created might be different from the date and time stamp of the file. A backlog of files can indicate that some site systems' clocks are not synchronized with the site server. Examine status messages for the Status Manager for possible problems. You can also examine the Statmgr.log file for errors or additional information.
\Statmgr.box\Queue

This folder receives status messages from SMS Executive components on the site server if the in-memory queue is not available. A backlog of files can indicate a problem with the Status Manager or that the component is trying to process too many messages. Examine status messages for the Status Manager for possible problems. You can also examine the Statmgr.log file for errors or additional information.
\Statmgr.box\Retry

This folder stores status messages that could not be processed to the site database. A backlog of files can indicate problems with the connection to the computer that is running SQL Server. Examine status messages for the Status Manager for possible problems. You can also examine the Statmgr.log file for errors or additional information.
\Statmgr.box\Statmsgs

This folder stores status messages from site systems and from Configuration Manager 2007 clients before the messages are processed by the Status Manager. A backlog of files can indicate a problem with the Status Manager or that the Status Manager is trying to process too many messages. Examine status messages for the Status Manager for possible problems. You can also examine the Statmgr.log file for errors or additional information.
\swmproc.box

This folder and its subfolders are used to temporarily store software metering information from Configuration Manager 2007 clients. A backlog of .sum and .sur files can indicate that the Software Metering Processor component cannot connect to the SMS database. Examine the status messages for the Software Metering Processor component for possible problems. You can also examine the Swmproc.log file for errors or additional information.

See Also