Glad you found that.. I'm so glad I don't have to deal with Exchange nonsense anymore!!
On Thu, 6 Jul 2017, Kennedy, Jim wrote: > Found it like 5 minutes before MS returned my PSS call, saving us 500 bucks. > > From: [email protected] [mailto:[email protected]] > On Behalf Of Michael B. Smith > Sent: Thursday, July 6, 2017 11:39 AM > To: [email protected] > Subject: RE: [NTSysADM] Exchange time insanity. > > Stupid BIOS ??? > > From: [email protected] [mailto:[email protected]] > On Behalf Of Eldridge, Dave > Sent: Thursday, July 6, 2017 11:30 AM > To: '[email protected]' > Subject: RE: [NTSysADM] Exchange time insanity. > > Wow! Thanks for sharing that. > dave > > From: [email protected]<mailto:[email protected]> > [mailto:[email protected]] On Behalf Of Kennedy, Jim > Sent: Thursday, July 06, 2017 9:10 AM > To: '[email protected]' > Subject: RE: [NTSysADM] Exchange time insanity. > > Fixed. > > http://h20564.www2.hpe.com/hpsc/doc/public/display?docId=emr_na-c04557232 > > > From: [email protected]<mailto:[email protected]> > [mailto:[email protected]] On Behalf Of Kennedy, Jim > Sent: Thursday, June 29, 2017 3:55 PM > To: '[email protected]' > Subject: RE: [NTSysADM] Exchange time insanity. > > 2012 R2 > > > From: [email protected]<mailto:[email protected]> > [mailto:[email protected]] On Behalf Of Miller Bonnie L. > Sent: Thursday, June 29, 2017 3:45 PM > To: '[email protected]' > Subject: RE: [NTSysADM] Exchange time insanity. > > Is this on Server 2016? > > From: [email protected]<mailto:[email protected]> > [mailto:[email protected]] On Behalf Of Kennedy, Jim > Sent: Thursday, June 29, 2017 12:32 PM > To: '[email protected]' > <[email protected]<mailto:[email protected]>> > Subject: RE: [NTSysADM] Exchange time insanity. > > So that is the issue, time on the server is freaking out during startup. If > I let it settle out and sync with the domain and restart MS Information Store > it is all better now. > > > From: [email protected]<mailto:[email protected]> > [mailto:[email protected]] On Behalf Of Kennedy, Jim > Sent: Thursday, June 29, 2017 8:17 PM > To: '[email protected]' > Subject: RE: [NTSysADM] Exchange time insanity. > > There was a reboot before this started. Just did a shutdown to check the MB > clock and time zone, it is correct. Shutdown shows at 3:07 PM in the event > log. Power on came at 8:11 PM. Services start, normal boot messages then > Time Service corrects it. > > > From: Kennedy, Jim > Sent: Thursday, June 29, 2017 8:17 PM > To: [email protected]<mailto:[email protected]> > Subject: RE: [NTSysADM] Exchange time insanity. > > If I send to a 2010 box the received time on their end is ok. But when they > look at my email the sent time is incorrect. You can see that below in your > quote of me: ???On Thu, Jun 29, 2017 at 6:17 PM, Kennedy, Jim??? > > From: [email protected]<mailto:[email protected]> > [mailto:[email protected]] On Behalf Of Mike > Sent: Thursday, June 29, 2017 3:11 PM > To: [email protected]<mailto:[email protected]> > Subject: Re: [NTSysADM] Exchange time insanity. > > What if you send to a mailbox still on 2010? Same behavior? > > On Thu, Jun 29, 2017 at 6:17 PM, Kennedy, Jim > <[email protected]<mailto:[email protected]>> wrote: > Stood up an Exch 2016 server in my 2010 org. Moved my mailbox over more than > a week ago. It has been fine. Moved another box today and the below started > happening to both of us. What you are seeing is emails I sent to myself. > The send time is listed to the right of my name, so 1:47 pm, 1:48 pm and so > on. Next you see the received time. It makes no sense. That happens with > internal mail and external mail. > > Time zones on the mailboxes, Outlook and servers are correct. They all have > the correct time from the domain. > > > > > [cid:[email protected]] > >
