- 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: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 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 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 12:48 pm to TigerGman
the better question is why the hell you'd still be running Server 2008.
But shouldn't be any problem installing updates on it.
But shouldn't be any problem installing updates on it.
Posted on 8/7/14 at 2:13 pm to TigerGman
I'm thinking that there should be a Change Management Policy in place for installing patches or updates to the system.
There should also been a auditable approval process. The person who approves the changes shouldn't be able to make the changes.
There should also been a auditable approval process. The person who approves the changes shouldn't be able to make the changes.
Posted on 8/7/14 at 11:53 pm to TigerGman
We apply updates to all 200+ of our Windows Servers monthly and have never had a major problem. Most are 2008R2 but there's still plenty of 2008 servers out there and even some 2003 servers that haven't been upgraded yet. On a rare occasion you might have to back out a patch because the application got wonky. Some of the production servers have updates installed manually after the updates are tested in the test environments.
Unfortunately, many custom applications are risky/costly to have migrated to brand new servers so if they were built on a 32-bit 2000 or 2003 server then 2008 is the end of the line in terms of in-place upgrades. Many organizations will ride that out as long as they have to, depending on the application. Server 2003 isn't end of life until next year, I believe.
Most organizations set up a WSUS server to approve updates and use group policy to point servers at it. This also helps with not saturating your internet connection. Bigger shops use SCCM to push updates out.
Wal-Mart has the oldest servers I've ever heard of at a big company. They have a bunch of servers that are 10 years old. I'm pretty sure that they have to catch on fire before approval is given to replace a server/host. Virtual environment runs 5,000 servers on 8 year old equipment and is at near 100% RAM utilization.
Unfortunately, many custom applications are risky/costly to have migrated to brand new servers so if they were built on a 32-bit 2000 or 2003 server then 2008 is the end of the line in terms of in-place upgrades. Many organizations will ride that out as long as they have to, depending on the application. Server 2003 isn't end of life until next year, I believe.
Most organizations set up a WSUS server to approve updates and use group policy to point servers at it. This also helps with not saturating your internet connection. Bigger shops use SCCM to push updates out.
Wal-Mart has the oldest servers I've ever heard of at a big company. They have a bunch of servers that are 10 years old. I'm pretty sure that they have to catch on fire before approval is given to replace a server/host. Virtual environment runs 5,000 servers on 8 year old equipment and is at near 100% RAM utilization.
This post was edited on 12/14/14 at 8:08 pm
Page 1 of 1
Popular
Back to top
Follow TigerDroppings for LSU Football News