Hi,
I've noticed that there's a significant number of endpoints getting stuck in the 'Unknown - Client check passed/Active' state. While this issue typically resolves itself after a while, I'm looking for ways to expedite the process.
To clarify, this issue isn't related to OS updates but rather involves various softwares where the devices remain in this state for extended periods, sometimes up to a month. For example, I have around twelve test VMs where the installation proceeds without a hitch on eleven of them, but the twelfth remains stubbornly stuck in this state. All devices are on the same subnet, have the same client version, reporting as healthy and are fully operational and pingable. (I have noted that Appdiscovery sometimes takes an incredibly long time to actually acknowledge the software, even when i've forced a discovery several times.)
Occasionally, running one of my scripts to reset the policies helps resolve the issue:
# Reset Policy
Invoke-CIMMethod -Namespace root\ccm -ClassName SMS_CLIENT -MethodName "ResetPolicy" -Arguments @{ uFlags = [uint32]1}
# Machine Policy Assignments Request
Invoke-CIMMethod -Namespace root\ccm -ClassName SMS_CLIENT -MethodName "TriggerSchedule" -Arguments @{ sScheduleID = '{00000000-0000-0000-0000-000000000021}'}
# Machine Policy Evaluation
Invoke-CIMMethod -Namespace root\ccm -ClassName SMS_CLIENT -MethodName "TriggerSchedule" -Arguments @{ sScheduleID = '{00000000-0000-0000-0000-000000000022}'}
# Send Unsent State Message
Invoke-CIMMethod -Namespace root\ccm -ClassName SMS_CLIENT -MethodName "TriggerSchedule" -Arguments @{ sScheduleID = '{00000000-0000-0000-0000-000000000111}'}
```
At other times, updating the application deployments does the trick. However, I am struggling to identify a consistent method to remediate this issue across all affected endpoints.
I am reaching out to ask if anyone is aware of any scripts or methods that could help force the clients out of this state more reliably. Any insights or suggestions would be greatly appreciated.
I have only begun to dig into this rabbithole that is SCCM, so there's a fair chance I'm missing some vital things.
Sidenote: I'm looking into getting Recast implemented, perhaps that would remediate alot of my current issues.
Thanks in advance.
I've noticed that there's a significant number of endpoints getting stuck in the 'Unknown - Client check passed/Active' state. While this issue typically resolves itself after a while, I'm looking for ways to expedite the process.
To clarify, this issue isn't related to OS updates but rather involves various softwares where the devices remain in this state for extended periods, sometimes up to a month. For example, I have around twelve test VMs where the installation proceeds without a hitch on eleven of them, but the twelfth remains stubbornly stuck in this state. All devices are on the same subnet, have the same client version, reporting as healthy and are fully operational and pingable. (I have noted that Appdiscovery sometimes takes an incredibly long time to actually acknowledge the software, even when i've forced a discovery several times.)
Occasionally, running one of my scripts to reset the policies helps resolve the issue:
# Reset Policy
Invoke-CIMMethod -Namespace root\ccm -ClassName SMS_CLIENT -MethodName "ResetPolicy" -Arguments @{ uFlags = [uint32]1}
# Machine Policy Assignments Request
Invoke-CIMMethod -Namespace root\ccm -ClassName SMS_CLIENT -MethodName "TriggerSchedule" -Arguments @{ sScheduleID = '{00000000-0000-0000-0000-000000000021}'}
# Machine Policy Evaluation
Invoke-CIMMethod -Namespace root\ccm -ClassName SMS_CLIENT -MethodName "TriggerSchedule" -Arguments @{ sScheduleID = '{00000000-0000-0000-0000-000000000022}'}
# Send Unsent State Message
Invoke-CIMMethod -Namespace root\ccm -ClassName SMS_CLIENT -MethodName "TriggerSchedule" -Arguments @{ sScheduleID = '{00000000-0000-0000-0000-000000000111}'}
```
At other times, updating the application deployments does the trick. However, I am struggling to identify a consistent method to remediate this issue across all affected endpoints.
I am reaching out to ask if anyone is aware of any scripts or methods that could help force the clients out of this state more reliably. Any insights or suggestions would be greatly appreciated.
I have only begun to dig into this rabbithole that is SCCM, so there's a fair chance I'm missing some vital things.
Sidenote: I'm looking into getting Recast implemented, perhaps that would remediate alot of my current issues.
Thanks in advance.
