CCMSETUP not updating on SCCM 2012 SP1 CU3/CU4 primary site

I have a SCCM 2012 SP1 CU3 primary site and i can't upgrade the local installed SCCM Client.
The error I get in ccmsetup.log is:
<![LOG[MSI: Setup was unable to register the CCM_Service_HostingConfiguration endpoint
The error code is 80041002]LOG]!><time="15:44:22.408-60" date="02-08-2014" component="ccmsetup" context="" type="3" thread="2496" file="msiutil.cpp:300">
<![LOG[MSI: Action 15:44:22: Rollback. Rolling back action:]LOG]!><time="15:44:22.562-60" date="02-08-2014" component="ccmsetup" context="" type="0" thread="2496" file="msiutil.cpp:314">
<![LOG[File C:\windows\ccmsetup\{59A0EA77-D28C-4286-83A6-04BB57B9CDD6}\client.msi installation failed. Error text: ExitCode: 1603
Action: CcmRegisterHostingConfiguration.
ErrorMessages:
Setup was unable to register the CCM_Service_HostingConfiguration endpoint
The error code is 80041002
]LOG]!><time="15:45:00.798-60" date="02-08-2014" component="ccmsetup" context="" type="3" thread="2496" file="msiutil.cpp:872">
<![LOG[Client installation has failed too many times. Ccmsetup will now abort.]LOG]!><time="15:45:00.830-60" date="02-08-2014" component="ccmsetup" context="" type="3" thread="2496" file="ccmsetup.cpp:7941">
<![LOG[Successfully deleted the ccmsetup service]LOG]!><time="15:45:05.831-60" date="02-08-2014" component="ccmsetup" context="" type="1" thread="2496" file="ccmsetup.cpp:3320">
<![LOG[InstallFromManifest failed 0x80070643]LOG]!><time="15:45:05.831-60" date="02-08-2014" component="ccmsetup" context="" type="3" thread="2496" file="ccmsetup.cpp:7086">
<![LOG[CcmSetup failed with error code 0x80070643]LOG]!><time="15:45:05.832-60" date="02-08-2014" component="ccmsetup" context="" type="1" thread="2324" file="ccmsetup.cpp:10544">
I have this on my primary and secondary servers as well.
Is upgrading to R2 recommended and will that solve this issue ?
When googling to this issue i found that there is a solution for this: remove MP, upgrade Client, install MP.
But this is my primary and secondary and on secondary i am not allowed to remove the MP. It is hardcoded enabled.

Try the following steps to specify the hotfix when installing the client.
1. Open an elevated command prompt.
2. Run a command line similar to the following – if CU3 has already been installed, the MSP file below should be on the site server, in the
\\servername\SMS_SITE\Client\hotfix folder:
\ccmsetup.exe PATCH=\Configmgr2012ac-sp1-kb2882125-x64.msp
Juke Chou
TechNet Community Support

Similar Messages

New SCCM 2012 client machines still getting SCCM 2012 SP1 client not the new SCCM 2012 SP1 CU3 client

Hi,
I've successfully (as far as I can tell) deployed SCCM 2012 SP1 CU3 and all my existing clients are showing a client version of 5.00.7804.1400. But when I setup a new client system recently I noticed that the client version was showing 5.00.7804.1000,
and not 5.00.7804.1400.
For new client systems, do I need to redeploy the packages that were created for SCCM 2012 SP1 CU3 so that the new systems get the new SCCM 2012 SP1 CU3 client?
Thanks,
Nick

