ready for daylight savings??

dubbs112

For people in the US daylight savings has been changed to this weekend!!


Is everyone ready?

KGhaleon

The world is ending!

georgemc

Aaaargh!

shednik

Yea things are lookin good for Sunday! Took long enough to get all the patches to work...

hanakuin

I loathe DST!!!

sthomas

JDMurray

The new change in the start of DST (second Sunday in March) and the end of DST (first Sunday in November ) is due to the Energy Policy Act of 2005. A study will be performed to see if DST actually saves energy. If it is found to save energy, we may eventually have year-round DST with no change. If no energy savings are recognized, the USA may switch back to the previous DST start/end dates.

http://en.wikipedia.org/wiki/Daylight_saving_time

blargoe

I'm ready but some of the vendors that support us apparently aren't.

hanakuin

Option 2: DST update

For customers who prefer to have a hotfix, Microsoft lets customers purchase all DST 2007 hotfixes for $4,000, for affected Microsoft products in Extended Support by using an Extended Hotfix Support contract. Customers will only be charged a single fee of $4,000 to obtain all hotfixes needed to update their systems for DST 2007.

I found this insane!!! I almost fell out of my chair laughing. Maybe I should try to get a $4,000 bonus for creating a patch for our older systems.

JDMurray

Microsoft isn't the only DST problem. It seems that the BlackBerry Enterprise Server for Microsoft Exchange also needs patching--unfortunately, the first patch released not only doesn't fully work, but it screws up the BlackBerry. Anyone having a fun time patching Exchange Servers specifically for BlackBerry users?

Plantwiz

jdmurray wrote:

The new change in the start of DST (second Sunday in March) and the end of DST (first Sunday in November ) is due to the Energy Policy Act of 2005. A study will be performed to see if DST actually saves energy. If it is found to save energy, we may eventually have year-round DST with no change. If no energy savings are recognized, the USA may switch back to the previous DST start/end dates.

http://en.wikipedia.org/wiki/Daylight_saving_time

Funny, back in 2005 around the time of this Act, there was a study released (source is not turning up quick tonight) pointing out that people started getting up EARLIER to get to work so were actually using more electricity (lights, cooking...microwave/toaster etc.., hair dryers, etc...) just to make their day.


I miss living in South Bend.....we didn't have this DST crap

neo468

jdmurray wrote:

Microsoft isn't the only DST problem. It seems that the BlackBerry Enterprise Server for Microsoft Exchange also needs patching--unfortunately, the first patch released not only doesn't fully work, but it screws up the BlackBerry. Anyone having a fun time patching Exchange Servers specifically for BlackBerry users?

Very much so, we had to reconfigure several BlackBerry in our enterprise from the first patch, and ended up doing a manual DST update from blackberry site. The main concern in our enterprise is the Outlook calendar issue. Have a feeling our Help Desk is going to get bombarded with calls why they were 1 hour late to there appointments!! Typical of users to address the issue after it's already happened.

JDMurray

neo468 wrote:

The main concern in our enterprise is the Outlook calendar issue. Have a feeling our Help Desk is going to get bombarded with calls why they were 1 hour late to there appointments!!

I know one site where they decided it was easier to delete all Outlook calendar appointments scheduled after March 10th and re-schedule the appointments on the 11th rather than updating Outlook on every computer.

Also, no patches were released by Microsoft on this last "Patch Tuesday," although there are (at least) five zero-day exploits for Windows and Office that are still not patched. MS supposedly skipped this month because of the DST patching problems, and they are giving the world's IT departments time to catch up.

Webmaster

Reminds me of when we introduced the Euro and all systems had to be patched. We also received stickers to put over the Guilder sign on the keyboard. Kinda like a small millenium bug but less scary.

hanakuin

On my way in to work this morning I notice that all of the banks that had time/temp on their signs had the wrong time!!! Must be a manual update

Kaminsky

Webmaster wrote:

Kinda like a small millenium bug but less scary.

GAH! Now that was a complete farce! Planes dropping out of the sky, all your money disapearing from the bank, no electricity, would your car suddenly stop! What a joke that was.

Very sneaky plan by the pc/os manufacturers that was. They raked it in along with old age pensioners who got paid a fortune to come in and patch old legacy systems that were sitting at the core of many modern systems. I expect they were laughing all the way to the bingo hall after that.

garv221

From researching and having to patch clients and servers, I am fully convinced that MS is the worst operating system and company associated with IT.

