Clients cannot update from WSUS server - error 8024400E

Alright, so I'm troubleshooting our WSUS server and seem to be stuck. I am running WSUS 3.2.7600.226 on Server 2003. The client I have been using for testing is Windows 7 x64, but we have this issue on all clients (XP, 7 x86, and 7 x64). I started
with an error of 800B0001 and after googling installed KB2720211 to fix it. Now I am getting error 8024400E on clients when I attempt to update. I followed a technet walkthrough and verified that my WSUS settings are all correct (at least regarding iis,
registry, gpo settings, and file system permissions). I am able to download CAB files from the WSUS server by going to the proper address in a browser. Here is a snippet from my WindowsUpdate log on my client:
2013-12-20 10:27:29:784 972 23ac AU #############
2013-12-20 10:27:29:784 972 23ac AU ## START ## AU: Search for updates
2013-12-20 10:27:29:784 972 23ac AU #########
2013-12-20 10:27:29:785 972 23ac AU <<## SUBMITTED ## AU: Search for updates [CallId = {749E5CD5-F4DE-48FC-A691-3610EF622CE3}]
2013-12-20 10:27:29:785 972 2bcc Agent *************
2013-12-20 10:27:29:785 972 2bcc Agent ** START ** Agent: Finding updates [CallerId = AutomaticUpdates]
2013-12-20 10:27:29:785 972 2bcc Agent *********
2013-12-20 10:27:29:785 972 2bcc Agent * Online = Yes; Ignore download priority = No
2013-12-20 10:27:29:785 972 2bcc 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"
2013-12-20 10:27:29:785 972 2bcc Agent * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
2013-12-20 10:27:29:785 972 2bcc Agent * Search Scope = {Machine}
2013-12-20 10:27:29:785 972 2bcc Setup Checking for agent SelfUpdate
2013-12-20 10:27:29:785 972 2bcc Setup Client version: Core: 7.6.7600.256 Aux: 7.6.7600.256
2013-12-20 10:27:29:785 972 2bcc Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
2013-12-20 10:27:29:789 972 2bcc Misc Microsoft signed: Yes
2013-12-20 10:27:29:794 972 2bcc Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
2013-12-20 10:27:29:797 972 2bcc Misc Microsoft signed: Yes
2013-12-20 10:27:29:799 972 2bcc Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
2013-12-20 10:27:29:803 972 2bcc Misc Microsoft signed: Yes
2013-12-20 10:27:29:808 972 2bcc Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
2013-12-20 10:27:29:812 972 2bcc Misc Microsoft signed: Yes
2013-12-20 10:27:29:821 972 2bcc Setup Determining whether a new setup handler needs to be downloaded
2013-12-20 10:27:29:821 972 2bcc Setup SelfUpdate handler is not found. It will be downloaded
2013-12-20 10:27:29:821 972 2bcc Setup Evaluating applicability of setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.256"
2013-12-20 10:27:29:823 972 2bcc Setup Setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.256" is already installed.
2013-12-20 10:27:29:823 972 2bcc Setup Evaluating applicability of setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256"
2013-12-20 10:27:29:835 972 2bcc Setup Setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256" is already installed.
2013-12-20 10:27:29:835 972 2bcc Setup Evaluating applicability of setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256"
2013-12-20 10:27:29:852 972 2bcc Setup Setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256" is already installed.
2013-12-20 10:27:29:852 972 2bcc Setup SelfUpdate check completed. SelfUpdate is NOT required.
2013-12-20 10:27:29:884 972 2bcc PT +++++++++++ PT: Synchronizing server updates +++++++++++
2013-12-20 10:27:29:884 972 2bcc PT + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://wsusservername/ClientWebService/client.asmx
2013-12-20 10:27:29:896 972 2bcc PT WARNING: Cached cookie has expired or new PID is available
2013-12-20 10:27:29:896 972 2bcc PT Initializing simple targeting cookie, clientId = 488f3922-1a4e-4921-b015-25957eeb6500, target group = http://wsusservername, DNS name = mycomputer.domain.local
2013-12-20 10:27:29:896 972 2bcc PT Server URL = http://wsusservername/SimpleAuthWebService/SimpleAuth.asmx
2013-12-20 10:27:29:902 972 2bcc PT WARNING: GetAuthorizationCookie failure, error = 0x8024400E, soap client error = 7, soap error code = 400, HTTP status code = 200
2013-12-20 10:27:29:902 972 2bcc PT WARNING: SOAP Fault: 0x000190
2013-12-20 10:27:29:902 972 2bcc PT WARNING: faultstring:Fault occurred
2013-12-20 10:27:29:902 972 2bcc PT WARNING: ErrorCode:InternalServerError(5)
2013-12-20 10:27:29:902 972 2bcc PT WARNING: Message:(null)
2013-12-20 10:27:29:902 972 2bcc PT WARNING: Method:"http://www.microsoft.com/SoftwareDistribution/Server/SimpleAuthWebService/GetAuthorizationCookie";
2013-12-20 10:27:29:902 972 2bcc PT WARNING: ID:9d989bf6-04e3-44a9-8ffd-f20bb997b3f0
2013-12-20 10:27:29:902 972 2bcc PT WARNING: Failed to initialize Simple Targeting Cookie: 0x8024400e
2013-12-20 10:27:29:902 972 2bcc PT WARNING: PopulateAuthCookies failed: 0x8024400e
2013-12-20 10:27:29:902 972 2bcc PT WARNING: RefreshCookie failed: 0x8024400e
2013-12-20 10:27:29:902 972 2bcc PT WARNING: RefreshPTState failed: 0x8024400e
2013-12-20 10:27:29:902 972 2bcc PT WARNING: Sync of Updates: 0x8024400e
2013-12-20 10:27:29:902 972 2bcc PT WARNING: SyncServerUpdatesInternal failed: 0x8024400e
2013-12-20 10:27:29:902 972 2bcc Agent * WARNING: Failed to synchronize, error = 0x8024400E
2013-12-20 10:27:29:902 972 2bcc Agent * WARNING: Exit code = 0x8024400E
2013-12-20 10:27:29:902 972 2bcc Agent *********
2013-12-20 10:27:29:902 972 2bcc Agent ** END ** Agent: Finding updates [CallerId = AutomaticUpdates]
2013-12-20 10:27:29:902 972 2bcc Agent *************
2013-12-20 10:27:29:902 972 2bcc Agent WARNING: WU client failed Searching for update with error 0x8024400e
2013-12-20 10:27:29:902 972 1bc8 AU >>## RESUMED ## AU: Search for updates [CallId = {749E5CD5-F4DE-48FC-A691-3610EF622CE3}]
2013-12-20 10:27:29:902 972 1bc8 AU # WARNING: Search callback failed, result = 0x8024400E
2013-12-20 10:27:29:902 972 1bc8 AU # WARNING: Failed to find updates with error code 8024400E
2013-12-20 10:27:29:902 972 1bc8 AU #########
2013-12-20 10:27:29:902 972 1bc8 AU ## END ## AU: Search for updates [CallId = {749E5CD5-F4DE-48FC-A691-3610EF622CE3}]
2013-12-20 10:27:29:902 972 1bc8 AU #############
2013-12-20 10:27:29:903 972 1bc8 AU Successfully wrote event for AU health state:0
2013-12-20 10:27:29:903 972 1bc8 AU AU setting next detection timeout to 2013-12-20 21:27:29
2013-12-20 10:27:29:903 972 1bc8 AU Setting AU scheduled install time to 2013-12-21 10:00:00
2013-12-20 10:27:29:903 972 1bc8 AU Successfully wrote event for AU health state:0
2013-12-20 10:27:29:904 972 1bc8 AU Successfully wrote event for AU health state:0
2013-12-20 10:27:34:498 972 2bcc Report REPORT EVENT: {2519DC64-E7F9-499B-A2F8-B58DA4A0C08A} 2013-12-20 10:27:29:902-0600 1 148 101 {00000000-0000-0000-0000-000000000000} 0 8024400e AutomaticUpdates Failure Software Synchronization Windows Update Client failed
to detect with error 0x8024400e.
2013-12-20 10:27:34:502 972 2bcc Report CWERReporter::HandleEvents - WER report upload completed with status 0x8
2013-12-20 10:27:34:502 972 2bcc Report WER Report sent: 7.6.7600.256 0x8024400e 00000000-0000-0000-0000-000000000000 Scan 101 Managed
2013-12-20 10:27:34:502 972 2bcc Report CWERReporter finishing event handling. (00000000)
I focused in on "GetAuthorizationCookie failure, error = 0x8024400E, soap client error = 7, soap error code = 400, HTTP status code = 200" and did some googling which all points at Microsoft Office 2003 SP1 update as being the culprit, and I followed
the instructions on a technet site to disable the update and am still getting the same error. I'm stumped at this point, and I thought I would post here in the hope that someone can help me before I end up just wiping it out and reinstalling (which I'm worried
won't even solve it).