Hi,
Here's some good information to look over:
http://sccmfaq.wordpress.com/2013/09/24/sccm-2012-include-cu-in-osd/
I haven't followed these instructions myself, since I haven't really had any good reason to include CUs during the initial installation process. I use this method instead and I've never run into any problems:
http://www.ronnipedersen.com/2013/06/installing-sccm-2012-sp1-cu2-quick-start-guide/
Don't retire TechNet! -
(Don't give up yet - 12,575+ strong and growing)

Office 2013 Professional Plus - 32 bit Deployment takes an unacceptable time to deploy in SCCM 2012 - SP1 CU3

We recently migrated over to SCCM 2012 SP1 - CU3 the first of the year from SCCM 2007 SP2. We have used SCCM in the past to deploy Office 2010 and had deployed Office 2013 to our IT Dept. before moving over to SCCM 2012. The deployment went as
expected. Now that we are ready to start deploying Office 2013 to our corporate workstations, the deployment time is running 4.5 hours to 5.5 hours from the local site server DP. I am afraid to find out what time we are looking at for remote DP's.
The three factors that are different is that our SCCM site server is virtual, it is running 2012 for the OS, and obviously SCCM 2012-SP1 - CU3. We are using the same package source files. Previous to a successful deployment we were
seeing hash mismatch errors which MS support pointed us to the nic driver on the VM was using E1000E and to change it to a VMX something driver.
So I guess my question is anyone else out there deploying Office 2013 ProPlus - 32 bit from this type of environment? Our previous deployment time for office was a little over an hour (not five hours). Any suggestions where to look to improve
the deployment time?
I am expected to deploy this in one week and have been working on these issues for weeks.

I see now that you are using a combination of scripts and ConfigMgr package/program.
The AppEnforce.log file is for use with the new ConfigMgr Application model.
Is there any reason that you don't use the new model for deploying Office 2013? It's a single step process and perfect for it. If you use the Office Customisation Tool you can customise what you like. The process will then uninstall Office 2010 and install
Office 2013.
This is how you do it
http://www.gerryhampsoncm.blogspot.ie/2013/03/sccm-2012-sp1-step-by-step-guide-part_9368.html
Gerry Hampson | Blog:
www.gerryhampsoncm.blogspot.ie | LinkedIn:
Gerry Hampson | Twitter:
@gerryhampson

Deploy Java Updates using SCCM 2012 SP1 and SCUP 2011

What is the best way to deploy Java updates using sccm 2012 SP1 and SCUP 2011?

I didn´t find Kent´s blog useful when talking about Java. I can deploy Adobe products fine, but I have to import Java manually because not having Shavlik certificate. So with that said, I have the fallowing problem;
I have full offline installer unpacked, .msi file and Data1.cab. When I´m importing these binaries to SCUP, I only can point to .msi. Doing that, installation fails in client side fails because of lack of data1.cab fine, which is the main file.
Should I use some other downloaded files of Java? I couldn´t find any Java-update-file only type of files to download.

SCCM 2012 Sp1 CU3 support Windows 2012 R2 deployment?

Hi,
Sorry for so basic question, but I have read few docuemnts, blogs and official materials and I'm a bit confused.
In our organization we have SCCM Sp1 CU3. We are planning create and next deploy Windows 2012R2 Server images. On some documentations there is CU3 supports only application managment, inventory and so on. but there is nothing about image deployment.
So, my question is - I have to upgrade SCCM 2012 Sp1 CU3 to SCCM2012R2 to capture, build and deploy Windows 2012R2 system?
Thank you.

Yes, you do. See what's new with ConfigMgr 2012 R2
http://technet.microsoft.com/en-us/library/dn236351.aspx
Gerry Hampson | Blog:
www.gerryhampsoncm.blogspot.ie | LinkedIn:
Gerry Hampson | Twitter:
@gerryhampson

Software Update error - SCCM 2012 SP1

HI,
I have SCCM 2012 SP1 installed on Windows server 2008 R2 server. I have configured SUP role and tried sync from sccm console. I get the below error.
LOg:
WSUS sync running~ $$<SMS_WSUS_CONFIGURATION_MANAGER><01-30-2014 14:11:42.047+00><thread=3840 (0xF00)>
WSUS sync running~ $$<SMS_WSUS_CONFIGURATION_MANAGER><01-30-2014 14:12:42.255+00><thread=3840 (0xF00)>
Microsoft.SystemsManagementServer.WSUS.WSUSMSPException: WSUS sync failed with UssCommunicationError: ~~ at Microsoft.SystemsManagementServer.WSUS.WSUSServer.IsSyncRunning() $$<SMS_WSUS_CONFIGURATION_MANAGER><01-30-2014 14:13:12.462+00><thread=3840
(0xF00)>
Done using DEVSWAD\SWDTR-SRV-CMPATCH credentials~ $$<SMS_WSUS_CONFIGURATION_MANAGER><01-30-2014 14:13:12.478+00><thread=3840 (0xF00)>
Failed to set Subscriptions on the WSUS
. Error:(-2146233088)Unknown error 0x80131500~ $$<SMS_WSUS_CONFIGURATION_MANAGER><01-30-2014 14:13:12.478+00><thread=3840 (0xF00)>
STATMSG: ID=6603 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_CONFIGURATION_MANAGER" SYS=DCMPSTPV01.devswad.net SITE=SCW PID=2764 TID=3840 GMTDATE=Thu Jan 30 14:13:12.479 2014
I have configured proper proxy account which can connect to microsoft website and the port i have configured in proxy to allow is
80 and 443. I feel the port i need to allow may be i am not sure 8530 and 8531. Or 80 and 443 is fine. Please help
Regards, Pratap

It says to check WCM.log which i posted above
wsync log:
Sync failed: WSUS update source not found on site SCW. Please refer to WCM.log for configuration error details.. Source: getSiteUpdateSource $$<SMS_WSUS_SYNC_MANAGER><01-31-2014 14:02:14.118+00><thread=4388 (0x1124)>
STATMSG: ID=6703 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=DCMPSTPV01.devswad.net SITE=SCW PID=2764 TID=4388 GMTDATE=Fri Jan 31 14:02:14.119 2014 ISTR0="getSiteUpdateSource" ISTR1="WSUS update source not found on site SCW. Please
refer to WCM.log for configuration error details." ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 $$<SMS_WSUS_SYNC_MANAGER><01-31-2014 14:02:14.122+00><thread=4388 (0x1124)>
Sync failed. Will retry in 60 minutes $$<SMS_WSUS_SYNC_MANAGER><01-31-2014 14:02:14.122+00><thread=4388 (0x1124)>
Setting sync alert to active state on site SCW $$<SMS_WSUS_SYNC_MANAGER><01-31-2014 14:02:14.123+00><thread=4388 (0x1124)>
Sync time: 0d00h00m00s $$<SMS_WSUS_SYNC_MANAGER><01-31-2014 14:02:14.132+00><thread=4388 (0x1124)>
Wakeup for a polling cycle $$<SMS_WSUS_SYNC_MANAGER><01-31-2014 15:02:14.495+00><thread=4388 (0x1124)>
Starting Sync $$<SMS_WSUS_SYNC_MANAGER><01-31-2014 15:02:15.157+00><thread=4388 (0x1124)>
Performing sync on retry schedule $$<SMS_WSUS_SYNC_MANAGER><01-31-2014 15:02:15.163+00><thread=4388 (0x1124)>
Read SUPs from SCF for DCMPSTPV01.devswad.net $$<SMS_WSUS_SYNC_MANAGER><01-31-2014 15:02:15.577+00><thread=4388 (0x1124)>
Found 1 SUPs $$<SMS_WSUS_SYNC_MANAGER><01-31-2014 15:02:15.830+00><thread=4388 (0x1124)>
Found active SUP DCMPSTPV01.devswad.net from SCF File.~ $$<SMS_WSUS_SYNC_MANAGER><01-31-2014 15:02:15.833+00><thread=4388 (0x1124)>
Sync failed: WSUS update source not found on site SCW. Please refer to WCM.log for configuration error details.. Source: getSiteUpdateSource $$<SMS_WSUS_SYNC_MANAGER><01-31-2014 15:02:15.876+00><thread=4388 (0x1124)>
STATMSG: ID=6703 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=DCMPSTPV01.devswad.net SITE=SCW PID=2764 TID=4388 GMTDATE=Fri Jan 31 15:02:15.882 2014 ISTR0="getSiteUpdateSource" ISTR1="WSUS update source not found on site SCW. Please refer
to WCM.log for configuration error details." ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 $$<SMS_WSUS_SYNC_MANAGER><01-31-2014 15:02:15.892+00><thread=4388 (0x1124)>
Sync failed. Will retry in 60 minutes $$<SMS_WSUS_SYNC_MANAGER><01-31-2014 15:02:15.912+00><thread=4388 (0x1124)>
Setting sync alert to active state on site SCW $$<SMS_WSUS_SYNC_MANAGER><01-31-2014 15:02:15.915+00><thread=4388 (0x1124)>
Sync time: 0d00h00m01s $$<SMS_WSUS_SYNC_MANAGER><01-31-2014 15:02:17.024+00><thread=4388 (0x1124)>
Next scheduled sync is a retry sync at 31/01/2014 16:02:15 $$<SMS_WSUS_SYNC_MANAGER><01-31-2014 15:02:17.151+00><thread=4388 (0x1124)>
Regards, Pratap

SCCM 2012 SP1 CU3 - Client Install on SiteServer (PrimarySite)

We have an issue with SCCM 2012 Client deployment on our primary site all other clients are installing correctly the error is attached.
I have tried various ways to install client push even tried the SP1 Client using ccmsetup /source and this also fails at the same point.
I have done self service google and discovered this
http://www.mail-archive.com/[email protected]/msg03811.html
Anyone any ideas????

80041002=
Not found
Source: Windows Management (WMI)
Also, 1603 is a MSI exit code meaning fatal error occurred.
Have you verified you are running the SP1 sccm client and not RTM on the machine is question?
Justin Chalfant | My Blog |
LinkedIn | Please mark as helpful/answer if this resolved your post
Thanks, we have checked the error codes.
We have tested the client install onto the primary server in three different sites, on different networks/labs/environments with the same result.
Yes we have verified we are running SP1 CU3 and that the client files are the correct versions.
To eliminate the probable cause of CU3 updates being at fault, we have obtained the Client folder from the SP1 ISO (the later released updated SP1 ISO), with the exact same error.

Some of the machines are not installing windows updates in SCCM 2012 SP1

I have deployed the current month patches to the machines. But, some of the machines are failed to install.
Most commonly I am getting the below errors in windowsupdate.log ,
Report REPORT EVENT: {811D3FE5-A254-4C7E-B7F1-6132320AD5E0}
2015-02-23 08:18:40:851-0000 1
148 101
{00000000-0000-0000-0000-000000000000}
0 80072ee2
CcmExec Failure
Software Synchronization Windows Update Client failed to detect with error 0x80072ee2.
::OnScanComplete -Scan Failed with Error=0x80072f78
How to resolve this issue with installing windows updates?
0x80072ee2 looks like time out error.

I have uploaded the log file on dropbox
https://www.dropbox.com/s/bt09vpyhab56dgs/WindowsUpdate%20log.txt?dl=0
I am going to check WSUS IIS log file. I will keep you posted with my findings.
I dont know how to confirm whether the client is talking with wsus server or not. But, I could see some more errors in softwareupdates related logs,
Below is the error in updatestore.log,
Failed to refresh Resync state message. Error = 0x87d00310.
Below are the errors in update deployment.log,
Job error (0x80072ee2) received for assignment ({1566B12B-1731-479D-BFD1-98F2D24346B2}) action - Update Deployment
Job error (0x80072ee2) received for assignment ({1566B12B-1731-479D-BFD1-98F2D24346B2}) action
Updates will not be made available

SCCM 2012 SP1 CU4 ccmsetup runs with SMS Agent Host on the "Service" mmc after upgrading the client to CU4.

Dear Brothers,
I have an issue with two (2) of my Site Servers, I have below scenarioa and explained issue details:
Scenario:
1. Server1: Windows 2012 Server, CAS, SCCM 2012 Hierarchy Roles: Management Point, DP, SUP, Component Server.
2. Server2: Windows 2008 R2 Server, Secondary Site Role, SCCM 2012 Hierarchy Roles: Management Point, DP, Component Server.
Issue:
After updating the SCCM 2012 Client to CU4 on the actual Site Server, the "ccmsetup" appears also with "SMS Agent Host"
at the Service MMC. Which I believed this is very unusual behavior.
The Client however it seems properly installed and working please see below details:
Questions: I believed the Client installations are still running on the background, even though the Client tends to look working on the Control Panel.
1. How can I resolved this issue?
2. Should I need to perform a total Client uninstallation, even depth till removing entries in the Registry levels?
3. Or this is a normal behavior for the scenario?
Advance thanks for your future replies, my brothers in technology.

Dear Brother,
2 Weeks since I installed the CU4, it seems a little bit to long isn't it? for both the ccmsetup and the SMS Host Agent Services to exist, for the errors on the ccmsetup.log there are some errors after uninstallation since I am trying to removed
the issue .
CCMsetup.log
==========[ ccmsetup started in process 5376 ]========== 7/1/2014 7:14:45 PM 4104 (0x1008)
Running on platform X64 7/1/2014 7:14:45 PM 4104 (0x1008)
Updated security on object C:\Windows\ccmsetup\cache\. 7/1/2014 7:14:45 PM 4104 (0x1008)
Launch from folder C:\Windows\ccmsetup\ 7/1/2014 7:14:45 PM 4104 (0x1008)
CcmSetup version: 5.0.7804.1500 7/1/2014 7:14:45 PM 4104 (0x1008)
Running on OS (6.2.9200). Service Pack (0.0). SuiteMask = 272. Product Type = 3 7/1/2014 7:14:45 PM 4104 (0x1008)
Ccmsetup command line: ccmsetup.exe /uninstall 7/1/2014 7:14:45 PM 4104 (0x1008)
Command line parameters for ccmsetup have been specified. No registry lookup for command line parameters is required. 7/1/2014 7:14:45 PM 4104 (0x1008)
Command line: ccmsetup.exe /uninstall 7/1/2014 7:14:45 PM 4104 (0x1008)
SslState value: 224 7/1/2014 7:14:45 PM 4104 (0x1008)
Detected client version 5.00.7804.1500 from WMI. 7/1/2014 7:14:45 PM 4104 (0x1008)
Updated security on object C:\Windows\ccmsetup\. 7/1/2014 7:14:45 PM 4104 (0x1008)
Another instance of ccmsetup is already running. 7/1/2014 7:14:45 PM 4104 (0x1008)
Task 'Configuration Manager Client Upgrade Task' does not exist 7/1/2014 7:14:45 PM 4104 (0x1008)
CcmSetup is exiting with return code 3 7/1/2014 7:14:45 PM 4104 (0x1008)
MSI: Action 19:15:20: SmsRemoveUIEvents. This custom action is no longer used. The custom action used to remove the COM+ event subscriber and publisher used for UI notifications. We no longer use COM+ events for UI notifications. 7/1/2014 7:15:20 PM 5628
(0x15FC)
MSI: Action 19:15:20: CcmUnregisterPerfCounters. Removes performance counters gathered in the CcmUnregisterPerfCountersInit action 7/1/2014 7:15:20 PM 5628 (0x15FC)
MSI: Action 19:15:20: CcmRemoveLanternDocuments. Removing documents from Microsoft Policy Platform that have been submitted by Configuration Manager authority. 7/1/2014 7:15:20 PM 5628 (0x15FC)
MSI: Action 19:15:30: CcmTypelibRollback. In the event of install failing, this event rolls back the type libraries to the state before install started. 7/1/2014 7:15:30 PM 5628 (0x15FC)
MSI: Action 19:15:30: SmsDeinstallDesktopClient. This custom action uninstalls the desktop client with following steps-
1. Makes sure there are no desktop client installations in progress and prevents any new instance of intallation.
2. Checks the desktop client version and gets the installation direcotry.
3. Stops remote control and other desktop components.
4. Kills the following client processes - clisvc1.exe, pea32.exe, smsapm32.exe, smsmon32.exe and sms_reen.exe.
5. Saves information needed for migration and uninstalls the desktop components followed by clean up. 7/1/2014 7:15:30 PM 5628 (0x15FC)
MSI: Action 19:15:30: CcmDetectFilesInUseRollback. Rolls back files moved by CcmDetectFilesInUse. 7/1/2014 7:15:30 PM 5628 (0x15FC)
MSI: Action 19:15:30: CcmDetectFilesInUse. Moves files that are in use so that they will be deleted upon the next reboot. 7/1/2014 7:15:30 PM 5628 (0x15FC)
MSI: Action 19:15:31: CcmDetectFilesInUseCommit. Commits action of CcmDetectFileInUse. After this we cannot rollback. 7/1/2014 7:15:31 PM 5628 (0x15FC)
MSI: Action 19:15:31: InstallFiles. Copying new files 7/1/2014 7:15:31 PM 5628 (0x15FC)
MSI: Internal Error 2902. ixfAssemblyCopy 7/1/2014 7:15:32 PM 5628 (0x15FC)
MSI: Action 19:15:32: Rollback. Rolling back action: 7/1/2014 7:15:32 PM 5628 (0x15FC)
File C:\Windows\ccmsetup\configmgr2012ac-sp1-kb2882125-x64.msp installation failed. Error text: ExitCode: 1603
Action: InstallFiles.
ErrorMessages:
Internal Error 2902. ixfAssemblyCopy
7/1/2014 7:15:33 PM 5628 (0x15FC)
A Fallback Status Point has not been specified. Message with STATEID='301' will not be sent. 7/1/2014 7:15:33 PM 5628 (0x15FC)
Deleted file C:\Windows\ccmsetup\ccmsetup.xml 7/1/2014 7:15:33 PM 5628 (0x15FC)
Deleted file C:\Windows\ccmsetup\client.msi 7/1/2014 7:15:33 PM 5628 (0x15FC)
CcmSetup failed with error code 0x80070643 7/1/2014 7:15:33 PM 5628 (0x15FC)
Regards,

Cannot install SCCM 2012 SP1 CU4

Hi,
I just tried to apply CU4 over one of my SCCM 2012 SP1 CU3 deployments and I receive the following message during the initial verification phase:
Server update status: This update applies to product version 5.0.7804. The installed version on this computer is 5.0.7958.1000. This update is not applicable to this computer.
Console update status: No serviceable configuration manager role was found on the local system.
If I engage the verification phase on this installation for CU2 and CU3 there is no problem at all, so this must be a CU4 package specific error.
Anybody experiencing the same behavior ?

The latest CU that I see for SCCM 2012 SP1 is SP1 Cumulative Update 3, are you sure you are working with the proper file? .
CU4 was released this week:
http://blogs.technet.com/b/configurationmgr/archive/2014/01/29/now-available-cumulative-update-4-for-system-center-2012-configuration-manager-service-pack-1.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!)

SCCM 2012 R2 CU3 UPGRADE BROKE REMOTE ADMIN CONSOLE CONNECTIVITY

I installed SCCM 2012 R2 CU3 on my site server but it broke a couple things. I've never had problems with SCCM upgrades before. The admin console works if you log into the site server and run it from there but not when you try it from anywhere else (another
server or a workstation). When you open the admin console on the site server it does have the new version of 5.00.7958.1401. Of the five suggestions that appear when your console won't connect, here's what I know:
1) the remote machines can all ping the site server (call it server 01)
2) we know it's not my account that's a problem as I can open the console on the site server itself
3) This problem happens on server 02, which I put the new admin console on. It also happens with other machines which still have the CU2 console
4) Yes, I'm an admin role, shown by logging into the console on the site server
5) I have another network where everything works. I have not put CU3 on it yet, of course. The WMI permissions on Root, Root\SMS, and Root\SMS\site_ABC are identical on both site servers yet it works on non-upgraded one and not on the upgraded one.
WMI info-I can WMI connect from the site server to these other machines but not WMI connect from the other machines to the site server: not root, SMS, or SMS\site_ABC, nor cimv2, even though the permissions match what is on the working network.
When I launch the console from the site server entries about loading the console loading ok are in SMSAdminUI.log, but when I try to launch the console from other machines no entries are made, even though I changed the SmsAdminSNapIN value to VERBOSE.
I checked DCOM permissions and they are the same on both networks.
Another issue that appeared with this upgrade: I can install the client upgrade to CU3 on other machines but on the site server it fails with "Internal Error 2503" and when you click OK it you get "Internal Error 2502".
Ben JohnsonWY

