Answered by:
Last Logon Time for Exchange 2010 Mailbox Users Show Wrong !

Question
-
Hi all !
My company use exchange 2010 and DC & exchange server install on 1 server
User logon email every day by outlook and OWA
When i use this command
get-mailboxstatistics -database "Mailbox Database 0196964945" | Where {$_.LastLogonTime -lt (Get-Date).AddDays(-5)} | sort-object lastlogontime | select displayname,lastlogontime,lastlogouttime,lastloggedonuseraccount | export-csv c:\thongketest.csv
The result show wrong. the day userlog on .
Time of server correct with time zone
How can i fix it !
Friday, December 9, 2011 2:37 AM
Answers
-
Hi ChoiTiepDi,
I test users by OWA and MAPI and POP3.
It showes correctly with OWA and MAPI users. Blank value for POP3 users.
I also test it in my Exchange 2010 SP2 lab. Same result as Exchange 2010 SP1 RU6.
As I know, you have to enable POP3 and IMAP logging to track activities for these Exchange 2010 users at the moment.
Frank Wang
TechNet Community Support
- Marked as answer by emma.yoyo Friday, December 16, 2011 1:56 AM
Wednesday, December 14, 2011 6:58 AM
All replies
-
The result show wrong. the day userlog on .
Time of server correct with time zone
Hi ChoiTiepDi,
Could you please post the wrong result here?
I run the cmdlet in my lab(Exchange 2010 SP1 RU6), and the time is correct.
By the way, you should select LastLogoffTime instead of lastlogouttime.
Frank Wang
TechNet Community Support
Monday, December 12, 2011 7:16 AM -
Hi Frank.Wang ,
Does your user logon by owa only or by imap, pop3,outlook anywhere ? or all
Monday, December 12, 2011 7:41 AM -
Hi ChoiTiepDi,
I test users by OWA and MAPI and POP3.
It showes correctly with OWA and MAPI users. Blank value for POP3 users.
I also test it in my Exchange 2010 SP2 lab. Same result as Exchange 2010 SP1 RU6.
As I know, you have to enable POP3 and IMAP logging to track activities for these Exchange 2010 users at the moment.
Frank Wang
TechNet Community Support
- Marked as answer by emma.yoyo Friday, December 16, 2011 1:56 AM
Wednesday, December 14, 2011 6:58 AM -
Hi ChoiTiepDi
This is an old thread, but just in case you (or anyone else like me!) are still seeking an answer, this issue was addressed in Update Rollup 2 for Exchange Server 2010 SP2: http://support.microsoft.com/kb/2664365
-=Francois
Tuesday, June 12, 2012 9:07 PM