Tom Wright

Marcos, Thank you for making that clear and while I'm still uneasy about certain options being implemented this makes it bit easier to manage.

I agree with Techguy007, I must confess this seems like a very odd thing to introduce. I would like to be able to "choose" what it does. The only choice I seem to have in this decision for OUR infrastructure is I can either wait for this to automatically turn on or turn it on now. If the above is true and you can't disable this built in rule that's really not helpful. A key question I have on this subject is does the rule trigger an automated reboot after an update is installed ? If it does this really presents a serious issue for some of my servers. I have several key products that if they where to reboot in our 24/7 operation would cause me some serious headaches and possible data loss. I think you should really make this an option we can choose to keep off and by that I mean not forcing an option that we have to disable. I would be happy to click a conformation box every month advising me to add a policy for auto updates but would like to retain the control. Am I also correct in assuming that when an update happens some features are disabled until the update is fully completed depending on the update? I would rather have a few days old version of the software while I organise a restart with it all operational than have some features go offline until a restart.