locked
Unable to deploy clients. SMSClient share not available. RRS feed

  • Question

  • I have setup SCCM 2012 R2 on a single server but I have not been able to deploy any clients. I downloaded the log tool and noticed a couple things that I am unsure how to correctly fix (these are from client logs):

    Failed to get client version for sending messages to FSP. Error 0x8004100e ccmsetup 2/16/2015 5:59:25 PM 3312 (0x0CF0)

    Performing AD query: '(&(ObjectCategory=mSSMSManagementPoint)(mSSMSDefaultMP=TRUE)(mSSMSSiteCode=NLR))' ccmsetup 2/16/2015 5:59:26 PM 3312 (0x0CF0)

    Retrieved 0 MP records from AD for site 'NLR' ccmsetup 2/16/2015 5:59:26 PM 3312 (0x0CF0)

    Failed to get site version from AD with error 0x87d00215 ccmsetup 2/16/2015 5:59:26 PM 3312 (0x0CF0)
    Source \\SCCM.CLOUD.LOCAL\SMSClient is inaccessible (67) ccmsetup 2/16/2015 5:59:26 PM 3312 (0x0CF0)

    Now what I've noticed is SMSClient is not a share on my SCCM server. So I'm thinking something may have not configured properly during the install.

    Anyone have any ideas?


    Tuesday, February 17, 2015 1:59 AM

Answers

  • I just got it working. I removed the management point from the site.. waiting a bit and added the Management Point role back and now the client push works.
    • Marked as answer by Quadrantids Wednesday, February 18, 2015 5:25 PM
    Wednesday, February 18, 2015 5:25 PM

All replies

  • As your question is related to System Center Configuration Manager I moved this thread to the SCCM forums.

    Andreas Baumgarten | H&D International Group

    Tuesday, February 17, 2015 7:14 AM
  • Hi,

    Have you configured the boundaries and client push installation account?

    Please refer to the link below:

    How to Install Configuration Manager Clients by Using Client Push

    https://technet.microsoft.com/en-us/library/gg712298.aspx


    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.


    Tuesday, February 17, 2015 8:19 AM
  • Failed to get client version for sending messages to FSP. Error 0x8004100e
    ccmsetup 2/16/2015 5:59:25 PM
    3312 (0x0CF0)

    This is perfectly normal on systems where the client agent is not installed.

    Now what I've noticed is SMSClient is not a share on my SCCM server.

    There's not supposed to be a share for this. The client agent source files are downloaded from DPs in 2012 although it will fallback to an MP -- in either case, it comes from an IIS via WebDAV and never an SMB share. 


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

    • Proposed as answer by Jörgen NilssonMVP Tuesday, February 17, 2015 10:10 PM
    • Unproposed as answer by Quadrantids Wednesday, February 18, 2015 3:27 PM
    Tuesday, February 17, 2015 4:06 PM
  • It fails right after it can't find the SMSClient share. From all my reading on tutorials and such I have SCCM setup properly (but obviously not). This includes the link above. My boundaries are in place and I only have one group.

    I just can't for the life of me figure out why the client push isn't working. It fails because it can't seem to find the files according to the log.

    Is SCCM integrated with AD Schema? This error exists in the client logs:Failed to get site version from AD with error 0x87d00215

    Wednesday, February 18, 2015 3:29 PM
  • How exactly are you installing these client agents? Are you using the /source switch?

    As mentioned, SMSClient is *not* a default share. Many folks have traditionally created one manually, but there is no need to do this unless you are using the /source switch in which case I'd ask why in the world you are doing this? In 2012, the client files are downloaded from the nearest DP automatically and by default.


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

    Wednesday, February 18, 2015 3:35 PM
  • Here is where it fails:

    Ccmsetup is being restarted due to an administrative action. Installation files will be reset and downloaded again. ccmsetup 2/18/2015 9:57:34 AM 6444 (0x192C)
    No MPs were specified from commandline or the mobileclient.tcf. ccmsetup 2/18/2015 9:57:34 AM 6444 (0x192C)
    Downloading file ccmsetup.cab ccmsetup 2/18/2015 9:57:34 AM 6444 (0x192C)
    Determining source location... ccmsetup 2/18/2015 9:57:34 AM 6444 (0x192C)
    Source \\SCCM.cloud.local\SMSClient is inaccessible (67) ccmsetup 2/18/2015 9:57:34 AM 6444 (0x192C)
    Source \\SCCM.CLOUD.LOCAL\SMSClient is inaccessible (67) ccmsetup 2/18/2015 9:57:34 AM 6444 (0x192C)
    Failed to find accessible source. Waiting for retry. ccmsetup 2/18/2015 9:57:34 AM 6444 (0x192C)

    Wednesday, February 18, 2015 3:58 PM
  • Please answer the questions: "How exactly are you installing these client agents? Are you using the /source switch?"

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

    Wednesday, February 18, 2015 4:05 PM
  • I just got it working. I removed the management point from the site.. waiting a bit and added the Management Point role back and now the client push works.
    • Marked as answer by Quadrantids Wednesday, February 18, 2015 5:25 PM
    Wednesday, February 18, 2015 5:25 PM
  • Hello,

    Can you more specific on how to remove the management point and add it back?

    Thank you,

    John

    Friday, February 9, 2018 6:24 PM
  • Mine was working before, but now got the same error message

    SMSClient is inaccessible (67)

    Can anyone shed the light of fixing it?

    Friday, February 9, 2018 6:27 PM
  • To remove a role, go to Administration->Site Configuration->Servers and Site System Roles.

    Then in the list view on the right, select the server you want to remove the role from. After that, you will see the list of roles at the bottom.

    You can then Right Click and remove the role.



    Jason | https://home.configmgrftw.com | @jasonsandys

    Saturday, February 10, 2018 4:33 PM