Debate, and discuss, just dont Bore me.
Published on March 12, 2007 By Dr Guy In Personal Computing

Well, as Gideon says, Y2Kv7 has come and gone.  ANd it was not without pain.  From Solaris boxes that needed a lib-c and kernel patch, to firewalls that did not like a manual work around.  it has been an interesting 2 weeks.  2 weeks to the day I returned.

Cisco was the easiest.  Just a one line configuration change, and voila!  200+ routers and a bunch of switches were patched. Ditto NetApp boxes (running a modified Unix core).  Microsoft?  Well, if you were XP or 2K3, welcome to the patch heaven!  If you were running something like 2k (or god forbid NT4 - as there was zip, nada, zilch and zero on it), there was a registry hack.  Ok, that is fine, we can do that.

So we patched all the systems.  And at 2am 3/11/07, the 2K3 servers flipped over, the Netapp and Cisco boxes did as well.  The 2K boxes?  Nada!  Did not change.  A run to TZEdit showed the right settings, but you cant fool 2K!  No way!  They were not budging!  We finally figured it out (took about 1/2 hour).  Here is the critical line from Microsoft.

j. Select the new time zone you created, and then click Apply.

Ok, so you see that, open the control panel, click on time zones, and it has the correct one.  No new one there.  It was and always was Eastern (-5 UTC).  So you are done, right?

WRONG!  You have to RESELECT IT.  Even tho it was always right!  And not just click and select, but double click on it so you can get an Apply button!

So instead of being an hour and back to sleep, it was up all night with coast to coast (an adventure in itself) as I went to each 2k server and double clicked and applied.  Thanks for nothing Microsoft!

Oh, and that Solaris firewall?  Kept syncing all servers to the wrong time.  It does not like being manually set.  SO it was manually set back.  I would like to manually set it to something, and time is not on my mind.


Comments
on Mar 12, 2007
Ding Ding Ding! You freakin solved it!

We have been trying to figure out why the reg update didn't work. We just changed the time on the servers. My boss went in and reset the time zone on the mail server and poof everyone's inbox was no longer conflicted with time issues. Of course he didn't remeber he dit that until I reassigned the time zone to all of the server and the exchange server was the only one that did reset.

I just love chasing my tail.
on Mar 12, 2007

Reply By: just john

I am glad I was not the only one.  I hesitated writing this as I know there are a ton out there that are going to say "You Dummy!".  But at least one other read MS literally and it never said "reset" your time zone!

BTW:  If you just change the time on the servers, and you are using an NTP, it will change back.  So once you do this, just make sure the time is right as well. I only set the time on a handful (out of about 35) before I figured this one out, so the other 30 were fine.  But I did have to go back to the others.

on Mar 12, 2007
If you had Vista, you wouldn't have had to do anything. Mine changed itself correctly. But, I can't blame you for not running Vista at business yet.
on Mar 12, 2007
We are in AZ and also never set the time on any router to anything but Zulu time so the change took nothing at all.
on Mar 12, 2007

But, I can't blame you for not running Vista at business yet.

That plus Longhorn has not been released.  These were servers, not workstations.

on Mar 12, 2007

We are in AZ and also never set the time on any router to anything but Zulu time so the change took nothing at all.

I knew someone was going to bring up Az!  Curses you smart state!  I'll draw and quarter you when I move there!

on Mar 12, 2007
Gotta love Microsoft eh? I updated my Linux system with a simple file replacement. Geez, it was a terrible experience.
on Mar 12, 2007

Gotta love Microsoft eh? I updated my Linux system with a simple file replacement. Geez, it was a terrible experience.

As I did the NetAPP (BSD off spring).  Yea, I Sooooo love MS!

on Mar 12, 2007
As I did the NetAPP (BSD off spring).


BSD isn't too bad. Any *nix makes life so much easier.
on Mar 12, 2007
We had over a hundred Win2K desktops, and a few servers, that we updated using the Intelliadmin tool. We used PSTools to push it across the network, and then manually updated the ones that didn't respond. Of course the XP and 2K3 machines went off fine.
The OS-X workstations updated with the latest Mac patches. A couple OS9 machines remain to be manually patched.
on Mar 13, 2007
BSD isn't too bad. Any *nix makes life so much easier.


As long as you do not include Solaris in that. That was the one ghat needed the kernel patch. Bleeecccchhh!  
on Mar 13, 2007
A couple OS9 machines remain to be manually patched.


Geez! You still running those? I thought they died years ago. Well,not the hardware. Macs never die,they just retire.
on Mar 13, 2007
Geez! You still running those? I thought they died years ago. Well,not the hardware. Macs never die,they just retire.


Yeah, we don't like to jump into all this fancy-shmancy newfangled OSX stuff too quick now.....

Actually it's more a case of supporting the platforms our customers use, and a few of them still run OS9, so we have to keep a couple systems to run the same versions of the apps they're running. We're a printing company with customers supplying files in every conceivable format, and we have to be able to support them since they are the customer after all.

Just a note, I found about a half-dozen boxes that didn't take the update we pushed, but I'd say over 90% of them took.
All in all, Microsoft knows there are still a huge number of W2K systems, especially in enterprise situations. They could have made everyone's lives easier by pushing out the patch themselves instead of shucking it off on the local support staff.
on Mar 14, 2007
They could have made everyone's lives easier by pushing out the patch themselves instead of shucking it off on the local support staff.


But then they would not have been Microsoft.
Meta
Views
» 2401
Comments
» 14
Sponsored Links