Sometimes a PST file is not being deleted by Source File Remover module. The affected PST file has been set to the status "Migration Complete", but it is hanging in the "Running" status on the Source File Remover module.
There may be a few reasons why the source file deletion command hasn’t been executed for the particular PST file yet (Source File Remover module hasn't been completed with the status "Success"):
Please make sure there is running Migration Agent under the user account the PST file is assigned to. You can find this information in the workstation report in the Migration Manager for PSTs Admin Console (Reports -> Workstation).
The report gives you the date when the Migration Agent of the particular user was started last time. Please make sure you check the right workstation in case the user has more workstations and the affected PST file is located on one of them.
Last Discovery Date
This information gives you the date when the particular PST file was discovered by the FileScanner last time. If you get a recent date it means the discovery process works fine.
Sometimes it might be necessary to retrieve the Migration Agent log files to investigate this issue further:
In case the affected user / workstation is online and no issue has been discovered (recent last discovery date & recent last Migration Agent start-up date).
There is also an option to re-queue the source file deletion command for a particular PST file again. Please follow these steps:
Then the source files deletion command will be queued to Migration Agent again. Relevant Migration Agent will pick the command up once it asks for new for items next time.