The error message "SUP0108: A deployment or update operation is already in progress" typically occurs in the context of System Center Configuration Manager (SCCM) or Microsoft Endpoint Configuration Manager, especially when you're trying to deploy or update software, applications, or configurations to client machines. This review aims to provide insights into understanding and resolving this issue.
Once you have resolved the error, implement these best practices to ensure it never returns:
Frequently, the previous operation has technically completed (success or failure), but the extension service status on the VM has not updated to a "Ready" state. This leaves a semaphore/lock file in place on the local agent, blocking all future actions.
The SUP0108 "deployment or update operation is already in progress" error is a classic WSUS lock contention issue. While the word "(best)" in the log might seem cryptic, it simply means WSUS is refusing a new command because it is executing a prior one.
By following the solutions above—starting with clearing the RefreshNow flag and escalating to a full SUP reinstall—you can resolve the error in under 15 minutes. More importantly, by respecting the boundary between WSUS (the engine) and ConfigMgr (the manager), you will rarely see this error again.
Remember: When it comes to SUP0108, the fix is not about force; it is about releasing the invisible lock. Clear the flag, clean the database, and let the sync flow. The error message "SUP0108: A deployment or update
Do you still see the error after trying these steps? Check your wsyncmgr.log for additional error codes like 0x80072ee2 (timeout) or 0x80070002 (missing file) that may accompany SUP0108.
The error code ("A deployment or update operation is already in progress") is a Dell Lifecycle Controller message typically encountered during iDRAC or system firmware updates.
It indicates that the system's update engine is currently busy or locked by a previous task Immediate Solutions Wait for Completion
: Initial firmware packages can take over 5 minutes to download, and full updates may take much longer depending on network speed. Some users report stuck updates eventually completing after several hours. Reset the iDRAC
: If the operation is genuinely stuck, you can reset the iDRAC to clear the active update job. A previous deployment/update is still running or stuck
This can be done via the iDRAC web interface or by holding the "i" button on the physical server for 16 seconds. Perform a Cold Boot
: This error often occurs because a RAM drive created for a previous upgrade was not cleared. Shut down the server, unplug the power cables for 10 seconds, and restart to clear the drive. Server Fault Troubleshooting Stuck Jobs Clear the Job Queue
: Use RACADM commands to forcibly clear the job queue if the UI is unresponsive. Check for Ghost Processes
: This message sometimes appears even when no operation is active if the Lifecycle Controller was not closed properly. Alternative Update Methods
: If updating via the Lifecycle Controller continues to fail, try updating directly through the iDRAC web interface by uploading the Windows 64-bit firmware file. Best Practices for Firmware Updates Sequential Updates Best Practices to Avoid SUP0108
: For older systems, avoid skipping too many versions at once; perform updates in smaller "steps". Avoid High CPU Loads
: Do not perform firmware updates when the CPU is under heavy utilization, as it may impact cooling and stability. Use the Right File : Ensure you are using the correct
image rather than just the self-extracting executable in some interface modes. RACADM commands to clear the job queue or instructions for a physical power drain iDRAC10 Version 1.20.25.00 Release Notes - Dell
This error message (SUP0108) typically appears in Swarm or Kubernetes environments (like Docker Enterprise or Mirantis Kubernetes Engine) when you try to update a service while a previous update or deployment is still running.
Here are the best ways to resolve it, ranked from the easiest to the more forceful solutions.