locked
Installing the SCCM 2012 client onto a PullDP RRS feed

  • Question

  • Hi,

    we are having an issue when trying to install the CCM client onto a PullDP.
    the pull dp did not previously have the SCCM 2012 client agent installed.

    When attempting to install the agent, the ccmsetup.log reports the following error message:

    MSI: Setup was unable to compile the file UpdatesAgent.mof
    The error code is 80041002

    client.msi.log

    [10:18:49] Failed to compile 'C:\Windows\CCM\UpdatesAgent.mof' (Phase: 3, Object: 1, Lines: 12 - 17, Error: 80041002)
    [10:18:49] Compiled 'C:\Windows\CCM\UpdatesAgentSchema.mof'
    MSI (s) (6C!3C) [10:18:55:014]: Product: Configuration Manager Client -- Error 25140. Setup was unable to compile the file UpdatesAgent.mof
    Error 25140. Setup was unable to compile the file UpdatesAgent.mof

    the mof file doesn't exist in the ccm folder.

    If I remove the PullDP role, then rename the ccm folder to .old, and re-push the client installation, it succeeds.

    Any ideas why we can't push the client to a PullDP?

    Sunday, October 20, 2013 11:25 PM

All replies

  • Any additional errors in the log files in %windir%\system32\wbem\logs?
    Monday, October 21, 2013 10:06 AM
  • the WMIProv.Log shows:
    (Tue Oct 22 15:09:47 2013.1421241773) : WDM call returned error: 4200
    (Tue Oct 22 15:10:17 2013.1421271819) : WDM specific return code: 4200

    This seems to pre-exist on all the PullDP's that I have attempted to install to.
    Infact, that same error exists on other servers that are still CM07 DP's, with the CM07 Client, so I don't think this is related.

    client.msi.log:
    [15:08:25] Failed to compile 'C:\Windows\CCM\UpdatesAgent.mof' (Phase: 3, Object: 1, Lines: 12 - 17, Error: 80041002)
    [15:08:26] Failed to compile 'C:\Windows\CCM\DataTransferService.mof' (Phase: 3, Object: 5, Lines: 318 - 323, Error: 80041002)
    [15:08:26] Failed to compile 'C:\Windows\CCM\proxydefault.mof' (Phase: 3, Object: 1, Lines: 19 - 24, Error: 80041002)
    [15:08:26] Failed to compile 'C:\Windows\CCM\ContentTransferManager.mof' (Phase: 3, Object: 6, Lines: 352 - 357, Error: 80041002)
    [15:08:26] Failed to compile 'C:\Windows\CCM\CcmPolicySdk.mof' (Phase: 3, Object: 1, Lines: 21 - 26, Error: 80041002)
    [15:08:26] Failed to compile 'C:\Windows\CCM\CPApplet.mof' (Phase: 3, Object: 13, Lines: 160 - 165, Error: 80041002)
    [15:08:27] Failed to compile 'C:\Windows\CCM\InventoryDefaultPolicy.mof' (Phase: 3, Object: 25, Lines: 269 - 288, Error: 80041002)
    [15:08:27] Failed to compile 'C:\Windows\CCM\SWDistPolicy.mof' (Phase: 3, Object: 8, Lines: 234 - 239, Error: 80041002)
    [15:08:27] Failed to compile 'C:\Windows\CCM\SrcUpdatePolicy.mof' (Phase: 3, Object: 4, Lines: 80 - 85, Error: 80041002)
    [15:08:28] Failed to compile 'C:\Windows\CCM\SMSNapPolicy.mof' (Phase: 3, Object: 2, Lines: 51 - 56, Error: 80041002)
    [15:08:28] Failed to compile 'C:\Windows\CCM\ScanAgent.mof' (Phase: 3, Object: 5, Lines: 65 - 70, Error: 80041002)
    [15:08:30] Failed to compile 'C:\Windows\CCM\VAppManager.mof' (Phase: 3, Object: 1, Lines: 13 - 18, Error: 80041002)
    MSI (s) (20!F4) [15:08:30:449]: Product: Configuration Manager Client -- Error 25140. Setup was unable to compile the file UpdatesAgent.mof
    The error code is 80041002
    Error 25140. Setup was unable to compile the file UpdatesAgent.mof
    The error code is 80041002
    CustomAction CcmRegisterWmiMofFile returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)


    Any more ideas?
    As soon as I Remove the PullDP role, and push the client, it installs.
    Then I can add the PullDP role back.  Not ideal though, as there are >150 of these to do now.
    Tuesday, October 22, 2013 4:30 AM
  • I am experiencing the exact same issue. Did you ever discover the root cause?
    Wednesday, December 11, 2013 3:12 PM
  • After some digging I stumbled across the solution for my problem, below is what fixed the issue for me... hopefully this will help someone else.

    Environment

    • Configuration Manager 2012 SP1 with CU3.
    • The issue was on a freshly installed DP installing the client.

    Solution

    The issue was resolved by using the switch PATCH=<path_to_CU3_client_hotfix_msp> along with our normal installation parameters. While I didn’t test this extensively, the PATCH switch seems to need the full path to the msp file (not a relative one).


    Wednesday, December 11, 2013 4:19 PM
  • the PATCH switch seems to need the full path to the msp file (not a relative one).

    Thanks for posting the above. Also note the fully qualified path requirement is accurate (although that's a Windows Installer requirement and is not specific to ConfigMgr or CU3 in any way).

    Jason | http://blog.configmgrftw.com

    Wednesday, December 11, 2013 4:24 PM
  • Thanks for the posting your findings

    Sorry I haven't replied yet - we have now upgraded to R2!

    Now when I run the client installer while the PullDP role is installed, it installs correctly without error.

    One thing I have noted though:  if you use the CCMINSTALLDIR=M:\SMS_CCM param, it will ignore it as some client components are already installed as a part of the PullDP role.

    Now if I want to move it to M:\ for example, I would need to first remove the PullDP the use a /ForceInstall parameter to make it re-install to the new directory.  We need to still do this, So I might look at automating it :)

    All up - R2 for the win!

    Friday, December 13, 2013 12:00 AM
  • Glad to hear R2 solved the problem in your case!

    Not sure if it will help, but I've noticed that the when the DP is installing itself and some of the client components, it respects NO_SMS_ON_DRIVE.SMS. So that, when I go to install the full client later it also installs on the same drive in the SMS_CCM directory without any special parameters.

    So in my environment (we have very simple DPs) each DP has two drives C:\ and D:\. On C: I place the NO_SMS file and D:\ ends up houses the content library, various related files, and the client without any special effort on my behalf.

    Not that this helps the situation of moving the files once they are in place, but hey!


    Friday, December 13, 2013 2:17 PM