Episode 57 - DST Part III
Posted by Podcast Team on 12 Mar 2007 8:15 pm. Filed under Podcasts.
Your Hosts: Matt and Bill
* Bill’s DST Story
- Matt’s DST Story
- Problems with the Mixer
- TV
- Favorites ADM Template
- AutoPatcher
- Wii Info
Running time: 25:32
Download Here
On March 15th, 2007 at 2:53 pm
Hey guys, glad to hear that you made it thru the “pain in the arse? DST update without too many issues.
You had mentioned that you wanted to get my take on the process.
I did have some unusual results.
My environment is as follows The Exchange server is Win2K with Exchange 2K, with all of the MS patches updated.
have under 15 2K boxes. I used the IntelAdmin Network Administrator tool. I could have used the command line, or the 3 at a time crippleware trial version, but I liked the tool enough that I wanted to support the continuing efforts of the programmers, so I purchased a seat.
On Sunday March 11th I drove in to the office (65 miles each way, thank goodness for Podcasts, and XM Radio) to ensure that all was well. I had tested the client tool on my workstation earlier, and all seemed well. I had warned my users that they might see issues in Outlook and our CRM tool SalesLogix (Sage software) via e-mail the prior week.
I ended up updating all of my local client computers with the latest MS patches, since I was in the office anyway. On Monday morning, I had a few users who wanted to run the TZMove patch to update their outlook calendar items. I setup a computer in my training room where Domain users were given local admin rights to the computer. None of my users are allowed local Admin, or power user rights, not even the owners of the company. There are a few exceptions to this rule, however those situations are closely monitored.
After the TZMove was run on one of the VP’s system, everything looked great, Then it was run on another VP’s and that proved interesting. All of the events were back in sync, however they were now an hour off. This was for both reoccurring and single events. As of today 3/15, I had not discovered the reason for this behavior.
Interesting note: When a client computer has the SalesLogix installed and the xp client was patched with the DST patch, SalesLogix and MS outlook (Outlook 2000, 2003, & 2007), would error out and fail to launch. The fix, provided by Sage software, was some additional reg entries to add and or change some additional DST data.