IT mgrs/admin/directors, CTOs
 

quick poll for those here: How much time has the DST issues affected you? Gresch I already know what you think! :)

DST :gun:

We support a Time and Labor Management product and as of yesterday we still had about 5,000 clients that still didn't update.

So hasWindows put through updates or will I need to manually reset the time on my computer, which run XP?

:hijack:

SANGuru specifically asked IT Managers/admins/directors/cto's how they're handling it, not "does anyone need tech support for the DST change".

Thou shall not hijack! :)

not changing the time XP machine means nothing. Not changing it on servers, Network attached storage, enterprise backup software, etc could mean business going down entirely. Do yourself a favor and google it if you want to know... Next stupid question

Not true. XP part of active directory and if the desktop is out of sync, you are doomed. Same goes for Share point sites, SQL enterprise needs it's own fix..you name it..MICROSUCKS!!!

We are going through a tough time. Updating 400 routers and several firewalls. No fun. Most of the CISCO IOS(es) are still not updated with the DST fix.

he's talking about personal laptops. so who give a rat ass.. except for mickey.. LOL:rofl: besides if he paid attention, it would've been in the auto updates. but you know! WINBLOWS

one of my peers is a die hard republicans and has stated this will make him switch to democrat because it is so stupid

It's been a pain in our ass... a mini Y2K of sorts. We've patched up/updated just about all our servers, including Exchange, Windows, and Unix... under our AD domain. Those Divisions under their own AD are also updating, but we can't control them, so... who knows? But, yeah, it has been a major pain. We also use Decru dataforts for encryption, and those have had to be updated. Yuk... We'll see what happens on 3/11. :D

Juan

You could always move to Japan - no DST there!

Acutally, non-North American windows users do need to patch their systems otherwise if they use any applications that calculate time differential between their local time zone and a NA time zone, it will be off by 1 hour for 2 weeks now, and 1 week come November. (Think Group Calendering in Exchange/Office)

mini y2k is right
 

Bunch of crap going on. And now - Oracle just rolled out a patch for their AS. Nice of them - especially when we were first told it was not necessary....

its been a living hell brothas....

not to hijack the thread, but no DST here in Taiwan, either :D

Acutally, non-North American windows users do need to patch their systems otherwise if they use any applications that calculate time differential between their local time zone and a NA time zone, it will be off by 1 hour for 2 weeks now, and 1 week come November. (Think Group Calendering in Exchange/Office)

By the way, Java needs to be patched :(

You know what runs Java? Blackberry. Guess who has 225 Blackberry's deployed?

:(

A pain, but manageable so far. The BES server patch was this past weekend, caused some problems.

Worst thing is it is all for naught. We only did it in Canada to remain synched with our largest trading partner. Thanks guys.

It seems like every single one of my customers have been pinging me about this. I've gotten about 70+ calls from my customers worldwide asking if my product will need modification or patches. It's caused some major pain for me to.. I could only imagine for you guys.

very much a mini y2k and as head of our global networks i've heard more than once "america's forcing another dumb mistake down our throats."

I'm hearing the same thing from our European and SE Asia offices....

Have I ever mentioned how VERY VERY little I miss being an IT program manager? :)

True. Its a mini-Y2k experience. :tsk:

*SLAP




carry on :P

We are having to rewrite the time change system on our mainframe...it sucks because we only have one guy that can program on our system locally due to the fact it is very old and was written in RM Cobol and there are very few programmers left that know the language

Where do you work? Met Life?

Not a huge deal here. Our OS guys were on the necessary patches and changed needed for some time now and finished all prodution systems this past weekend. My basis team coordinated with the oracle guys and those patches are all set to go in and we've applied the necessary note to our systems.

Not a big headache... thankfully

Right now I'm making sure our update server has the proper updates ready to be pushed out. It shouldn't be bad, but the helpdesk admin will be busy on the 12th.

My family company electronics distribution covering 18 states in the centeral US...system was written in the late 80's and has been continually modified one of the most stable invintory management systems for our industry over 50% of the companys that started with this system in the 80's/90's are still running it...designed for distirbution logistics and invintory management by SESCOR on Unix platform...we have performed many modifications and a Linux platform transfer over the years...looking at new systems but will probably be a year or two before we get one implimented

We have 600 plus servers and 2,700 client PC's. This has been bad for us and there are some not so nice bugaboos with Outlook calendaring (or as we call it lovingly Outbreak or Lookout!). So our changes are this weekend and we'll see the fallout next Monday. Can't wait. (sigh) I just dream of the good old days with Novell and GroupWise; life was easier then....

This might help you:


http://support.microsoft.com/kb/931836

Wow, I thought that only a HUGE insurance company would still be on a Cobol based system. (and I used to work at Met Life in the late 80's :))

well, I got everything on our SUS server configured to push the updates for exchange 2003, win xp, and win 2003. Outlook I will do some research on.

Outlook takes it's time from the OS.

don't even get me started on Groupwise!! There is a good reason why there is not too many SUSE linux or netware shops left!

there are actually quite a few banks still running Z-OS, AS400 mainframes with apps programmed in Cobol. I'm surprised a lot of those survived Y2K but what do I know.. LOL

Netware's x.500 runs circles around MS's. If Microsoft ever gets their hands on that model and changes their permissions model, i will become an instant MS fan.

I'm surprised that they survived y2k as well.... that's why i said it :rofl:

you can throw security out the door.. do you really think their permissions/authentification method will hold water (ie, loading and unloading of NLMs, netware debugger modes - jumping in and out to bypass security, hacking of NDS files containing passwords which we all know have been done just to name a few even in 6.5.)

I'm just talking about how file/directory permissions are set within the admin tools. i.e. to give your id access to directory xyz in netware i simply give you permission to that directory and you can map to it.

The same thing in MS means that the user has to be able to see the ENTIRE directory structure from the root to the directory and they have to be DENIED access to all of the other directories up the tree from the target directory.

It's ridiculous.

Don't even get me started on group permissioning.

haha.. I hear ya... wait til you get into NAS mixed mode authentication with CIFS and NFS... don't think you have a gateway in your environment right?there's a reason why they call it usercrapper. Til this day, I still hate messing with UIDs, GIDs, and still get pretty confused.

Also over a hundred heavy equipment dealers, all on AS400s with a legacy system written in Cobol. Yes, finding programmers is hard. I wasn't involved then, but I heard that Y2K was tough with that application too.

no doubt. I was heavily involved in my old company's Y2K conversion. (damn that was a long time ago!!) At the time it wasn't really hard, just hard to FIND the people who could do it.. lost art if you know what I mean.

Exactly the problem the fix was not a big issue just the people with the skills to change what needed to be fixed

Also AT&T still uses cobol systems my Uncle is a cobol programmer currently his job consists of teaching new young programmers Cobol to support frame relay systems

Our program may be dated but I can honsetly say we have not had any problems with this system we update around the core program about every six months (support of IP based printing etc) and upgrade to new servers every two years this system also interfaces with our Apache webserver and two SQL servers to provide active invintory and ordering capabilities to our customers...Using ICE.TCP to interface with the system from workstations. Looking at SAP or Citrix solutions for our system change...anyone have insight on these?

Please help us IT nons
 

I am not trying to hijack this tread but was wondering if all you smart people could tell us non IT types what we need to do our computers to accommodate the change in Day Light Savings time.

Thank you,

Blue

So if we have the current updates, SP2 for XP, we are ok and don't have to do anthing else?

That is the approach I am taking with my home computers and network.

And for the record, I am not a smart IT guy, I just have a lot of them working for me ;)

Thank you!