(imported topic written by nberger91)
When querying SQL directly for the LRT, the format is GMT which i believe is expected behaviour for BES vers 7 and 8. The time zone conversion when viewing the data via the console is handled by the console application.
What im looking to do is create a property that will return the LRT based on the endpoint s time zone (using the local time zone inspector)
Has anyone done this, or know the best way to code it up ?
Thanks !
(imported comment written by SystemAdmin)
When I read this, I was just thinking that ‘apparent registration server time’ (as used in the LRT property) could be used, but I suppose that using ‘now’ is a bit simpler.
I did find it amusing that in the inspector description it states that ‘apparent registration server time’ is shorthand for what would be ‘now of registration server’. How can a statement that is longer be described as shorthand? 
Or if you wanted to be even more accurate (as to what time the clients ‘report’ landed on the server), would you take the difference between the ARST and the clients now result, halve it and then add that to the clients now time? (Obviously the delivery and reciept times are not the same, but this assumption should be good enough.)
-Jim
(imported comment written by nagaraj.s)
hi admin,
in my infra i have run TEM v9.
TEM console clients “last report time” 12.15pm , but the server current time 14.35pm,
i have checked the clients logs also , it’s shown “at report==12.15.46pm” successfully communicated.
my query is why the client and server no connection between 12.15pm to 14.35pm
also i have set the preferance fixlet refresh==5 sec.
clients sent heart beat every 5 min.
clients offline after 15 min.
please find the solution
regards
Nagarajan.
(imported comment written by nberger91)
thanks for the ideas … the now inspector is excatly what i need.
first 25 of (now as string)