Applies To: System Center Configuration Manager 2007, System Center Configuration Manager 2007 R2, SystemCenter Configuration Manager 2007 R3, System Center Configuration Manager 2007 SP1, System CenterConfiguration Manager 2007 SP2

 You can monitor inbox folders on a Microsoft System Center Configuration Manager 2007 site to help troubleshootproblems 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 beprocessed. The inbox folders temporarily store files before they are processed to the site database or transferred toanother site or site component. A backlog of files can indicate that a component is not running or is experiencing aproblem. For example, when the Microsoft SQL Server database runs out of space, a backlog of files occurs until thefiles are processed to the site database.

Inbox Folders

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

\Auth\dataldr.box This folder stores .mif files that represent hardware inventory data for Configuration Manager 2007 clientcomputers. This folder also stores IDMIF files for custom architectures. A backlog of files can indicateproblems accessing the site database. Examine the status messages for the Inventory Data Loader forpossible 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 sitedatabase. Examine the status messages for the Inventory Data Loader for possible problems. You can alsoexamine 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 alsoexamine 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 problemor a problem with the DDM. Configuration Manager 2007 automatically deletes .ddr files that are olderthan 25 hours. Examine the status messages for the Discover Data Manager component for possibleproblems. 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 managementpoint. A backlog of files can indicate that the Software Inventory Processor cannot connect to the sitedatabase or that too many files were received. Examine the status messages for the Software InventoryProcessor for possible problems. You can also examine the Sinvproc.log file for errors or additionalinformation.

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

\Auth\statesys.box This folder stores information related to state messages. For more information about state messagebacklogs, see Troubleshooting State Message Backlogs.

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

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

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

 

\Ddm.box This folder temporarily stores discovery data records (.ddr files) after a client or server agent generates adiscovery 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 problemor a problem with the DDM. Configuration Manager 2007 automatically deletes .ddr files that are olderthan 25 hours. Examine status messages for the DDM for possible problems. You can also examine theDdm.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 processedand moved as soon as Configuration Manager 2007 receives the instruction file (.ins file). Examine statusmessages for the Despooler for possible problems. You can also examine the Despool.log file for errors oradditional information.

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

\OfferSum.box This folder receives summarization messages (.sum files) for advertisements from child sites andprocesses the files to the site database. A backlog of files can indicate a performance problem that iscaused by a large number of messages. Examine status messages for the Offer Status Summarizer forpossible 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. Wheneverthe 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 indicatesthat the policy provider component is not running. The policy provider component might not be able toread the site control file, or the component cannot write to the database. You can examine the Policypv.login 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 SMSReplication Manager determines whether the file is transaction-oriented and then verifies that the serialnumbers are correct. If the file is not transaction-oriented, no additional verification is performed. TheReplication Manager transfers the file to the recipient component for final processing. Examine statusmessages for the Replication Manager for possible problems. You can also examine the Replmgr.log file forerrors or additional information.

\Replmgr.box\Outbound This folder temporarily stores files that are destined for another site. This folder also contains three outboxsubfolders 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, theReplication Manager waits for additional files before moving the files to the \Process subfolder and then tothe \Ready subfolder. Examine status messages for the Replication Manager for possible problems. You canalso 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 theScheduler for transmission. A backlog of files can indicate that the Scheduler is backlogged or is alreadyprocessing files of the same priority. In this scenario, the Scheduler has to wait for the transmission tocomplete. Examine status messages for the Replication Manager for possible problems. You can alsoexamine 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 Schedulerturns the .job files into Sender jobs. A backlog of files can indicate that the Sender cannot connect to orcannot transfer data to another site. A backlog can also indicate that the Scheduler cannot process themini-job files because files are missing from the \Schedule.box\Uid folder. Examine status messages for theScheduler for possible problems. You can also examine the Sched.log file for errors or additionalinformation.

\Schedule.box\Outboxes This folder contains the outbox folders for each installed sender. In the sender's outbox folder, you can findsend request files (.srq files) or send request status files (.srs files). A backlog of .srq files indicates that thesender cannot process the number of jobs scheduled for that sender or that the sender cannot connect toor transfer data to another site. Examine status messages for the Scheduler for possible problems. You canalso 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. Thisfolder 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 filefor errors or additional information. Also examine the sender log file (Sender.log) for any errors when ittries to communicate to the remote site.

\Schedule.box\Tosend This folder stores package and instruction files before they are transferred to another site. Package andinstruction files start with .p00 and .i00 file name extensions, and the file name extensions incrementnumerically. 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 thefiles. Examine status messages for the Scheduler for possible problems. You can also examine theSched.log file for errors or additional information. Also examine the sender log file (Sender.log) for anyerrors 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 managementpoint. A backlog of files can indicate that the Software Inventory Processor cannot connect to the sitedatabase or that too many files were received. Examine status messages for the Software InventoryProcessor for possible problems. You can also examine the Sinvproc.log file for errors or additionalinformation.

\Sinv.box\BadSinv This folder stores corrupted software inventory files. A backlog of files can indicate problems with specificclients, with management points, or with the network, causing data corruption. Make sure that there is nota backlog of zero-byte files in this folder. If zero-byte files exist, manually delete them. Examine statusmessages for the Software Inventory Processor for possible problems. You can also examine theSinvproc.log file for errors or additional information.

\SiteStat.Box This folder receives summarization messages (.sum files) for site system status from child sites before thefiles 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 alsoexamine 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 andtime of the message is in the future compared to the site server's clock. The Status Manager does notprocess these messages until the computer clock matches the date and time when the status messagewas created. The date and time when the status message was created might be different from the dateand time stamp of the file. A backlog of files can indicate that some site systems' clocks are notsynchronized 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-memoryqueue is not available. A backlog of files can indicate a problem with the Status Manager or that thecomponent is trying to process too many messages. Examine status messages for the Status Manager forpossible 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 canindicate problems with the connection to the computer that is running SQL Server. Examine statusmessages for the Status Manager for possible problems. You can also examine the Statmgr.log file forerrors or additional information.

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

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