This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(179.20000000000002, 41%, 27%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ELM%3C/text%3E%3C/svg%3E)
We found that when deploying updates on those servers with clustering, the deployment status would get stuck in unknown state - client check passed/active. Other servers within same deployment job able to moved to compliant status after patched. Is there any solution for this?
Version - 2103
Console ver - 5.2103.1059.1800
Site ver - 5.0.9049.1000
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(297.6, 24%, 38%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ERH%3C/text%3E%3C/svg%3E)
@Low Mian Shao
Please help to confirm the Scan 1 - Last scan states by collection on Monitoring on the MECM console.
Here is a screenshot in my lab for your reference:
In addition, please try to review the ScanAgent.log and UpdatesStore.log on one of the affected Server.
Hope the above will be helpful.
Best regards,
Rita
this collection had 9 server, 2 of it is under unknown state.
I had downloaded ScanAgent.log and UpdatesStore.log what should I looking for?
Is there any error tips in the ScanAgent.log? Note that we could use the cmtrace.exe to open the log files and get more information. The cmtrace.exe is located on the following path by default in Site Server:
Also we could review the StateMessage.log on the affected Servers and the log records details about software update state messages that are created and sent to the management point. And we could confirm whether the servers send state message to MP successfully.
Since the issue only occurred on the two servers in the collection. So it is recommended to troubleshoot from the client side.
Best regards,
Rita