Inconsistent Windows Update policy

We have a group of XP machines which have not been getting their Windows Updates even
though I've specified it in the ZEN workstation policy. This policy is applied to
all of our campus XP computers, and since it seems to work in most places I can't
figure out why these machines are having a problem.
The policy specifies to automatically download and install updates. However, some of
these systems are configured to download but wait for administrator approval to
install. The weirdest part is that some of them seem to be switching back and forth
between these two settings. As I was working on one yesterday that was set for admin
approval, I noticed that it had changed to automatic installation. I have no idea
why, but I suspect it's a policy issue.
Below are some lines pulled from the windowsupdate.log file on one the machines. It
shows the Windows auto update mode switching back and forth, and most of the time it
is not "scheduled" like it should be.
I've checked everything I know of. How does one troubleshoot this kind of thing?
Thanks for any assistance.
2009-10-01 08:03:32:390 1444 278 AU # Approval type: Scheduled (Policy)
2009-10-01 08:04:22:953 1444 278 AU # Approval type: Pre-install notify (Policy)
2009-10-01 08:53:18:453 1460 278 AU # Approval type: Pre-install notify (Policy)
2009-10-01 08:53:25:062 1460 278 AU # Approval type: Pre-install notify (Policy)
2009-10-02 11:34:42:687 1460 288 AU # Approval type: Pre-install notify (Policy)
2009-10-02 11:34:52:265 1460 288 AU # Approval type: Pre-install notify (Policy)
2009-10-05 08:13:53:671 1444 27c AU # Approval type: Pre-install notify (Policy)
2009-10-05 08:14:12:406 1444 27c AU # Approval type: Scheduled (Policy)
2009-10-05 08:14:31:890 1444 27c AU # Approval type: Pre-install notify (Policy)
2009-10-05 13:54:32:187 1444 278 AU # Approval type: Pre-install notify (Policy)
2009-10-05 13:54:41:031 1444 278 AU # Approval type: Pre-install notify (Policy)
2009-10-06 08:11:00:312 1444 274 AU # Approval type: Pre-install notify (Policy)
2009-10-06 08:11:32:796 1444 274 AU # Approval type: Pre-install notify (Policy)
2009-10-07 08:09:00:250 1464 27c AU # Approval type: Pre-install notify (Policy)
2009-10-07 08:09:14:656 1464 27c AU # Approval type: Pre-install notify (Policy)
2009-10-07 11:21:50:812 1464 27c AU # Approval type: Scheduled (Policy)
2009-10-07 11:49:44:328 1440 264 AU # Approval type: Pre-install notify (Policy)
2009-10-07 11:49:50:437 1440 264 AU # Approval type: Scheduled (Policy)
2009-10-07 11:58:02:390 1448 27c AU # Approval type: Pre-install notify (Policy)
2009-10-07 11:58:22:015 1448 27c AU # Approval type: Scheduled (Policy)
2009-10-08 08:09:51:546 1456 284 AU # Approval type: Pre-install notify (Policy)
2009-10-08 08:10:21:921 1456 284 AU # Approval type: Scheduled (Policy)
2009-10-08 08:10:42:046 1456 284 AU # Approval type: Pre-install notify (Policy)
- Jim Wagner

