How to disabled windows update notification?
Hi,
We have 2 servers, a Windows Server 2003 SBS running as our DC and a Windows Server 2008 running as a TS that end users connect to.
The problem is the end users are prompted to restart the server, but the restart now button is grayed out. How do we disable this pop-up entirely? So the users don't have to postpone a message that they are unable action.
The end users are not local administrators. We've search Google for a solution but can find nothing out there.
We've tried enforcing a GPO with the Allow non-administrators to receive update notifications disabled but this hasn't prevent the message from appearing.
We have 2 servers, a Windows Server 2003 SBS running as our DC and a Windows Server 2008 running as a TS that end users connect to.
The problem is the end users are prompted to restart the server, but the restart now button is grayed out. How do we disable this pop-up entirely? So the users don't have to postpone a message that they are unable action.
The end users are not local administrators. We've search Google for a solution but can find nothing out there.
We've tried enforcing a GPO with the Allow non-administrators to receive update notifications disabled but this hasn't prevent the message from appearing.
Check this link with one GPO solution (http://www.online-tech-tips.com/computer-tips/disable-restart-now/). I know that this example is for Windows XP, but the GPO in Windows 2008 might be similar/the same.
Cheers.
Cheers.
ASKER
Applying the GPO to the TS servers OU.
Applied the above,
Read the description for this policy setting and it indicates that it may then automatically re-prompt after 10 minutes.
"If the status is set to Disabled or Not Configured, the default interval is 10 minutes."
Would this prevent the message from displaying?
Or it will prompt once then disappear for good?
Applied the above,
Read the description for this policy setting and it indicates that it may then automatically re-prompt after 10 minutes.
"If the status is set to Disabled or Not Configured, the default interval is 10 minutes."
Would this prevent the message from displaying?
Or it will prompt once then disappear for good?
You should get ONE prompt only
You should also set this: No auto-restart with logged on users for scheduled automatic updates installations and Enable it. (also in the TS Servers OU) or else you may get one user upsetting everyone else :-)
We actually go the other way and have a reprompt after 24 hours. This way it doesn't get forgotten, but then we have all the TS Servers reboot every night
You should also set this: No auto-restart with logged on users for scheduled automatic updates installations and Enable it. (also in the TS Servers OU) or else you may get one user upsetting everyone else :-)
We actually go the other way and have a reprompt after 24 hours. This way it doesn't get forgotten, but then we have all the TS Servers reboot every night
ASKER
Thanks Kieran,
Although this partially resolves the problem, we need to prevent the message popping up entirely as we continually get phone calls from the end users asking what they need to do. Training the users isn't really an option as we have new remote workers on a weekly basis. So ideally we need to prevent this message from popping up all together. The agreement is that the server is restarted on a Friday which means we generally have 2 days between update and restart where we have an increase in telephone calls of end users kindly reminding us the TS server needs to be restarted.
Could it be this is a limitation between Windows 2003 and 2008 integration? i.e. the Group Policy doesn't exist that affects this aspect of Windows 2008?
Although this partially resolves the problem, we need to prevent the message popping up entirely as we continually get phone calls from the end users asking what they need to do. Training the users isn't really an option as we have new remote workers on a weekly basis. So ideally we need to prevent this message from popping up all together. The agreement is that the server is restarted on a Friday which means we generally have 2 days between update and restart where we have an increase in telephone calls of end users kindly reminding us the TS server needs to be restarted.
Could it be this is a limitation between Windows 2003 and 2008 integration? i.e. the Group Policy doesn't exist that affects this aspect of Windows 2008?
Would it not be simpler to change the install settings then?
Under Configure Automatic Updates
Chosing Option 4 (auto download and schedule the install)
set the install day to Friday and the time to 18:00, then have your Server reboot at least an hour after this
Under Configure Automatic Updates
Chosing Option 4 (auto download and schedule the install)
set the install day to Friday and the time to 18:00, then have your Server reboot at least an hour after this
ASKER
Its possible the server will need to be kept online due to workers working late, needs to be a manual process to ensure the server isn't restarted with users logged on.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
We do not use WSUS on this system.
Although this is potentially resolving the issue, it isn't answering the question.
We need to disable this pop-up not work around it.
Although this is potentially resolving the issue, it isn't answering the question.
We need to disable this pop-up not work around it.
If you use a loopback policy for your Terminal Server OU, you could apply a script that removes all update balloons completey. I've never tried this with TS, but there is definitely a registry hack that stops those balloons appearing, but bare in mind, this stops ALL notification balloons, not just those specific to Automatic Updates.
I'm not exactly sure how this would work within TS though, and would require some testing for sure!!
Let me see if I can find anything about doing it in a TS environment specifically first. I'll get back to you.
Pete
I'm not exactly sure how this would work within TS though, and would require some testing for sure!!
Let me see if I can find anything about doing it in a TS environment specifically first. I'll get back to you.
Pete
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks for your efforts.
You're welcome, I'm sorry I couldn't provide a better answer. :(
Pete
Pete
The setting you want to use is: