I have an odd one, and although there are other questions with a similar heading, they dont aseem to apply to mine…
Its a mac client that reports its last report time is 10/13/2017 at 7:44:25 and that desnt seem to change. The Computer responds to fixlets and tasks and is active… I have deleted it from the database and when it calls home again, it comes back with that same last report time,
its using the Global Reserved Property of "apparent registration server time as universal string"
Is there anything I can do to shake this loose?
I thought about deleting it from Database, Taking the server off like, Running the cleaup and waiting for it to call home but that involves server down time and how many days should I set the clean up for ?
Have you verified the clock is correct? There is a fixlet in BES Support to set the time to match the deployment (in local time zone) but the logs should be showing a disparity of the server time and the local time.
What is the plain “now” of the machine? The apparent registration server time takes the last registration time value and gets the delta when the computer registers so it shouldn’t drift but also it shouldn’t stay the same. This could be that the endpoint’s data is being rejected in FillDB?
Hi Alan,
Time Zone: -0400
Universal Time: Mon, 23 Apr 2018 23:23:02 +0000
Now Time as String: Mon, 23 Apr 2018 19:23:02 -0400
Last Report Time 10/13/2017 7:44:25 AM
Interestingly, the Now Time and the Universal time are the same today as they were yesterday. I spoke to the user and her clock shows correctly and is set to update from apple.
There is communication between the client and the relay(s) etc as I see it become active from being greyed out etc,
As an aside, the computer doesnt show up in fixlets like Restart BES Client on Mac OSC, or Reset Client.
So I’d check your FillDB logs for that computerid and see if you are losing things. If it doesn’t constantly stay greyed out I’d be surprised as well. Something is wrong with the endpoint for sure.