Hi, I have recently installed SCUP 2011 and imported HP updates.
We have HP System Management Homepage 7.4.0.12 (released on 9 Sep 2014) as per http://h18013.www1.hp.com/products/servers/management/agents
I tried importing the catalog couple of times but I don't see the update showing up in SCUP console. I am not sure if it takes a while to get the package uploaded or if I am missing anything?
What is the difference between the columns ScanPackageVersion and LastScanPackageVersion in the view v_UpdateScanStatus?
Running SCCM 2012 RC.
Setting up Software Updates as per this guide:
Downloading the Software Updates fails with the error "The Deploy Software Updates Wizard completed with errors - Access is Denied"
Permissions on the share are correct:
NTFS permissions are also correct.
I've seen this problem posted in other forums, all of whicvh say to make sure the share permissions are correct, which they are.
I've also managed to create a share in the same folder structure for Endpoint Definition Updates, so the process worked previously.
What on earth is going wrong?
Have you tried turning it off and back on again?
HI,
I am getting the below error in Update deployment.log. Because of this an advertised task sequence is not getting installed.
Job error (0x80004005) received for assignment ({54F48F2B-4838-4E79-8C15-FAED2504CC4D}) actionPlease let me know how to solve this
Regards,
Boopathi S
Folks
I have issues downloading windows updates from sccm 2007, it was working for years, all of sudden triggers error while downloading update.
"The update List wizard encountered warnings" Error: Connection to the server could not be established" Note: SCCM and WSUS on single server, no issues with proxy settings on sccm server.
please give us some heads up....
Cheers S
With best regards Siddarth Sajjan : Disclaimer: This posting is provided "as is" with no warranties, and confers no rights. http://siddarthsajjantechnotes.blogspot.co.nz/
Hi All,
Did any one have a sure shot resolution for the error message, that SCCM server is not able to download the software updates.
and gives an error message " A connection with the serve could not be established".
Rgs,
Hi all,
knowning that there are already a lot of posts concerning above message, I have to write an additional one as I could not find a solution on the web yet.
Situation:
Windows Server 2008 forest including empty root and two child domains, one child domain does have SCCM SP1 (central primary site WND) installed on W2k8 x64 machine including WSUS 3.0 SP1 => everything is working fine.
Second child domain also contains a SCCM SP1 server (primary site HUN) running on W2k8 x64 and is defined as child site of central site WND => everything is working fine too - except Software Updates.
WSUS 3.0 SP1 installed on both SCCM servers by creating additional web site (not using "defautl web site") and configured ports 8530 and 8531 (SSL not used!). No proxy necessary/used. All WSUS 3.0 requirements for W2k8 are installed (IIS roles)
Error:
SMS_WSUS_CONFIGURATION_MANAGER - MessageID 6600:
SMS WSUS Configuration Manager failed to configure upstream server settings on WSUS Server "xxxx0003".
Possible cause: WSUS Server version 3.0 SP1 and above is not installed or cannot be contacted.
Solution: Verify that the WSUS Server version 3.0 SP1 or greater is installed. Verify that the IIS ports configured in SMS are same as those configured on the WSUS IIS website.
wsusutil checkhealth =>OK
downloading updates from WSUS at central site (SUSDB and WSUS folder equal in size) =>OK
wsus admin console able to connect and configuration possible => OK
IIS ports configured within SMS are equal to those configured for WSUS website
SCCM config (using Configuration Manager Console) does look correct - ConfigMgr Software Update Point role properties and Software Update Point Component properties
wcm.log does report an error: (SCCM Log files at the end.)
"The request failed with HTTP status 503: Service Unavailable"
IIS log files of both websites (default web site and WSUS Administration website) do not show any errors.
Questions:
What else should I look at? (registyr, SUSDB content,..)
What exactly does happen during the attempt to configure the upstream server by the SMS_WSUS_Configuration_Manager component? I guess a SMS process tries to contact a webservice - would it be possible to debug in more detail ?
And finally - Who does know the solution ? 
wcm.log:
Found WSUS Admin dll of assembly version Microsoft.UpdateServices.Administration, Version=3.0.6000.273, Major Version = 0x30000, Minor Version = 0x17700111 SMS_WSUS_CONFIGURATION_MANAGER 16.07.2008 12:49:47 4468 (0x1174)
Found WSUS Admin dll of assembly version Microsoft.UpdateServices.Administration, Version=3.1.6001.1, Major Version = 0x30001, Minor Version = 0x17710001 SMS_WSUS_CONFIGURATION_MANAGER 16.07.2008 12:49:47 4468 (0x1174)
The installed WSUS build has the valid and supported WSUS Administration DLL assembly version (3.1.6001.65) SMS_WSUS_CONFIGURATION_MANAGER 16.07.2008 12:49:47 4468 (0x1174)
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(String serverName, Boolean useSecureConnection, Int32 portNumber)~~ at Microsoft.SystemsManagementServer.WSUS.WSUSServer.ConnectToWSUSServer(String ServerName, Boolean UseSSL, Int32 PortNumber) SMS_WSUS_CONFIGURATION_MANAGER 16.07.2008 12:49:47 4468 (0x1174)
Remote configuration failed on WSUS Server. SMS_WSUS_CONFIGURATION_MANAGER 16.07.2008 12:49:47 4468 (0x1174)
STATMSG: ID=6600 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_CONFIGURATION_MANAGER" SYS=xxxx0003 SITE=HUN PID=2424 TID=4468 GMTDATE=Mi Jul 16 10:49:47.758 2008 ISTR0="xxxx0003" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_WSUS_CONFIGURATION_MANAGER 16.07.2008 12:49:47 4468 (0x1174)
Waiting for changes for 59 minutes SMS_WSUS_CONFIGURATION_MANAGER 16.07.2008 12:49:47 4468 (0x1174)
wsusctrl.log (looks fine to me - is able to connect to local WSUS !):
SMS_EXECUTIVE started SMS_WSUS_CONTROL_MANAGER as thread ID 6156 (0x180C). SMS_WSUS_CONTROL_MANAGER 16.07.2008 12:04:01 2732 (0x0AAC)
This is a WSUS Role as WSUS registry key exists. SMS_WSUS_CONTROL_MANAGER 16.07.2008 12:04:01 6156 (0x180C)
Found WSUS Admin dll of assembly version Microsoft.UpdateServices.Administration, Version=3.0.6000.273, Major Version = 0x30000, Minor Version = 0x17700111 SMS_WSUS_CONTROL_MANAGER 16.07.2008 12:04:01 6156 (0x180C)
Found WSUS Admin dll of assembly version Microsoft.UpdateServices.Administration, Version=3.1.6001.1, Major Version = 0x30001, Minor Version = 0x17710001 SMS_WSUS_CONTROL_MANAGER 16.07.2008 12:04:01 6156 (0x180C)
The installed WSUS build has the valid and supported WSUS Administration DLL assembly version (3.1.6001.65) SMS_WSUS_CONTROL_MANAGER 16.07.2008 12:04:01 6156 (0x180C)
Successfully connected to local WSUS server SMS_WSUS_CONTROL_MANAGER 16.07.2008 12:04:01 6156 (0x180C)
Local WSUS Server Proxy settings are correctly configured as Proxy Name and Proxy Port 80 SMS_WSUS_CONTROL_MANAGER 16.07.2008 12:04:01 6156 (0x180C)
Waiting for changes for 0 minutes SMS_WSUS_CONTROL_MANAGER 16.07.2008 12:04:01 6156 (0x180C)
Timed Out... SMS_WSUS_CONTROL_MANAGER 16.07.2008 12:04:01 6156 (0x180C)
Found WSUS Admin dll of assembly version Microsoft.UpdateServices.Administration, Version=3.0.6000.273, Major Version = 0x30000, Minor Version = 0x17700111 SMS_WSUS_CONTROL_MANAGER 16.07.2008 12:04:01 6156 (0x180C)
Found WSUS Admin dll of assembly version Microsoft.UpdateServices.Administration, Version=3.1.6001.1, Major Version = 0x30001, Minor Version = 0x17710001 SMS_WSUS_CONTROL_MANAGER 16.07.2008 12:04:01 6156 (0x180C)
The installed WSUS build has the valid and supported WSUS Administration DLL assembly version (3.1.6001.65) SMS_WSUS_CONTROL_MANAGER 16.07.2008 12:04:01 6156 (0x180C)
Successfully connected to local WSUS server SMS_WSUS_CONTROL_MANAGER 16.07.2008 12:04:01 6156 (0x180C)
Local WSUS Server Proxy settings are correctly configured as Proxy Name and Proxy Port 80 SMS_WSUS_CONTROL_MANAGER 16.07.2008 12:04:01 6156 (0x180C)
Successfully connected to local WSUS server SMS_WSUS_CONTROL_MANAGER 16.07.2008 12:04:01 6156 (0x180C)
There are no unhealthy WSUS Server components on WSUS Server xxxx0003 SMS_WSUS_CONTROL_MANAGER 16.07.2008 12:04:01 6156 (0x180C)
Successfully checked database connection on WSUS server xxxx0003 SMS_WSUS_CONTROL_MANAGER 16.07.2008 12:04:02 6156 (0x180C)
Waiting for changes for 57 minutes SMS_WSUS_CONTROL_MANAGER 16.07.2008 12:04:02 6156 (0x180C)
wsyncmgr.log (as a result of being not able to configure upstream server I guess):
STATMSG: ID=6701 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=xxxx0003 SITE=HUN PID=2424 TID=4476 GMTDATE=Mi Jul 16 10:03:51.481 2008 ISTR0="" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_WSUS_SYNC_MANAGER 16.07.2008 12:03:51 4476 (0x117C)
Sync failed: WSUS server not configured. Source: CWSyncMgr:
oSync SMS_WSUS_SYNC_MANAGER 16.07.2008 12:08:51 4476 (0x117C)
STATMSG: ID=6703 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=xxxx0003 SITE=HUN PID=2424 TID=4476 GMTDATE=Mi Jul 16 10:08:51.636 2008 ISTR0="CWSyncMgr:oSync" ISTR1="WSUS server not configured" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_WSUS_SYNC_MANAGER 16.07.2008 12:08:51 4476 (0x117C)
Hi All,
SCCM Clients are failing to complete Software Update Scan Cycle, Below is the error found in WUAHandler.log
OnSearchComplete - Failed to end search job. Error = 0x80244018.
Scan failed with error = 0x80244018.
Scenario:-
SCCM Server on Domain A , SUP Server on Domain A
SCCM Clients migrated from Domain B to Domain A. After migration they are not completing the Update Scan Cycle.
Clients which are in Domain A are able to complete scan successfully.
Checks Done: -
1. No Proxy Server between Client and SUP/SCCM Site Server
2. No Firewall between Client and SUP/SCCM Site Server
3. Ran WSUS Client Diag Tool Below is the Output
C:\WSUSTool>ClientDiag.exe
WSUS Client Diagnostics Tool
Checking Machine State
Checking for admin rights to run tool . . . . . . . . . PASS
Automatic Updates Service is running. . . . . . . . . . PASS
Background Intelligent Transfer Service is not running. PASS
Wuaueng.dll version 7.4.7600.226. . . . . . . . . . . . PASS
This version is WSUS 2.0
Checking AU Settings
AU Option is 2 : Notify Prior to Download . . . . . . . PASS
Option is from Control Panel
Checking Proxy Configuration
Checking for winhttp local machine Proxy settings . . . PASS
Winhttp local machine access type
<Direct Connection>
Winhttp local machine Proxy. . . . . . . . . . NONE
Winhttp local machine ProxyBypass. . . . . . . NONE
Checking User IE Proxy settings . . . . . . . . . . . . PASS
User IE Proxy. . . . . . . . . . . . . . . . . NONE
User IE ProxyByPass. . . . . . . . . . . . . . NONE
User IE AutoConfig URL Proxy . . . . . . . . . NONE
User IE AutoDetect
AutoDetect not in use
Checking Connection to WSUS/SUS Server
WUServer =http://SUPSERVER:80
WUStatusServer =http://SUPSERVER:80
UseWuServer is enabled. . . . . . . . . . . . . . . . . PASS
Connection to server. . . . . . . . . . . . . . . . . . PASS
SelfUpdate folder is present. . . . . . . . . . . . . . PASS
Press Enter to Complete
Appriciate your time and help.
Regards,
SB
My question is how do customers that have signed up for extended support agreement with Microsoft for Windows XP get any NEW Windows XP security updates through SCCM/WSUS?
1. How are these NEW security updates released to the customer?
2. How can they deploy these through SCCM 2007/2012?
3., If updates are released through another mechanism , I presume the customer woyuld need to manually deploy these through SCCM?
Appreciate if anyone has had experience recently around this?
I think maybe I'm doing something wrong. I am using the SCCM Software Update to install updates on clients. Everything seems to be working correctly, but the clients are not running the updates I push. I looked in windows\system32\ccm\cache and the update files are there, but they are not being executed. Can I assume SCCM starts the exe files on the clients or does another process start the execution of the files? Did I forget to check a box in my setup some place? I have been thru the guides several times and performed all the proper steps. I can't seem to find any troubleshooting info on this particular issue. Do any of you folks out there have any suggestions I can look at to resolve this issue. Thank you in advance.
Bob Royce
Arrrghh! Going bonkers here.
We're rolling out Windows 7 SP1 across several thousand machines, via Software Updates, and getting reports of a few users who are getting a failed install.
In all the cases so far, I have been able to fix them by getting the user to download the System Readiness Update Tool, which appears to install using the Windows Standalone Installer (WUSA.exe) and does a one-time scan and fixes packages under C:\Windows\Servicing\Packages which, for some reason, sometimes don’t match with corresponding names in the registry.
Great so far....but we want a more pro-active fix, so I've created a Software Update Deployment in SCCM for this update (which fortunately is available as a regular Software Update from MS). Now the 'blurb' on this update states that "The System Update Readiness Tool (KB947821) is offered, only when there is a problem that the tool could resolve.”
And sure enough, SCCM reports only a small number of machines 'requiring' this update and shows the machines that already installed this update from MS as status "Installed". So presumably there are some installable rules at work here, for the update to know which machines may have problems with their Windows Service Packages. Despite this, there seems to be no way of forcing the delivery of this update to a test machine. I've tried to replicate the issues that we've seen on other machines and sat patiently to see if SCCM updates and picks up the test machine, but no joy.
Also, once you install this update from MS, you can't remove it. It's not installed in the regular way, with a listing in "Installed Updates" and any attempts to remove the KB via MSIEXEC and WUSA result in messages which state that KB947821 is not installed on the machine. Yet a machine that has run the update in the past will report "Installed" against SCCM.
The Update does stick an entry in the registry when installed, under:
HKLM>Software>Microsoft>Windows>CurrentVersion>Component Based Servicing>ApplicationEvaluationCache>Package_for_KB947821~31bf3856ad364e35~x86~~6.1.1.0
I've tried deleting this and then breaking one of the Service Packages (by deleting it or renaming it) to see if SCCM re-evaluates the need for the update, but nowt.
Trust your work , do not trust your company. Love your work , do not love company.
Since a few days, I get errors when synchronizing SCCM with the WSUS server. In wsyncmgr.log following errors appear:
*** [42000][701][Microsoft][ODBC SQL Server Driver][SQL Server]There is insufficient system memory to run this query. : sp_SetupSDMPackage
For this error, I tried the suggested solution in http://social.technet.microsoft.com/Forums/en-US/configmgrsum/thread/e45e72f5-cf1b-4089-8522-c686562bce95 but the server max mem has already it's maximum value
Next error is:
Failed to sync update 1847ae6d-8360-4e5a-9d15-da82b24deffd. Error: Failed to create SDM package Site_C4C56584-A6AC-4E0F-85E3-AF1ED3C1C96F/SUM_1fd4eb6d-808f-4693-bf9a-425fdc345c9a(2). CSDMTypeSource error: -1. Source: Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.UpdatesManager.UpdatesManagerClass.DefineUpdate
I haven't found anything related to this error yet.
These 2 error messages appear for 5 updates and the the synchronization fails because of too many consecutive failures.
I'm struggling a few days with these errors, any suggestions on how to resolve this?
Thanks!
Pieter-Jan
Hello!
I have SCCM 2007 SP2 R2 and trying to setup the Software Update Point!.
The weird thing is that the computers finds updates that is not deployed or not even downloaded and tries to install them but the fail with the error code: 80242006.
See Pic:
http://img51.imageshack.us/img51/3180/errorjo.jpg
Some of those updates in the picture actually are downloaded and deployed but many of them are not.
"Computer Configuration --> Administrative Templates --> Windows Update --> Specify Intranet Microsoft Update Service Location" is pointing to our SCCM.
"Install Software Uppdates" in Task Sequance are disable.
The Update package is distrubuted to all DPs
Why does my computer find updates that is not is deployed or downloaded and why does it fail to install those that are?
Where do i start the troubleshoot?
// Clint eastwood!
I think maybe I'm doing something wrong. I am using the SCCM Software Update to install updates on clients. Everything seems to be working correctly, but the clients are not running the updates I push. I looked in windows\system32\ccm\cache and the update files are there, but they are not being executed. Can I assume SCCM starts the exe files on the clients or does another process start the execution of the files? Did I forget to check a box in my setup some place? I have been thru the guides several times and performed all the proper steps. I can't seem to find any troubleshooting info on this particular issue. Do any of you folks out there have any suggestions I can look at to resolve this issue. Thank you in advance.
Bob Royce
Anyone had issues with Microsoft Windows Malicious Software Removal Tool (MSRT) taking a long time to install in the last couple of months?
I manage patching for about 2000 computer in SCCM 2007 and in the last couple of months have notice the MSRT taking more then an hour on some computers.
For example here are the log for one of my test computers for the last few months:-
Microsoft Windows Malicious Software Removal Tool v5.14, July 2014 (build 5.14.10402.0) Started On Thu Jul 10 16:05:06 2014 Engine: 1.1.10701.0 Signatures: 1.177.949.0 Results Summary: ---------------- No infection found. Microsoft Windows Malicious Software Removal Tool Finished On Thu Jul 10 16:10:10 2014 Return code: 0 (0x0) --------------------------------------------------------------------------------------- Microsoft Windows Malicious Software Removal Tool v5.15, August 2014 (build 5.15.10500.0) Started On Thu Aug 14 15:08:04 2014 Engine: 1.1.10802.0 Signatures: 1.179.1796.0 Results Summary: ---------------- No infection found. Microsoft Windows Malicious Software Removal Tool Finished On Thu Aug 14 15:12:26 2014 Return code: 0 (0x0) --------------------------------------------------------------------------------------- Microsoft Windows Malicious Software Removal Tool v5.16, September 2014 (build 5.16.10602.0) Started On Thu Sep 11 15:45:22 2014 Engine: 1.1.10904.0 Signatures: 1.183.882.0 Results Summary: ---------------- No infection found. Microsoft Windows Malicious Software Removal Tool Finished On Thu Sep 11 17:20:06 2014 Return code: 0 (0x0) --------------------------------------------------------------------------------------- Microsoft Windows Malicious Software Removal Tool v5.17, October 2014 (build 5.17.10700.0) Started On Fri Oct 17 16:25:49 2014 Engine: 1.1.11005.0 Signatures: 1.185.2035.0 Results Summary: ---------------- No infection found. Microsoft Windows Malicious Software Removal Tool Finished On Fri Oct 17 18:14:29 2014 Return code: 0 (0x0)
July and Aug both take less than 5min, Sept and Oct take longer than 90min.
In all 4 cases the MSRT is being installed by normal SCCM patching process.
I understand that MSRT has a quick scan mode and a full scan mode I'm just concerned about what has caused it to switch to full scan mode only on some computers.
