March 13th, 2007
You are currently browsing the articles from datapoohbah.com written on March 13th, 2007.
Well, they ‘almost’ got it right. (ignoring the fact that they waited until the last minute like everyone else and grossly underestimated the effort involved in everyone updating)
Most things work, and have the right time. That is unless you have a 797x color phone. You know one of the ‘good’ phones, the expensive ones.

If you have one of these, check the time. Is it right?
It probably is because when you did your update you rebooted all of the phones right?
Now reach around back and unplug it (if you are using this powered over Ethernet simply unplug the cable, if you have a power brick, just unplug that).
Let the phone boot up.
What time does your phone say now? Yeah, that’s what I thought, it’s back to the wrong time.
Now simply reset your phone, ‘hit settings, **#**’ and viola!, you’re back to the right time.
So what’s the difference from a ‘powered-off boot’ and a reset/reboot? And why does that screw up the time? Who knows, but it’s stuff like this that drive us absolutely crazy.
Written by datapoohbah on March 13th, 2007 with 1 comment.
Read more articles on Commentary and IT and The Truth Hurts and VOIP.
Not only does Microsoft provide you with a spectacular tool (Tzmove.exe), not to be confused with (Tzmove.exe) that you can distribute to all of your brilliant end users and ask them to run on your behalf.
(This works so well because as we know, end users just love running tools to fix IT problems that really should be addressed at the server level, and of course they fully understand what has to happen and why things are broken. Yes, delegating IT problems down to the user level is always the best move).
The best they could do from an Exchange administrator perspective is this:
- Create a client fix tool.
- Create absolutely the most convoluted way to take that ‘client’ based tool and script it to run on one machine, mailbox after mailbox. (That is in fact what they are doing).
- Exchange security issues as side, this should be fixable at the server level, without pretending to be a MAPI client for crying out loud.
Remember when Microsoft released the Windows NT domain, and promised us Single point of administration? This is not what I had in mind, if I wanted to script client tools to do things in bulk across my organization, we’d still be running DOS.
Written by datapoohbah on March 13th, 2007 with no comments.
Read more articles on Commentary and IT and The Truth Hurts.