LOL
This whole change over has been very expensive for our IT department- not to mention the fact that we don't know if there will be issues when the underlying OS tries to kick in the old DST in three weeks.
At this point, as a country, can't we just pick a time and stick with it?
Tomorrow's going to be bad. How Microsoft did the update is that everyone will have to run a tool. If there were no meetings, no problem. But lately there are lots of companies that live by using Outlook to schedule meetings and resources.
Here's the ugly part- the meeting won't get changed until the organizer runs the update tool. What we don't know is if this will cause the resources to reject all scheduled meetings -- you can't double book a conference room, etc.
What we've done is to ask the users to print out their calendar for one month before they run the tool. Otherwise there would be no trail as to what went wrong later.
Congress would have had no way of knowing this. But after this little test drive happens, it would be helpful to let them know how expensive it really was.
Oh and then the desupported pdas were a hassle too. The techs had to build a separate server to support them and had to cobble a fix together. I feel sorry for the tech who is in the cube next to mine.
You and your associates in the IT business obviously anticipated it. I urge you to write up an invoice and submit it to your congress critters. Work it right and you can get it into the cybermedia.
Good morning SL!
This is going to be as successful as smaller toilet bowl tanks are to saving water!