tag:blogger.com,1999:blog-13490395.post5732397259462621871..comments2017-05-30T09:42:16.183-05:00Comments on The Appian Way: Y2K7Chuck Russellhttp://www.blogger.com/profile/15429587155202866452noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-13490395.post-19737063014591158482007-03-01T17:42:00.000-06:002007-03-01T17:42:00.000-06:00Yeah, I concur with Clif here. On the web applicat...Yeah, I concur with Clif here. On the web application side, we can get around it by using a Mac or Linux box. I'm also involved with the WEC team developing software, which is where we came across this problem. http://webempoweredchurch.com<BR/><BR/>Our suggestion for users of the software is to input a wrong date to fake it out, or use a Mac or Linux box. Neither are good options. Like Clif said, we're just working with it the best we can and letting people know the problem exists.<BR/><BR/>If someone out there is reading and knows more, we'd love to hear from you. Thanks!Brian Slezakhttps://www.blogger.com/profile/11442325956355607876noreply@blogger.comtag:blogger.com,1999:blog-13490395.post-54893081632023893802007-03-01T17:31:00.000-06:002007-03-01T17:31:00.000-06:00Brian's responsibility is limited to web stuff. S...Brian's responsibility is limited to web stuff. So I'll take a crack at the answer.<BR/><BR/>My prior reading on this suggested it was a matter of applying patches, like any other Microsoft patch. So I wasn't worried. Now we're just over a week out and I'm discovering it's much more. We're already having users notice appointments within the affected date range are off by an hour. <BR/><BR/>Microsoft provides a piece of software that will go through everyone's Exchange calendar and fix the appointments in the date range from March 11 to April 1, but it simply changes the UTC, knowing that Windows will render it incorrectly. How's that for a fix? <BR/><BR/>Ian, our network admin, is having trouble getting the thing to run. It gets to a certain user's mailbox and errors out. Are we having fun yet? <BR/><BR/>Bottom line: our strategy for COR is to work through it as best we can, based on tools and advice provided by Microsoft. But we're finding their tools and advice to be inadequate.Clif Guyhttps://www.blogger.com/profile/03546100664377891125noreply@blogger.comtag:blogger.com,1999:blog-13490395.post-79463028795798616622007-03-01T16:48:00.000-06:002007-03-01T16:48:00.000-06:00So, Brian... what was your stragegy for COR? We'd...So, Brian... what was your stragegy for COR? We'd already figured out that the patch was not really a fix... and could screw things up between install and March 11. I've been expecting a fix from MS... but now I'm not so sure.<BR/><BR/>What to do?Kirk Longhoferhttps://www.blogger.com/profile/06874549419748687748noreply@blogger.com