Frederick, The user in question has a User Preference record....with the Time Zone blank, as are most User Preference Records in our current system(I found four NON-null Time Zone entries, out of many thousands of records--all the rest are null). Of course, whether the Time Zone *should* be left null, is another matter........ I changed my user preference on that server to our local time zone, and the timestamps are now correct in Vista--both IE and Firefox. One could conclude that a correct Time Zone entry will indeed behave correctly with Vista; however, if anyone else sees strange time behavior in Vista where other Microsoft platforms are behaving properly, in the same Mid-Tier environment, Frederick has pointed us to an item worth checking. The exact mechanism by which Vista interprets this timestamp differently from XP is not yet known to me, and probably will not be pursued---but, user beware! ** Don W. McClure, P.E. Systems Engineer University of North Texas dwmac_at_unt.edu 940.565.3287
"Not everything that can be counted counts, and not everything that counts can be counted." (Albert Einstein) >>> "Grooms, Frederick W" <[EMAIL PROTECTED]> 12-Jul-07 1:00 PM >>> Question ... Does the user you are testing Mid-Tier with have a AR System User Preference record? (And if so does it have the correct Time Zone?) From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Don McClure Sent: Thursday, July 12, 2007 12:35 PM To: arslist@ARSLIST.ORG Subject: Re: timestamp ** We have also encountered an inconsistency with MS Vista. Specifically: Experiment was: observe the same helpdesk record (HD 5.5) with: - Windows UT, XP -- timestamp correct and local - MT, IE 7.0, XP -- timestamp correct and local - MT, IE 7.0, Vista -- timestamp reading GMT (sorry, old-school aviation background) - MT FireFox 2.0, Vista -- timestamp reading GMT I have not checked the WinUT on a Vista machine--no intention of installing a 5.1.2 UT on this machine along with the 7.x stuff. Further, the Vista platform only displays this behavior with Remedy Mid-Tier (that is, only mis-stamp encountered so far); timestamps on other websites are correct/local. There are too many other issues to face for extensive analysis at the moment--so I will simply live with this issue, for now (until encountered in the 7.x MidTier!!). Don W. McClure, P.E. Systems Engineer University of North Texas dwmac_at_unt.edu 940.565.3287 "Not everything that can be counted counts, and not everything that counts can be counted." (Albert Einstein) >>> James Collins <[EMAIL PROTECTED]> 12-Jul-07 11:27 AM >>> Simple question, I think. Where does timestamp time come from? I have two workstations on my desk, one my regular one with my time on the east coast. The other a vista box, always has the wrong time and is usually colorado time. I manually change it every day. When I submit tickets into remedy the timestamp shows colorado time instead of east coast. My boss said "wow you got in at 6 A.M. I did not know what he was talking about. If I changed it on the local workstation why is the timestamp still showing up as incorrect. The server time is eastern as well. James __20060125_______________________This posting was submitted with HTML in it___ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