I am still running Exchange 2000 (upgrade 07' this summer) exchange 03 and 07 had simple install patches. MS wanted $4,000 for an Exchange 2000 patch which was free for 03 and 07 users. The DST help site was a **** to read with more information than I gave a **** about, complicating the process. I believe they were charging $4,000 to Exchange 2000 users simply to tax them for not upgrading or convincing them now to upgrade after this mess. I got my server updated with some .exe's MS had available but I'm sure not everyone figured it out. It was a horrible process, with little explanation and required me to edit a few log files including copying users from the error log into the active log to ensure all users were updated (instructions not on MS site) and then run a batch file created. I really hope for a better operating system from a better company in the future. This was it for me with MS... I cannot stress how much I absolutely despise MS Windows and everything they stand for, I even hate Steve Ballmer's penguin shaped bald head.

dubbs112

jdmurray wrote:

neo468 wrote:

The main concern in our enterprise is the Outlook calendar issue. Have a feeling our Help Desk is going to get bombarded with calls why they were 1 hour late to there appointments!!

I know one site where they decided it was easier to delete all Outlook calendar appointments scheduled after March 10th and re-schedule the appointments on the 11th rather than updating Outlook on every computer.
.

We were very close to doing the same. The patch for Outlook was crap it did not fix any of the re-occurring appointments properly.

Megadeth4168

dubbs112 wrote:

jdmurray wrote:

neo468 wrote:

The main concern in our enterprise is the Outlook calendar issue. Have a feeling our Help Desk is going to get bombarded with calls why they were 1 hour late to there appointments!!

I know one site where they decided it was easier to delete all Outlook calendar appointments scheduled after March 10th and re-schedule the appointments on the 11th rather than updating Outlook on every computer.
.

We were very close to doing the same. The patch for Outlook was crap it did not fix any of the re-occurring appointments properly.

I found the Outlook patch to fix some problems but create new problems that didn't exist before the patch was applied! Many people that we support decided that they would rather recreate their calendars instead of having the patch applied.

blargoe

garv221 wrote:

From researching and having to patch clients and servers, I am fully convinced that MS is the worst operating system and company associated with IT.

I got my server updated with some .exe's MS had available but I'm sure not everyone figured it out. It was a horrible process, with little explanation and required me to edit a few log files including copying users from the error log into the active log to ensure all users were updated (instructions not on MS site) and then run a batch file created.

This was exactly my experience. Total BS, which was for the most part undocumented. Did you ever read the Exchange team's DST blog? Oh good God.

garv221

blargoe wrote:

garv221 wrote:

From researching and having to patch clients and servers, I am fully convinced that MS is the worst operating system and company associated with IT.

I got my server updated with some .exe's MS had available but I'm sure not everyone figured it out. It was a horrible process, with little explanation and required me to edit a few log files including copying users from the error log into the active log to ensure all users were updated (instructions not on MS site) and then run a batch file created.

This was exactly my experience. Total BS, which was for the most part undocumented. Did you ever read the Exchange team's DST blog? Oh good God.

lol yes! I started with that site after becoming extremely angry with MS's site. I also surfed a lot of forums and tried cyphering random users posts to find the correct answer. This was completely uncalled for, I even seen registry editing for Exchange! lol

I noticed a lot of people were getting hung up and using the wrong tzmove.exe and not using the one from Outlook or copying the tzmove.exe to the program files directory but not copying the associated ini file with it...I'm sorry you had to experience this also, what was the major help to you?

Kasor

I'm still fixing the problem... more and more W2K popping out the DTS problems......

The Win XP is OK with a simple update, but W2K have to install on the workstation to make work well. I tried update the from the group policy... nope.. not working.

I'm pushing to get rip of all the W2K..

Ahriakin

Last post Mar 19 2007
Your post Mar 18 2008

I think you have more than a single DST hour to deal with

stlsmoore

haha I didn't even catch that...I read the entire post without looking at the dates

JDMurray

I disabled auto DST switching on my W2K servers last year and manually changed them over this year. W2K is still too useful to give up on.

Kasor

The problem is some of the in-house program and database program need to run on W2K because they still working on the new project.

So, I cannot get rip of everything. However, as long as I found those W2K workstation and not mission essential to the company. They are out of the door.

Kasor

My senior tech still try to find a better way to do it. Currently, they are still using TZEdit everytime when DST shift.

Ahriakin

Have you run Microsoft's own DST update VBscript for 2000? It should permanently fix the problem.