I'm pestering Avaya to fix a bug in AAM 6.2 - don't know if every patch level has it, but 6.2 SP2 seems to. The subscriber activity log in the MSS requires a start and end date/time to show a user's logs.
The web interface into this does not care what time zone your PC or AAM is in. If you're in Pacific time at noon PST, your AAM is 3PM EST, and you left a test message to check something in a user's mbx at that time, and then went to the activity log to see it, AAM will tell you the "end date/time can't be after current date/time. But $CurrentDate/Time is arbitrarily determined to be the one in the bottom-right corner of your Windows PC, independent of time zone.
To say, to check logs at noon (GMT -5)today for an AAM in EST, I'd have to use a browser on a PC in EST, or wait until noon GMT -8 to be able to submit noon through AAM's logging webpage.
Perhaps more people complaining might make it noticed...
The web interface into this does not care what time zone your PC or AAM is in. If you're in Pacific time at noon PST, your AAM is 3PM EST, and you left a test message to check something in a user's mbx at that time, and then went to the activity log to see it, AAM will tell you the "end date/time can't be after current date/time. But $CurrentDate/Time is arbitrarily determined to be the one in the bottom-right corner of your Windows PC, independent of time zone.
To say, to check logs at noon (GMT -5)today for an AAM in EST, I'd have to use a browser on a PC in EST, or wait until noon GMT -8 to be able to submit noon through AAM's logging webpage.
Perhaps more people complaining might make it noticed...