SCCM 2012 R2 CU4 - WSUS Sync issues

*EDIT/Update*
I had incorrectly diagnosed this as an issue with CU4. The issue was in fact between Microsoft and WSUS.
The method listed in this thread ended up working for me.
Here is an official KB article for the issue: https://support.microsoft.com/en-us/kb/3058255?wa=wsignin1.0
(I have a small environment - only 1 SCCM server [primary] and 200 servers managed)
I upgraded from CU3 to CU4 last week and I cannot get my WSUS to sync all of the updates for April 2015. I also upgraded my test server and it is syncing fine.
I did some digging yesterday and found out that even tho the site server upgraded (I only have one SCCM server), the SQL update failed because I did not have proper permissions. I've since had a DBA run the update.sql file included with the CU (found at:
%Program Files%\Microsoft Configuration Manager\hotfix\KB3026739)
I restarted my SCCM server again this morning and tried running multiple syncs with Microsoft and it is still pulling in nothing. 
I am not getting any errors in WSUS, wsyncmgr.log, WCM.log, or the change.log for wsus. Everything just looks like it attempted to sync - found nothing - then ended the sync successfully.
I had one of the networking guys look at the firewall and he says its getting thru and establishing a connection - but it looks like MS is terminating the connection? I cannot see anything that would indicate this in my logs. Here is what he sent me: http://i.imgur.com/znOvxEN.jpg
Now, to make things even more interesting. In the many many attempts I have made over to the last two days to get SCCM/WSUS to sync April's updates, it has worked in small amounts.... it once expired 16 updates and another time pulled in 2 updates released
on 4/15/15 (but only 2!). I have my sync settings set up exactly like my test server which, again, is working fine. 
As always, any help is appreciated!

sounds like there might be a bigger issue with WSUS and Microsoft?
https://social.technet.microsoft.com/Forums/en-US/6dbe893b-39f5-4367-902d-678a2a897b9b/wsus-not-syncronizing-aprils-updates?forum=configmanagersecurity
https://social.technet.microsoft.com/Forums/en-US/a323d2f9-a1ac-48e3-978a-054915c3f1ea/wsus-april-2015-updates-not-synced-from-microsoft?forum=winserverwsus