I focused in on "GetAuthorizationCookie failure, error = 0x8024400E, soap client error = 7, soap error code = 400, HTTP status code = 200" and did some googling which all points at Microsoft Office 2003 SP1 update as being the culprit, and I followed
the instructions on a technet site to disable the update and am still getting the same error.
While you're definitely on the right track, the Office2003SP1 update really has not been an issue since WSUS Service Pack 2 was released in October 2009 (and really, the Office2003SP1 update that was the cause of this was replaced long before that even,
so you probably don't even have the defective update on your server).
However, the error is generally associated with the presence of defective update(s) on the WSUS server, so the first thing to do is address any potential issues caused by a failed install of KB2720211.
If the error still persists after verifying that all other aspects of the server are fully operational, review the list of not-Declined updates on your WSUS server and make sure that:
All Expired updates are Declined (and then run the Server Cleanup Wizard and let it delete the expired updates).
All approvals for older revisions have been removed (and then run the Server Cleanup Wizard and let it delete the older revisions).
All approvals for superseded updates have been removed. (And then, when they report as 100% Not Applicable, decline them, and then run the Server Cleanup Wizard so that it can delete the files associated with those updates).
Once all of the potentially problematic updates have been removed from the view of the Windows Update Agent, and if this error then persists, we can evaluate it from a more focused perspective.
Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
SolarWinds Head Geek
Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
http://www.solarwinds.com/gotmicrosoft
The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

Similar Messages

Clients cannot connect to WSUS Server

Hi there,
I have a Server 2012 with the WSUS feature installed. I successfully synchronised with Microsoft to download the updates. After that, I managed to add two clients (Win 8 and 8.1 respectively) into WSUS.
The next day, both clients lost connection with WSUS and returns 80072EE2 and 80248440 errors.
Could someone help me with this?
Regards,
Vinod

Hi Vinod,
The 80072EE2 means ERROR_INTERNET_TIMEOUT.
Please check if the client can access the WSUS server on TCP port 8530.
Also, please check if client has configured to update from WSUS server. We can verify this by check the registry below,
HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate
Here is the screenshot of lab server,
Besides, if it is possible, please post the windowsupdate.log of the client here. It may give some hints.
Best Regards.
Steven Lee
TechNet Community Support

Windows Server 2012R2 fails to get update from WSUS with error code 80072ee6

Hi all,
I've deployed WSUS role on a Windows Server 2012R2 machine. WSUS listen on port 8530. Now I'm trying a test server (this machine runs WIndows Server 2012R2 too). I've configured a GPO but when I try to check for updates I get the errore in the subject.
I've checked windowsupdate.log and theese are the settings of the client:
AIR Mode is disabled
2014-02-05 12:59:00:357
776 fe0
AU # Policy Driven Provider: http://MyWSUS.MyDomain.local:8530
2014-02-05 12:59:00:357
776 fe0
AU # Detection frequency: 22
2014-02-05 12:59:00:357
776 fe0
AU # Target group: CSM Servers
2014-02-05 12:59:00:357
776 fe0
AU # Approval type: Pre-install notify (Policy)
2014-02-05 12:59:00:357
776 fe0
AU # Auto-install minor updates: No (User preference)
2014-02-05 12:59:00:357
776 fe0
AU # Will interact with non-admins (Non-admins are elevated (User preference))
I confirm that from the test server I can telnet to my wsus server on TCP port 8530

Hi,
This issue occurs if the URL under the Group Policy setting 'Specify intranet Microsoft update service location' is invalid.
You receive a "80072EE6" error code when you download an update from Windows Server Update Services in Windows 7-based or Windows Server 2008 R2-based
computer
http://support.microsoft.com/kb/2724184
Make sure that the URL is correct and the name can be resolved.
Hope this helps.

Server behind TMG to grab updates from WSUS server

