I am so elephanting mad at Microsoft right now I think I'll just......
-
You had one job to do Ron. Go to that attorney's office at lunch and down a 2011 small business server, put more RAM in and bring it up, all in an hour. So I showed up, they all went to lunch I went start, shutdown and then it happened. Installing Update 1 of 76 Don't tun off your computer. That was 2.5 hours ago and it's 61 of 79. Look M.S., you and I know this is a server OS. The least you could have done was consider other people's time and reputation and give us admins the option to not do it right now as when they come back from lunch they are going to expect to be able to get at their files. This happened to us last year when we were to just down and up the server for trivial matters and ran into 176 updates. I am now connecting to all of the servers in our care and A. Disabling the Windows Update Service and B. creaming c:\windows\Software Distribution I am so mad I could cry. I feel like grabbing my dog and riding the rails to who knows where. :mad:
No doubt a frustrating predicament. You're damned if you do and damned if you don't, so you do with the innocent thought of 'it's good hardware, it should be done in a jiffy' and get bitten when 76 updates, 2 restarts (false hope) and 3 hours later you can finally get your work done. I have seen (and probably ranted about it) server updates (2016 to be specific) where you just had to walk away from it to not get pissed that it's been at 41% for 40 minutes :wtf: ...is it 'stuck'? (one of the joys of the new indeterminate progress indicators :| ) I've come damned close myself to just yanking the cable and seeing what happens. :laugh: I have also been an optimistic fool and waited patiently for progress that never came. :sigh: I hope by now your troubles are over! :)
"Go forth into the source" - Neal Morse
-
You had one job to do Ron. Go to that attorney's office at lunch and down a 2011 small business server, put more RAM in and bring it up, all in an hour. So I showed up, they all went to lunch I went start, shutdown and then it happened. Installing Update 1 of 76 Don't tun off your computer. That was 2.5 hours ago and it's 61 of 79. Look M.S., you and I know this is a server OS. The least you could have done was consider other people's time and reputation and give us admins the option to not do it right now as when they come back from lunch they are going to expect to be able to get at their files. This happened to us last year when we were to just down and up the server for trivial matters and ran into 176 updates. I am now connecting to all of the servers in our care and A. Disabling the Windows Update Service and B. creaming c:\windows\Software Distribution I am so mad I could cry. I feel like grabbing my dog and riding the rails to who knows where. :mad:
-
Postpone updates, you get bitten.
why? I visit sites with internal servers that haven't run update for a long time - disabled for good, one since 2012 that one runs 24/7 and at very most gets shut down once a year for building power maintenance or similar external reasons only. It works, leave it alone, no shutting down for updates, NO FAILED UPDATES because there aren't any, no incompatibilities introduced by updates - heard a lot about that too.... (oh, and virus scans on demand only) better than 99.995% up-time. (None of those clients has ever regretted that advice I gave them to do that.) Yeah I know laughing at the idiots fighting update issues is cruel, but apart from that ... am I doing something wrong? Name it! (Please no MS evangelism bullshit, 99% of the reasons ms and the flocks of ms-lemings give for "always updating" and always full time virus scans are complete and utter bullshit.)
-
You had one job to do Ron. Go to that attorney's office at lunch and down a 2011 small business server, put more RAM in and bring it up, all in an hour. So I showed up, they all went to lunch I went start, shutdown and then it happened. Installing Update 1 of 76 Don't tun off your computer. That was 2.5 hours ago and it's 61 of 79. Look M.S., you and I know this is a server OS. The least you could have done was consider other people's time and reputation and give us admins the option to not do it right now as when they come back from lunch they are going to expect to be able to get at their files. This happened to us last year when we were to just down and up the server for trivial matters and ran into 176 updates. I am now connecting to all of the servers in our care and A. Disabling the Windows Update Service and B. creaming c:\windows\Software Distribution I am so mad I could cry. I feel like grabbing my dog and riding the rails to who knows where. :mad:
Ron Anders wrote:
I feel like grabbing my dog and riding the rails to who knows where.
I hope that's not some sort of dirty euphemism, because the image it conjured in my mind could send me to prison if I gave voice to it.
“That which can be asserted without evidence, can be dismissed without evidence.”
― Christopher Hitchens
-
why? I visit sites with internal servers that haven't run update for a long time - disabled for good, one since 2012 that one runs 24/7 and at very most gets shut down once a year for building power maintenance or similar external reasons only. It works, leave it alone, no shutting down for updates, NO FAILED UPDATES because there aren't any, no incompatibilities introduced by updates - heard a lot about that too.... (oh, and virus scans on demand only) better than 99.995% up-time. (None of those clients has ever regretted that advice I gave them to do that.) Yeah I know laughing at the idiots fighting update issues is cruel, but apart from that ... am I doing something wrong? Name it! (Please no MS evangelism bullshit, 99% of the reasons ms and the flocks of ms-lemings give for "always updating" and always full time virus scans are complete and utter bullshit.)
Whoa, just being practical. If you don't want 76 patches at once, patch often. Same thing applies to Linux. That's all.
-
You had one job to do Ron. Go to that attorney's office at lunch and down a 2011 small business server, put more RAM in and bring it up, all in an hour. So I showed up, they all went to lunch I went start, shutdown and then it happened. Installing Update 1 of 76 Don't tun off your computer. That was 2.5 hours ago and it's 61 of 79. Look M.S., you and I know this is a server OS. The least you could have done was consider other people's time and reputation and give us admins the option to not do it right now as when they come back from lunch they are going to expect to be able to get at their files. This happened to us last year when we were to just down and up the server for trivial matters and ran into 176 updates. I am now connecting to all of the servers in our care and A. Disabling the Windows Update Service and B. creaming c:\windows\Software Distribution I am so mad I could cry. I feel like grabbing my dog and riding the rails to who knows where. :mad:
-
Ron Anders wrote:
I am so mad I could cry. I feel like grabbing my dog and riding the rails to who knows where.
Now picture when it fails on update 75 and decides to roll everything back.
You kick puppies too, don't you? :laugh:
Software Zen:
delete this; -
Whoa, just being practical. If you don't want 76 patches at once, patch often. Same thing applies to Linux. That's all.
Joe Woodbury wrote:
Same thing applies to Linux
A perhaps minor difference being that you decide when.
I wanna be a eunuchs developer! Pass me a bread knife!
-
You kick puppies too, don't you? :laugh:
Software Zen:
delete this; -
You had one job to do Ron. Go to that attorney's office at lunch and down a 2011 small business server, put more RAM in and bring it up, all in an hour. So I showed up, they all went to lunch I went start, shutdown and then it happened. Installing Update 1 of 76 Don't tun off your computer. That was 2.5 hours ago and it's 61 of 79. Look M.S., you and I know this is a server OS. The least you could have done was consider other people's time and reputation and give us admins the option to not do it right now as when they come back from lunch they are going to expect to be able to get at their files. This happened to us last year when we were to just down and up the server for trivial matters and ran into 176 updates. I am now connecting to all of the servers in our care and A. Disabling the Windows Update Service and B. creaming c:\windows\Software Distribution I am so mad I could cry. I feel like grabbing my dog and riding the rails to who knows where. :mad:
Just switch the power off. It'll be be fine. Most likely. They've got backups, haven't they.