![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
(no subject)
Mar. 13th, 2007 10:44 amSo yesterday when I got into work there was an e-mail from our so-called computer/network guru saying that all computers that were connected to the network should change to reflect the correct time according to the new daylight savings time schedule, and if they didn't you would have to set your computer time manually.
Which was all fine and good, except for several problems:
1. In order to show the correct time, Windows has to be currently updated.
2. Nobody in IT (that would be our ever-busy guru, he has no assistants) bothers to go around making sure the computers are updated.
3. Few employees bother to update their computers. Most are too busy doing their jobs. Many don't know how. More importantly, most lack admin authority on their computer and therefore cannot update their computers even if they wanted to.
4. If you don't have admin authority to update your computer, then you don't even have authority to change the time manually (something that amused me greatly -- oh no, we can't allow you to change the time! Chaos might ensue!)
5. Naturally if you change the time manually but don't turn off the function that automatically corrects the clock via the web, it'll just reset itself. Almost nobody I work with knew how to do this however, even assuming they had the authority to change the clock in the first place.
Anyway the net result was that virtually nobody's computers could display the correct time yesterday. Since I have admin authority, I went ahead and updated Windows. I knew, after all, that my computers at home showed the correct time automatically. Who knows how long (if ever) my computer at work had been updated -- the whole process took over an hour, but then I was fine.
Dave just set his computer to Mountain Time. Problem solved, as far as he was concerned. Nobody else was able to fix the problem on their computer.
It'll be interesting to see where this all leads. ^_^
Which was all fine and good, except for several problems:
1. In order to show the correct time, Windows has to be currently updated.
2. Nobody in IT (that would be our ever-busy guru, he has no assistants) bothers to go around making sure the computers are updated.
3. Few employees bother to update their computers. Most are too busy doing their jobs. Many don't know how. More importantly, most lack admin authority on their computer and therefore cannot update their computers even if they wanted to.
4. If you don't have admin authority to update your computer, then you don't even have authority to change the time manually (something that amused me greatly -- oh no, we can't allow you to change the time! Chaos might ensue!)
5. Naturally if you change the time manually but don't turn off the function that automatically corrects the clock via the web, it'll just reset itself. Almost nobody I work with knew how to do this however, even assuming they had the authority to change the clock in the first place.
Anyway the net result was that virtually nobody's computers could display the correct time yesterday. Since I have admin authority, I went ahead and updated Windows. I knew, after all, that my computers at home showed the correct time automatically. Who knows how long (if ever) my computer at work had been updated -- the whole process took over an hour, but then I was fine.
Dave just set his computer to Mountain Time. Problem solved, as far as he was concerned. Nobody else was able to fix the problem on their computer.
It'll be interesting to see where this all leads. ^_^
