Bloody Microsoft

[Clart]

I don't normally have much of a problem with them, and this whole saga could have been avoided. but last night i was called into work at 6:30, and again at 8:30 because a microsoft update closed a specific port on our land rover order receiving PC. This meant that production would be stopped if no orders were coming in. To cut a long story short, I used the system restore function on the PC after a lot of shouting by managers and worried faces (potential loss of £50k).

Makes me laugh that we have a new multi mullion pound production line and all it takes is one crappy microsoft update on a £400 PC to completely screw things up!

 

[martynh]

Re: Fcuking Microsoft

I work for Universal Music and we have a similar system at a site at Milton Keynes, it's a PC(old PIII) that runs a massive coveyor belt system, if that goes tits up nothing leaves the warehouse and that would mean half the top 10 albums not being delivered to stores like HMV, Tesco, etc.
We have a spare hot swap PC just in case, do you carry a spare "just in case"?

 

[Darren S]

Re: Fcuking Microsoft

Keep thinking like that m8, and you'll drive yourself insane. There are many things that you have to 'hope' work ok and then fix them if they don't. We've got our C&C machine which runs on a 24-7 basis being controlled by a P166 Compaq PC, caked in sh1t and dust. It's still working for now, so I've got other things to concern myself with!

I know what you're saying with MSoft - and any other updates, for that matter. We're very careful in applying stuff to the servers, but desktops get all the updates they can. It's worked so far....... (he says)

D.

 

[Clart]

Re: Fcuking Microsoft

its funny, that no one that tests these updates in the states though to tell us that one will close a specific port! its madness.

Don't carry a spare (the line has only been running 3 months) - i think this highlights the need for a backup solution

 

[martynh]

Re: Fcuking Microsoft

Look on the brightside, think of the call out pay and the overtime!

 

[Dafthead]

Re: Fcuking Microsoft

I make sure my ass will never be on the line like that, everything running anything important is on a proper server (some of them small desktop type servers) and they're all ASR backup'd to our NAS, If they blow up, I can get them back up and running within 40 mins

 

[dk]

Re: Fcuking Microsoft

its funny, that no one that tests these updates in the states though to tell us that one will close a specific port! its madness.

Don't carry a spare (the line has only been running 3 months) - i think this highlights the need for a backup solution

we have a windows update server that downloads everything, then we test it all and when its deemed ok its then pushed out to the desktops but not before, would never allow the automatic update thing to happen on corporate machines if thats what is happening.

 

[Rasclart]

Echo what Dave said

What port was it Ian? I assume MS deemed it a threat to have this port open!

 

[Clart]

The team in the states are supposed to test all these updates before pushing them out - we don't really have any control over it.

I think the port was 9100

 

[Pete]

Echo what Dave said

What port was it Ian? I assume MS deemed it a threat to have this port open!

Echo what the yokel b**ch says, we have 3 wsus servers, 2 live and one for testing!

I wonder if Weeman has this problem?

 

[martynh]

I doubt wee man has any problems that can't be fixed by a good fisting.