PENDING SCCM Policy Request Date not Updating

[patelke]

I am reaching out regarding an issue one of our customers is experiencing. In the MECM console, all clients have a policy request date/time stamp that is over six months old. I retrieved the client activity information from the SQL database in the vWorkstationStatus view, and the last policy request date is also over six months ago. Interestingly, the heartbeat DDR, hardware scan, and software scan all have current date/time stamps.
We have thoroughly checked the configurations, but we are still unable to resolve this issue. Any guidance or support you can provide to help us address this would be greatly appreciated.

 

[Prajwal Desai]

So the clients not getting new deployments then? Are the client agents updated to the latest version?

 

[patelke]

That's the strange part-there are no issues with deployments and also the client policy download but why is policy request timestamp not getting updated?

I came across this workaround when I was doing some research, but I'm nervous about messing with SQL:

When there are a large number of clients that are having old timestamp, i started digging into the database as well and found a SQL table called v_CH_PendingPolicyRequests.

This SQL Table list the information about policy request including the GUID of the request.

Run the following syntax on your SQL management studio:

select * from v_CH_PendingPolicyRequests



As you can see above, a large number of clients with an old timestamp, GUID, and also its Management point.
Remove all the pending records from this table v_CH_PendingPolicyRequests and monitor the client policy request again.

On your SQL management studio, perform the following syntax.

TRUNCATE TABLE v_CH_PendingPolicyRequests

Now run the SQL Query to verify if there are any more results or not?

select * from v_CH_PendingPolicyRequests

Confirm that, there are no records in it.

Now delete the backlog files inside the inbox folder polreq.box


Thoughts?

 

[Prajwal Desai]

I am not exactly sure why is this happening. When I previously encountered this issue, I noticed that the timestamp was not updating for the majority of the functions, including heartbeat DDR, hardware scan, and software scan. Has anyone modified or changed something in the ConfigMgr database? Ideally, I wouldn't recommend editing the DB or making any changes. You can run the SQL queries against the database though.