As many of you know, there will be a change next year in the transition dates for US daylight saving time. I won't go into all the gory details here, but if you want them follow this link http://ww...
Published Nov 13, 2006
Version 1.0
Blog Post
In reply to Englebert:
Look, I run a large network with lots of servers. Depending on when a server is built, a particular version of an OS and app(s) are installed.
Then the idea is to keep it all running smoothly, securely,.....yada yada yada. If we're lucky enough, we size a box such that it runs fine for three years or so, and then migrate off to new hardware, OS, apps etc.
I do run MS products sometimes into extended support, but by then a plan to migrate off is firmly in place. Testing and such follows in a lab. Finally, it goes to production hopefully to run for another three years. The goal all the while being data integrity and system availability, and affording me enough time to do my other administrative duties. That's the way its done in the real world.
MS knew back in August 2005 that this would be an issue, but decided not to take care of the Exchange 2000 folks anyway. No warning either. I'd be whining if I was looking for something for nothing, but that's not the case here. My organization plunked down thousands of dollars for Exchange 2000, and counted on support for issues known during mainline phase, not an "oh well" on something like this. Oh right, just plunk down thousands more, upgrade at MS' command, and don't whine...
I take offense to your insinuation of not being a decent admin, but I'll drop it at that as I've got better ways to use my time. One thing I will say is Microsoft has so far dropped the ball on this, but then again that's obvious to anyone with common sense.
Look, I run a large network with lots of servers. Depending on when a server is built, a particular version of an OS and app(s) are installed.
Then the idea is to keep it all running smoothly, securely,.....yada yada yada. If we're lucky enough, we size a box such that it runs fine for three years or so, and then migrate off to new hardware, OS, apps etc.
I do run MS products sometimes into extended support, but by then a plan to migrate off is firmly in place. Testing and such follows in a lab. Finally, it goes to production hopefully to run for another three years. The goal all the while being data integrity and system availability, and affording me enough time to do my other administrative duties. That's the way its done in the real world.
MS knew back in August 2005 that this would be an issue, but decided not to take care of the Exchange 2000 folks anyway. No warning either. I'd be whining if I was looking for something for nothing, but that's not the case here. My organization plunked down thousands of dollars for Exchange 2000, and counted on support for issues known during mainline phase, not an "oh well" on something like this. Oh right, just plunk down thousands more, upgrade at MS' command, and don't whine...
I take offense to your insinuation of not being a decent admin, but I'll drop it at that as I've got better ways to use my time. One thing I will say is Microsoft has so far dropped the ball on this, but then again that's obvious to anyone with common sense.