Configuration manager, client push error 0x80070643

Posted on 2009-02-10
Last Modified: 2013-11-21
Hopefully someone can shed some light on this problem..

When attempting to push a client install from System Centre Configuration Manager V.4.00.6221.1000, is returning error on XP sp2 client as listed below:

Event Type:      Error
Event Source:      Windows Update Agent
Event Category:      Installation
Event ID:      20
Date:            10/02/2009
Time:            03:13:59
User:            N/A
Computer:      LTC85
Installation Failure: Windows failed to install the following update with error 0x80070643: Configuration Manager Client Installation.

For more information, see Help and Support Center at
0000: 57 69 6e 33 32 48 52 65   Win32HRe
0008: 73 75 6c 74 3d 30 78 38   sult=0x8
0010: 30 30 37 30 36 34 33 20   0070643
0018: 55 70 64 61 74 65 49 44   UpdateID
0020: 3d 7b 41 33 33 31 44 34   ={A331D4
0028: 43 38 2d 38 42 41 34 2d   C8-8BA4-
0030: 34 37 39 31 2d 41 33 35   4791-A35
0038: 46 2d 39 46 41 34 37 35   F-9FA475
0040: 41 37 41 30 44 34 7d 20   A7A0D4}
0048: 52 65 76 69 73 69 6f 6e   Revision
0050: 4e 75 6d 62 65 72 3d 31   Number=1
0058: 20 00
Question by:Adrian McGarry
    LVL 5

    Expert Comment

    LVL 4

    Author Comment

    by:Adrian McGarry
    No sorry! this has nothing to do with the Office Source Engine service in this instance.  On the offending unit this service is set to it's default "Manual" state.
    LVL 4

    Author Comment

    by:Adrian McGarry
    Thanks for the suggestion, but have now resolved this issue:-

    Within the SCCM management console the "Network Access account" did not have the appropriate permissions to deploy the client to the units in question.
    LVL 2

    Accepted Solution

    Check the "Network access" account has the appropriate permissions to deploy the client.

    We have also come across this issue and discovered not only this permissions problem was blocking deployment but it was not picking-up the ConfigMgr Site assigned code, even on discovery, after deployed.

    This was caused from installation of SCCM on the server to soon after extending the schema, which had not given it time to propogate.
    LVL 4

    Author Closing Comment

    by:Adrian McGarry
    Thanks! Had figured the network access account issue, but came across the next part immediately after.
    You saved me a lot of frustation!

    Expert Comment

    I found that i need to specify mp parameters in the template in GPO

    Write Comment

    Please enter a first name

    Please enter a last name

    We will never share this with anyone.

    Featured Post

    Why spend so long doing email signature updates?

    Do you spend loads of your time carrying out email signature updates? Not very interesting are they? Don’t let signature updates get you down. Let Exclaimer Cloud - Signatures for Office 365 make managing email signatures a breeze.

    Case Summary: In this Article we introduce the new method to configure the default user profile using Automated profile copy with sysprep rather than the old ways such as the manual copy of a configured profile to default user profile Old meth…
    Problem Description: Actually I found the below issue with some customers after migration from SMS 2003 to SCCM 2007 and epically if they change site code, some clients may appear in the console with old site code, plus old sites still appearing …
    how to add IIS SMTP to handle application/Scanner relays into office 365.
    In this sixth video of the Xpdf series, we discuss and demonstrate the PDFtoPNG utility, which converts a multi-page PDF file to separate color, grayscale, or monochrome PNG files, creating one PNG file for each page in the PDF. It does this via a c…

    737 members asked questions and received personalized solutions in the past 7 days.

    Join the community of 500,000 technology professionals and ask your questions.

    Join & Ask a Question

    Need Help in Real-Time?

    Connect with top rated Experts

    22 Experts available now in Live!

    Get 1:1 Help Now