I'd suspected this WMI problem was only affecting our Server 2012 boxes. I compared RSOPs and noticed the ones having this problem were all under the same OU and getting few GPOs. Our GPO person found a GPO that has somehow become unlinked. He relinked
it. After a gpo update AND a reboot these machines start working again. So CU3 did not cause this WMI after all.
And yes, the CU2 consoles won't connect to a CU3 site server, you have to run the console upgrade.
I fixed the "internal error 2503/2502" by doing this: open task manager, click details, end the explorer task (screen will look blank at first). Click File and select "start new task", enter "explorer.exe' and click the run as admin
button. The msp for CU3 client installed and the screen looks normal again. I only saw this error on the site server and have never seen it before.
Ben JohnsonWY

Part of a migration project from SCCM 2007 to 2012 SP1 CU3 - Updates no longer working and reporting not correct

Been working on a migration from 2007 sp1 to 2012 sp1 cu3. I first installed directly to sp1 but realized we had a few 8.1 clients being built so I added the cu3 mid-stream. I moved over two small subnets and pushed out some clients.
I was able to push out updates from the 2012 server for OS realted updates to a collection. After CU3 I tried to do the same process with Office 2013 updates and it just seems to sit there with the enforcement state showing unknown in the report.
Also I checked the version of client on the machines and they have the CU3 version but when I run a report to show client versions it does not show these machines with the latest version but version for sp1. It's almost like my management point
is not working. (just guessing). I checked in the component status and everything is showing green. I tried a wbemtest on one of the clients in the collection for the targeted updates and that is coming back with acceptable results.
Not sure where to look next.
I am not real proficient in 2012 yet and still bumping my way along. Any help reviewing specific logs, etc. would be appreciated. I have been searching for a solotion for several days now.

