locked
2012 CM Client Installation Issue RRS feed

  • Question

  • Unable to find a matching post so here goes:

    • 12CM stand-alone site
    • Client push to all machines work with success except to the domain controller; DC checkbox selected in client push attempt
    • 'vcredist_x86.exe' or 'vcredist_x64.exe' failing appears to be the culprit (see ccmsetup.log below)
    • unable to install directly from exe (see image below):

    • Account with client push is currently a Domain Admin account
    • This domain controller had the CM 2007 client install, I manually uninstalled with cleanup, 12CM client still unable to complete with same errors regarding 'vcredist' install.

    Thank you for your thoughts in advance.....

    ========12CM Client CCMSetup.log =========

    Adding file 'HTTP://CM.corp.lab.com:80/CCM_Client/x64/client.msi' to BITS job, saving as 'C:\Windows\ccmsetup\client.msi'. ccmsetup 4/20/2013 4:26:22 PM 864 (0x0360)
    Starting BITS download for client deployment files. ccmsetup 4/20/2013 4:26:22 PM 864 (0x0360)
    Successfully completed BITS download for client deployment files. ccmsetup 4/20/2013 4:26:23 PM 864 (0x0360)
    Successfully downloaded client files via BITS. ccmsetup 4/20/2013 4:26:23 PM 864 (0x0360)
    Validated file 'C:\Windows\ccmsetup\vcredist_x86.exe' hash '97C260D35BCFE18E046A1C413B9FC5A2754B8F790F7ACE669A3BE2500C0DF229' ccmsetup 4/20/2013 4:26:23 PM 864 (0x0360)
    Validated file 'C:\Windows\ccmsetup\vcredist_x64.exe' hash '7451BA5C6C05347789717561E871A303A4D171850790A3CDC99D4DDBF07E320B' ccmsetup 4/20/2013 4:26:23 PM 864 (0x0360)
    Validated file 'C:\Windows\ccmsetup\vc50727_x64.exe' hash '0551A61C85B718E1FA015B0C3E3F4C4EEA0637055536C00E7969286B4FA663E0' ccmsetup 4/20/2013 4:26:23 PM 864 (0x0360)
    Validated file 'C:\Windows\ccmsetup\MicrosoftPolicyPlatformSetup.msi' hash '8C42189693C3220017E8C93A79B989EE126ADF33EADBE229011404C123B7B897' ccmsetup 4/20/2013 4:26:23 PM 864 (0x0360)
    Validated file 'C:\Windows\ccmsetup\Silverlight.exe' hash '417B442E128D821119008ACEEEE6CDC2A41224377A829B6EC52BABA2724F0151' ccmsetup 4/20/2013 4:26:23 PM 864 (0x0360)
    Validated file 'C:\Windows\ccmsetup\client.msi' hash '2F0819F959E788CF843F42E9CA7B44E258B8B4BA37BB63902DB39ACF747BE7DA' ccmsetup 4/20/2013 4:26:24 PM 864 (0x0360)
    Retrieved client version '5.00.7804.1000' and minimum assignable site version '5.00.7783.1000' from client package ccmsetup 4/20/2013 4:26:24 PM 864 (0x0360)
    Checking compatibility of site version '5.00.7804.1000', expect newer than '5.00.7783.1000' ccmsetup 4/20/2013 4:26:24 PM 864 (0x0360)
    Site version '5.00.7804.1000' is compatible. Client deployment will continue. ccmsetup 4/20/2013 4:26:24 PM 864 (0x0360)
    C:\Windows\ccmsetup\vcredist_x86.exe is Microsoft trusted. ccmsetup 4/20/2013 4:26:24 PM 864 (0x0360)
    Installing file 'C:\Windows\ccmsetup\vcredist_x86.exe' with options '/q:a /c:"VCREDI~3.EXE /q:a /c:""msiexec /i vcredist.msi /qn"" "'. ccmsetup 4/20/2013 4:26:24 PM 864 (0x0360)
    File 'C:\Windows\ccmsetup\vcredist_x86.exe' returned failure exit code 1603. Fail the installation. ccmsetup 4/20/2013 4:26:26 PM 864 (0x0360)
    InstallFromManifest failed 0x80070643 ccmsetup 4/20/2013 4:26:26 PM 864 (0x0360)
    Sending Fallback Status Point message to 'CM.CORP.LAB.COM', STATEID='311'. ccmsetup 4/20/2013 4:26:26 PM 864 (0x0360)
    Failed to get client version for sending messages to FSP. Error 0x80041010 ccmsetup 4/20/2013 4:26:26 PM 864 (0x0360)
    Params to send FSP message '5.0.7804.1000 Deployment Error 0x80070643. Pre-req: vcredist_x86.exe' ccmsetup 4/20/2013 4:26:26 PM 864 (0x0360)
    State message with TopicType 800 and TopicId {7E0C3554-5EB5-43B4-8EFF-EF2DC0A78C8F} has been sent to the FSP FSPStateMessage 4/20/2013 4:26:26 PM 864 (0x0360)
    CcmSetup failed with error code 0x80070643 ccmsetup 4/20/2013 4:26:26 PM 2464 (0x09A0)

    Saturday, April 20, 2013 8:53 PM

Answers

  • This doesn't look like a ConfigMgr related issue. I think the problem is the target server itself.
    Do you see this issue on other servers ?

    What happens if you just try to run vcredist.exe directly on the server (without using ConfigMgr)?

    You can also try to remove/uninstall  old/other versions of Visual C++ you have installed, and then try again.

    

    Ronni Pedersen | Microsoft MVP - ConfigMgr | Blogs: www.ronnipedersen.com/ and www.SCUG.dk/ | Twitter @ronnipedersen

    Sunday, April 21, 2013 5:13 PM
  • Error code 1935 = "The computer you are signing into is protected by an authentication firewall. The specified account is not allowed to authenticate to the computer."

    I have no real idea what that means in this context though. Try manually installing with verbose logging enabled to see if there are more details.


    Jason | http://blog.configmgrftw.com

    Sunday, April 21, 2013 7:41 PM

All replies

  • This doesn't look like a ConfigMgr related issue. I think the problem is the target server itself.
    Do you see this issue on other servers ?

    What happens if you just try to run vcredist.exe directly on the server (without using ConfigMgr)?

    You can also try to remove/uninstall  old/other versions of Visual C++ you have installed, and then try again.

    

    Ronni Pedersen | Microsoft MVP - ConfigMgr | Blogs: www.ronnipedersen.com/ and www.SCUG.dk/ | Twitter @ronnipedersen

    Sunday, April 21, 2013 5:13 PM
  • Error code 1935 = "The computer you are signing into is protected by an authentication firewall. The specified account is not allowed to authenticate to the computer."

    I have no real idea what that means in this context though. Try manually installing with verbose logging enabled to see if there are more details.


    Jason | http://blog.configmgrftw.com

    Sunday, April 21, 2013 7:41 PM