Linked by Eugenia Loli on Thu 12th Jan 2006 07:36 UTC, submitted by Resolution
Thread beginning with comment 85125
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/23/13 23:22 UTC
Linked by Thom Holwerda on 05/23/13 22:04 UTC
Linked by Thom Holwerda on 05/23/13 22:01 UTC
Linked by Thom Holwerda on 05/23/13 17:52 UTC
Linked by Thom Holwerda on 05/22/13 22:23 UTC
Linked by Thom Holwerda on 05/22/13 13:38 UTC
Linked by Thom Holwerda on 05/22/13 13:30 UTC, submitted by JRepin
Linked by Thom Holwerda on 05/21/13 22:06 UTC
Linked by Thom Holwerda on 05/21/13 21:45 UTC
Linked by Thom Holwerda on 05/21/13 15:53 UTC
More News »
Sponsored Links



Member since:
2005-07-10
Nicc,
I understand your concern and frustration. The enterprise sector is more affected by this issue than home users due to some businesses can be financially affected both with downtime not planned and data loss. Forcing an update to be installed which reboots systems with out the end users permission is not acceptable. Microsoft should be held accountable for not ensuring this wouldn't happen. This is one of the differences between Windows and Linux systems where on Linux systems providing auto-update such as "SUSE Watcher" for SUSE Linux in most cases doesn't require a reboot. This in turn means providing less downtime while ensuring the system is up to date. The exception typically being only when a kernel or graphics driver is updated is when it's preferred to reboot on Linux.