Hi,
1.Please make sure the update deployment is show up on the Deployment tab(Assets and Compliance -> Overview -> Devices -> the specific client properties)
2.Check PolicyAgent.log on the client to see whether the specific client have received the deployment policy. If not, try to run the Actions about software updates on the Configuration Manager Properties from the client.
3.Examine UpdatesDeployment.log, UpdatesHandler.log. UpdatesStore.log on the client.
Best Regards,
Joyce Li
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

WSUS SP2; SCCM 2012 SP1; Sync failed: WSUS update source not found

Hi,
I have installed the Fresh SCCM 2012 SP1 and WSUS 3.0 SP2 + KB2720211 + KB2734608. However, still the Sync is getting failed. This is what I am getting in the wsyncmgr and WCM logs:
wsyncmgr:
Sync failed: WSUS update source not found on site PR1. Please refer to WCM.log for configuration error details.. Source: getSiteUpdateSource
SMS_WSUS_SYNC_MANAGER 1/9/2015 12:00:00 PM
3668 (0x0E54)
STATMSG: ID=6703 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=ABC.XYZ.net SITE=PR1 PID=2724 TID=3668 GMTDATE=Fri Jan 09 18:00:00.537 2015 ISTR0="getSiteUpdateSource" ISTR1="WSUS update source not found
on site PR1. Please refer to WCM.log for configuration error details." ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
SMS_WSUS_SYNC_MANAGER 1/9/2015 12:00:00 PM
3668 (0x0E54)
Sync failed. Will retry in 60 minutes SMS_WSUS_SYNC_MANAGER
1/9/2015 12:00:00 PM 3668 (0x0E54)
WCM:
Checking for supported version of WSUS (min WSUS 3.0 SP2 + KB2720211 + KB2734608)
SMS_WSUS_CONFIGURATION_MANAGER 1/9/2015 11:19:03 AM
4176 (0x1050)
Checking runtime v2.0.50727... SMS_WSUS_CONFIGURATION_MANAGER
1/9/2015 11:19:03 AM 4176 (0x1050)
Did not find supported version of assembly Microsoft.UpdateServices.Administration.
SMS_WSUS_CONFIGURATION_MANAGER 1/9/2015 11:19:03 AM
4176 (0x1050)
Checking runtime v4.0.30319... SMS_WSUS_CONFIGURATION_MANAGER
1/9/2015 11:19:03 AM 4176 (0x1050)
Did not find supported version of assembly Microsoft.UpdateServices.Administration.
SMS_WSUS_CONFIGURATION_MANAGER 1/9/2015 11:19:03 AM
4176 (0x1050)
Supported WSUS version not found SMS_WSUS_CONFIGURATION_MANAGER
1/9/2015 11:19:03 AM 4176 (0x1050)
STATMSG: ID=6607 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_CONFIGURATION_MANAGER" SYS=ABC.XYZ.net SITE=PR1 PID=2724 TID=4176 GMTDATE=Fri Jan 09 17:19:03.489 2015 ISTR0="DEF.XYZ.net" ISTR1="" ISTR2="" ISTR3=""
ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
SMS_WSUS_CONFIGURATION_MANAGER 1/9/2015 11:19:03 AM
4176 (0x1050)
Remote configuration failed on WSUS Server.
SMS_WSUS_CONFIGURATION_MANAGER 1/9/2015 11:19:03 AM
4176 (0x1050)
STATMSG: ID=6600 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_CONFIGURATION_MANAGER" SYS=ABC.XYZ.net SITE=PR1 PID=2724 TID=4176 GMTDATE=Fri Jan 09 17:19:03.515 2015 ISTR0="DEF.XYZ.net" ISTR1="" ISTR2="" ISTR3=""
ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
SMS_WSUS_CONFIGURATION_MANAGER 1/9/2015 11:19:03 AM
4176 (0x1050)
I have used the default port numbers 80 and 443 still the sync is failing. Please provide your advise to fix this issue.
Regards,
Malwinder

