For SCCM administrator having big environments, one of the issues in such environments is backlogging.
if the number of files in an inbox reached critical level, SCCM will not be able to handle the new files that comes in and also whatever that is in the backlog unless you stop all data transferring between sites for several days. Try to run "DIR /P" command in folder with million files and you will see it takes 3-5 minutes. Windows Explorer hangs when you try to open.
All your changes may be delayed for days and even weeks or changes already happened on client side (package installed, new update lists, updates to collections.. you name it :)) but SCCM server is not updated because it has yet to processed status files yet.
How to resolve this?
Follow the below
1) Stop all SCCM services. It may take up to 10-15 minutes to stop SMS_EXECUTIVE service. (Have some patience to allow it to stop properly and not kill the process :)
2) Create a "DELAY” folder under <SCCM_INSTALL_PATH>\inboxes\replmgr.box\incoming
and move all RPT files from replmgr.box\incoming to delay folder.
3) Start all SCCM Related services which was stopped in step 1.
Watch replmgr.box\incoming folder. Once SCCM finished processing old files (number of files in the folder will be dropped) you can start moving back RPT files. It should be done in blocks.
The below is something that would help to ease the pain of having to manually move the file back into the incoming folder.
Create the batch file in the Delay folder which you create in step 2.
@echo off & setlocal EnableDelayedExpansion
for %%i in (*.rpt) do (
set /A N+=1
move “%%i” “..”
if !N! geq !LIM! (TimeOut 3600 & set /A LIM+=300)