- My Forums
- Tiger Rant
- LSU Recruiting
- SEC Rant
- Saints Talk
- Pelicans Talk
- More Sports Board
- Fantasy Sports
- Golf Board
- Soccer Board
- O-T Lounge
- Tech Board
- Home/Garden Board
- Outdoor Board
- Health/Fitness Board
- Movie/TV Board
- Book Board
- Music Board
- Political Talk
- Money Talk
- Fark Board
- Gaming Board
- Travel Board
- Food/Drink Board
- Ticket Exchange
- TD Help Board
Customize My Forums- View All Forums
- Show Left Links
- Topic Sort Options
- Trending Topics
- Recent Topics
- Active Topics
Started By
Message
Server 2008 update goes bad...
Posted on 8/7/14 at 7:23 am
Posted on 8/7/14 at 7:23 am
Small office, --friend ran suggested windows security updates and something went wrong. System went tits up including backup and server couldn't be accessed on network.
Long story but this has caused a major disruption and friend is catching flack for running the update.
IT said " you don't ever run updates on an older system"
I call B.S. on that. I've never heard anyone say don't run a suggested update cause your computer is too old. Besides that would mean leaving the system full of bugs and especially security holes.
Thoughts?
Long story but this has caused a major disruption and friend is catching flack for running the update.
IT said " you don't ever run updates on an older system"
I call B.S. on that. I've never heard anyone say don't run a suggested update cause your computer is too old. Besides that would mean leaving the system full of bugs and especially security holes.
Thoughts?
This post was edited on 8/7/14 at 7:24 am
9
Posted on 8/7/14 at 7:31 am to TigerGman
How old is the system?
I did updates for first time in awhile. One of them caused blue screen of death and I had to delete it
I did updates for first time in awhile. One of them caused blue screen of death and I had to delete it
Posted on 8/7/14 at 7:51 am to TigerGman
quote:
you don't ever run updates on an older system
Not all systems require all updates
Posted on 8/7/14 at 8:05 am to HailToTheChiz
quote:
How old is the system?
Not sure I'll try to find out. But isn't that the point? What difference does it make? If it runs the base operating system it should run any suggested updates to the system.
Posted on 8/7/14 at 8:17 am to TigerGman
there are a lot of options here that we aren't aware of. is it a software or hardware issue that caused the failure?
and, is your friend responsible for the backups that can't be restored?
and, is your friend responsible for the backups that can't be restored?
Posted on 8/7/14 at 8:31 am to TigerGman
quote:
Thoughts?
Why did your friend have access to the server
Posted on 8/7/14 at 8:32 am to TigerGman
How did the update cause the backup media to fail?
Posted on 8/7/14 at 8:59 am to stat19
quote:
How did the update cause the backup media to fail?
They don;t know. Friend says it was later that night a bad storm came through and he suspects a power surge is the real culprit.
I'm just looking for some backup that updating the software OS on an "older computer" is a no no is bull crap.
I been facking with computers since DOS 5.0 and that's a first for me.
Posted on 8/7/14 at 9:10 am to TigerGman
quote:Depends on how critical the system is, and whether it can be reached from the internet.
I'm just looking for some backup that updating the software OS on an "older computer" is a no no is bull crap.
"If it ain't broke, don't fix it" definitely applies in many cases.
Posted on 8/7/14 at 9:11 am to TigerGman
No matter how old if you run Server 2008 you need to install updates. But you have to be careful installing them, you can always uninstall updates if you suspect one of them has caused problems.
Posted on 8/7/14 at 9:12 am to Korkstand
quote:
"If it ain't broke, don't fix it" definitely applies in many cases.
Are you saying you don't run Microsoft's recommended security updates on your server software?
Posted on 8/7/14 at 9:17 am to TigerGman
quote:
Are you saying you don't run Microsoft's recommended security updates on your server software?
Yes
Posted on 8/7/14 at 9:28 am to TigerGman
quote:
Are you saying you don't run Microsoft's recommended security updates on your server software?
I'm saying if you have a critical system that is not reachable from the internet, then you'd better have a damn good reason for installing any updates. And if you do install anything, you do them one at a time, you know exactly what each update does, and you verify that there are no side effects afterward. You might even do a full backup after each one, too.
You should probably never just click "install updates" if a machine is as critical as this one seems to be.
Posted on 8/7/14 at 9:35 am to Korkstand
quote:
You should probably never just click "install updates" if a machine is as critical as this one seems to be.
Well that's why I'm asking. I was trying to get a handle on what you IT guys do in actual practice.
ETA: Still, you guys seem to be talking in general for all systems. My question is why would an older system be more susceptible to problems. I simply don't see it. It will either run the OS or it won't. Updates shouldn't do anything to change system requirements.
This post was edited on 8/7/14 at 9:40 am
Posted on 8/7/14 at 9:50 am to TigerGman
Microsoft Updates are really the last line of defense in securing critical systems. Sure, IT people install them when they can. But, they aren't the 1st, 2nd, 3rd, etc. line of defense as far as security is concerned.
Posted on 8/7/14 at 10:01 am to TigerGman
quote:It's not that an update might change system requirements, it's the fact that any update has the potential to cause a problem, and the older the system the more likely it is that it is widely depended on.
My question is why would an older system be more susceptible to problems. I simply don't see it. It will either run the OS or it won't. Updates shouldn't do anything to change system requirements.
I don't know the specific scenario for your friend's company, and we can't be sure that they have an actual policy of "never update old systems", but generally the older the system, the more it is relied upon, and the more cautious you should be about changing anything.
Posted on 8/7/14 at 10:06 am to TigerGman
quote:
said " you don't ever run updates on an older system"
I'd say they are about right, given a small office environment. If it ain't broke....
At least do a full backup before hand
Posted on 8/7/14 at 10:12 am to jcole4lsu
Two thoughts:
1- I have a Win 2003 server that get's every update that's ever come out and have never had a problem
2- It's not a mission critical server, and if it was, I would not touch that shite without having another just like it as a staging server that would get all updates first before doing anything to the production server
One of my customers had a Win 2000 server until about 3 weeks ago.. it managed a critical SAN. Nobody got within 10 feet of that thing and everyone puckered up when we needed to do anything on it. (we did not trust the customers backup either)
1- I have a Win 2003 server that get's every update that's ever come out and have never had a problem
2- It's not a mission critical server, and if it was, I would not touch that shite without having another just like it as a staging server that would get all updates first before doing anything to the production server
One of my customers had a Win 2000 server until about 3 weeks ago.. it managed a critical SAN. Nobody got within 10 feet of that thing and everyone puckered up when we needed to do anything on it. (we did not trust the customers backup either)
Posted on 8/7/14 at 10:20 am to Meauxjeaux
quote:this is one thing that companies fail hard at. And, it is because they are cheap and don't want to pay to duplicate their systems.
It's not a mission critical server, and if it was, I would not touch that shite without having another just like it as a staging server that would get all updates first before doing anything to the production server
Frick, we have over 550 Virtual Servers. We have the ability to snapshot servers prior to doing updates and then failing back if they cause issues. That has been done with maybe 50 machines ever, and probably just maybe 25 of them on a regular basis.
Of course, we also have backups of our stuff and can rebuild them if need be.
The organization really needs to look at their backup solution and figure out why this critical system wasn't backed up. And if it was, why they aren't able to recover it. If it is that critical. They should have regular backups onsite and offsite. And, they should be testing backup recovery on a regular basis.
Posted on 8/7/14 at 10:27 am to hashtag
quote:
The organization really needs to look at their backup solution and figure out why this critical system wasn't backed up. And if it was, why they aren't able to recover it. If it is that critical. They should have regular backups onsite and offsite. And, they should be testing backup recovery on a regular basis.
This is pretty much it. shite happens, back it up. We have walked out on customers who refuse to get some sort of backup protection. My boss has called a business owner a dumbass right to his face because of it.
Page 1 of 3
Popular
Back to top
Follow TigerDroppings for LSU Football News