The cleanup task takes longer than expected - Generate a Debug Log (4314284)

To add logging, download the cleanup debug task, extract the zip file and copy the 4 PO files into the \\SDA\restore share. In the web interface, navigate to Settings | Package Management | Import Packages | checkmark the 2 tasks | Choose action... Import selected

This will create two new Postinstall tasks : cleanup task debug logging ( drive c) and cleanup task last PO time stamp (drive c).

cleanup task debug logging ( drive c) replaces the cleanup.vbs file in the deployment with a debug version that will write out a log with time stamps for each command it runs. It will also log the process list of all running processes at the time kcleanup.exe is started. Lastly it will gather the taskResults.xml file which contains the results of each task that ran during deployment.

cleanup task last PO time stamp (drive c)  is a batch command that will log the date/time of its execution into the same log used by the cleanup task debug logging ( drive c) task.

When using these tasks to debug a deployment, cleanup task debug logging ( drive c) should be the very first PO task in the deployment and cleanup task last PO time stamp (drive c) should be the very last PO task in the deployment. This will allow logging when the last PO task ended and when the cleanup.vbs script started.

When the deployment is complete, there will be three log files on the C partition.

• c:\kacedebug.txt
• c:\processlist.txt
• c:\taskresults.xml

Note this assumes the OS is installed on drive C. Should you need to install the OS on drive D copy both tasks and change the names to "cleanup task debug logging ( drive d)" and "cleanup task last PO time stamp (drive d)"

For cleanup task debug logging ( drive d) change:
cleanupdebuginstall_C.bat
to
cleanupdebuginstall_D.bat

For cleanup task last PO time stamp (drive d)  change:
echo last PO task %date% %time% > c:\kacedebug.txt
to
echo last PO task %date% %time% > d:\kacedebug.txt

Possible return codes :
98 : Cleanup.vbs could not be found. make sure you are running this task on the OS partition
99:  The cleanup.vbs replacement failed (xcopy failed)

If there are any entries in the processlist.txt file for items such as security or antivirus software, try adding an exception/whitelist for the kcleanup.exe application and cleanup.vbs script, as that has been known to cause delays in the cleanup task execution. Alternatively, you can disable scanning until the next reboot, or deploy the software from your SMA.

If you are experiencing this issue on a USB Image deployment, you will need also need to either create the USB Image on a system that does not have antivirus software, or add exceptions for kcleanup.exe and cleanup.vbs in the security/antivirus software.