Jim,
It appears that in the past few days you have not received a response to your
posting. That concerns us, and has triggered this automated reply.
Has your problem been resolved? If not, you might try one of the following options:
- Visit http://support.novell.com and search the knowledgebase and/or check all
the other self support options and support programs available.
- You could also try posting your message again. Make sure it is posted in the
correct newsgroup. (http://forums.novell.com)
Be sure to read the forum FAQ about what to expect in the way of responses:
http://forums.novell.com/faq.php
If this is a reply to a duplicate posting, please ignore and accept our apologies
and rest assured we will issue a stern reprimand to our posting bot.
Good luck!
Your Novell Product Support Forums Team
http://support.novell.com/forums/

Similar Messages

My SCCM 2012 server is listed in the Windows updates local policy

On my end user computers Navigate to Computer Configuration > Administrative Templates > Windows Components > Windows Updates > Specify intranet Microsoft update service location
Does it specify your Primary Site server? YES
Endpoint Protection leverages the software update component of ConfigMgr for delivery of definitions. This local Windows Updates policy was created when you configured this component.
1. How do I disable this local Windows Updates policy in SCCM ? Thanks

The client will set these local policy settings if your Client Settings are set to manage software updates and you don't have a group policy in place.
If you do NOT want ConfigMgr to control updates, then you can go to Client Settings > Software Updates and change "Enable software updates on clients" to No.
Nash Pherson, Senior Systems Consultant
Now Micro -
My Blog Posts
If you've found a bug or want the product worked differently,
share your feedback.
<-- If this post was helpful, please click "Vote as Helpful".

How to install Windows Updates on a 2012 Domain Controller w/Group Policy Settings

Hello All,
I'm having an issue installing Windows Updates on my Windows Server 2012 Standard with AD DS role, acting as a backup DC.
I have Group Policies setup for the Domain Controllers to download updates from my WSUS server but not to install them. When I go to my Windows Server 2003 R2 Domain Controller, I can install updates via the "Install Updates and Shutdown". That
option doesn't show up on the 2012 server. I can see from my WSUS server and the event viewer that the updates are being downloaded to the 2012 server........just no option for me to install the updates.
Am I just missing something or will I need to change the way my Group Policy is setup to allow installs and/or downloads? Any help would be greatly appreciated!
Tony

So I've totally removed the GPO settings for configuring updates on the Default Domain Controllers OU and I can get the Windows Server 2003 Server to get updates from Windows Updates, but the 2012 Server still won't show me how to download or install any
updates. It just states on the log-in screen that there are "Windows Updates Sign in and install important updates".
Well guess what Microsoft! I've signed in and still don't see where I can install updates!!!
I guess because you've set AU=3.
There doesn't seem to be much documented in depth about AU/WUAgent (not in the history of forever), but Lawrence and others in the WSUS forum do cover a lot of related question about the agent and also GP settings.
Lawrence has blogged a lot of detail about the registry settings which are available for AU/WU, and how some of those settings are not practically of any use since WinXP.
So, even though your question isn't about WSUS, the WSUS forum is a great place to visit for help for WUAgent etc.
Anyway, "where can I install updates?" :
on the Start screen, Search for "Windows Update"
or
Settings charm
Change PC Settings
Update and Recovery
Windows Update
or
Control Panel\System and Security\Windows Update
Some further (light) discussion on the "new" behaviour:
http://blogs.msdn.com/b/b8/archive/2011/11/14/minimizing-restarts-after-automatic-updating-in-windows-update.aspx
Don
(Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

Uninstall a windows update usign group policy

Hi !
Recently I installed Service Pack 1 for windows server 2008 R2 and after that i lost RDP to it.
Investigated it and found a security update is the cause.
I connected using iLo and uninstalled it and all went ok
so here is what i want
is there anyway to uninstall a windows update from different clients using group policy or WSUS ?

Hi,
On Group Policy Management Console, Go to GPO that will contain the script and go to Computer Configuration > Policies > Windows Settings > Scripts (Start up/Shutdown)
Click Add and then Browse. This will open the GPO in the Sysvol share for you to create the batch file.Add Shutdown
script
use Shutdown scripts when you need to remove an update which creates issue.
Note: updates may require a reboot after removal. By using a Shutdown script, the script can run at the next system shutdown/reboot event and the update removal process gets the reboot it needs.
By using a Startup script, you may end up needing two reboots to remove the update: one reboot so that the script runs at the next system start and a possible second reboot if the update removal process requires it.
Use the below script by replacing the you own KB that needs to be kicked from servers.
Make below .bat
C:\Windows\System32\wusa.exe/uninstall/kb:example12345555/quiet/norestart/log
By adding the optional, /log, you can go into the Setup Event Log and check that your update was removed.
Event Log- Windows update was successfully uninstalled
Regards
Raj
ADS/DNS/DHCP/RIS/GROUP POLICY/PowerShell/VMware/Esxi/Storage.

Domain Group Policy changes causes clients to be unable to connect to WSUS for Windows Updates

Domain Controller is Windows Server 2008 R2 64-bit, Group Policy Management version 6.0.0.1. WSUS server is Windows Server 2008 Enterprise 32-bit, Update Services version 3.2.7600.226. Client machines are Windows 7, some are 64-bit and some are 32-bit.
Every time we make any changes to any of our Group Policies most of our clients stop getting their Windows Updates from the WSUS server within 2-3 days. This occurs when we add a new policy for a group of users, temporarily disable a policy or edit a policy.
Check of the WindowsUpdate.log on affected client machines shows:
2014-06-25 13:40:44:976 760 1610 PT WARNING: GetAuthorizationCookie failure, error = 0x80072EE2, soap client error = 5, soap error code = 0, HTTP status code = 200
2014-06-25 13:40:44:977 760 1610 PT WARNING: Failed to initialize Simple Targeting Cookie: 0x80072ee2
2014-06-25 13:40:44:977 760 1610 PT WARNING: PopulateAuthCookies failed: 0x80072ee2
2014-06-25 13:40:44:977 760 1610 PT WARNING: RefreshCookie failed: 0x80072ee2
2014-06-25 13:40:44:977 760 1610 PT WARNING: RefreshPTState failed: 0x80072ee2
2014-06-25 13:40:44:977 760 1610 PT WARNING: PTError: 0x80072ee2
2014-06-25 13:40:44:977 760 1610 Report WARNING: Reporter failed to upload events with hr = 80072ee2.
A further check of the log files shows:
2014-06-21 19:36:06:995 156 1b0c Misc WARNING: SendRequest failed with hr = 80072ee2. Proxy List used: <proxy server name:8080> Bypass List used : <(null)> Auth Schemes used : <>
We do not use a proxy except for Internet connections. We configure IE with a pac file. This is set through Group Policy since we restrict user accounts from being able to set it.
The clients that are connecting to the WSUS server have these entries instead:
2014-06-24 09:12:16:779 992 270 Agent Setting download properties on call A20329BC-3467-4B7E-B9F4-6AC6ACBA23E1: priority=3, interactive=1, owner is system=0, proxy settings=1, proxy session id=2
I have a routine that will fix the problem but it is time-consuming and pulls me away from other things I should be doing:
Run registry files on client machine (WindowsUpdate and AU) This is not always necessary and is already set by Group Policy and the affected clients already have the registry settings. No idea why it is necessary to do but it the steps below don't always
work unless it is.
netstop bits and netstop wuauserv
ipconfig /flushdns
Delete qmgr*.* files from Downloader folder
Delete Software Distribution folder
Run from command prompt:
sc.exe sdset bits D:(A;;CCLCSWRPWPDTLOCRRC;;;SY)(A;;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;BA)(A;;CCLCSWLOCRRC;;;AU)(A;;CCLCSWRPWPDTLOCRRC;;;PU)
sc.exe sdset wuauserv D:(A;;CCLCSWRPWPDTLOCRRC;;;SY)(A;;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;BA)(A;;CCLCSWLOCRRC;;;AU)(A;;CCLCSWRPWPDTLOCRRC;;;PU)
netstart bits and netstart wuauserv
wuauclt /resetauthorization /detectnow
Run Windows Updates again from Control Panel
This routine always fixes the problem but I've found that I must do each step to guarantee success.
How or where is the proxy setting being changed for WSUS that we see in the WindowsUpdate logs and how do I prevent this from happening? It is also curious that it happens to most but not all of the client machines. When it does happen it's not always the
same client machines.

You're right - the WSUS server is on the inside and does not need a proxy server. Tried running the netsh winhttp reset proxy command but was still not able to connect to the WSUS server. After running the netsh winhttp reset proxy command received response:
Current WinHTTP proxy setting: Direct access <no proxy server>.
Ran the command at 13:49 and then tried Windows Updates again. Here's snippet from the log file:
2014-06-27 13:49:56:889 548 f6c AU Triggering AU detection through DetectNow API
2014-06-27 13:49:56:890 548 f6c AU Triggering Online detection (interactive)
2014-06-27 13:49:56:890 548 4b8 AU #############
2014-06-27 13:49:56:890 548 4b8 AU ## START ## AU: Search for updates
2014-06-27 13:49:56:890 548 4b8 AU #########
2014-06-27 13:49:56:893 548 4b8 AU <<## SUBMITTED ## AU: Search for updates [CallId = {9CE06AB2-E859-4B4D-8D1A-193AD89623C5}]
2014-06-27 13:49:56:893 548 1260 Agent *************
2014-06-27 13:49:56:893 548 1260 Agent ** START ** Agent: Finding updates [CallerId = AutomaticUpdates]
2014-06-27 13:49:56:893 548 1260 Agent *********
2014-06-27 13:49:56:893 548 1260 Agent   * Online = Yes; Ignore download priority = No
2014-06-27 13:49:56:893 548 1260 Agent   * Criteria = "IsInstalled=0 and DeploymentAction='Installation' or IsPresent=1 and DeploymentAction='Uninstallation' or IsInstalled=1 and DeploymentAction='Installation' and RebootRequired=1
or IsInstalled=0 and DeploymentAction='Uninstallation' and RebootRequired=1"
2014-06-27 13:49:56:893 548 1260 Agent   * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
2014-06-27 13:49:56:893 548 1260 Agent   * Search Scope = {Machine}
2014-06-27 13:49:56:893 548 1260 Setup Checking for agent SelfUpdate
2014-06-27 13:49:56:893 548 1260 Setup Client version: Core: 7.6.7600.256 Aux: 7.6.7600.256
2014-06-27 13:49:56:894 548 1260 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
2014-06-27 13:49:56:901 548 1260 Misc Microsoft signed: Yes
2014-06-27 13:49:56:927 548 1260 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
2014-06-27 13:49:56:934 548 1260 Misc Microsoft signed: Yes
2014-06-27 13:49:56:936 548 1260 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
2014-06-27 13:49:56:943 548 1260 Misc Microsoft signed: Yes
2014-06-27 13:49:56:956 548 1260 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
2014-06-27 13:49:56:962 548 1260 Misc Microsoft signed: Yes
2014-06-27 13:49:56:974 548 1260 Setup Determining whether a new setup handler needs to be downloaded
2014-06-27 13:49:56:974 548 1260 Setup SelfUpdate handler is not found. It will be downloaded
2014-06-27 13:49:56:974 548 1260 Setup Evaluating applicability of setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.256"
2014-06-27 13:49:56:976 548 1260 Setup Setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.256" is already installed.
2014-06-27 13:49:56:976 548 1260 Setup Evaluating applicability of setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256"
2014-06-27 13:49:56:989 548 1260 Setup Setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256" is already installed.
2014-06-27 13:49:56:989 548 1260 Setup Evaluating applicability of setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256"
2014-06-27 13:49:57:007 548 1260 Setup Setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256" is already installed.
2014-06-27 13:49:57:007 548 1260 Setup SelfUpdate check completed. SelfUpdate is NOT required.
2014-06-27 13:49:57:165 548 1260 PT +++++++++++ PT: Synchronizing server updates +++++++++++
2014-06-27 13:49:57:165 548 1260 PT   + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL =
http://(FQDN of WSUS server)/ClientWebService/client.asmx
2014-06-27 13:49:57:175 548 1260 PT WARNING: Cached cookie has expired or new PID is available
2014-06-27 13:49:57:175 548 1260 PT Initializing simple targeting cookie, clientId = 6be4a1ae-3313-4855-bdb1-57e3312f03ec, target group = AGENCIES, DNS name = dpk2.clear-rcic.rcc.org
2014-06-27 13:49:57:175 548 1260 PT   Server URL =
http://(FQDN of WSUS server)/SimpleAuthWebService/SimpleAuth.asmx
2014-06-27 13:50:57:280 548 1260 Misc WARNING: SendRequest failed with hr = 80072ee2. Proxy List used: <(proxy server):8080> Bypass List used : <(null)> Auth Schemes used : <>
2014-06-27 13:50:57:281 548 1260 PT   + Last proxy send request failed with hr = 0x80072EE2, HTTP status code = 0
2014-06-27 13:50:57:281 548 1260 PT   + Caller provided proxy = No
2014-06-27 13:50:57:281 548 1260 PT   + Proxy list used = webgate.rcc.org:8080
2014-06-27 13:50:57:281 548 1260 PT   + Bypass list used = <NULL>
2014-06-27 13:50:57:281 548 1260 PT   + Caller provided credentials = No
2014-06-27 13:50:57:281 548 1260 PT   + Impersonate flags = 0
2014-06-27 13:50:57:281 548 1260 PT   + Possible authorization schemes used =
2014-06-27 13:50:57:281 548 1260 PT WARNING: GetAuthorizationCookie failure, error = 0x80072EE2, soap client error = 5, soap error code = 0, HTTP status code = 200
2014-06-27 13:50:57:281 548 1260 PT WARNING: Failed to initialize Simple Targeting Cookie: 0x80072ee2
2014-06-27 13:50:57:281 548 1260 PT WARNING: PopulateAuthCookies failed: 0x80072ee2
2014-06-27 13:50:57:281 548 1260 PT WARNING: RefreshCookie failed: 0x80072ee2
2014-06-27 13:50:57:281 548 1260 PT WARNING: RefreshPTState failed: 0x80072ee2
2014-06-27 13:50:57:281 548 1260 PT WARNING: Sync of Updates: 0x80072ee2
2014-06-27 13:50:57:281 548 1260 PT WARNING: SyncServerUpdatesInternal failed: 0x80072ee2
2014-06-27 13:50:57:281 548 1260 Agent   * WARNING: Failed to synchronize, error = 0x80072EE2
2014-06-27 13:50:57:282 548 1260 Agent   * WARNING: Exit code = 0x80072EE2
2014-06-27 13:50:57:282 548 1260 Agent *********
2014-06-27 13:50:57:282 548 1260 Agent ** END ** Agent: Finding updates [CallerId = AutomaticUpdates]
2014-06-27 13:50:57:282 548 1260 Agent *************
2014-06-27 13:50:57:282 548 1260 Agent WARNING: WU client failed Searching for update with error 0x80072ee2
2014-06-27 13:50:57:302 548 e04 AU >>## RESUMED ## AU: Search for updates [CallId = {9CE06AB2-E859-4B4D-8D1A-193AD89623C5}]
2014-06-27 13:50:57:302 548 e04 AU   # WARNING: Search callback failed, result = 0x80072EE2
2014-06-27 13:50:57:302 548 e04 AU   # WARNING: Failed to find updates with error code 80072EE2
2014-06-27 13:50:57:302 548 e04 AU #########
2014-06-27 13:50:57:302 548 e04 AU ## END ## AU: Search for updates [CallId = {9CE06AB2-E859-4B4D-8D1A-193AD89623C5}]
2014-06-27 13:50:57:302 548 e04 AU #############
2014-06-27 13:50:57:303 548 e04 AU Successfully wrote event for AU health state:0
2014-06-27 13:50:57:303 548 e04 AU AU setting next detection timeout to 2014-06-27 22:50:57
2014-06-27 13:50:57:304 548 e04 AU Setting AU scheduled install time to 2014-06-28 05:00:00
2014-06-27 13:50:57:304 548 e04 AU Successfully wrote event for AU health state:0
2014-06-27 13:50:57:305 548 e04 AU Successfully wrote event for AU health state:0
2014-06-27 13:51:02:285 548 1260 Report REPORT EVENT: {BD25B39C-6570-454C-A046-AF3AF2DEBDD4} 2014-06-27 13:50:57:282-0400 1 148 101 {00000000-0000-0000-0000-000000000000} 0 80072ee2 AutomaticUpdates Failure Software
Synchronization Windows Update Client failed to detect with error 0x80072ee2.
2014-06-27 13:51:02:295 548 1260 Report CWERReporter::HandleEvents - WER report upload completed with status 0x8
2014-06-27 13:51:02:295 548 1260 Report WER Report sent: 7.6.7600.256 0x80072ee2 00000000-0000-0000-0000-000000000000 Scan 101 Managed
2014-06-27 13:51:02:295 548 1260 Report CWERReporter finishing event handling. (00000000)
2014-06-27 13:51:48:184 548 4b8 AU ########### AU: Uninitializing Automatic Updates ###########
2014-06-27 13:51:48:187 548 4b8 DnldMgr FATAL: DM:CBitsJob::SetCallbackHandler: SetNotifyInterface failed with 0x80080008.
2014-06-27 13:51:48:187 548 4b8 DnldMgr FATAL: DM:CBitsJob::SetCallbackHandler: SetNotifyInterface failed with 0x80080008.
2014-06-27 13:51:48:187 548 4b8 DnldMgr FATAL: DM:CBitsJob::SetCallbackHandler: SetNotifyInterface failed with 0x80080008.
2014-06-27 13:51:48:187 548 4b8 DnldMgr FATAL: DM:CBitsJob::SetCallbackHandler: SetNotifyInterface failed with 0x80080008.
2014-06-27 13:51:48:187 548 4b8 Report CWERReporter finishing event handling. (00000000)
2014-06-27 13:51:48:252 548 4b8 Service *********
2014-06-27 13:51:48:252 548 4b8 Service ** END ** Service: Service exit [Exit code = 0x240001]
2014-06-27 13:51:48:252 548 4b8 Service *************
2014-06-27 13:51:53:002 548 160c Misc =========== Logging initialized (build: 7.6.7600.256, tz: -0400) ===========
2014-06-27 13:51:53:002 548 160c Misc   = Process: C:\Windows\system32\svchost.exe
2014-06-27 13:51:53:002 548 160c Misc   = Module: c:\windows\system32\wuaueng.dll
Ran a batch file which resets the AU and WindowsUpdate registry keys and then runs the steps listed above:
regedit /s C:\WindowsUpdate.reg
regedit /s C:\AU.reg
net stop bits
net stop wuauserv
Ipconfig /flushdns
del C:\ProgramData\Microsoft\Network\Downloader\qmgr*.*
del /F /Q C:\Windows\SoftwareDistribution\*.*
sc.exe sdset bits D:(A;;CCLCSWRPWPDTLOCRRC;;;SY)(A;;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;BA)(A;;CCLCSWLOCRRC;;;AU)(A;;CCLCSWRPWPDTLOCRRC;;;PU)
sc.exe sdset wuauserv D:(A;;CCLCSWRPWPDTLOCRRC;;;SY)(A;;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;BA)(A;;CCLCSWLOCRRC;;;AU)(A;;CCLCSWRPWPDTLOCRRC;;;PU)
net start bits
net start wuauserv
wuauclt /resetauthorization /detectnow
After this runs, am able to connect to WSUS server for updates. I mentioned Group Policy changes because this only breaks after the Group Policy changes. It doesn't affect every client machine but most of them. Was wondering how the proxy gets reset from
none to the proxy server for Windows Updates?

Disabling windows update via group policy

hi,
i would like to disable automatic windows upate via group policy on windows server 2008. is it possible?
thanks.
sundeep

hi,
disabling the automatic update is not a recommended practice, but here are the steps,
Click Start, and then click
Run.
Type gpedit.msc, and then click
OK.
Expand Computer Configuration.
Right-click Administrative Templates, and then click
Add/Remove Templates.
Click Add, click
Wuau.admin the Windows\Inf folder, and then click Open.
Click Close.
Under Computer Configuration, expand
Administrative Templates, expand Windows Components, and then expand Windows Update.
The Configure Automatic Updatespolicy appears. This policy specifies whether the computer receives security updates and other important downloads through the Windows Automatic Updates feature. The settings for this policy let you specify if
automatic updates are enabled on the computer. If the service is enabled, you must select one of the three configuration options.
To view the policy settings, double-click the
Configure Automatic Updatespolicy.
To turn on Automatic Updates, click
Enabled or to turn off select
Disabled
hope this helps
thanks

Block Patch KB3002657 from installing/being available via Windows Update via Group Policy

Hi Everyone,
Been hearing a lot of issues around with KB3002657 causing Authentication issues. We've recently appeared to have similar issues. I'm currently getting out SCCM guru's to run
an inventory on our environment to review if we have had this deployed to our environment, either by Windows Update (manual), SCCM/Wsus etc. If we do we're looking to have this removed and not deployed via our normal mechanisms to stop any production outages.
I would like to see if it is possible to block/hide this update from being visible from Windows Update, possibly by Group Policy.
From memory Microsoft created specifc ADM templates for blocking updated for Internet Explorer version to assist with the same type of issues (i.e. to stop IE from being updated
via Automatic Updates). Would there by anything like this available for this update, or does anyone know of another way (specifc Registry settings or ADM files that could be edited) to achieve this?
Thanks in advance.
Simon

Please, see solution:
The V2 release of MS15-027 / KB 3002657 that resolves NTLM v2
authentication failures by Windows Server 2003 DCs is available:
The X86 version is at http://www.microsoft.com/en-us/download/details.aspx?id=46147
The ia64 version is at: http://www.microsoft.com/en-us/download/details.aspx?id=46204
The amd64 is at: http://www.microsoft.com/en-us/download/details.aspx?id=46054
Best Regards, Andrei ...
Microsoft Certified Professional

Windows Update Group Policy Settings?

I browsed through SCCM 2012 documentation for an answer of what to set in a GPO when wanting to use SCCM 2012 SP1 to handle updates.
At the moment I have:
WSUS/Reporting pointing to wsus server and its appropriate ports
Allow Automatic Updates immediate installation: Enabled
All signed updates from intranet Microsoft Updates: Enabled
Configure Automatic Updates: Enabled
Configure automatic Updating - 4 Auto download and schedule the install
Scheduled install day: Every Friday
Scheduled install time: 21:00
Enabling Windows Update Power Management to auto wakeup the system to install Enabled
No auto-restart with logged on users for scheduled automatic updates installations: Enabled
Reschedule Automatic Updates scheduled installation: Disabled
I didn't see any hint, perhaps it is there and I missed it, on what might be the prescribed settings for a GPO.
What is happening is Windows 8ish is drawing a band across the screen and reporting that your computer needs to reboot; and then reboots. From what I could tell in the WindowsUpdate.log file is that round the time it was observed rebooting smsexec
requested a reboot. But oddly I also saw in the Windows Update log was a reboot was scheduled to expire on the 26th, two days after the observed behavior and I also saw that other reboot requests either expired or had been scheduled.
What I have recently done to various Windows Update deployments was to remove the check boxes for Deadline behavior to prevent Software Updates and System restarts outside the Maintenance Window and also checked Device restart behavior
Suppress system restart on the following devices Servers and Workstations.
At the moment I would like to figure out what the GPO settings should be and also how to determine what had requested reboot and when and if the reboot actually happened.
Thanks!

This blog series by Jason should help you with that (it's still applicable):
http://blog.configmgrftw.com/software-update-management-and-group-policy-for-configmgr-what-else/
http://blog.configmgrftw.com/software-updates-management-and-group-policy-for-configmgr-cont/
My Blog: http://www.petervanderwoude.nl/
Follow me on twitter: pvanderwoude

Regarding the Windows Update

Regarding the Windows Update, is this given answers are Right? Thank you :)
Aruna

Hi,
1. In the Group Policy Object Editor, expand Computer Configuration, expand
Administrative Templates, expand Windows Components, and then click
Windows Update.
2. In the details pane, click Specify Intranet Microsoft update service location.
3. Click Enabled and type the HTTP(S) URL of the same WSUS server in the
Set the intranet update service for detecting updates box and in the
Set the intranet statistics server box. For example, type
http(s)://servername in both boxes, where servername is the name of the server. If the port is not 80 for HTTP or 443 for HTTPS, you should add the port number:
https://servername:portnumber.
4. Click OK.
For more information, please read this article:Configure Clients Using Group Policy
https://technet.microsoft.com/en-us/library/cc708574(v=ws.10).aspx
Karen Hu
TechNet Community Support

Shutdown directive bundle doesn't allow windows updates

I have a directive bundle to shutdown a machine. The bundle works fine in terms of shutting down the machine at the appointed time, however, what it does not seem to do, at least on Windows 7, is to apply any updates.
If you have pending updates to apply, choosing, Start/Shutdown will shutdown the computer and apply updates. This doesn't work with the ZCM 10 directive bundle to shutdown.
Any ideas why?

Originally Posted by craig_wilson
The WSUS GPO settings for Shutdown behavior
On 1/24/2012 4:46 PM, motc7 wrote:
>
> craig_wilson;2170342 Wrote:
>> But what are your settings?
>>
>> On 1/24/2012 3:26 PM, motc7 wrote:
>>>
>>> spond;2170124 Wrote:
>>>> Motc7,
>>>>
>>>> are these updates that you have got ready for install, or Windows
>>>> Update? How do you have Windows Update configured?
>>>>
>>>> --
>>>>
>>>> Shaun Pond
>>>
>>> these are updates that have already come down from the WSUS server
>> and
>>> are awaiting installation.
>>>
>>>
>>
>>
>> --
>> Craig Wilson - MCNE, MCSE, CCNA
>> Novell Knowledge Partner
>>
>> Novell does not officially monitor these forums.
>>
>> Suggestions/Opinions/Statements made by me are solely my own.
>> These thoughts may not be shared by either Novell or any rational
>> human.
>
> I guess I am not following when you mean "what are your settings?" In
> WSUS? Zenworks? Not following sorry.
>
>
Craig Wilson - MCNE, MCSE, CCNA
Novell Knowledge Partner
Novell does not officially monitor these forums.
Suggestions/Opinions/Statements made by me are solely my own.
These thoughts may not be shared by either Novell or any rational human.
I looked on our Domain Controller where we have our Group Policy. I looked at the local policy and it says "not configured" all the way down the line. Is that what you are looking for?

Windows Update Error 80080005 Windows 7 Client with WSUS 3.0 SP2 server

Hello everyone, I've looked around at other threads related to my issue, and I can't seem to find a correct answer.
I have a computer lab that I've recently installed a Windows 7 Enterprise image onto 35 Dell Optiplex computers (most are 380's, a few older 360's).
I created the image using MDT2010 and used one of the 380's as a reference.
All has been well for about a month or two but recently 6 computers are giving me Windows Update errors with the error code of 80080005.
I have a WSUS 3.0 SP2 server running, and all of my other computers seem to be getting their updates just fine. WSUS has the problematic computers in it's database, but it shows that they haven't checked in for "x" days.
I have Avast 4.8 Professional installed, I have OpenDNS configured to block bad websites, ____, etc. and I also use an Untangle server to prevent access to bad websites. I've ran a Malwarebytes' Anti-Malware scan on the affected computers, as well
as Windows Defender scan, and Windows Live OneCare scans, and all have found no malicious software.
I have also tried resetting the Windows update service as described here: http://support.microsoft.com/kb/971058 as well as a script that supposedly does the same thing, but also resets all previous
update events, but I can't find the script source right now (I had ran it last week, and it didn't work).
I'm currently running a SFC /Scannow on one of the computers, and now it has finished. It gives the error: Windows Resource Protection could not start the repair service. I'll have to google that next.
The last windows update that ran on the computer that I'm working on now was installed on 11-18-2010 and was a Windows Defender Update (KB915597 Def: 1.93.1985.0)
Previous to that was 11/9/2010 2 updates: KB977165 and KB981852.
I guess I'll have to look at all of the other machines to see if they have the same updates installed.
Anyway, has anyone else had this problem? I've seen vista home editions, and RC's but no real Windows 7 Pro+ RTM versions in business environments where updates were controlled by WSUS.
Thanks for any help that you can provide!
By the way, I only work at this location once a week (tuesdays, well thursdays too, but I'm next door to this building, but I have remote access), so bare with me on trying to fix things.

Ok, for the sake of completeness, I have completed the instructions given by Miya Yao.
After stopping the Windows Update Service (from an Admin Command prompt window), renaming the SoftwareDistribution folder to SDold, then starting the update service again, I still receive the same error when checking for updates.
The windows update log shows this (starting from about 4am) and I just reset the service at about 9:10, which you can see in the log.
2010-12-21 04:19:02:342 940 f20 Agent WARNING: WU client failed Searching for update with error 0x80080005
2010-12-21 04:19:02:342 940 cd4 AU >>## RESUMED ## AU: Search for updates [CallId = {8957B50F-46F1-44C4-A347-20D4C5E91D47}]
2010-12-21 04:19:02:342 940 cd4 AU # WARNING: Search callback failed, result = 0x80080005
2010-12-21 04:19:02:342 940 f20 Report CWERReporter finishing event handling. (00000000)
2010-12-21 04:19:02:342 940 cd4 AU # WARNING: Failed to find updates with error code 80080005
2010-12-21 04:19:02:342 940 cd4 AU #########
2010-12-21 04:19:02:342 940 cd4 AU ## END ## AU: Search for updates [CallId = {8957B50F-46F1-44C4-A347-20D4C5E91D47}]
2010-12-21 04:19:02:342 940 cd4 AU #############
2010-12-21 04:19:02:342 940 cd4 AU Successfully wrote event for AU health state:0
2010-12-21 04:19:02:342 940 cd4 AU AU setting next detection timeout to 2010-12-21 14:19:02
2010-12-21 04:19:02:342 940 cd4 AU Setting AU scheduled install time to 2010-12-22 08:00:00
2010-12-21 04:19:02:342 940 cd4 AU Successfully wrote event for AU health state:0
2010-12-21 04:19:02:342 940 cd4 AU Successfully wrote event for AU health state:0
2010-12-21 04:19:07:350 940 f20 Report REPORT EVENT: {A472759C-BEE7-4161-84E8-41F1C1D03AB4} 2010-12-21 04:19:02:342-0500 1 148 101 {61CA813A-7585-442E-A66B-B0D15CE6BDC0} 1 80080005 SelfUpdate Failure Software Synchronization Windows Update Client failed to detect with error 0x80080005.
2010-12-21 04:19:07:350 940 f20 Report CWERReporter::HandleEvents - WER report upload completed with status 0x8
2010-12-21 04:19:07:350 940 f20 Report WER Report sent: 7.4.7600.226 0x80080005 61CA813A-7585-442E-A66B-B0D15CE6BDC0 Scan 101 Managed
2010-12-21 04:19:07:350 940 f20 Report CWERReporter finishing event handling. (00000000)
2010-12-21 04:24:22:767 940 f20 PT WARNING: Cached cookie has expired or new PID is available
2010-12-21 04:24:22:767 940 f20 PT Initializing simple targeting cookie, clientId = a6d6dc1c-d844-451c-8609-3879e6cacb33, target group = , DNS name = lab24.sja.local
2010-12-21 04:24:22:767 940 f20 PT Server URL = http://server2:8530/SimpleAuthWebService/SimpleAuth.asmx
2010-12-21 04:24:22:814 940 f20 Report Uploading 2 events using cached cookie, reporting URL = http://server2:8530/ReportingWebService/ReportingWebService.asmx
2010-12-21 04:24:22:814 940 f20 Report Reporter successfully uploaded 2 events.
2010-12-21 06:59:23:020 940 b4c AU AU was unable to detect updates for more than 48 hours
2010-12-21 06:59:28:027 940 c78 Report REPORT EVENT: {511B1C92-939C-4E97-A51B-50E75FCB7AEF} 2010-12-21 06:59:23:020-0500 1 149 102 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Failure Software Synchronization Unable to Connect: Windows is unable to connect to the automatic updates service and therefore cannot download and install updates according to the set schedule. Windows will continue to try to establish a connection.
2010-12-21 06:59:28:027 940 c78 Report CWERReporter finishing event handling. (00000000)
2010-12-21 09:02:03:476 940 2f4 AU Triggering AU detection through DetectNow API
2010-12-21 09:02:03:476 940 2f4 AU Triggering Online detection (interactive)
2010-12-21 09:02:03:476 940 b4c AU #############
2010-12-21 09:02:03:476 940 b4c AU ## START ## AU: Search for updates
2010-12-21 09:02:03:477 940 b4c AU #########
2010-12-21 09:02:03:488 940 b4c AU <<## SUBMITTED ## AU: Search for updates [CallId = {B65ACC67-ED84-45D4-9774-D0475806E74B}]
2010-12-21 09:02:03:488 940 e38 Agent *************
2010-12-21 09:02:03:488 940 e38 Agent ** START ** Agent: Finding updates [CallerId = AutomaticUpdates]
2010-12-21 09:02:03:488 940 e38 Agent *********
2010-12-21 09:02:03:488 940 e38 Agent * Online = Yes; Ignore download priority = No
2010-12-21 09:02:03:488 940 e38 Agent * Criteria = "IsInstalled=0 and DeploymentAction='Installation' or IsPresent=1 and DeploymentAction='Uninstallation' or IsInstalled=1 and DeploymentAction='Installation' and RebootRequired=1 or IsInstalled=0 and DeploymentAction='Uninstallation' and RebootRequired=1"
2010-12-21 09:02:03:488 940 e38 Agent * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
2010-12-21 09:02:03:488 940 e38 Agent * Search Scope = {Machine}
2010-12-21 09:02:03:488 940 e38 Setup Checking for agent SelfUpdate
2010-12-21 09:02:03:489 940 e38 Setup Client version: Core: 7.4.7600.226 Aux: 7.4.7600.226
2010-12-21 09:02:03:489 940 e38 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
2010-12-21 09:02:03:496 940 e38 Misc Microsoft signed: Yes
2010-12-21 09:02:06:071 940 e38 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
2010-12-21 09:02:06:078 940 e38 Misc Microsoft signed: Yes
2010-12-21 09:02:06:080 940 e38 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
2010-12-21 09:02:06:087 940 e38 Misc Microsoft signed: Yes
2010-12-21 09:02:06:100 940 e38 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
2010-12-21 09:02:06:107 940 e38 Misc Microsoft signed: Yes
2010-12-21 09:02:06:123 940 e38 Setup Determining whether a new setup handler needs to be downloaded
2010-12-21 09:02:06:123 940 e38 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\Handler\WuSetupV.exe:
2010-12-21 09:02:06:129 940 e38 Misc Microsoft signed: Yes
2010-12-21 09:02:06:129 940 e38 Setup SelfUpdate handler update NOT required: Current version: 7.4.7600.226, required version: 7.4.7600.226
2010-12-21 09:02:06:129 940 e38 Setup Evaluating applicability of setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~x86~~7.4.7600.226"
2010-12-21 09:02:15:386 940 b4c AU AU received policy change subscription event
2010-12-21 09:02:36:165 940 e38 Setup WARNING: Cbs StartSession, error = 0x80080005
2010-12-21 09:02:36:165 940 e38 Setup FATAL: Applicability evaluation for setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~x86~~7.4.7600.226" failed, error = 0x80080005
2010-12-21 09:02:36:165 940 e38 Setup FATAL: SelfUpdate check failed, err = 0x80080005
2010-12-21 09:02:36:165 940 e38 Agent * WARNING: Skipping scan, self-update check returned 0x80080005
2010-12-21 09:02:36:165 940 e38 Agent * WARNING: Exit code = 0x80080005
2010-12-21 09:02:36:165 940 e38 Agent *********
2010-12-21 09:02:36:165 940 e38 Agent ** END ** Agent: Finding updates [CallerId = AutomaticUpdates]
2010-12-21 09:02:36:165 940 e38 Agent *************
2010-12-21 09:02:36:165 940 e38 Agent WARNING: WU client failed Searching for update with error 0x80080005
2010-12-21 09:02:36:165 940 e8c AU >>## RESUMED ## AU: Search for updates [CallId = {B65ACC67-ED84-45D4-9774-D0475806E74B}]
2010-12-21 09:02:36:165 940 e8c AU # WARNING: Search callback failed, result = 0x80080005
2010-12-21 09:02:36:165 940 e8c AU # WARNING: Failed to find updates with error code 80080005
2010-12-21 09:02:36:165 940 e8c AU #########
2010-12-21 09:02:36:165 940 e8c AU ## END ## AU: Search for updates [CallId = {B65ACC67-ED84-45D4-9774-D0475806E74B}]
2010-12-21 09:02:36:165 940 e8c AU #############
2010-12-21 09:02:36:165 940 e8c AU Successfully wrote event for AU health state:0
2010-12-21 09:02:36:165 940 e8c AU AU setting next detection timeout to 2010-12-21 19:02:36
2010-12-21 09:02:36:165 940 e8c AU Setting AU scheduled install time to 2010-12-22 08:00:00
2010-12-21 09:02:36:165 940 e8c AU Successfully wrote event for AU health state:0
2010-12-21 09:02:36:165 940 e8c AU Successfully wrote event for AU health state:0
2010-12-21 09:02:41:172 940 e38 Report REPORT EVENT: {678C2913-B3B3-4F14-9310-C2E2B1F3334A} 2010-12-21 09:02:36:165-0500 1 148 101 {61CA813A-7585-442E-A66B-B0D15CE6BDC0} 1 80080005 SelfUpdate Failure Software Synchronization Windows Update Client failed to detect with error 0x80080005.
2010-12-21 09:02:41:172 940 e38 Report CWERReporter::HandleEvents - WER report upload completed with status 0x8
2010-12-21 09:02:41:172 940 e38 Report WER Report sent: 7.4.7600.226 0x80080005 61CA813A-7585-442E-A66B-B0D15CE6BDC0 Scan 101 Managed
2010-12-21 09:02:41:172 940 e38 Report CWERReporter finishing event handling. (00000000)
2010-12-21 09:06:07:779 940 b4c AU ########### AU: Uninitializing Automatic Updates ###########
2010-12-21 09:06:37:809 940 b4c Handler FATAL: UH: 0x80080005: StartSession failed in CCbs::IsCbsPending
2010-12-21 09:06:37:840 940 b4c Report CWERReporter finishing event handling. (00000000)
2010-12-21 09:06:37:872 940 b4c Service *********
2010-12-21 09:06:37:872 940 b4c Service ** END ** Service: Service exit [Exit code = 0x240001]
2010-12-21 09:06:37:872 940 b4c Service *************
2010-12-21 09:08:37:104 940 e84 Misc =========== Logging initialized (build: 7.4.7600.226, tz: -0500) ===========
2010-12-21 09:08:37:104 940 e84 Misc = Process: C:\Windows\system32\svchost.exe
2010-12-21 09:08:37:104 940 e84 Misc = Module: c:\windows\system32\wuaueng.dll
2010-12-21 09:08:37:104 940 e84 Service *************
2010-12-21 09:08:37:104 940 e84 Service ** START ** Service: Service startup
2010-12-21 09:08:37:104 940 e84 Service *********
2010-12-21 09:08:37:108 940 e84 Agent * WU client version 7.4.7600.226
2010-12-21 09:08:37:108 940 e84 Agent * Base directory: C:\Windows\SoftwareDistribution
2010-12-21 09:08:37:108 940 e84 Agent * Access type: No proxy
2010-12-21 09:08:37:108 940 e84 Agent * Network state: Connected
2010-12-21 09:08:37:453 940 e84 DtaStor Default service for AU is {00000000-0000-0000-0000-000000000000}
2010-12-21 09:08:37:462 940 e84 DtaStor Default service for AU is {9482F4B4-E343-43B6-B170-9A65BC822C77}
2010-12-21 09:08:37:464 940 e84 Agent WARNING: failed to access the auth cab, fatal error 0x80070003
2010-12-21 09:08:37:464 940 e84 Agent WARNING: Invalid service in the backup data store; cleaning up
2010-12-21 09:08:37:465 940 e84 Agent WARNING: Failed to add and register service 7971f918-a847-4430-9279-4a52d1efe18d to the data store 0x80240031
2010-12-21 09:08:37:465 940 e84 Agent WARNING: Default Service Recovery: Attempting to add pending registration for service 7971f918-a847-4430-9279-4a52d1efe18d to the data store
2010-12-21 09:09:22:474 940 e84 Report CWERReporter::Init succeeded
2010-12-21 09:09:22:474 940 e84 Agent *********** Agent: Initializing Windows Update Agent ***********
2010-12-21 09:09:22:475 940 e84 Agent *********** Agent: Initializing global settings cache ***********
2010-12-21 09:09:22:475 940 e84 Agent * WSUS server: http://server2:8530
2010-12-21 09:09:22:475 940 e84 Agent * WSUS status server: http://server2:8530
2010-12-21 09:09:22:475 940 e84 Agent * Target group: (Unassigned Computers)
2010-12-21 09:09:22:475 940 e84 Agent * Windows Update access disabled: No
2010-12-21 09:09:22:475 940 e84 DnldMgr Download manager restoring 0 downloads
2010-12-21 09:09:22:476 940 e84 AU ########### AU: Initializing Automatic Updates ###########
2010-12-21 09:09:22:477 940 e84 AU # WSUS server: http://server2:8530
2010-12-21 09:09:22:477 940 e84 AU # Detection frequency: 22
2010-12-21 09:09:22:477 940 e84 AU # Approval type: Scheduled (Policy)
2010-12-21 09:09:22:477 940 e84 AU # Scheduled install day/time: Every day at 3:00
2010-12-21 09:09:22:477 940 e84 AU # Auto-install minor updates: Yes (Policy)
2010-12-21 09:09:22:478 940 e84 AU Setting AU scheduled install time to 2010-12-22 08:00:00
2010-12-21 09:09:22:751 940 e84 Report *********** Report: Initializing static reporting data ***********
2010-12-21 09:09:22:751 940 e84 Report * OS Version = 6.1.7600.0.0.65792
2010-12-21 09:09:22:751 940 e84 Report * OS Product Type = 0x00000004
2010-12-21 09:09:22:772 940 e84 Report * Computer Brand = Dell Inc.
2010-12-21 09:09:22:772 940 e84 Report * Computer Model = OptiPlex 380
2010-12-21 09:09:22:775 940 e84 Report * Bios Revision = A01
2010-12-21 09:09:22:775 940 e84 Report * Bios Name = Phoenix ROM BIOS PLUS Version 1.10 A01
2010-12-21 09:09:22:775 940 e84 Report * Bios Release Date = 2010-03-11T00:00:00
2010-12-21 09:09:22:775 940 e84 Report * Locale ID = 1033
2010-12-21 09:09:22:777 940 e84 AU Successfully wrote event for AU health state:0
2010-12-21 09:09:22:777 940 e84 AU Initializing featured updates
2010-12-21 09:09:22:777 940 e84 AU Found 0 cached featured updates
2010-12-21 09:09:22:777 940 e84 AU Successfully wrote event for AU health state:0
2010-12-21 09:09:22:778 940 e84 AU Successfully wrote event for AU health state:0
2010-12-21 09:09:22:778 940 e84 AU AU finished delayed initialization
2010-12-21 09:09:27:781 940 36c Report CWERReporter finishing event handling. (00000000)
2010-12-21 09:10:20:421 940 bf0 AU Triggering AU detection through DetectNow API
2010-12-21 09:10:20:422 940 bf0 AU Triggering Online detection (interactive)
2010-12-21 09:10:20:422 940 e84 AU #############
2010-12-21 09:10:20:422 940 e84 AU ## START ## AU: Search for updates
2010-12-21 09:10:20:422 940 e84 AU #########
2010-12-21 09:10:20:425 940 e84 AU <<## SUBMITTED ## AU: Search for updates [CallId = {F1E8D669-5A48-4C25-832F-4A5ABD80270F}]
2010-12-21 09:10:20:425 940 36c Agent *************
2010-12-21 09:10:20:425 940 36c Agent ** START ** Agent: Finding updates [CallerId = AutomaticUpdates]
2010-12-21 09:10:20:425 940 36c Agent *********
2010-12-21 09:10:20:425 940 36c Agent * Online = Yes; Ignore download priority = No
2010-12-21 09:10:20:425 940 36c Agent * Criteria = "IsInstalled=0 and DeploymentAction='Installation' or IsPresent=1 and DeploymentAction='Uninstallation' or IsInstalled=1 and DeploymentAction='Installation' and RebootRequired=1 or IsInstalled=0 and DeploymentAction='Uninstallation' and RebootRequired=1"
2010-12-21 09:10:20:425 940 36c Agent * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
2010-12-21 09:10:20:425 940 36c Agent * Search Scope = {Machine}
2010-12-21 09:10:20:425 940 36c Setup Checking for agent SelfUpdate
2010-12-21 09:10:20:426 940 36c Setup Client version: Core: 7.4.7600.226 Aux: 7.4.7600.226
2010-12-21 09:10:22:715 940 36c Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
2010-12-21 09:10:22:725 940 36c Misc Microsoft signed: Yes
2010-12-21 09:10:22:745 940 36c Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
2010-12-21 09:10:22:750 940 36c Misc Microsoft signed: Yes
2010-12-21 09:10:22:765 940 36c Setup Determining whether a new setup handler needs to be downloaded
2010-12-21 09:10:22:765 940 36c Setup SelfUpdate handler is not found. It will be downloaded
2010-12-21 09:10:22:765 940 36c Setup Evaluating applicability of setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~x86~~7.4.7600.226"
2010-12-21 09:10:52:778 940 36c Setup WARNING: Cbs StartSession, error = 0x80080005
2010-12-21 09:10:52:778 940 36c Setup FATAL: Applicability evaluation for setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~x86~~7.4.7600.226" failed, error = 0x80080005
2010-12-21 09:10:52:778 940 36c Setup FATAL: SelfUpdate check failed, err = 0x80080005
2010-12-21 09:10:52:779 940 36c Agent * WARNING: Skipping scan, self-update check returned 0x80080005
2010-12-21 09:10:52:779 940 36c Agent * WARNING: Exit code = 0x80080005
2010-12-21 09:10:52:779 940 36c Agent *********
2010-12-21 09:10:52:779 940 36c Agent ** END ** Agent: Finding updates [CallerId = AutomaticUpdates]
2010-12-21 09:10:52:779 940 36c Agent *************
2010-12-21 09:10:52:779 940 36c Agent WARNING: WU client failed Searching for update with error 0x80080005
2010-12-21 09:10:52:779 940 ba0 AU >>## RESUMED ## AU: Search for updates [CallId = {F1E8D669-5A48-4C25-832F-4A5ABD80270F}]
2010-12-21 09:10:52:780 940 ba0 AU # WARNING: Search callback failed, result = 0x80080005
2010-12-21 09:10:52:780 940 ba0 AU # WARNING: Failed to find updates with error code 80080005
2010-12-21 09:10:52:780 940 ba0 AU #########
2010-12-21 09:10:52:780 940 ba0 AU ## END ## AU: Search for updates [CallId = {F1E8D669-5A48-4C25-832F-4A5ABD80270F}]
2010-12-21 09:10:52:780 940 ba0 AU #############
2010-12-21 09:10:52:783 940 ba0 AU Successfully wrote event for AU health state:0
2010-12-21 09:10:52:783 940 ba0 AU AU setting next detection timeout to 2010-12-21 19:10:52
2010-12-21 09:10:52:783 940 ba0 AU Setting AU scheduled install time to 2010-12-22 08:00:00
2010-12-21 09:10:52:783 940 ba0 AU Successfully wrote event for AU health state:0
2010-12-21 09:10:52:784 940 ba0 AU Successfully wrote event for AU health state:0

Windows 8.1 Professional x64: Windows will not run Windows Update after fresh install

Greetings everyone. I'm having a strange issue that I can't seem to figure out. I'm developing an image with the following specs:
Hardware:
Dell XPS 12 Ultrabook Convertible
Haswell i7
8 GB RAM
256 SSD HD
Software:
Windows 8.1 Professional x64
Problem description:
After formatting and partitioning the hard drive (UEFI) with a corporate copy of Windows 8.1 x64, the laptop is booted up in Audit mode. No OEM drivers or software is installed. Windows is then activated to the KMS server and verified.
I then connect to a hotspot (no proxy required) and open up IE 11. I click tools and select Windows Update. The laptop then searches and searches for updates and never finds any. I've let it search for over 10 hours. The laptop never
returns an error message.
Troubleshooting performed:
1. I've tried different copies of Windows 8.1 - same result.
2. I've tried installing the OS with different types of media (external hd and multiple bootable USB drives) - same result.
3. I've disable the Windows Update service, deleted the contents of the SoftwareDistribution folder, restarted the Windows Update service and rebooted laptop - same result
4. I've installed this copy of Windows 8.1 on different models of laptops with no OEM drivers or software installed - same result.
5. I've installed all of the OEM device drivers in the correct order and ensured that the device manager is clear of bang signs - same result.
6. Date and time is set correctly.
Has anyone else experienced this with Windows 8.1 x64? If I take a copy of Windows 7 x64 or 8 x64 and install it on this laptop, it updates Windows without any issues. The problem seems to be with Windows 8.1.
Thank you in advance for any help you can provide.

2014-03-04 13:49:52:826
888 9f8
Misc =========== Logging initialized (build: 7.9.9600.16403, tz: -0800) ===========
2014-03-04 13:49:52:826
888 9f8
Misc = Process: C:\Windows\system32\svchost.exe
2014-03-04 13:49:52:826
888 9f8
Misc = Module: c:\windows\system32\wuaueng.dll
2014-03-04 13:49:52:826
888 9f8
Service *************
2014-03-04 13:49:52:826
888 9f8
Service ** START ** Service: Service startup
2014-03-04 13:49:52:826
888 9f8
Service *********
2014-03-04 13:49:52:842
888 9f8
Agent * WU client version 7.9.9600.16403
2014-03-04 13:49:52:842
888 9f8
Agent * Base directory: C:\Windows\SoftwareDistribution
2014-03-04 13:49:52:842
888 9f8
Agent * Access type: No proxy
2014-03-04 13:49:52:842
888 9f8
Service UpdateNetworkState Ipv6, cNetworkInterfaces = 5.
2014-03-04 13:49:52:842
888 9f8
Service UpdateNetworkState Ipv4, cNetworkInterfaces = 1.
2014-03-04 13:49:52:842
888 9f8
Agent * Network state: Connected
2014-03-04 13:49:52:858
888 9f8
Service UpdateNetworkState Ipv6, cNetworkInterfaces = 5.
2014-03-04 13:49:52:858
888 9f8
Service UpdateNetworkState Ipv4, cNetworkInterfaces = 1.
2014-03-04 13:49:53:045
888 9f8
DtaStor Default service for AU is {00000000-0000-0000-0000-000000000000}
2014-03-04 13:49:53:045
888 9f8
DtaStor Default service for AU is {9482F4B4-E343-43B6-B170-9A65BC822C77}
2014-03-04 13:49:53:045
888 9f8
DtaStor Data store successfully created
2014-03-04 13:49:53:061
888 9f8
Agent *********** Agent: Initializing global settings cache ***********
2014-03-04 13:49:53:061
888 9f8
Agent * Endpoint Provider: 00000000-0000-0000-0000-000000000000
2014-03-04 13:49:53:061
888 9f8
Agent * WSUS server: <NULL>
2014-03-04 13:49:53:061
888 9f8
Agent * WSUS status server: <NULL>
2014-03-04 13:49:53:061
888 9f8
Agent * Target group: (Unassigned Computers)
2014-03-04 13:49:53:061
888 9f8
Agent * Windows Update access disabled: No
2014-03-04 13:49:53:076
888 9f8
WuTask WuTaskManager delay initialize completed successfully..
2014-03-04 13:49:53:076
888 9f8
Report CWERReporter::Init succeeded
2014-03-04 13:49:53:076
888 9f8
Agent *********** Agent: Initializing Windows Update Agent ***********
2014-03-04 13:49:53:076
888 9f8
DnldMgr Download manager restoring 0 downloads
2014-03-04 13:49:53:092
888 9f8
AU ########### AU: Initializing Automatic Updates ###########
2014-03-04 13:49:53:092
888 9f8
AU AIR Mode is enabled
2014-03-04 13:49:53:092
888 9f8
AU # AU is not configured yet
2014-03-04 13:49:53:092
888 9f8
AU # Will interact with non-admins (Non-admins are elevated (User preference))
2014-03-04 13:49:53:092
888 9f8
AU # Accelerated install is required
2014-03-04 13:49:53:092
888 9f8
Agent Switching to hardware-verified ClientId.
2014-03-04 13:49:53:092
888 9f8
AU WARNING: Failed to get Wu Exemption info from NLM, assuming not exempt, error = 0x80070490
2014-03-04 13:49:53:108
888 9f8
AU AU finished delayed initialization
2014-03-04 13:49:53:108
888 8c4
IdleTmr Incremented idle timer priority operation counter to 1
2014-03-04 13:49:53:108
888 13c
DnldMgr Asking handlers to reconcile their sandboxes
2014-03-04 13:49:57:239
888 af8
AU ########### AU: Setting new AU options ###########
2014-03-04 13:49:57:239
888 af8
AU Setting AU Approval Type to 4
2014-03-04 13:49:57:239
888 af8
AU # Policy changed, AU refresh required = Yes
2014-03-04 13:49:57:239
888 af8
AU # Approval type: Scheduled (User preference)
2014-03-04 13:49:57:239
888 af8
AU # Auto-install minor updates: Yes (User preference)
2014-03-04 13:49:57:239
888 af8
AU # Will interact with non-admins (Non-admins are elevated (User preference))
2014-03-04 13:49:57:239
888 af8
AU # Accelerated install is required
2014-03-04 13:49:57:239
888 af8
AU AU Refresh required....
2014-03-04 13:49:57:239
888 af8
AU AU setting next detection timeout to 2014-03-04 21:49:57
2014-03-04 13:49:57:239
888 af8
AU AIR Mode is enabled
2014-03-04 13:49:57:239
888 af8
AU AIR Mode is disabled
2014-03-04 13:49:57:239
888 af8
AU Accelerate Install required state reset
2014-03-04 13:49:57:239
888 af8
AU Triggering Online detection (interactive)
2014-03-04 13:49:57:239
888 9f8
AU Windows OOBE is still in progress. AU deferring detection
2014-03-04 13:49:57:239
888 9f8
AU WARNING: BeginDetection failed, hr:0x8024a008
2014-03-04 13:49:57:239
888 9f8
AU All AU searches complete.
2014-03-04 13:49:57:239
888 9f8
AU # WARNING: Failed to find updates with error code 8024a008
2014-03-04 13:49:57:239
888 9f8
AU AU setting next detection timeout to 2014-03-04 22:19:57
2014-03-04 13:49:57:239
888 9f8
AU OOBE is in progress, so cannot perform Accelerated Install
2014-03-04 13:53:34:838
888 9f8
Service UpdateNetworkState Ipv6, cNetworkInterfaces = 4.
2014-03-04 13:53:34:838
888 9f8
Service UpdateNetworkState Ipv6, cNetworkInterfaces = 3.
2014-03-04 13:54:16:402
888 9f8
Service UpdateNetworkState Ipv6, cNetworkInterfaces = 4.
2014-03-04 13:54:16:417
888 9f8
Service UpdateNetworkState Ipv6, cNetworkInterfaces = 5.
2014-03-04 13:58:48:942
888 6d4
IdleTmr Decremented idle timer priority operation counter to 0
2014-03-04 13:58:56:990
888 9f8
Service UpdateNetworkState Ipv6, cNetworkInterfaces = 3.
2014-03-04 13:58:57:022
888 9f8
Service UpdateNetworkState Ipv6, cNetworkInterfaces = 4.
2014-03-04 13:58:57:272
888 9f8
Service UpdateNetworkState Ipv6, cNetworkInterfaces = 5.
2014-03-04 13:58:58:830
888 9f8
Service UpdateNetworkState Ipv4, cNetworkInterfaces = 2.
2014-03-04 13:58:58:846
888 9f8
Service UpdateNetworkState Ipv6, cNetworkInterfaces = 4.
2014-03-04 13:58:58:877
888 9f8
Service UpdateNetworkState Ipv6, cNetworkInterfaces = 3.
2014-03-04 13:58:58:892
888 9f8
Service UpdateNetworkState Ipv6, cNetworkInterfaces = 4.
2014-03-04 13:58:59:267
888 9f8
Service UpdateNetworkState Ipv6, cNetworkInterfaces = 5.
2014-03-04 13:59:01:937
888 9f8
Service UpdateNetworkState Ipv6, cNetworkInterfaces = 4.
2014-03-04 13:59:01:937
888 9f8
Service UpdateNetworkState Ipv6, cNetworkInterfaces = 3.
2014-03-04 13:59:01:953
888 9f8
Service UpdateNetworkState Ipv6, cNetworkInterfaces = 4.
2014-03-04 14:08:49:957
888 9f8
AU ########### AU: Uninitializing Automatic Updates ###########
2014-03-04 14:08:50:007
888 9f8
WuTask Uninit WU Task Manager
2014-03-04 14:08:50:219
888 9f8
Service *********
2014-03-04 14:08:50:219
888 9f8
Service ** END ** Service: Service exit [Exit code = 0x240001]
2014-03-04 14:08:50:219
888 9f8
Service *************
2014-03-04 14:13:11:111
888 ba4
Misc =========== Logging initialized (build: 7.9.9600.16403, tz: -0800) ===========
2014-03-04 14:13:11:111
888 ba4
Misc = Process: C:\Windows\system32\svchost.exe
2014-03-04 14:13:11:111
888 ba4
Misc = Module: c:\windows\system32\wuaueng.dll
2014-03-04 14:13:11:111
888 ba4
Service *************
2014-03-04 14:13:11:111
888 ba4
Service ** START ** Service: Service startup
2014-03-04 14:13:11:111
888 ba4
Service *********
2014-03-04 14:13:11:126
888 ba4
Agent * WU client version 7.9.9600.16403
2014-03-04 14:13:11:126
888 ba4
Agent * Base directory: C:\Windows\SoftwareDistribution
2014-03-04 14:13:11:126
888 ba4
Agent * Access type: No proxy
2014-03-04 14:13:11:126
888 ba4
Service UpdateNetworkState Ipv6, cNetworkInterfaces = 5.
2014-03-04 14:13:11:126
888 ba4
Service UpdateNetworkState Ipv4, cNetworkInterfaces = 1.
2014-03-04 14:13:11:126
888 ba4
Agent * Network state: Connected
2014-03-04 14:13:11:126
888 ba4
Service UpdateNetworkState Ipv6, cNetworkInterfaces = 5.
2014-03-04 14:13:11:126
888 ba4
Service UpdateNetworkState Ipv4, cNetworkInterfaces = 1.
2014-03-04 14:13:11:142
888 ba4
Agent *********** Agent: Initializing global settings cache ***********
2014-03-04 14:13:11:142
888 ba4
Agent * Endpoint Provider: 00000000-0000-0000-0000-000000000000
2014-03-04 14:13:11:142
888 ba4
Agent * WSUS server: <NULL>
2014-03-04 14:13:11:142
888 ba4
Agent * WSUS status server: <NULL>
2014-03-04 14:13:11:142
888 ba4
Agent * Target group: (Unassigned Computers)
2014-03-04 14:13:11:142
888 ba4
Agent * Windows Update access disabled: No
2014-03-04 14:13:11:142
888 ba4
WuTask WuTaskManager delay initialize completed successfully..
2014-03-04 14:13:11:142
888 ba4
Report CWERReporter::Init succeeded
2014-03-04 14:13:11:142
888 ba4
Agent *********** Agent: Initializing Windows Update Agent ***********
2014-03-04 14:13:11:142
888 ba4
DnldMgr Download manager restoring 0 downloads
2014-03-04 14:13:11:142
888 ba4
AU ########### AU: Initializing Automatic Updates ###########
2014-03-04 14:13:11:142
888 ba4
AU AIR Mode is disabled
2014-03-04 14:13:11:142
888 ba4
AU # Approval type: Scheduled (User preference)
2014-03-04 14:13:11:142
888 ba4
AU # Auto-install minor updates: Yes (User preference)
2014-03-04 14:13:11:142
888 ba4
AU # Will interact with non-admins (Non-admins are elevated (User preference))
2014-03-04 14:13:11:142
888 ba4
Agent Switching to hardware-verified ClientId.
2014-03-04 14:13:11:142
888 ba4
AU WARNING: Failed to get Wu Exemption info from NLM, assuming not exempt, error = 0x80070490
2014-03-04 14:13:11:158
888 ba4
AU AU finished delayed initialization
2014-03-04 14:13:11:158
888 ba4
AU OOBE is in progress, so cannot perform Accelerated Install
2014-03-04 14:13:11:158
888 764
IdleTmr Incremented idle timer priority operation counter to 1
2014-03-04 14:13:11:158
888 10c
DnldMgr Asking handlers to reconcile their sandboxes
2014-03-04 14:13:13:353
888 764
AU Triggering AU detection through DetectNow API
2014-03-04 14:13:13:353
888 764
AU Triggering Online detection (interactive)
2014-03-04 14:13:13:353
888 ba4
AU Windows OOBE is still in progress. AU deferring detection
2014-03-04 14:13:13:353
888 ba4
AU WARNING: BeginDetection failed, hr:0x8024a008
2014-03-04 14:13:13:353
888 ba4
AU All AU searches complete.
2014-03-04 14:13:13:353
888 ba4
AU # WARNING: Failed to find updates with error code 8024a008
2014-03-04 14:13:13:353
888 ba4
AU AU setting next detection timeout to 2014-03-04 22:43:13
2014-03-04 14:13:13:353
888 ba4
AU OOBE is in progress, so cannot perform Accelerated Install
2014-03-04 14:43:13:405
888 ba4
AU Windows OOBE is still in progress. AU deferring detection
2014-03-04 14:43:13:405
888 ba4
AU WARNING: BeginDetection failed, hr:0x8024a008
2014-03-04 14:43:13:405
888 ba4
AU All AU searches complete.
2014-03-04 14:43:13:405
888 ba4
AU # WARNING: Failed to find updates with error code 8024a008
2014-03-04 14:43:13:405
888 ba4
AU AU setting next detection timeout to 2014-03-04 23:13:13
2014-03-04 14:43:13:405
888 ba4
AU OOBE is in progress, so cannot perform Accelerated Install
2014-03-04 14:47:37:066
888 764
IdleTmr Decremented idle timer priority operation counter to 0

Windows Firewall and Windows Update (Win 8.1)

Since Windows Vista I have always been using the Windows Firewall with "blocked outgoing traffic". As this is not the default setting, some basic windows services seem not to be included as firewall rules on the outgoing side.
My Problem is with the Windows Update:
On Windows Vista and 7 it was sufficient to create a rule for "wuauserv".
On Windows 8.1 however this seems not to be enough. The UI gives me error code 80240438 and the WindowsUpdate.log shows the following lines:
2014-06-14   20:11:08:150   952   538   IdleTmr   WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover) started; operation # 2044; does use network; is at background
priority
2014-06-14   20:11:08:151   952   538   WS   WARNING: Nws Failure: errorCode=0x803d0010
2014-06-14   20:11:08:151   952   538   WS   WARNING: Original error code: 0x80072efd
2014-06-14   20:11:08:151   952   538   WS   WARNING: Fehler bei der Kommunikation mit dem Endpunkt bei "https://fe2.update.microsoft.com/v6/ClientWebService/client.asmx".
2014-06-14   20:11:08:151   952   538   WS   WARNING: Fehler beim Senden der HTTP-Anforderung.
2014-06-14   20:11:08:151   952   538   WS   WARNING: Der Remoteendpunkt konnte nicht erreicht werden.
(.... and a lot of similar WARNING lines)
2014-06-14   20:11:12:921   952   538   IdleTmr   WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover, operation # 2044) stopped; does use network; is at background
priority
If I create a rule for the whole svchost.exe, the update works fine. Giving all services internet access is however not an option for me. Could you please tell me through which service(s) except wuauserv Windows Update performs its network activities?

Windows 8 upgraded to 8.1 on a Gateway SX2370.  Purchased Sep. 2013.
As of Dec. 28, 2014 I have not gotten ANY windows defender updates and windows update has not been working at all. When I go to my start screen and type "update" Windows update still shows in the list, only now when I click on it, it brings
up a blank window and can only be closed by right clicking the tab on the taskbar. I cannot max or minimize the window either.
Up until Dec. 28th it was working perfectly, notifying me when updates were available, almost everyday for windows defender.
I have tried everything I could find to fix this, even a complete restore, with recovery media made for Win 8.1 and Win 8. Still no windows updates, of anything. To top it off as of Jan. 22, 2015 the Diagnostic Policy Service has stopped and I am denied
access when I try restarting it.
Windows XP was great until MS stopped support. Vista sucked, near as bad as Millenium or 2000. I never tried windows 7 instead going for windows 8, being the most recent version when I could afford a new PC. Adapting to win 8-8.1 was no easy task.
I'm not a tech guru, but I've owned & used windows from Dos 6.0, '95, '98, '98SE, Millenium, XP, XP home & Pro (sp1-2 & 3) and still have the installation/restore CDs for all of them. Even taught myself how to write the recovery
console directly from the hard drive of XP, OEM or full MS versions without using the CDs & now I'm using Windows 8 - 8.1. Getting rid of the recovery console was a BIG mistake in my opinion.
At one time I had a multi-boot system of win.95, 98, 98SE, Mill., XP home sp2 and XP Pro sp3 on a 1.5 TB self built system. Microsoft told me it was impossible, until I allowed two tech support reps remote access for 5 min.. Which also lead to me being
blocked from most MS websites &?suggestions windows forums for 3 years.
But so far, this failure of windows updates and the Diagnostic policy Service in Windows 8.1 has got me stumped. Can ANYONE give me a quick simple way to correct this? Please?
Thanks for reading this and any help or suggestions anyone has to offer. GOD bless you all and my thanks to every military person, their families and veterans for my freedom.

Windows Updates on Server Core

I am having no updates on Windows 2008 R2 SP1 Server Core for 2 years.
Initially, as I installed them, I ran sconfig, manual updates and it downloaded a bunch of updates at that time.
But since then I always get "No applicable updates"
I checked the WUA version - it is 7.5.7601.17514 as opposed to 7.6.7600.320 which we have on Full version machines. The recent patching cycle updated the Windows Updates on full version but does not update it on Server Core.
We have no WSUS, we update directly at MS. I also cannot set up automatic updates - it is against the company policy and this is out of my control.
I've read all articles on MS updates, but the recommendations always apply to GUI, which I cannot use in Server Core. Is there a way to download and install the new WUA? I did not find a download link for Windows 2008 server, only for 2012.
Is there another way to update my Server Core installation aside from sconfig?
I would be thankful for any advice.
IA
P.S. I am concerned, because one of my test Server Core servers DID download updates this time, but the others did not. It means that there are some updates for Server core. Servers are all cloned from the same image and I do not see any reason why
the updates are not coming.

Thanks for your answer, it is interesting.
I fixed the problem, it was simple enough.
We have an SCCM installation with a Software Updates Point configured, but not supplying any updates. The Updates were not approved but the SCCM client was installed on the Server Core machine. And on installation it pointed the machine to the unused Software
Update Point for updates instead of the MS Windows Update site.
No updates approved - it reports "no applicable updates"!
And no one remebers the fact that this SCCM SUP exists at all - it is unused. Server Core does not have a GUI where you could see it. I found it by ckecking the WindowsUpdate.log in the C:\Windows directory.
The solution is to switch back to MS Windows Update site.
HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\WindowsUpdate\AU\UseWUServer
- set to 0 instead of 1 and restart the Windows Update service.

How to block Windows update services?

We have a need to prevent windows update traffic to flow thru our network on certain dates. Basically this type of traffic will clog our mpls bandwidth preventing other type of traffic to flow. We are using up to some part QoS on out routers but it not working all the time. Eg, we put in ip address of one windows update server but updates are pulled of the other, then you enter second ip and updates are coming from third, etc.
I would like to explore other, a bit more controllable options utilizing Cisco's technology: ASA 8.4, IronPort WSA.
In summary, to create a traffic policy, not specific to IP addresses, that will kick in at certain date/time, be on for certain period of time and turned off after (automatically).
Any ideas, suggestions how to tackle this issues would be greatly appreciated.
Regards,.

In WSA, go to Web Security Manager/Define Custom Time ranges, and create a time range, call it "Workday", set it for the time you want to block.
Create a new Access Policy, set the identies to All Users, click Advanced at the bottom.
Set the time range to the Workday time range.
Set the user agent to the Microsof Windows Updates (Its under Common User Agents/Others)
In the Protocols section of the policy, set it for "Define custom settings", and tell it to http, ftp, etc.
There are other ways to do it, creating an Identity for example, and then creating a policy for that, but this should work...

Inconsistent Windows Update policy

Similar Messages

Maybe you are looking for