Similar Messages

  • SMS Provider Locations Do Not Match - Problem installing SCCM 2012 R2 CU4

    I have an SCCM 2012R2 CU1 site that has been upgraded from SCCM 2012 non-SP1, so I have gone from 2012 to 2012SP1 through CU5 and then to R2 and then to CU1.
    Over the course of the life of this site, which has more than 10k clients and 10 Site Systems, we have installed roles, removed roles, moved roles and removed Site Systems.
    I have also installed and removed SMS providers . . . which is where my issues begin.
    The site properties in the console list 6 SMS Providers and even lists an SMS provider on a server that was retired and is no longer a Site System.  When I query WMI using the following VBS script it only returns the *ACTUAL* SMS Provider locations,
    2 of the 6 listed in the GUI.
    On Error Resume Next
    Const ForReading = 1, ForWriting = 2, ForAppending = 8
    strComputer = "." 
    Set oFS = CreateObject("Scripting.FileSystemObject")
    Set objWMIService = GetObject("winmgmts:\\" & strComputer & "\root\sms")
    If Err.Number <> 0 Then
    WScript.Echo "Cannot connect to WMI"
    WScript.Echo vbTab & "Error " & Err.Number & " - " & Err.Description
    End If
    Set oLog = oFS.OpenTextFile("C:\Temp\SMS_ProvList.log",ForAppending, True)
    If Err.Number <> 0 Then
    WScript.Echo "Could not create output file"
    WScript.Echo vbTab & "Error " & Err.Number & " - " & Err.Description
    End If
    Set colItems = objWMIService.ExecQuery("SELECT * FROM SMS_ProviderLocation",,48)
    count = 0
    For Each objItem in colItems
        count = count + 1
        oLog.WriteLine "-----------------------------------"
        oLog.WriteLine Now()
        oLog.WriteLine "Provider instance " & count &  " : " & objItem.Machine
        oLog.WriteLine "NamespacePath : " & objItem.NamespacePath     
        oLog.WriteLine ""
    Next
    I have a test environment which has also gone through some growth over its lifetime and has had the same changes to SMS Providers made.  When I first attempted to install SCCM 2012 R2 CU4 in this test environment the installer continually failed the
    prerequisite checker when querying the CU level of the SMS Providers.  The only way that I could get past that issue was by running a site maintenance task via the CM installer and installing an SMS Provider at the location that had previously been an
    SMS Provider but I had uninstalled that role.
    I do not want to have to do that in my production environment, and would not even be able to do so if I wanted as I have retired one of the servers listed and cannot re-provision that machine.
    Any CM12 gurus out there with suggestions?  This strikes me as a standard MS problem when having multiple development teams working on a product/update and not having a standard location to check for configuration information (This is exactly the problem
    when configuring DNS suffixes via GPO and not manually setting the GUI to match).
    Thanks!
    Josh Gerner
    Cornell University.

    The issue I have is that I cannot find the WMI class that holds the SMS Providers that are returned by the GUI.
    I actually engaged MS Premier for a SCCM 2012 RAAS about 2 years ago and that was when the discrepancy first reared it's head.  The support person that I worked with couldn't give me a way of cleaning those entries at that point which is when I started
    logging the locations to be sure that my maintenance task was really installing or removing the SMS Providers.
    Josh Gerner

  • After installing SCCM 2012 R2 CU4, I show a Distribution Point warning that won't clear.

    I recently installed SCCM 2012 R2 CU4 on a LAB environment, and nowhere is it more important to wait until all requisite site roles are reinstalled before doing anything else.
    I did, and still do, have an warning/ error on the Site components that shows up on one of the child primary sites after the CU4 installation.
    Distribution Manager has not tried to install IIS component of operating system to distribution point “[“Display=\\SCxxx\”]MSWNET:[“SMS_SITE=xxx”]\\xxx\”. You should install and configure IIS manually. Please ensure RDC is also enabled.
    IIS is installed, RDC is enabled, but I get this error. What could be the real issue?

    Hi,
    So you have tried to reinstall IIS conponents and DP?
    Have you checked the distmgr.log? Anything helpful?
    Best Regards,
    Joyce
    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 Subscriber Support, contact [email protected]

  • After SCCM 2012 R2 CU4 update Client won't report status message back

    We had SCCM 2012 R2 CU3, just updated it to CU4 (all site servers and clients) last week.
    Right after the clients received the CU4 update (no reboot), I saw these started popping up the event log:
    The ConfigMgr Client encountered a certificate for Management Point SCCM that could not be verified.
    I checked online and it has to do with trusted root key mismatch, but there was no site change. The only thing we did was upgrading from CU3 to CU4. 
    Right now the symptom is that all these clients do not report status messages back to the MP so we have no idea how our deployments would go.

    i am having what i think is a similar issue. i upgraded to CU4 and the only clients to report back in are my SCCM site server and my only DP server. no clients have reported in since. i checked a few clients and they did get the CU4 client update
    and installed it but they are not reporting back
    I have pretty much the same situation.
    A successfully upgrade to SCCM 2012 r2 cu4 on the primary site.
    Deployed the cu4 to a few computers which was successfully. Later I also deployed the cu4 to the primary site server and it turned out to be the only computer reporting back with the proper client version.
    There is no errors or warnings in the event logs which could explain this strange issue. As far as I can tell the clients is operational but they are just not reporting back with the proper client version. A quick look at the sccm client
    logs has also not revealed the root cause.
    Any ideas would be appreciated a lot.
    Per Dahl Christiansen

  • SCCM 2012 SP1 CU4 migrated DP shows package status "unknown"

    I have a SCCM 2012 SP1 CU4 environment and have shared SCCM 2007 distribution points.
    Today I migrated one of the DP's which seems to work well.
    However all my packages shows now the status "unknown" for this migrated DP.
    This is a problem which should be fixed in CU4 according to the CU4 description. But it is not :-(
    Any idea how to solve this ? R2 install ?

    Some additional information:
    I noticed that the package sources are still available at the "old" ditribution point share abd not on the new sccm 2012 distribution point share. When performing actions described in step 3 below the package becomes available on the distribution point
    share......then i guess i can remove the content from the "old" distribution point share ????
    I noticed that when a package got the status "unknown" for de migrated DP the following action fix the problem:
    --> i remove the DP from the package and immediately add it again, the package status becomes "Successful".....hummm....ok....maybe a script could be created for this
    I noticed that when a package got the status "unknown" and the package is also located on the "distribution point share" then following will fix the issue:
    --> edit the package and remove the migrated DP and remove the checkbox for string on the distribution point share. Then add the DP again, click Apply and then set the checkbox for storing on the distribution point share and Apply again. Then wait and package
    will become available Successful and the package will become available on the distribution point share
    But i have 800 packages and 50 to be migrated DP's.....this is not a solution....but what is ????
    Any help, ideas, tips, hints, recommendations ?
    My overal thoughts are that migrating of a SCCM 2007 DP is not really working at all !!!!!
    Or does someone has other experience with e.g. R2 installed ? If so then I will upgrade first...

  • Machines not Joining Domain SCCM 2012 R2 CU4

    SCCM 2012 R2 CU4
    Recent change CU1-4
    This was all working until recently. The SMSTS log shows no failures. The Netsetup.log has no entries. The Panther\setupact.log shows a few odd things " [msoobe.exe] Failed to open event to start up services [0x80070002]" but then appears
    to proceed fine.
    The account used for Domain join is not locked out. I have no log telling me why it is not working. I have refreshed the drivers on the DP just incase the NIC driver got corrupt, though it appears to be fine in device manager and works.
    I am just lost as I don't have any log that shows me any real failures and since SCCM passes the Domain Join off to the OS I don't know where else to look.

    Is this a duplicate of
    https://social.technet.microsoft.com/Forums/en-US/9122cebc-11b9-4f81-a5d7-3a14667f874c/smts-not-correct-showing-code-0-for-programs-while-none-get-installed-no-domain-join?forum=configmanagerosd#d5670eeb-55de-493c-abf1-eec9397d7081 ?
    Torsten Meringer | http://www.mssccmfaq.de

  • SCCM 2012 R2 WSUS Sync issues

    hi all.
    We have implemented SCCM 2012 R2 with remote SQL instance, since we don’t have internet in CM server, we have used WSUS from upstream DMZ server . When we try to Sync we are getting below error
    System.Security.SecurityException: Request for principal permission failed.~~  
    at Microsoft.UpdateServices.Administration.AdminProxy.CreateUpdateServer(Object[] args)~~  
    at Microsoft.SystemsManagementServer.WSUS.WSUSServer.ConnectToWSUSServer(String ServerName, Boolean UseSSL, Int32 PortNumber)~~The Zone of the assembly that failed was:~~MyComputer
    Failed to refresh categories from WSUS server
    Failed to set Subscriptions on the WSUS Server. Error:(-2147467259)Unspecified error
    Can anyone help me on this?

    I spot the word "proxy" in the error message. Make sure that the servers can communicate with each other without a proxy.
    Torsten Meringer | http://www.mssccmfaq.de

  • Upgrade from SCCM 2012 SP1 CU4 to R2 Fails - Unsupported Upgrade Path

    Hi everybody,
    I'm currently upgrading our SCCM infrastructure to SCCM 2012 R2 after have finished with the upgrade from SCCM 2012 RTM to SP1 CU4, thus far everything works fine, but when I try to update any
    of the site servers, whether CAS or Primary, I'm getting the following error message in the Prerequisites Check:
    I've gone through the system requirements and prerequisites over and over again and I can assure you that every possible update, supported OS, feature set, SQL Server, check list, etc,
    etc, have been followed as per the official documentation available, however I'm stuck in this point, and surely enough I haven't been able to find out a similar case.Additionally I'm adding
    the ConfigMgrPrereq log (the relevant portion of it) in case someone could kindly take a look at it.
    <04-25-2014 02:06:46> ******* Start Prerequisite checking. *******
    <04-25-2014 02:06:47> ********************************************
    <04-25-2014 02:07:00> INFO: Detected current installed build version [7711] for sitecode [BRA]. For Upgrade,
    minimum supported installed build version is [7804].
    <04-25-2014 02:07:00> INFPROSCCMCMS.usersad.everis.int;   
    Unsupported upgrade path;    Error;   
    Configuration Manager has detected that one or more sites in the hierarchy are installed with a version of Configuration Manager that is not supported for upgrade.
    <04-25-2014 02:07:00> INFO: This rule only apply to primary site, skip checking.
    <04-25-2014 02:07:00> INFPROSCCMCMS.usersad.everis.int;   
    Active Replica MP;    Passed
    <04-25-2014 02:07:00> INFO: This rule only applies to primary or secondary site in hierarchy, skip checking.
    <04-25-2014 02:07:00> INFPROSCCMCMS.usersad.everis.int;   
    Parent site replication status;    Passed
    <04-25-2014 02:07:00> <<<RuleCategory: Database Upgrade Requirements>>>
    <04-25-2014 02:07:00> <<<CategoryDesc: Checking the target ConfigMgr database is ready to upgrade...>>>
    <04-25-2014 02:07:00> ===== INFO: Prerequisite Type & Server: SQL:INFPROSCCMCDB.usersad.everis.int
    =====
    <04-25-2014 02:07:00> <<<RuleCategory: Access Permissions>>>
    <04-25-2014 02:07:00> <<<CategoryDesc: Checking access permissions...>>>
    <04-25-2014 02:07:00> INFPROSCCMCDB.usersad.everis.int;   
    SQL Server sysadmin rights;    Passed
    <04-25-2014 02:07:00> INFPROSCCMCDB.usersad.everis.int;    SQL Server sysadmin rights
    for reference site;    Passed
    <04-25-2014 02:07:00> INFO: CheckLocalSys is Admin of <INFPROSCCMCDB.usersad.everis.int>.
    <04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;   
    Site server computer account administrative rights;    Passed
    <04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;   
    SQL Server security mode;    Passed
    <04-25-2014 02:07:09> <<<RuleCategory: System Requirements>>>
    <04-25-2014 02:07:09> <<<CategoryDesc: Checking system requirements for ConfigMgr...>>>
    <04-25-2014 02:07:09> INFO: OS version:601, ServicePack:1.
    <04-25-2014 02:07:09> INFO: Target computer is a Windows server.
    <04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;   
    Unsupported site server operating system version for Setup;    Passed
    <04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;   
    Domain membership;    Passed
    <04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;   
    Pending system restart;    Passed
    <04-25-2014 02:07:09> <<<RuleCategory: Dependent Components>>>
    <04-25-2014 02:07:09> <<<CategoryDesc: Checking dependent components for ConfigMgr...>>>
    <04-25-2014 02:07:09> INFO: Return code:0, Major:10, Minor:50, BuildNum:4000
    <04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;   
    SQL Server version;    Passed
    <04-25-2014 02:07:09> INFO: Get Sql edition:Enterprise Edition.
    <04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;   
    SQL Server Edition;    Passed
    <04-25-2014 02:07:09> INFO: Checking Tcp is enabled to Static port, SQL Server:INFPROSCCMCDB.usersad.everis.int,
    Instance:.
    <04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;   
    SQL Server Tcp Port;    Passed
    <04-25-2014 02:07:09> INFO: Checking if SQL Server memory is limited.
    <04-25-2014 02:07:09> INFO: SQL Server memory is limited.
    <04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;   
    Configuration for SQL Server memory usage;    Passed
    <04-25-2014 02:07:09> INFO: Checking if SQL Server memory is configured to reserve minimum memory.
    <04-25-2014 02:07:09> INFO: Installing the central administration site or primary site, requires SQL
    Server to reserve a minimum of 8 gigabytes (GB) of memory.
    <04-25-2014 02:07:09> WARN: SQL Server minimum memory is 8000 MB.
    <04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;    SQL Server process memory allocation;   
    Warning;    Configuration Manager requires SQL Server to reserve a minimum of 8 gigabytes (GB) of memory for the central administration site and primary site and a minimum of 4 gigabytes (GB) for the secondary site. This memory is reserved by
    using the Minimum server memory setting under Server Memory Options and is configured by using SQL Server Management Studio. For more information about how to set a fixed amount of memory, see
    http://go.microsoft.com/fwlink/p/?LinkId=233759.
    <04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;   
    Case-insensitive collation on SQL Server;    Passed
    <04-25-2014 02:07:09> INFO: Check Machine FQDN: <INFPROSCCMCDB.usersad.everis.int>.
    <04-25-2014 02:07:09> INFO: getaddrinfo returned success.
    <04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;   
    Validate FQDN of SQL Server Computer;    Passed
    <04-25-2014 02:07:09> INFO:CheckSupportedFQDNFormat <INFPROSCCMCDB.usersad.everis.int>
    <04-25-2014 02:07:09> INFO: NetBIOS <INFPROSCCMCDB>
    <04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;   
    Primary FQDN;    Passed
    <04-25-2014 02:07:09> <<<RuleCategory: Site Upgrade Requirements>>>
    <04-25-2014 02:07:09> <<<CategoryDesc: Checking if the target ConfigMgr site is ready to upgrade...>>>
    <04-25-2014 02:07:09> <<<RuleCategory: Database Upgrade Requirements>>>
    <04-25-2014 02:07:09> <<<CategoryDesc: Checking the target ConfigMgr database is ready to upgrade...>>>
    <04-25-2014 02:07:09> ===== INFO: Prerequisite Type & Server: SDK:INFPROSCCMCMS.usersad.everis.int
    =====
    <04-25-2014 02:07:09> <<<RuleCategory: Access Permissions>>>
    <04-25-2014 02:07:09> <<<CategoryDesc: Checking access permissions...>>>
    <04-25-2014 02:07:09> INFO: The rule 'Administrative rights on site system' has been run on server 'INFPROSCCMCMS.usersad.everis.int',
    skipped.
    <04-25-2014 02:07:09> <<<RuleCategory: System Requirements>>>
    <04-25-2014 02:07:09> <<<CategoryDesc: Checking system requirements for ConfigMgr...>>>
    <04-25-2014 02:07:09> INFO: The rule 'Unsupported site server operating system version for Setup' has
    been run on server 'INFPROSCCMCMS.usersad.everis.int', skipped.
    <04-25-2014 02:07:09> INFO: The rule 'Domain membership' has been run on server 'INFPROSCCMCMS.usersad.everis.int',
    skipped.
    <04-25-2014 02:07:09> INFO: Windows Cluster not found on INFPROSCCMCMS.usersad.everis.int.
    <04-25-2014 02:07:10> INFPROSCCMCMS.usersad.everis.int;   
    Windows Failover Cluster;    Passed
    <04-25-2014 02:07:10> INFO: The rule 'Pending system restart' has been run on server 'INFPROSCCMCMS.usersad.everis.int',
    skipped.
    <04-25-2014 02:07:10> <<<RuleCategory: Dependent Components>>>
    <04-25-2014 02:07:10> <<<CategoryDesc: Checking dependent components for ConfigMgr...>>>
    <04-25-2014 02:07:10> INFPROSCCMCMS.usersad.everis.int;   
    Windows Deployment Tools installed;    Passed
    <04-25-2014 02:07:10> INFO: CheckAdkWinPeInstalled on INFPROSCCMCMS.usersad.everis.int.
    <04-25-2014 02:07:10> INFPROSCCMCMS.usersad.everis.int;    Windows Preinstallation Environment
    installed;    Passed
    <04-25-2014 02:07:10> INFPROSCCMCMS.usersad.everis.int;   
    SMS Provider machine has same domain as site server;    Passed
    <04-25-2014 02:07:10> <<<RuleCategory: Site Upgrade Requirements>>>
    <04-25-2014 02:07:10> <<<CategoryDesc: Checking if the target ConfigMgr site is ready to upgrade...>>>
    <04-25-2014 02:07:10> <<<RuleCategory: Database Upgrade Requirements>>>
    <04-25-2014 02:07:10> <<<CategoryDesc: Checking the target ConfigMgr database is ready to upgrade...>>>
    <04-25-2014 02:07:10> ***************************************************
    <04-25-2014 02:07:10> ******* Prerequisite checking is completed. *******
    <04-25-2014 02:07:10> ******************************************<04-25-2014 02:07:10> INFO: Updating
    Prerequisite checking result into the registry
    <04-25-2014 02:07:10> INFO: Connecting to INFPROSCCMCMS.usersad.everis.int registry
    <04-25-2014 02:07:10> INFO: Setting registry values
    If you wonder whether it might be related to this error:
    -2014 02:07:00> INFO: Detected current installed build version [7711] for sitecode [BRA]. For Upgrade, minimum supported installed build version is [7804].
    I confirm that this one site is a secondary one that's attached to a primary site and this log is from the CAS server, I managed to tall it and delete it from that site, but still appears listed
    on the CAS management console, any idea how to force the removal of a secondary site that's attached to a primary from the CAS site when it has been removed already from said primary?
    I've already tried the
    Preinst /DELSITE XXX  command but it only works when the site to remove it's attached to the local site and certainly not from a CAS
    Finally,  the version, build number and everything is correct, no idea what could be the problem, does anybody know a way to bypass this or force the re-evaluation of this rules, I've got
    the impression that it's being cached somehow.
    Any help would be highly appreciated,
    Thank you.
    Marcelo Estrada MCP-MCTS-MCITP-MCSA-MCSE

    Hello again everybody,
    I've finally managed to fix this up, in the end I had to delete those entries manually from the database as Garry suggested. After this was done the upgrade has gone through as expected with no further ado and has finalized already, now moving on to the
    primary sites.
    If anybody out there is facing the same issue, what I did was to delete those "stubborn" records executing the following statements over the CAS database:
    DELETE
    FROMServerDataWHERESiteCode='XXX'
    DELETE
    FROMSC_SiteDefinitionWHERESiteCode='XXX'
    And this is pretty much about it. I'd recommend to take a proper backup first though as best practice.
    Thank you all anyways for your answers and comments,
    Marcelo Estrada MCP-MCTS-MCITP-MCSA-MCSE

  • 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,

  • SCCM 2012 R2 CU4, how can we make sure clients without any CU upgrade will continue to communicate?

    Hi,
    We're about to upgrade the SCCM 2012 R2 server from CU1 to CU4. However no clients were ever upgraded (don't even have CU1). Is there any way(matrix or other) we can assure ourselves clients will keep on communicating (f.e. for SCCM R2 CU4, clients need at
    least to be at CU1)?
    Please advise.
    J.
    Jan Hoedt

    Go through each one and see for yourself. Note that they are cumulative so you only need to deploy the latest. CU4 contains all the others. The issues that are fixed are listed.
    CU4
    https://support.microsoft.com/en-us/kb/3026739?wa=wsignin1.0
    CU3
    https://support.microsoft.com/en-us/kb/2994331
    CU2
    https://support.microsoft.com/en-us/kb/2970177
    CU1
    https://support.microsoft.com/en-us/kb/2938441
    It's always better to use the latest version where possible.
    Gerry Hampson | Blog:
    www.gerryhampsoncm.blogspot.ie | LinkedIn:
    Gerry Hampson | Twitter:
    @gerryhampson

  • SCCM 2012 complains about WSUS version

    Our SCCM 2012SP1 cannot communicate with the newly installed WSUS 6.2.
    They're both on Server 2012.  Is there any special patch to install on WSUS 6.2 to get it to work?
    We've changed the default port to port 80/443.
    From WCM.log:
    Checking for supported version of WSUS (min WSUS 3.0 SP2 + KB2720211 + KB2734608)
    SMS_WSUS_CONFIGURATION_MANAGER 3/21/2013 10:26:31 AM
    680 (0x02A8)
    Checking runtime v2.0.50727... SMS_WSUS_CONFIGURATION_MANAGER
    3/21/2013 10:26:31 AM 680 (0x02A8)
    Did not find supported version of assembly Microsoft.UpdateServices.Administration.
    SMS_WSUS_CONFIGURATION_MANAGER 3/21/2013 10:26:31 AM
    680 (0x02A8)
    Checking runtime v4.0.30319... SMS_WSUS_CONFIGURATION_MANAGER
    3/21/2013 10:26:31 AM 680 (0x02A8)
    Did not find supported version of assembly Microsoft.UpdateServices.Administration.
    SMS_WSUS_CONFIGURATION_MANAGER 3/21/2013 10:26:31 AM
    680 (0x02A8)
    Supported WSUS version not found SMS_WSUS_CONFIGURATION_MANAGER
    3/21/2013 10:26:31 AM 680 (0x02A8)
    STATMSG: ID=6607 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_CONFIGURATION_MANAGER" SYS=XXX-SCENTER SITE=XXX PID=6496 TID=680 GMTDATE=Thu Mar 21 17:26:31.636 2013 ISTR0="XXX-WSUS" ISTR1="" ISTR2="" ISTR3=""
    ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
    SMS_WSUS_CONFIGURATION_MANAGER 3/21/2013 10:26:31 AM
    680 (0x02A8)

    After installing the admin console on site server, software updates in software library started to show up.  v(^.^)
    However, I am still getting error messages all over the place.
    I have not tried to uninstall/reinstall WSUS 6.2 yet; that would be the last thing I try.
    From SMS_WSUS_SYNC_MANAGER:
     WSUS Synchronization failed.
     Message: Failed to sync some of the updates.
     Source: Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WsusSyncAction.WSyncAction.SyncUpdates.
    This is from SMS_WSUS_CONTROL_MANAGER:
    WSUS Control Manager failed to configure proxy settings on WSUS Server "CTB-WSUS.CHINATRUST.CORP".
    Possible cause: WSUS Server version 3.0 SP2 or above is not installed or cannot be contacted.
    Solution: Verify that the WSUS Server version 3.0 SP2 or greater is installed. Verify that the IIS ports configured in the site are same as those configured on the WSUS IIS website.You can receive failure because proxy is set but proxy name is not specified
    or proxy server port is invalid.
    I confirmed that the SCCM default site and WSUS's Administration site are both using port 80.

  • Cannot publish Flash Updates Verification of file signature failed for file SCUP 2011, SCCM 2012 R2 and WSUS all on same Windows Server 2012 machine

    I am attempting to distribute Adobe Flash updates using SCUP 2011, SCCM 2012 R2, WSUS ver4 and Windows Server 2012.  Everything installs without error.  I have acquired a certificate for SCUP signing from the internal Enterprise CA.  I have
    verified the signing certificate has a 1024 bit key.  I have imported the certificate into the server's Trusted Publishers and Trusted Root CA stores for the computer.  When I attempt to publish a Flash update with Full content I receive the following
    error:
    2015-02-13 23:00:48.724 UTC Error Scup2011.21 Publisher.PublishPackage PublishPackage(): Operation Failed with Error: Verification of file signature failed for file:
    \\SCCM\UpdateServicesPackages\a2aa8ca4-3b96-4ad2-a508-67a6acbd78a4\3f82680a-9028-4048-ba53-85a4b4acfa12_1.cab
    I have redone the certificates three times with no luck.  I can import metadata, but any attempt to download content results in the verification error.
    TIA

    Hi Joyce,
    This is embarrassing, I used that very post as my guide when deploying my certificate templates, but failed to change the bit length to 2048.  Thank you for being my second set of eyes.
    I changed my certificate key bit length to 2048, deleted the old cert from all certificate stores, acquired the a new signing cert, verified the key length was 2048, exported the new cert to pfx and cer files, imported into my Trusted publishers
    and Trusted Root Authorities stores, reconfigured SCUP to use the new pfx file, rebooted the server and attempted to re-publish the updates with the following results:
    2015-02-16 13:35:44.006 UTC Error Scup2011.4 Publisher.PublishPackage PublishPackage(): Operation Failed with Error: Verification of file signature failed for file:
    \\SCCM\UpdateServicesPackages\a2aa8ca4-3b96-4ad2-a508-67a6acbd78a4\3f82680a-9028-4048-ba53-85a4b4acfa12_1.cab.
    Is there a chance this content was already created and signed with the old cert, so installing the new cert has no effect?  In ConfigMgr software updates I see 4 Flash updates, all marked Metadata Only (because they were originally published as "Automatic." 
    No Flash updates in the ConfigMgr console are marked as downloaded.  I can't find any documentation on how the process of using SCUP for downloading content for an update marked Metadata Only actually works. 
    Comments and suggestions welcome.

  • SCCM 2012 R2 CU4 - Site Backup Task failed

    Hi, I set up a Site Maintenance Task for Backup our Primary Site, but every time I run this task it fail with the following message:
    Error: Backup folder \\backupserver\backupshare$ does not exist or backup service does not have permission to access the folder.
    I tried to use "erveryone" in share permissions and NTFS Permissions with Full Control and then the Backup works! ... I tried to remove the everyone from NTFS completely then the Backup also still works .. but when I remove everyone from the share
    permissions (and grant the SCCM Site Server and SQL Server Computer Accounts the Full Control Permission) the backup fails..
    so it seems to me that I have a permission issue ... what is the correct Permission setup for UNC Backup? (Share and NTFS Permissions) ... I tried to give the SCCM Server and SQL Server Computer and SQL Cluster Account Full Control without success...)
    kind regards
    Klaus

    "The computer account of the site server and the computer account of the SQL Server, if SQL Server is installed on another computer, must have
    Write NTFS and share permissions to the shared network folder."
    https://technet.microsoft.com/en-us/library/gg712697.aspx
    Also have you read this:
    http://blog.msvconsultancy.co.uk/2014/07/sccm-2012-sp1-site-maintenance-backup-task-error/

  • SCCM 2012 R2 configure WSUS got error remote SQL Server 2012

    Hi All,
    I got question ask on when i want to configure the WSUS component it failed as per screenshot and my SCCM cant work with it.
    SCCM Server : Windows Server 2012 R2 (WSUS featured installed)
    SCCM Version: System Center Config Manager R2
    Remote SQL Server : Windows Server 2012 R2
    SQL Version: SQL Server 2012 SP1 -11.0.3153
    WSUS Error:
    SCCM Error:
    Hope you all can provide me a good solution on it I had no clue on this.
    Regards,
    Sam

    Sam,
    Recommend you 
    Remove SUP
    Remove WSUS role
    Delete the SUSDB on the remote SQL server
    Reboot the server
    Reinstall WSUS feature
    Reinstall SUP
    Take a look at my blog on installing a SUP on 2012 from the section 'Install WSUS on the remote SUP server'
    http://sccmentor.wordpress.com/2014/09/11/installing-a-remote-sup-in-sccm-2012-r2-on-windows-server-2012-r2/
    Make sure you run the Post Install tasks as well.
    Cheers
    Paul | sccmentor.wordpress.com

  • Server 2012 R2 - Complete WSUS Installation Issue - The service cannot be started...

    Hi all,
    installed SCCM 2012 R2 CAS on a 2012 server. The SQL is off box on a server cluster. I've installed WSUS through the 'Add Roles and Features'. I configured it to have local storage for the content and a remote DB instance (called SQL1 on our cluster). All this
    worked well and the install completed as expected. I checked the SQL cluster and the "SUSDB" database was created ok.
    As a final step, i went to Tools in Server Manager and launched Windows Server Update Services. This brought up the 'Complete WSUS Installation' dialogue box. I entered the exact same DB info as i had done when completing the initial install of WSUS:
    Yet when i hit 'run' the following message returns:
    The relevant bit of logging is shown here:
    2015-01-14 16:58:42  Starting service W3SVC
    2015-01-14 16:58:42  Configuring IIS...
    2015-01-14 16:58:42  Start: ConfigureWebsite
    2015-01-14 16:58:42  System.Runtime.InteropServices.COMException (0x80070422): The service cannot be started, either because it is disabled or because it has no enabled devices associated with it.
    Since i'm pretty sure i need WSUS working correctly to use it for SCCM, can anyone suggest what my problem is here? I'd assume it's falling down because the 'ConfigureWebsite' job can't start but what service does that need to run?
    Really stumpoed by this so any help would be much appreciated! Thanks

    2015-01-14 16:58:42  Start: ConfigureWebsite
    Did you install the Web Server role before installing the WSUS Server role? Is the Web Server role already installed? If so, is it installed and configured in a compatible manner with the WSUS role?
    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.

Maybe you are looking for