locked
SCCM 2012 R2 CLient Push installation Issues RRS feed

  • Question

  • We are running into a issue where we are unable to push Client from SCCM 2012 R2 console

      1. Tested WMI successfully by using wbemtest to the client machine to make sure we are able to connect to

    \\computer\root\cimV2

    2.Windows Firewall was turned off, BITS and ccmsetp service were started. Initially BITS was in Stopped State.

    3.In CCM.log found it’s looking for client.msi in D:\Program Files\Microsoft Configuration Manager\client which was not there initially, so I copied ccmsetp.exe and client.msi copied to this location in I386 Folder.

    4. We are using Proper Service Account for the client Push

    5.  Ccmsetp gets created in the client machine however it’s empty.

    CCM.log has the below information

    Unable to connect to WMI (root\ccm) on remote machine "JOES_SCCMTEST", error = 0x8004100e.  $$<SMS_CLIENT_CONFIG_MANAGER><08-14-2015 13:45:20.090+300><thread=4840 (0x12E8)>

    ---> Mobile client on the target machine has the same version, and 'forced' flag is turned on.~  $$<SMS_CLIENT_CONFIG_MANAGER><08-14-2015 13:45:20.103+300><thread=4840 (0x12E8)>

    ---> Creating \ VerifyingCopying exsistance of destination directory

    \\JOES_SCCMTEST\admin$\ccmsetup.~  $$<SMS_CLIENT_CONFIG_MANAGER><08-14-2015 13:45:20.112+300><thread=4840 (0x12E8)>

    ---> Copying client files to

    \\JOES_SCCMTEST\admin$\ccmsetup.~  $$<SMS_CLIENT_CONFIG_MANAGER><08-14-2015 13:45:20.289+300><thread=4840 (0x12E8)>

    ---> Error setting ACL on TCF file, deleting file and failing install.  $$<SMS_CLIENT_CONFIG_MANAGER><08-14-2015 13:45:20.298+300><thread=4840 (0x12E8)>

    ---> Failed to install CCM Client Bootstrap component on client (1)  $$<SMS_CLIENT_CONFIG_MANAGER><08-14-2015 13:45:20.307+300><thread=4840 (0x12E8)>

    ---> Deleting SMS Client Install Lock File '\\JOES_SCCMTEST\admin$\SMSClientInstall.CHI'~  $$<SMS_CLIENT_CONFIG_MANAGER

    Error: cannot get version of client installation file: D:\Program Files\Microsoft Configuration Manager\client\I386\Client.msi  $$<SMS_CLIENT_CONFIG_MANAGER><08-14-2015 14:00:37.331+300><thread=8172 (0x1FEC)>

    We tested with few machines and it's the same behavior,any help would be highly Appreciated.

    Regards,

    Gautham.K



    MCTS-Microsoft Exchange Adminstrator,2010

    Monday, August 17, 2015 10:19 AM

Answers

  • First note for number 3 above, you don't have to copy anything. The CCM process is simply looking for their existence to know what work it needs to perform. Just because there's a message in the log file does not mean there is something wrong or something unexpected occurred.

    For your issue, you'll need to dig into the client machine. An ACL is an Access Control List, it's what Windows used to track and enforce permissions. The error message is a bit generic but the ccm process has no true way of knowing what is preventing it from setting the ACL. You'll need to examine things your AV and the Windows event log on your target system. Also keep in mind this isn't an issue with the client push process per se, it's an issue on the target system. You may have to use procmon to track all activity to see if you can pinpoint something preventing the process from setting permissions.

    - What is the target OS here?

    - Is this happening on many systems or just one?

    - Have you reviewed the current permissions on the ccmsetup folder created by the ccm process?

    - Do you have any security lockdowns in place (GPO or otherwise)?

    - Have you tried disabling your AV on the target system?


    Jason | http://blog.configmgrftw.com | @jasonsandys

    Monday, August 17, 2015 12:38 PM

All replies

  • It hard to determine base on the error messages being out of context. But first error seem to be the ACL error, that is where I would start looking.

    Garth Jones | My blogs: Enhansoft and Old Blog site | Twitter: @GarthMJ

    Monday, August 17, 2015 11:26 AM
  • Thank you Garth,

    Could you please let me know what would you be checking on ACL errors.

    Where Should I start looking out for ACL errors on the client machine?

    Regards,

    Gautham.K


    MCTS-Microsoft Exchange Adminstrator,2010

    Monday, August 17, 2015 12:07 PM
  • First note for number 3 above, you don't have to copy anything. The CCM process is simply looking for their existence to know what work it needs to perform. Just because there's a message in the log file does not mean there is something wrong or something unexpected occurred.

    For your issue, you'll need to dig into the client machine. An ACL is an Access Control List, it's what Windows used to track and enforce permissions. The error message is a bit generic but the ccm process has no true way of knowing what is preventing it from setting the ACL. You'll need to examine things your AV and the Windows event log on your target system. Also keep in mind this isn't an issue with the client push process per se, it's an issue on the target system. You may have to use procmon to track all activity to see if you can pinpoint something preventing the process from setting permissions.

    - What is the target OS here?

    - Is this happening on many systems or just one?

    - Have you reviewed the current permissions on the ccmsetup folder created by the ccm process?

    - Do you have any security lockdowns in place (GPO or otherwise)?

    - Have you tried disabling your AV on the target system?


    Jason | http://blog.configmgrftw.com | @jasonsandys

    Monday, August 17, 2015 12:38 PM