locked
Deploying Clients via WSUS RRS feed

  • Question

  • When I search for instructions on deploying the SCCM 2012 R2 clients, I find this link http://technet.microsoft.com/en-us/library/gg712298.aspx that basically says to create and assign a GPO with settings pointing clients to check updates from your SCCM server.

    "In the box Set the intranet update service for detecting updates, specify the name of the software update point server that you want to use and the port."

    Is the SCCM client supposed to just automatically download with just those steps? That does not seem to be enough.

    I created a GPO and assigned it to a few PCs and I see nothing happening.

    What else do you do after that?  Do you need to "approve" the client somewhere like a WSUS Windows update?

    I don't see how it finds the client installation files and deploys it with those minimal instructions.

    Wednesday, June 25, 2014 2:31 AM

All replies

  • After rebooting the client and manually checking for updates again, it sees the client available for download, but it fails to install.

    The windowsupdate.log has this info:


    2014-06-24 21:44:11:463 380 6a8 Agent *************
    2014-06-24 21:44:11:463 380 6a8 Agent ** START **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2014-06-24 21:44:11:463 380 6a8 Agent *********
    2014-06-24 21:44:11:463 380 6a8 Agent  * Online = No; Ignore download priority = No
    2014-06-24 21:44:11:463 380 6a8 Agent  * Criteria = "IsInstalled=0 and DeploymentAction='Installation' or IsPresent=1 and DeploymentAction='Uninstallation' or IsInstalled=1 and DeploymentAction='Installation' and RebootRequired=1 or IsInstalled=0 and DeploymentAction='Uninstallation' and RebootRequired=1"
    2014-06-24 21:44:11:463 380 6a8 Agent  * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
    2014-06-24 21:44:11:463 380 6a8 Agent  * Search Scope = {Machine}
    2014-06-24 21:44:11:463 380 df4 AU Getting featured update notifications.  fIncludeDismissed = true
    2014-06-24 21:44:11:463 380 df4 AU No featured updates available.
    2014-06-24 21:44:13:026 380 6a8 Agent  * Added update {8427071A-DA80-48C3-97DE-C9C528F73A2D}.1 to search result
    2014-06-24 21:44:13:026 380 6a8 Agent  * Found 1 updates and 76 categories in search; evaluated appl. rules of 243 out of 4445 deployed entities
    2014-06-24 21:44:13:041 380 6a8 Agent *********
    2014-06-24 21:44:13:041 380 6a8 Agent **  END  **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2014-06-24 21:44:13:041 380 6a8 Agent *************
    2014-06-24 21:44:13:120 380 c3c AU >>##  RESUMED  ## AU: Search for updates [CallId = {9596DDD6-E32D-43FF-A634-A60462D271DD}]
    2014-06-24 21:44:13:120 380 c3c AU  # 1 updates detected
    2014-06-24 21:44:13:120 380 c3c AU WARNING: AU ignoring update during offline scan:
    2014-06-24 21:44:13:120 380 c3c AU #########
    2014-06-24 21:44:13:120 380 c3c AU ##  END  ##  AU: Search for updates [CallId = {9596DDD6-E32D-43FF-A634-A60462D271DD}]
    2014-06-24 21:44:13:120 380 c3c AU #############
    2014-06-24 21:44:13:120 380 c3c AU Featured notifications is disabled.
    2014-06-24 21:44:13:120 380 c3c AU Setting AU scheduled install time to 2014-06-25 10:00:00
    2014-06-24 21:44:13:120 380 c3c AU Successfully wrote event for AU health state:0
    2014-06-24 21:44:13:151 380 c3c AU Successfully wrote event for AU health state:0
    2014-06-24 21:44:13:151 380 df4 AU Getting featured update notifications.  fIncludeDismissed = true
    2014-06-24 21:44:13:151 380 df4 AU No featured updates available.
    2014-06-24 21:44:16:166 380 6a8 Report REPORT EVENT: {D2651F48-6BEE-449A-BAD5-DAD6C5659588} 2014-06-24 21:44:11:167-0700 1 182 101 {8427071A-DA80-48C3-97DE-C9C528F73A2D} 1 80070643 AutomaticUpdates Failure Content Install Installation Failure: Windows failed to install the following update with error 0x80070643: Configuration Manager Client (5.00.7958.1000).
    2014-06-24 21:44:16:213 380 6a8 Report CWERReporter::HandleEvents - WER report upload completed with status 0x8
    2014-06-24 21:44:16:213 380 6a8 Report WER Report sent: 7.6.7600.256 0x80070643 8427071A-DA80-48C3-97DE-C9C528F73A2D Install 101 Managed
    2014-06-24 21:44:16:213 380 6a8 Report CWERReporter finishing event handling. (00000000)

    Wednesday, June 25, 2014 5:01 AM
  • http://blogs.technet.com/b/configurationmgr/archive/2014/06/24/how-to-install-the-configuration-manager-client-using-software-update-point-based-client-installation.aspx

    Torsten Meringer | http://www.mssccmfaq.de

    I was able to figure that much out and get it to try to download the client, but the installation fails with the error:

    {8427071A-DA80-48C3-97DE-C9C528F73A2D} 1 80070643 AutomaticUpdates Failure Content Install Installation Failure: Windows failed to install the following update with error 0x80070643: Configuration Manager Client (5.00.7958.1000).

    Wednesday, June 25, 2014 8:37 PM
  • Hi,

    The error code 0x80070643, decimal 1603 means " ERROR_INSTALL_FAILURE". It is a generic catch-all error code that means "Fatal error during installation". The 1603 error code is returned when any action fails during an installation.


    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.

    Thursday, June 26, 2014 8:52 AM
  • In addition, I recommend you use Jason Sandys startup script: http://blog.configmgrftw.com/?page_id=349
    It is much more flexible and will do the job.

    Note: Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.


    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.

    Thursday, June 26, 2014 8:55 AM
  • I'd like to get the problem with the client installing through SUP solved rather than bypassing it with a startup script since there may be an issue there that will cause other problems using SUP for other things later.

    I looked in the event log of the client and see these errors:

    Fault bucket 3911596714, type 5

    Event Name: WindowsUpdateFailure

    Response: Not available

    Cab Id: 0

    Problem signature:

    P1: 7.6.7600.256

    P2: 80070643

    P3: 8427071A-DA80-48C3-97DE-C9C528F73A2D

    P4: Install

    P5: 101

    P6: Managed

    P7:

    P8:

    P9:

    P10:

    Attached files:

    These files may be available here:

    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\NonCritical_7.6.7600.256_33b2c06ac3c5b2afc2eb67fea6f121cf6a2a1a3d_06f6f0ce

    Analysis symbol:

    Rechecking for solution: 0

    Report Id: 301ebdfc-fda5-11e3-8b24-00155d010406

    Report Status: 0

    and this:

    Fault bucket , type 0

    Event Name: WindowsUpdateFailure

    Response: Not available

    Cab Id: 0

    Problem signature:

    P1: 7.6.7600.256

    P2: 80070643

    P3: 8427071A-DA80-48C3-97DE-C9C528F73A2D

    P4: Install

    P5: 101

    P6: Managed

    P7:

    P8:

    P9:

    P10:

    Attached files:

    These files may be available here:

     

    Analysis symbol:

    Rechecking for solution: 0

    Report Id: 301ebdfc-fda5-11e3-8b24-00155d010406

    I looked at some people posting that this is solved by installing KB2734608 and KB2720211 on the server, but they both fail or are already installed.

    The SCCM server is running on Server 2012 R2 and I'm not sure this applies.

    Friday, June 27, 2014 3:10 AM