Hey Guys,
The last topic I created about grab superseeded updates from WSUS, is what this is stil about cause I can't accept this installing updates manually as a answer. So I went ahead an did even more research on this.
To keep it simple I went ahead and adjusted the Local Group Policy / Computer Conf / Admin Templates / Windows Comp / Windows Update / Specify an intranet Microsoft update server (http://172.16.3.3:8530)
Allowed a Rule through TMG to allow by directional traffic of TCP 8530 between the server lan (172.16.8.x <-> 172.16.3.3)
When I click check for updates its good I can see the established connection using netstat on port 8530.
As soon as I click download updates, it tries to grab from internet based Servers... i can see the SYN_SENT right away and I can see the blocked http traffic on the TMG.
So I went ahead and set the GPO setting and removed the port allocation behind it (http://172.16.3.3) Doing a netstat after clicking check for updates showed connection attempt to 172.16.3.3 via http, So I added the protocol to the allow rule between the
servers, and sure enough it changed to established, and I see the allow through the TMG. However this now gives an error when i click on check for updates...
There has to be a way for me to get this dang server to get updates from our WSUS server on the other side of the TMG firewall.. but how?! what am I doing wrong?!
*NOTE* with the port specified in the local GPO of 8530, I can access http://wsus/selfupdate/wuident.cab perfectly fine. I ran wuauclt /detectnow and no errors reported in the WindowsUpdate.log file
*NOTE* The Wsus server is setup to cache all update to a local dir, attempted to see the files in there but all contained random string .cab files, wish they would just contain just the KBnumber and the msu files for easier verification of updates available
in the cache.

The last topic I created about grab superseeded updates from WSUS, is what this is stil
A LINK to that post would be most helpful as I am absolutely clueless about what this post is about.
Allowed a Rule through TMG to allow by directional traffic of TCP 8530 between the server lan (172.16.8.x <-> 172.16.3.3)
The correct implementation for TMG is to create a Web Publishing Rule for the WSUS Server and ALLOW passthru of the client identity.
When I click check for updates its good I can see the established connection using netstat on port 8530.
As soon as I click download updates, it tries to grab from internet based Servers... i can see the SYN_SENT right away and I can see the blocked http traffic on the TMG.
So I went ahead and set the GPO setting and removed the port allocation behind it (http://172.16.3.3) Doing a netstat after clicking check for updates showed connection attempt to 172.16.3.3 via http, So I added the protocol to the allow rule between the
servers, and sure enough it changed to established, and I see the allow through the TMG. However this now gives an error when i click on check for updates...
I see that you've specified a PRIVATE IP Address as the target of the WSUS server (172.16.3.3), so the first set of questions revolves around why there's a TMG server involved in the first place, where this "WSUS Client" is located with respect to the
TMG interfaces, and where the WSUS Server is located with respect to the TMG interfaces. Maybe all of this is in the original post... wherever that might be. I'm going to assume that you're *routing* traffic through the TMG from one private network to another
private network, most likely from the DMZ to the WSUS server in the Internal LAN. (Just an educated guess.)
The second set of questions... is 172.16.3.3 the IP Address of the WSUS Server on the Internal LAN, or is that the address of the DMZ Interface on the TMG. Configured correctly, it should be the former.
Third set of questions.... always a question I ask because it invariably sheds amazing insights into other network issues.... Why are you configuring the policy with an IP Address, rather than the hostname of the WSUS server?
There has to be a way for me to get this dang server to get updates from our WSUS server on the other side of the TMG firewall.. but how?!
Properly configure a Web Publishing Rule. It's that simple. I have a WSUS server "published" to the DMZ so I can patch my DMZ servers and it works perfectly.
Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
SolarWinds Head Geek
Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
http://www.solarwinds.com/gotmicrosoft
The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

Microsoft Security Essentials not taking definition updates from WSUS Server.

Hi Experts,
I have a WSUS server installed on network on which MSE definition updates are installed, but the MSE on the client computer is not getting updates from it.
When I click the update button it gives me error "Virus and spyware definitions couldn't be updated".
The error code i am getting is 0x80244018. The definition updates couldn't be installed please try again later.
I also have TMG on my network as a default gateway, I want to update MSE from WSUS not from microsoft update.
Do I have to change rules....??? or any suggesstions that how MSE can be automatically updated from WSUS, the WSUS setting is saved into a GROUP Policy and applied....
Please advice......

The error code i am getting is 0x80244018.
This is an HTTP 403 error, which is generally (but not always) indicative of a proxy server interfering with the download. Assuming this is happening when the client is trying to get Definition Updates from Microsoft during the daily scan, this error will
likely go away once you properly set up WSUS to provide the definition updates.
I want to update MSE from WSUS not from microsoft update.
To do this, you need the following:
The Definition Updates classification must be configured for synchronization.
An Automatic Approval rule that approves the Definition Updates classification for the appropriate target group(s) must be configured and enabled.
The policy setting Allow Automatic Updates immediate installation must be ENABLED.
Your WSUS server should be configured to synchronize multiple times per day (at least 2).
Your clients should be configured with a shorter Detection Frequency (8 hours is ideal).
With the above configured, the clients will check the WSUS server 3x-4x per day, find the latest available Definition Update, download it and install it immediately.
Note, however, that if the client fails to download and install Definition Updates, MSE will continue to do a check, and attempt to update the Definition Updates during the daily scan. If your TMG blocks the client's Internet access, then they
will continue to log HTTP 403 errors when this definition update attempt is executed. (This is why you configure multiple syncs and scans per day -- so the client *never* has to go to Microsoft to get the current definition updates.)
Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
SolarWinds Head Geek
Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
http://www.solarwinds.com/gotmicrosoft
The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

How do you configure a client to update from the server

I found the information on how to point clients to a software update server but the problem I have is the URL.
The example is http://su.example.com:8088/index.sucatalog
I don't have a URL as far as I know and if I did, is the default port 8088 or where can I change or check that?
And where is a list of the catalog file for the specific versions of OS X?
Basically I have 8 Macs all running Yosemite except for one running 10.8.5. Instead of all the machines hitting the internet for updates, I'd like just my server to down the updates and then all clients update from the server.
If there is better instructions on how to do this, please point the way.
TIA
Chris

John Lockwood wrote:
This does mean you need to buy a DNS load balancer to do this. The Mac itself cannot.
FWIW, OS X Server is capable of performing round-robin access with the inbound traffic using multiple IP addresses for a single host name. The addresses are each of the software update servers in your server pool.
This'll toss errors for some translations when one of the servers is down — you can tweak the definition if one of the servers is going to be offline for a while — but some of the updates will get through.
Set the DNS TTL fairly short — probably somewhere between a few minutes and an hour — to allow the DNS translations to be changed fairly quickly, if your software update servers are prone to outages.

CLIENT UNABLE TO UPDATE from WSUS SERVER

Dear all
we have a WSUS server installed on windows server 2012, the clients is no longer able to download updates, getting error WindowsUpdate_80072EE2" "WindowsUpdate_dt000"
here is the client log file
2014-02-17 18:20:13:346 1024 f98 Misc WARNING: Send failed with hr = 80072ee2.
2014-02-17 18:20:13:346 1024 f98 Misc WARNING: SendRequest failed with hr = 80072ee2. Proxy List used: <(null)>
Bypass List used : <(null)> Auth Schemes used : <>
2014-02-17 18:20:13:346 1024 f98 Misc WARNING: WinHttp: SendRequestUsingProxy failed for <http://rwf-1:8530/selfupdate/wuident.cab>.
error 0x80072ee2
2014-02-17 18:20:13:346 1024 f98 Misc WARNING: WinHttp: SendRequestToServerForFileInformation MakeRequest failed.
error 0x80072ee2
2014-02-17 18:20:13:346 1024 f98 Misc WARNING: WinHttp: SendRequestToServerForFileInformation failed with 0x80072ee2
2014-02-17 18:20:13:346 1024 f98 Misc WARNING: WinHttp: ShouldFileBeDownloaded failed with 0x80072ee2
2014-02-17 18:20:13:358 1024 f98 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
2014-02-17 18:20:13:363 1024 f98 Misc Microsoft signed: Yes
2014-02-17 18:20:13:365 1024 f98 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
2014-02-17 18:20:13:371 1024 f98 Misc Microsoft signed: Yes
2014-02-17 18:20:13:379 1024 f98 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
2014-02-17 18:20:13:385 1024 f98 Misc Microsoft signed: Yes
2014-02-17 18:20:13:400 1024 f98 Setup Determining whether a new setup handler needs to be downloaded
2014-02-17 18:20:13:400 1024 f98 Setup SelfUpdate handler is not found. It will be downloaded
2014-02-17 18:20:13:400 1024 f98 Setup Evaluating applicability of setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~x86~~7.6.7600.256"
2014-02-17 18:20:13:403 1024 f98 Setup Setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~x86~~7.6.7600.256"
is already installed.
2014-02-17 18:20:13:403 1024 f98 Setup Evaluating applicability of setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~x86~~7.6.7600.256"
2014-02-17 18:20:13:414 1024 f98 Setup Setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~x86~~7.6.7600.256"
is already installed.
2014-02-17 18:20:13:414 1024 f98 Setup Evaluating applicability of setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~x86~~7.6.7600.256"
2014-02-17 18:20:13:432 1024 f98 Setup Setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~x86~~7.6.7600.256"
is already installed.
2014-02-17 18:20:13:432 1024 f98 Setup SelfUpdate check completed. SelfUpdate is NOT required.
2014-02-17 18:20:13:723 1024 f98 PT +++++++++++ PT: Synchronizing
server updates +++++++++++
2014-02-17 18:20:13:723 1024 f98 PT  + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL
= http://rwf-1:8530/ClientWebService/client.asmx
2014-02-17 18:20:13:858 1024 f98 PT WARNING: Cached cookie has expired or new PID is available
2014-02-17 18:20:13:858 1024 f98 PT Initializing simple targeting cookie, clientId = 5c40eee5-ae54-4cbd-8758-a694a59ade20,
target group = ROLMAN, DNS name = it.rolmanworld.com
2014-02-17 18:20:13:858 1024 f98 PT  Server URL = http://rwf-1:8530/SimpleAuthWebService/SimpleAuth.asmx
2014-02-17 18:21:14:006 1024 f98 Misc WARNING: Send failed with hr = 80072ee2.
2014-02-17 18:21:14:006 1024 f98 Misc WARNING: SendRequest failed with hr = 80072ee2. Proxy List used: <(null)>
Bypass List used : <(null)> Auth Schemes used : <>
2014-02-17 18:21:14:006 1024 f98 PT  + Last proxy send request failed with hr = 0x80072EE2, HTTP status
code = 0
2014-02-17 18:21:14:006 1024 f98 PT  + Caller provided credentials = No
2014-02-17 18:21:14:006 1024 f98 PT  + Impersonate flags = 0
2014-02-17 18:21:14:006 1024 f98 PT  + Possible authorization schemes used =
2014-02-17 18:21:14:006 1024 f98 PT WARNING: GetCookie failure, error = 0x80072EE2, soap client error = 5, soap
error code = 0, HTTP status code = 200
2014-02-17 18:21:14:006 1024 f98 PT WARNING: PTError: 0x80072ee2
2014-02-17 18:21:14:006 1024 f98 PT WARNING: GetCookie_WithRecovery failed : 0x80072ee2
2014-02-17 18:21:14:006 1024 f98 PT WARNING: RefreshCookie failed: 0x80072ee2
2014-02-17 18:21:14:006 1024 f98 PT WARNING: RefreshPTState failed: 0x80072ee2
2014-02-17 18:21:14:006 1024 f98 PT WARNING: Sync of Updates: 0x80072ee2
2014-02-17 18:21:14:006 1024 f98 PT WARNING: SyncServerUpdatesInternal failed: 0x80072ee2
2014-02-17 18:21:14:006 1024 f98 Agent  * WARNING: Failed to synchronize, error = 0x80072EE2
2014-02-17 18:21:14:009 1024 f98 Agent  * WARNING: Exit code = 0x80072EE2
2014-02-17 18:21:14:009 1024 f98 Agent *********
2014-02-17 18:21:14:009 1024 f98 Agent ** END ** Agent: Finding updates [CallerId = AutomaticUpdates]
2014-02-17 18:21:14:009 1024 f98 Agent *************
2014-02-17 18:21:14:009 1024 f98 Agent WARNING: WU client failed Searching for update with error 0x80072ee2
2014-02-17 18:21:14:024 1024 d9c AU >>## RESUMED ## AU: Search for updates [CallId = {B6B4993C-E64D-41EE-BB3B-4C0259522B34}]
2014-02-17 18:21:14:024 1024 d9c AU  # WARNING: Search callback failed, result = 0x80072EE2
2014-02-17 18:21:14:024 1024 d9c AU  # WARNING: Failed to find updates with error code 80072EE2
2014-02-17 18:21:14:024 1024 d9c AU #########
2014-02-17 18:21:14:024 1024 d9c AU ## END ## AU: Search for updates [CallId = {B6B4993C-E64D-41EE-BB3B-4C0259522B34}]
2014-02-17 18:21:14:024 1024 d9c AU #############
2014-02-17 18:21:14:024 1024 d9c AU Successfully wrote event for AU health state:0
2014-02-17 18:21:14:024 1024 d9c AU AU setting next detection timeout to 2014-02-17 19:21:14
2014-02-17 18:21:14:024 1024 d9c AU Successfully wrote event for AU health state:0
2014-02-17 18:21:14:025 1024 d9c AU Successfully wrote event for AU health state:0
2014-02-17 18:21:19:010 1024 f98 Report REPORT EVENT: {37C49AAA-0782-441A-85BD-BC86F384B332}2014-02-17 18:21:14:009+0400 1 148 101 {00000000-0000-0000-0000-000000000000} 0 80072ee2AutomaticUpdates Failure Software
Synchronization Windows Update Client failed to detect with error 0x80072ee2.
2014-02-17 18:21:19:060 1024 f98 Report CWERReporter::HandleEvents - WER report upload completed with status
0x8
2014-02-17 18:21:19:060 1024 f98 Report WER Report sent: 7.6.7600.256 0x80072ee2 00000000-0000-0000-0000-000000000000
Scan 101 Managed
2014-02-17 18:21:19:060 1024 f98 Report CWERReporter finishing event handling. (00000000)
I've tried all the ways, restarting the services, file permissions, and many other
PLEASE HELP
thank you

thank you for your reply,
I tried so many ways but couldn't solve it, then I removed the WSUS rule, and re-install it
then after installing the rule i'm getting error when configuring the WSUS ERROR : http://i.imgur.com/eqm9ViT.png
Post install is starting
Fatal Error: Failed to start and configure the WSUS service
and here is the log file
2014-02-20 08:37:47 Postinstall started
2014-02-20 08:37:47 Detected role services: Api, UI, WidDatabase, Services
2014-02-20 08:37:47 Start: LoadSettingsFromParameters
2014-02-20 08:37:47 Content local is: True
2014-02-20 08:37:47 Content directory is: E:\WSUS
2014-02-20 08:37:47 SQL instname is:
2014-02-20 08:37:47 End: LoadSettingsFromParameters
2014-02-20 08:37:47 Start: Run
2014-02-20 08:37:47 Configuring content directory...
2014-02-20 08:37:47 Configuring groups...
2014-02-20 08:37:48 Starting group configuration for WSUS Administrators...
2014-02-20 08:37:48 Found group in regsitry, attempting to use it...
2014-02-20 08:37:48 Searching for existing group...
2014-02-20 08:37:48 Existing group was found
2014-02-20 08:37:48 Writing group to registry...
2014-02-20 08:37:48 Finished group creation
2014-02-20 08:37:48 Starting group configuration for WSUS Reporters...
2014-02-20 08:37:48 Found group in regsitry, attempting to use it...
2014-02-20 08:37:48 Searching for existing group...
2014-02-20 08:37:48 Existing group was found
2014-02-20 08:37:48 Writing group to registry...
2014-02-20 08:37:48 Finished group creation
2014-02-20 08:37:48 Configuring permissions...
2014-02-20 08:37:48 Fetching content directory...
2014-02-20 08:37:48 Fetching ContentDir from registry store
2014-02-20 08:37:48 Value is E:\WSUS
2014-02-20 08:37:48 Fetching group SIDs...
2014-02-20 08:37:48 Fetching WsusAdministratorsSid from registry store
2014-02-20 08:37:48 Value is S-1-5-21-495251104-1553465597-2720485832-1634
2014-02-20 08:37:48 Fetching WsusReportersSid from registry store
2014-02-20 08:37:48 Value is S-1-5-21-495251104-1553465597-2720485832-1635
2014-02-20 08:37:48 Creating group principals...
2014-02-20 08:37:49 Granting directory permissions...
2014-02-20 08:37:49 Granting permissions on content directory...
2014-02-20 08:37:49 Granting registry permissions...
2014-02-20 08:37:49 Granting registry permissions...
2014-02-20 08:37:49 Granting registry permissions...
2014-02-20 08:37:49 Configuring shares...
2014-02-20 08:37:49 Configuring network shares...
2014-02-20 08:37:49 Fetching content directory...
2014-02-20 08:37:49 Fetching ContentDir from registry store
2014-02-20 08:37:49 Value is E:\WSUS
2014-02-20 08:37:49 Fetching WSUS admin SID...
2014-02-20 08:37:49 Fetching WsusAdministratorsSid from registry store
2014-02-20 08:37:49 Value is S-1-5-21-495251104-1553465597-2720485832-1634
2014-02-20 08:37:49 Content directory is local, creating content shares...
2014-02-20 08:37:49 Creating share "UpdateServicesPackages" with path "E:\WSUS\UpdateServicesPackages" and description "A network share to be used by client systems for collecting all software packages (usually applications) published on this WSUS system."
2014-02-20 08:37:49 Deleting existing share...
2014-02-20 08:37:49 Creating share...
2014-02-20 08:37:49 Share successfully created
2014-02-20 08:37:49 Creating share "WsusContent" with path "E:\WSUS\WsusContent" and description "A network share to be used by Local Publishing to place published content on this WSUS system."
2014-02-20 08:37:49 Deleting existing share...
2014-02-20 08:37:49 Creating share...
2014-02-20 08:37:49 Share successfully created
2014-02-20 08:37:49 Creating share "WSUSTemp" with path "C:\Program Files\Update Services\LogFiles\WSUSTemp" and description "A network share used by Local Publishing from a Remote WSUS Console Instance."
2014-02-20 08:37:49 Deleting existing share...
2014-02-20 08:37:50 Creating share...
2014-02-20 08:37:50 Share successfully created
2014-02-20 08:37:50 Finished creating content shares
2014-02-20 08:37:50 Configuring WID database...
2014-02-20 08:37:50 Configuring the database...
2014-02-20 08:37:50 Establishing DB connection...
2014-02-20 08:37:50 Checking to see if database exists...
2014-02-20 08:37:50 Database exists
2014-02-20 08:37:50 Switching database to single user mode...
2014-02-20 08:37:53 Loading install type query...
2014-02-20 08:37:53 DECLARE @currentScriptVersion int
DECLARE @currentDBVersion int
IF NOT EXISTS(SELECT * FROM sys.databases WHERE name='SUSDB')
BEGIN
SELECT 1
END
ELSE
BEGIN
SET @currentScriptVersion = (9200 + 16384)
SET @currentDBVersion = (SELECT SchemaVersion FROM SUSDB.dbo.tbSchemaVersion WHERE ComponentName = 'CoreDB')
IF @currentDBVersion < 926
BEGIN
SELECT 3
END
ELSE IF @currentDBVersion < @currentScriptVersion
BEGIN
SELECT 2
END
ELSE IF @currentDBVersion = @currentScriptVersion
BEGIN
SELECT 0
END
ELSE
BEGIN
SELECT 4
END
END
2014-02-20 08:37:53 Install type is: Reinstall
2014-02-20 08:37:53 Creating logins...
2014-02-20 08:37:53 Fetching account info for S-1-5-20
2014-02-20 08:37:53 Found principal
2014-02-20 08:37:53 Found account
2014-02-20 08:37:53 Got binary SID
2014-02-20 08:37:53 Fetching WsusAdministratorsSid from registry store
2014-02-20 08:37:53 Value is S-1-5-21-495251104-1553465597-2720485832-1634
2014-02-20 08:37:53 Fetching account info for S-1-5-21-495251104-1553465597-2720485832-1634
2014-02-20 08:37:53 Fetching account info for S-1-5-21-495251104-1553465597-2720485832-1634
2014-02-20 08:37:53 Found principal
2014-02-20 08:37:53 Found account
2014-02-20 08:37:53 Got binary SID
2014-02-20 08:37:53 Setting content location...
2014-02-20 08:37:53 Fetching ContentDir from registry store
2014-02-20 08:37:53 Value is E:\WSUS
2014-02-20 08:37:53 Swtching DB to multi-user mode......
2014-02-20 08:37:56 Finished setting multi-user mode
2014-02-20 08:37:56 Writing DB settings to registry...
2014-02-20 08:37:56 Marking PostInstall done for UpdateServices-WidDatabase in the registry...
2014-02-20 08:37:56 Configuring IIS...
2014-02-20 08:37:56 Start: ConfigureWebsite
2014-02-20 08:37:56 Configuring website on port 8530
2014-02-20 08:38:48 2014-02-20 08:38:10 Info IISCustomAction Performing Setup Action, Command /Install
2014-02-20 08:38:46 Info IISCustomAction Command /Install Succeeded
2014-02-20 08:38:48 End: ConfigureWebsite
2014-02-20 08:38:48 Configuring performance counters...
2014-02-20 08:38:48 Configuring Stats.NET perf counter...
2014-02-20 08:38:48 Configuring reporting perf counter...
2014-02-20 08:38:48 Configuring client webservice perf counter...
2014-02-20 08:38:48 Configuring server sync webservice perf counter...
2014-02-20 08:38:48 Configuring API remoting perf counter...
2014-02-20 08:38:48 Bringing services online...
2014-02-20 08:38:48 Checking initialization status...
2014-02-20 08:38:48 StartServer starting...
2014-02-20 08:38:48 Generating encryption key to write to the registry...
2014-02-20 08:38:48 Generating encryption key to write to the database...
2014-02-20 08:38:48 Generating encryption key succeeded...
2014-02-20 08:38:48 Setting WSUSService to autostart...
2014-02-20 08:38:48 WSUSService is set to autostart.
2014-02-20 08:38:48 Starting WSUSService...
2014-02-20 08:38:48 Failed to start WsusService. Exception: System.InvalidOperationException: Cannot start service WSUSService on computer '.'. ---> System.ComponentModel.Win32Exception: An instance of the service is already running
--- End of inner exception stack trace ---
at System.ServiceProcess.ServiceController.Start(String[] args)
at Microsoft.UpdateServices.Setup.StartServer.StartServer.StartAndConfigureService()
2014-02-20 08:38:48 Importing default detectoids.
2014-02-20 08:38:48 Importing CriticalUpdates.xml...
2014-02-20 08:38:49 Importing Drivers.xml...
2014-02-20 08:38:49 Importing FeaturePacks.xml...
2014-02-20 08:38:49 Importing MicrosoftCorporation.xml...
2014-02-20 08:38:49 Importing SecurityUpdates.xml...
2014-02-20 08:38:49 Importing ServicePacks.xml...
2014-02-20 08:38:49 Importing Tools.xml...
2014-02-20 08:38:49 Importing UpdateRollups.xml...
2014-02-20 08:38:49 Importing Updates.xml...
2014-02-20 08:38:49 Importing Windows.xml...
2014-02-20 08:38:49 Importing Windows2000family.xml...
2014-02-20 08:38:49 Importing WindowsServer2003DatacenterEdition.xml...
2014-02-20 08:38:50 Importing WindowsServer2003Family.xml...
2014-02-20 08:38:50 Importing WindowsXPfamily.xml...
2014-02-20 08:38:50 Importing LocalPublisher.xml...
2014-02-20 08:38:50 Importing LocallyPublishedPackages.xml...
2014-02-20 08:38:50 Importing Applications.xml...
2014-02-20 08:38:50 Importing Exchange.xml...
2014-02-20 08:38:50 Importing Office.xml...
2014-02-20 08:38:50 Importing SQL.xml...
2014-02-20 08:38:50 Importing Exchange2000Server.xml...
2014-02-20 08:38:50 Importing ExchangeServer2003.xml...
2014-02-20 08:38:50 Importing OfficeXP.xml...
2014-02-20 08:38:50 Importing Office2003.xml...
2014-02-20 08:38:50 Importing SQLServer.xml...
2014-02-20 08:38:50 Importing WindowsXP64BitEditionVersion2003.xml...
2014-02-20 08:38:50 Importing DefinitionUpdateSusXml.xml...
2014-02-20 08:38:50 Importing ClientServicingApiDetectoid.xml...
2014-02-20 08:38:50 Importing default detectoids succeeded.
2014-02-20 08:38:52 FixSubscriptionCategories failed. Exception: System.Net.WebException: The request failed with HTTP status 400: Bad Request.
at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
at Microsoft.UpdateServices.Internal.ApiRemoting.GetServerVersion()
at Microsoft.UpdateServices.Internal.DatabaseAccess.AdminDataAccessProxy.GetServerVersion()
at Microsoft.UpdateServices.Internal.BaseApi.UpdateServer.CreateUpdateServer(String serverName, Boolean useSecureConnection, Int32 portNumber)
at Microsoft.UpdateServices.Internal.BaseApi.UpdateServer..ctor(Boolean bypassApiRemoting)
at Microsoft.UpdateServices.Setup.StartServer.StartServer.FixSubscriptionCategories()
2014-02-20 08:38:52 StartServer encountered errors. Exception=The request failed with HTTP status 400: Bad Request.
2014-02-20 08:38:52 Microsoft.UpdateServices.Administration.CommandException: Failed to start and configure the WSUS service
at Microsoft.UpdateServices.Administration.PostInstall.Run()
at Microsoft.UpdateServices.Administration.PostInstall.Execute(String[] arguments)
PLEASE HELP
BEST REGARDS

Clients not updating from new WSUS server

I had 2 DCs in place running 2008 and 2003. The 2003 server was also running WSUS. It has been replaced with a 2012 R2 Essentials server which is now the FSMO holder and I installed WSUS on it using the standard options like I always do. Administration
runs on 8530.
I updated the GPOs with the new server's name. All clients can ping the WSUS server by name. All clients are reporting to the server and updates have been approved days ago. However none of the clients, including the server itself, are seeing any new updates
available even though the WSUS console shows they are reporting.
I've searched the registry of the 2008 DC for references to the old WSUS server and none were found. I looked in the registry key where you would find the value put there from the GPO and it correctly shows the current WSUS server.
I looked in the windowsupdate log on the 2008 DC and I don't see any errors. So I'm stumped as to why the clients can at least see the WSUS server and report to it but they aren't seeing the approved updates. Any ideas?
Jonathan

Hi Jonathan,
Have you checked if the update is downloaded successfully? The update will not be available until it has been downloaded on the WSUS server.
Best Regards.
Steven Lee Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Yes the updates have all downloaded as verified in the WSUS console. So the updates are there, the clients are reporting in and showing what updates they need, but what is not happening is that final connection so you see the little "pending updates"
icon in the system tray. I've done wuauclt /detectnow many times (used to doing this with other sites I manage) and had WU check for updates but it always shows none available.
Jonathan

FCS Not Updating from WSUS / Cannot open MOM Console / Cannot connect to MOM DB

Hi,
My original problem was that FCS was not updating from WSUS. Then after reading up, and trying a whole lot of different things I managed to break it further. Now I cannot open the Microsoft Forefront Client Security Console on the management server, The
Administrator Console and the Operator Console cannot connect to the Management server (They are on the management server)
As a side note: The reporting hasn't worked at all, not even after the last Systems Admin reloaded the whole FCS implementation.
I need assistance to get everything working again, and I think it might take a while to get everything resolved.
I don't know what information to provide so here is some to start with:
I believe this is a on server topology:
1. There is the management server, with all the roles except the "distribution" role installed.
2. The updates to FCS are set to go through our WSUS server.
3. The WSUS server works fine in all regards except to push the FCS updates through (I release other MS updates every week and they all go through)
4. Management server is 32-bit Windows Server 2008 Standard with SP1, with Microsoft Operations Manager 2005 (Unsure of SP1 is installed, but I think it is), and Microsoft SQL Server 2005 (It doesn't have the SQL Studio thing)
5. I have domain admin credentials
6. When opening the Microsoft Forefront Client Security console it crashes with a "MMC has detected an error in a snap-in and will unload it". Clicking on ok gives a new error page of exception: "System.Reflection.TargetInvocationException"
7. Opening the Operator console give a message of "Error connecting to server" and clicking on ok brings up the console settings where you specify the MOM management server etc
8. Opening the Administrator conolse immediately brings up the "Connect to a different MOM Management Server" window.
I am hoping that someone here can ask the right questions and helped get through all these issues to get this system working again

Thanks Quan and Faron for your replies. Firstly, when I logged into the server today and tried to open the consoles, the FCS console did not give me an error. Before I originally posted my message I already downloaded and tried that hotfix. The problem is
there is no SQL Management Studio. Microsoft SQL Server 2005 is installed.
The only error that really stands out is this one under the application logs:
Source: Microsoft Operations Manager
Event ID: 20607
The Data Access Server (DAS) on computer SSCIS04 returned an error. System error code: -2147217770 System error text: IDispatch error #3222 DAS method called: ConfigurationGetOnePointFreeSpace Called from file: d:\bt\4\private\product\core\engine\managers\perfcountermanager\src\momperfcountermanager.cpp
Called from line: 984 Other than that there are some terminal server printer errors and print spooler errors (which are common on pretty much all our servers), and Heartbeat errors (Event ID: 21213: Heartbeat update failed for 1 or fewer agents. Error details:
IDispatch error #3222)
I have just checked again and the FCS console is still opening without error. And I can start a scan. (No clients report back to the server though)

System center endpoint protection update from WSUS faild on some computers: error 0x80070005

Hi, some computers, not all fail to update from WSUS.
Manual installing the full updates works.
From Windowsupdate.log:
WARNING: Failed to delete old install directory at C:\Windows\SoftwareDistribution\Download\Install. This may block future installs.
I also cannot manually delete this folder, after a fresh reboot there is no more Install folder.
From System logs:
Sorry, the errors are in German:
Beim Aktualisieren der Signaturen wurde von Microsoft-Antischadsoftware ein Fehler festgestellt.
    Neue Signaturversion:
    Vorherige Signaturversion: 1.169.55.0
    Aktualisierungsquelle: Interner Server für Definitionsupdates
    Aktualisierungsphase: Installieren
    Quellpfad: http://sus-server:80
    Signaturtyp: AntiVirus
    Aktualisierungstyp: Vollständig
    Benutzer: NT-AUTORITÄT\SYSTEM
    Aktuelle Modulversion:
    Vorherige Modulversion: 1.1.10401.0
    Fehlercode: 0x80070005
    Fehlerbeschreibung: Zugriff verweigert
Beim Aktualisieren der Signaturen wurde von Microsoft-Antischadsoftware ein Fehler festgestellt.
    Neue Signaturversion:
    Vorherige Signaturversion: 1.169.55.0
    Aktualisierungsquelle: Microsoft Update Server
    Aktualisierungsphase: Installieren
    Quellpfad: http://www.microsoft.com
    Signaturtyp: AntiVirus
    Aktualisierungstyp: Vollständig
    Benutzer: NT-AUTORITÄT\SYSTEM
    Aktuelle Modulversion:
    Vorherige Modulversion: 1.1.10401.0
    Fehlercode: 0x80070005
    Fehlerbeschreibung: Zugriff verweigert
Client is manually install, unmanaged, no SystemCenter server.

I know this is an old post, but I've seen this several times on client pc's. Seems to happen only with .NET updates, it'll install one, then fail the rest. Windowsupdate.log file shows WARNING: Failed to delete old install directory
at C:\windows\SoftwareDistribution\Download\Install. This may block future installs.   It seems like concurrent installs fail because of this folder, and like the OP, when I reboot, that folder is gone and I can install the next update, which fails
the remaining updates, and then we repeat the process. This actually happened to me today new pc build, installed .net 4.0, .NET updates fail with error code 80070005. Yes, I'm logged in with an admin account. Anyone have any suggestions?
I can post log files or whatever if needed.
Tim Magnuson | MCTS, MCITP | MCCA 2011 |
Ok, so I changed my name...you can still call me Tom if you like. It's a...jump...to conclusions...mat.
My Blog Site: http://tmagnuson.wordpress.com

Windows 8.1 will not get Forefront Client Updates from WSUS

Recently I noticed that my Windows 8.1 clients were not getting updates from WSUS 3.2. After some searching I found it was an issue with HTTPS and the solution was to disable HTTPS or enable TLS. So I enabled TLS on the Server 2008 R2 WSUS server
and that fixed the issue with my 8.1 clients not getting updates except for Forefront Endpoint Protection 2010. My SCCM server deploys the client fine but it is version 2.1 and normally the client and definition updates come from WSUS with the
latest client version being 4.5. However, my Windows 8.1 machines will not get the client updates even though they are automatically approved for all machines.
I am just wondering what else I can check or change to make sure my Windows 8.1 clients get the Forefront client updates as they should?? I am wondering if I manually install the 4.1 client update if it will take the client updates after that.
I only have about eight Windows 8.1 machines so if I have to do that by hand for now then I will and I think my organization will be moving to Server 2012 and SCCM 2012 this summer sometime.

I reread your post and have another suggestion. If your SCCM 2007 server is still deploying the old 2.1 FEP client version, then you should install the latest anti-malware platform update for the SCCM server so you can deploy it from there instead of WSUS:
http://support.microsoft.com/kb/2952678
http://blogs.msdn.com/b/minfangl/archive/2013/08/15/guidance-on-install-anti-malware-platform-updates-for-fep-2010-su1-and-scep-2012-sp1.aspx
Also, you may be affected by this:
"Anti-malware platform updates on MU will use special detection logic and applicability rules to make the anti-malware platform updates available only on computers with previous N-2 anti-malware platforms installed. For example, on April 8<sup>th</sup>,
anti-malware platform of version 4.5.x will be released on MU, and it will only be offered to computers where anti-malware platform version 4.3.x or 4.4.x is available. If a computer has FEP or SCEP client with version 4.1.x, it has to be upgraded to version
4.3.x first, then to the latest version (4.5.x). If a computer has FEP or SCEP client with version older than 4.1.x, because of the same N-2 rule, it has to be upgraded to 4.1.x first, then to 4.3.x, and then to the latest version (4.5.x). Required updates
will be kept on MU to ensure that this upgrade process is available for computers running older versions of the Microsoft anti-malware platform."
http://blogs.technet.com/b/configmgrteam/archive/2014/03/27/anti-malware-platform-updates-for-endpoint-protection-will-be-released-to-mu.aspx

I cannot update from OS 10.9.4 to 10.9.5. I get a message saying: File couldn't be installed error (513). I have configured my OS so that I have read and write permission followed by system with read and writ permission. Can someone help me? Thanks.

I cannot update from OS X 10.9.4 t0 10.9.5> Whenever I try I get the following message: File couldn't be installed error (513) and something about not having the proper permission. Under the Macintosh HD sharing and permissions settings I have customized the settings so that (Me) has read and write permission followed by the system with read and write permission, wheel and everyone have Read permissions.
I have no problems updating apps such as Adobe CC or iTunes but cannot update the operating system, can someone help me? Thanks.

1. Restart the computer in safe mode. Certain caches maintained by the system will be rebuilt.
Safe mode is much slower to start up than normal. The next normal startup may also be somewhat slow.
When the login screen appears, restart as usual (not in safe mode) and test. There's no need to log in while in safe mode.
Note: If FileVault is enabled, or if a firmware password is set, or if the startup volume is a software RAID, you can’t start in safe mode. In that case, go to Step 2.
If there's no change after taking this step, continue.
2. Back up all data before proceeding.
Triple-click anywhere in the line below on this page to select it:
/var/folders
Right-click or control-click the highlighted line and select
Services ▹ Reveal in Finder (or just Reveal)
from the contextual menu.* A folder should open with an item named "folders" selected. Move the selected item to the Trash. You may be prompted for your administrator login password. Restart the computer and empty the Trash.
*If you don't see the contextual menu item, copy the selected text to the Clipboard by pressing the key combination command-C. In the Finder, select
Go ▹ Go to Folder...
from the menu bar and paste into the box that opens by pressing command-V. You won't see what you pasted because a line break is included. Press return.

Either there is no default mail client or the current mail client cannot fulfill the messaging request" error message when you send e-mail from Office 2010 in Outlook

Hi,
If save and send as attachment used in MS Office 2010 then outlook 2010 displays error "Either
there is no default mail client of the current mail client cannot fulfill the messaging request-----error Outlook 2010"
Windows 7 32 bit Enterprise edition and Offoce Professional plus 2010 32 bit is installed in the machine.
I have followed the below troubleshooting steps but still getting the same error.
Method 1:
Followed the Microsoft fix
http://support.microsoft.com/kb/813745
1. On the Windows taskbar, click
Start > Run.
2. In the Open box, type the following text:
3. regedit
4. Press Enter.
5. Go to the following registry key:
6. HKEY_LOCAL_MACHINE\SOFTWARE\Clients\Mail
7. In the right pane, right-click
the following registry value:
8. PreFirstRun
9. Click Delete
10. Click Start, and then click Run.
11. In the Open box, type regedit, and then pressENTER.
12. InRegistry Editor, locate the followingsubkey in the registry:
13. HKEY_LOCAL_MACHINE\Software\Clients\Mail\Microsoft Outlook
14. Select thesubkey, and then pressDELETE.
15. Click
Yes.
Method 2:
Repaired Office
Method 3:
fixmapi.exe. Mapi32.dll
Method 4:
Created the below registry key HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Offlce\15.0\Outlook
Create the following String value if it does not exist: Bitness Set the String value for Bitness to the following if it is not already set to x86
Method 5:
Compared the installed applications
Uninstalled the below program :Microsfot Visuall C++ 2008 Redistributable - x86 - KB2467175" and installed "Microsfot Visuall C++ 2008 Redistributable - x86 - 9.0.21022"
Please help to solve the issue.
Regards,
Boopathi S

Hi,
Do you mean Send as Attachment button under File>Save & Send>Sending Using E-mail
in Office applications, like Excel or Word?
Is this an issue that come up recently? Have you ever made any changes to your system?
If you have installed multiple e-mail programs on the same computer, please try to make Outlook the default mail client and then try again:
http://office.microsoft.com/en-us/outlook-help/make-outlook-the-default-program-for-email-messages-contacts-and-calendar-HP010355552.aspx
http://support.microsoft.com/kb/223877
Regards,
Ethan Hua
TechNet Community Support
It's recommended to download and install
Configuration Analyzer Tool (OffCAT), which is developed by Microsoft Support teams. Once the tool is installed, you can run it at any time to scan for hundreds of known issues in Office
programs.

Windows 2012 r2 not able to get windows updates from WSUS 2012 r2

One of our windows 2012 R2 server is not getting windows updates from WSUS 2012 R2 but other 2012 R2 are getting updates.
I found on windowsupdate log on the server saying "WARNING: Failed to get Network Cost info from NLM, assuming network is NOT metered, error = 0x80240037"
Not sure what is the issue.

I believe the warning isn't really relevant in this case. Could you post a recent section from the windowsupdate.log from that machine?
0x80240037 WU_E_NOT_SUPPORTED The functionality for the operation is not supported.

Auto Deployment Rule download failed (0X87d20417) Failed to download the update from internet. Error = 16389

Hi there,
I have massive problems with Auto Deployment Rules.
I get the Error from above.
ruleengine.log says:
Failed to download the update from internet. Error = 16389 SMS_RULE_ENGINE 3/11/2015 11:41:57 AM 5608 (0x15E8)
Failed to download ContentID 16936340 for UpdateID 16953422. Error code = 16389 SMS_RULE_ENGINE 3/11/2015 11:41:57 AM 5608 (0x15E8)
Failed to download any update SMS_RULE_ENGINE 3/11/2015 11:41:58 AM 5608 (0x15E8)
Failed to download update contents. SMS_RULE_ENGINE 3/11/2015 11:41:58 AM 5608 (0x15E8)
No new update was added to the package. Package "00000116" would not be updated. SMS_RULE_ENGINE 3/11/2015 11:41:58 AM 5608 (0x15E8)
Failed to run the DownloadAction for the AutoDeployment. SMS_RULE_ENGINE 3/11/2015 11:41:58 AM 5608 (0x15E8)
STATMSG: ID=8706 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_RULE_ENGINE" SYS=NE-SCCM-02.services.internal SITE=000 PID=3392 TID=5608 GMTDATE=Mi Mrz 11 10:41:58.606 2015 ISTR0="SMS Rule Engine" ISTR1="Failed to download one or more content files" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_RULE_ENGINE 3/11/2015 11:41:58 AM 5608 (0x15E8)
CRuleHandler: Enforcing Actions for Rule 16777227 failed!
Failed to download the update from internet. Error = 16389 SMS_RULE_ENGINE 3/11/2015 11:51:03 AM 5608 (0x15E8)
Failed to download ContentID 16936340 for UpdateID 16953422. Error code = 16389 SMS_RULE_ENGINE 3/11/2015 11:51:03 AM 5608 (0x15E8)
CRuleHandler: Enforcing Actions for Rule 16777230 failed! SMS_RULE_ENGINE 3/11/2015 11:51:10 AM 5608 (0x15E8)
CRuleHandler: ResetRulesAndCleanUp() SMS_RULE_ENGINE 3/11/2015 11:51:10 AM 5608 (0x15E8)
Updated Failure Information for Rule: 16777226 SMS_RULE_ENGINE 3/11/2015 11:51:10 AM 5608 (0x15E8)
Updated Failure Information for Rule: 16777227 SMS_RULE_ENGINE 3/11/2015 11:51:10 AM 5608 (0x15E8)
Updated Failure Information for Rule: 16777230 SMS_RULE_ENGINE 3/11/2015 11:51:10 AM 5608 (0x15E8)
whereas in WSUSCTRL.log i get:
System.Net.WebException: The underlying connection was closed: A connection that was expected to be kept alive was closed by the server. ---> System.IO.IOException: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host. ---> System.Net.Sockets.SocketException: An existing connection was forcibly closed by the remote host~~ at System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size)~~ --- End of inner exception stack trace ---~~ at System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size)~~ at System.Net.PooledStream.Read(Byte[] buffer, Int32 offset, Int32 size)~~ at System.Net.Connection.SyncRead(HttpWebRequest request, Boolean userRetrievedStream, Boolean probeRead)~~ --- End of inner exception stack trace ---~~ at Microsoft.UpdateServices.Administration.AdminProxy.CreateUpdateServer(Object[] args)~~ at Microsoft.UpdateServices.Administration.AdminProxy.GetUpdateServer()~~ at Microsoft.SystemsManagementServer.WSUS.WSUSServer.ConnectToWSUSServer(String ServerName, Boolean UseSSL, Int32 PortNumber)
System.Net.WebException: The request failed with HTTP status 503: Service Unavailable.~~ at Microsoft.UpdateServices.Administration.AdminProxy.CreateUpdateServer(Object[] args)~~ at Microsoft.UpdateServices.Administration.AdminProxy.GetUpdateServer()~~ at Microsoft.SystemsManagementServer.WSUS.WSUSServer.ConnectToWSUSServer(String ServerName, Boolean UseSSL, Int32 PortNumber) SMS_WSUS_CONTROL_MANAGER 3/11/2015 11:57:04 AM 6032 (0x1790)
Failed to set WSUS Local Configuration. Will retry configuration in 1 minutes SMS_WSUS_CONTROL_MANAGER 3/11/2015 11:57:04 AM 6032 (0x1790)
Attempting connection to local WSUS server SMS_WSUS_CONTROL_MANAGER 3/11/2015 11:57:04 AM 6032 (0x1790)
System.Net.WebException: The request failed with HTTP status 503: Service Unavailable.~~ at Microsoft.UpdateServices.Administration.AdminProxy.CreateUpdateServer(Object[] args)~~ at Microsoft.UpdateServices.Administration.AdminProxy.GetUpdateServer()~~ at Microsoft.SystemsManagementServer.WSUS.WSUSServer.ConnectToWSUSServer(String ServerName, Boolean UseSSL, Int32 PortNumber) SMS_WSUS_CONTROL_MANAGER 3/11/2015 11:57:04 AM 6032 (0x1790)
Failures reported during periodic health check by the WSUS Server XYZ. Will retry check in 1 minutes SMS_WSUS_CONTROL_MANAGER 3/11/2015 11:57:04 AM 6032 (0x1790)
ooGDoo

There only is Patchdownloader.log under
\\SCCMSERVER\C$\Program Files\SMS_CCM\LOGS\Patchdownloader.log
Do you mean this Log?
Failed to move \\teg.teda\admin\SCCM\SU\Baseline\Patches\e7b56916-3356-4f59-ac71-be7ef2159050.1 to \\teg.teda\admin\SCCM\SU\Baseline\Patches\e7b56916-3356-4f59-ac71-be7ef2159050, error 64 Software Updates Patch Downloader 3/11/2015 11:50:33 AM 5608 (0x15E8)
Will retry in 10000ms Software Updates Patch Downloader 3/11/2015 11:50:33 AM 5608 (0x15E8)
Failed to move \\teg.teda\admin\SCCM\SU\Baseline\Patches\e7b56916-3356-4f59-ac71-be7ef2159050.1 to \\teg.teda\admin\SCCM\SU\Baseline\Patches\e7b56916-3356-4f59-ac71-be7ef2159050, error 5 Software Updates Patch Downloader 3/11/2015 11:50:43 AM 5608 (0x15E8)
Will retry in 10000ms Software Updates Patch Downloader 3/11/2015 11:50:43 AM 5608 (0x15E8)
Failed to move \\teg.teda\admin\SCCM\SU\Baseline\Patches\e7b56916-3356-4f59-ac71-be7ef2159050.1 to \\teg.teda\admin\SCCM\SU\Baseline\Patches\e7b56916-3356-4f59-ac71-be7ef2159050, error 5 Software Updates Patch Downloader 3/11/2015 11:50:53 AM 5608 (0x15E8)
Will retry in 10000ms Software Updates Patch Downloader 3/11/2015 11:50:53 AM 5608 (0x15E8)
Failed to move \\teg.teda\admin\SCCM\SU\Baseline\Patches\e7b56916-3356-4f59-ac71-be7ef2159050.1 to \\teg.teda\admin\SCCM\SU\Baseline\Patches\e7b56916-3356-4f59-ac71-be7ef2159050, error 5 Software Updates Patch Downloader 3/11/2015 11:51:03 AM 5608 (0x15E8)
MoveFile() failed to rename \\teg.teda\admin\SCCM\SU\Baseline\Patches\e7b56916-3356-4f59-ac71-be7ef2159050.1 to \\teg.teda\admin\SCCM\SU\Baseline\Patches\e7b56916-3356-4f59-ac71-be7ef2159050 with GetLastError() = 5 Software Updates Patch Downloader 3/11/2015 11:51:03 AM 5608 (0x15E8)
ERROR: DownloadContentFiles() failed with hr=0x80004005 Software Updates Patch Downloader
ooGDoo

Clients cannot update from WSUS server - error 8024400E

Similar Messages

Maybe you are looking for