Automatic Updates (AU) are, in general, designed for client computers; it is assumed the end users should use the AU and receive the updates as soon as possible.
However, the servers should not, in general, rely on AU or use that feature.
The reasons are:
The general idea is to turn off the AU for servers; in case the updates are critical (refer to significant vulnerabilities), they should first be tested on a sever replica (sandbox server) first, otherwise there's a risk to break the existing services on a real-life server. And, of course, full system and user data backup should be made before such patches are applied.
However, the servers should not, in general, rely on AU or use that feature.
The reasons are:
- all the patches/fixes should be well-tested first, prior to installing on real-life server
- mission-critical applications may be quite sensible to any changes, including the fixes applied to system components
The general idea is to turn off the AU for servers; in case the updates are critical (refer to significant vulnerabilities), they should first be tested on a sever replica (sandbox server) first, otherwise there's a risk to break the existing services on a real-life server. And, of course, full system and user data backup should be made before such patches are applied.