WCM:
Checking for supported version of WSUS (min WSUS 3.0 SP2 + KB2720211 + KB2734608)
It's not only a matter of installing the console, but also those hotfixes on a remote server ...
Torsten Meringer | http://www.mssccmfaq.de

SCCM 2012 SP1 Update to CU5 not showing version 1600 for clients updated !

Recently upgraded SCCM 2012 SP1 and its showing a version of 5.0.7804.1600 as it should be. Pushed out the CU 5 client manager update to few machines and they are also showing .1600 as the version, however in SCCM 2012 manager itself it is not updating the
status of those machines from say .1000 or .1400 to .1600. Why is this happening and any solution for it ? I have also updated the CM on the server hosting the SCCM and is current to .1600 version.

Because the client agent version is returned from clients via heartbeat discovery which only occurs by default every 7 days. Thus, you need to be patient. Note that I generally recommend reducing the heartbeat cycle to at least once a day partly for
this reason.
Jason | http://blog.configmgrftw.com | @jasonsandys

Windows Updates are not getting download after installation of SCCM 2012 SP1

I have installed SCCM 2012 SP1 step by step as per microsoft documents, Now I am getting error while downloading windows updates from microsoft site.
Error by WCM.log : System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a send. ---> 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
Error By wsyncmgr: DB Server not detected for SUP XYZ.com from SCF File. skipping.
Sync failed: WSUS update source not found on site KSL. Please refer to WCM.log for configuration error details.. Source: getSiteUpdateSource
STATMSG: ID=6703 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=KSL-MUM-SCCM01.KSEC.KotakGroup.com SITE=KSL PID=3688 TID=4752 GMTDATE=Tue May 21 10:59:06.745 2013 ISTR0="getSiteUpdateSource" ISTR1="WSUS
update source not found on site KSL. Please refer to WCM.log for configuration error details." ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
I have reinstall my SUP on site server, i have my WSUS & site server is on same server. I have kept my sup setting as per requirment (8530 & 8531)
Kindly suggest is any other settings need to be done on server side.

Yes, I know this is an old post, but I’m trying to clean them up. Did you solve this problem, if so what was the solution?
From your log snip-it, it looks like the firewall is causing your problem. Temporary turn off the firewall and see if that solves your problem.
Garth Jones | My blogs: Enhansoft and
Old Blog site | Twitter:
@GarthMJ

CCMSETUP not updating on SCCM 2012 SP1 CU3/CU4 primary site

Similar Messages

Maybe you are looking for