locked
Client Push not working - Error 67, 5 & Install issues RRS feed

  • Question

  • HI Everyone

    I cannot push the CCM Client to our computers.  You can manually install ccmsetup.exe on the client, and everything works.  There are no firewall issues.  I can get to the admin$ drive from the server to the client.  But when I push down the client, it comes up with error 67(---> ERROR: Unable to access target machine for request: "16777219", machine name: "CM-1208-O-CCB1",  access denied or invalid network path.)  

    The account I am using is a domain administrator, in the domain admin group.  The only way I can get push to work is to add our SCCM server to the clients admin group.  Then push works fine.  

    So its a permissions thing, but I can't figure out how to resolve it without adding our server to the domain admin group in AD.  We don't want to do this for security reasons.  

    We have not installed the Extended AD Schema; but I doubt that is the issue.  

    Can someone suggest something to help me fix this problem? What am I missing?

    Thanks

    Chad


    • Edited by Chadwicksracing Wednesday, October 29, 2014 4:34 PM Changed Title
    Tuesday, October 28, 2014 2:30 PM

Answers

  • I believe I got it working.  

    Under Client Installation Settings, I specified install properties.  Because we are opting not to use the SCCM extended AD Schema, ccmsetup would/could not locate the server via AD. 

    Once I put these properties in; it works with client push:

    SMSMP=FQDN SMSSITECODE=yoursitecode FSP=FQDN CCMLOGLEVEL=0 DNSSUFFIX=YOURDNSSERVER

    FQDN = Fully Qualified Domain Name  

    It doesn't have to be the FQDN, but for our organization, I thought it was best to use that.  You can use the Server name, or IP address in those fields.  

    Thanks all for the help



    Wednesday, October 29, 2014 4:33 PM

All replies

  • First, using a domain admin for this is a terrible practice security wise. The account simply needs to be a local admin on the target system whether is the site server's computer account or a normal user account. BTW, security wise, using the site server's computer account is the best choice because you do not have to maintain its password, the password is changed every 30 days (by default), the password is something like 180 characters long, and there is no way to interactively log in with this account.

    What does this mean: "The account I am using is a domain administrator"? The account you are using for what? Client push only uses accounts configured in the client push properties; it does not use the account of the user performing the admin activity in the console.

    Finally, Error 67 = "The network name cannot be found."

    This is not an explicit permissions issue (that would be error 5). This is a name resolution issue.

    Also, when posting errors from logs, its important to post entire relevant and unedited snippets of the logs as without the context of the activity reflected in the log, a message itself is almost always meaningless.


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

    Tuesday, October 28, 2014 2:50 PM
  • Yes the account I am using for push is a domain admin.  Yes, I am aware that the account using configuration manager is not being used to install the ccmsetup on the client machine.  

    Here is a full log of the issue:

    ======>Begin Processing request: "16777221", machine name: "CM-1208-O-CCB2"	SMS_CLIENT_CONFIG_MANAGER	10/28/2014 10:58:36 AM	13384 (0x3448)
    Execute query exec [sp_IsMPAvailable] N'SC1'	SMS_CLIENT_CONFIG_MANAGER	10/28/2014 10:58:36 AM	13384 (0x3448)
    ---> Trying each entry in the SMS Client Remote Installation account list	SMS_CLIENT_CONFIG_MANAGER	10/28/2014 10:58:36 AM	13384 (0x3448)
    ---> Attempting to connect to administrative share '\\CM-1208-O-CCB2\admin$' using account 'mccad\crazycarl'	SMS_CLIENT_CONFIG_MANAGER	10/28/2014 10:58:36 AM	13384 (0x3448)
    ---> WNetAddConnection2 failed (LOGON32_LOGON_NEW_CREDENTIALS) using account mccad\crazycarl (00000005)	SMS_CLIENT_CONFIG_MANAGER	10/28/2014 10:58:36 AM	13384 (0x3448)
    ---> Attempting to connect to administrative share '\\CM-1208-O-CCB2\admin$' using machine account.	SMS_CLIENT_CONFIG_MANAGER	10/28/2014 10:58:36 AM	13384 (0x3448)
    ---> Failed to connect to \\CM-1208-O-CCB2\admin$ using machine account (5)	SMS_CLIENT_CONFIG_MANAGER	10/28/2014 10:58:36 AM	13384 (0x3448)
    ---> ERROR: Failed to connect to the \\CM-1208-O-CCB2\admin$ share using account 'Machine Account'	SMS_CLIENT_CONFIG_MANAGER	10/28/2014 10:58:36 AM	13384 (0x3448)
    ---> Trying each entry in the SMS Client Remote Installation account list	SMS_CLIENT_CONFIG_MANAGER	10/28/2014 10:58:36 AM	13384 (0x3448)
    ---> Attempting to connect to administrative share '\\CM-1208-O-CCB2.mccad.mcc.edu\admin$' using account 'mccad\crazycarl'	SMS_CLIENT_CONFIG_MANAGER	10/28/2014 10:58:36 AM	13384 (0x3448)
    ---> WNetAddConnection2 failed (LOGON32_LOGON_NEW_CREDENTIALS) using account mccad\crazycarl (00000005)	SMS_CLIENT_CONFIG_MANAGER	10/28/2014 10:58:36 AM	13384 (0x3448)
    ---> Attempting to connect to administrative share '\\CM-1208-O-CCB2.mccad.mcc.edu\admin$' using machine account.	SMS_CLIENT_CONFIG_MANAGER	10/28/2014 10:58:36 AM	13384 (0x3448)
    ---> Failed to connect to \\CM-1208-O-CCB2.mccad.mcc.edu\admin$ using machine account (5)	SMS_CLIENT_CONFIG_MANAGER	10/28/2014 10:58:36 AM	13384 (0x3448)
    ---> ERROR: Failed to connect to the \\CM-1208-O-CCB2.mccad.mcc.edu\admin$ share using account 'Machine Account'	SMS_CLIENT_CONFIG_MANAGER	10/28/2014 10:58:36 AM	13384 (0x3448)
    ---> Trying each entry in the SMS Client Remote Installation account list	SMS_CLIENT_CONFIG_MANAGER	10/28/2014 10:58:36 AM	13384 (0x3448)
    ---> Attempting to connect to administrative share '\\CM-1208-O-CCB2\admin$' using account 'mccad\crazycarl'	SMS_CLIENT_CONFIG_MANAGER	10/28/2014 10:58:36 AM	13384 (0x3448)
    ---> WNetAddConnection2 failed (LOGON32_LOGON_NEW_CREDENTIALS) using account mccad\crazycarl (00000005)	SMS_CLIENT_CONFIG_MANAGER	10/28/2014 10:58:36 AM	13384 (0x3448)
    ---> Attempting to connect to administrative share '\\CM-1208-O-CCB2\admin$' using machine account.	SMS_CLIENT_CONFIG_MANAGER	10/28/2014 10:58:36 AM	13384 (0x3448)
    ---> Failed to connect to \\CM-1208-O-CCB2\admin$ using machine account (5)	SMS_CLIENT_CONFIG_MANAGER	10/28/2014 10:58:36 AM	13384 (0x3448)
    ---> ERROR: Failed to connect to the \\CM-1208-O-CCB2\admin$ share using account 'Machine Account'	SMS_CLIENT_CONFIG_MANAGER	10/28/2014 10:58:36 AM	13384 (0x3448)
    ---> ERROR: Unable to access target machine for request: "16777221", machine name: "CM-1208-O-CCB2",  access denied or invalid network path.	SMS_CLIENT_CONFIG_MANAGER	10/28/2014 10:58:36 AM	13384 (0x3448)
    Execute query exec [sp_CP_SetLastErrorCode] 16777221, 5	SMS_CLIENT_CONFIG_MANAGER	10/28/2014 10:58:36 AM	13384 (0x3448)
    Stored request "16777221", machine name "CM-1208-O-CCB2", in queue "Retry".	SMS_CLIENT_CONFIG_MANAGER	10/28/2014 10:58:36 AM	13384 (0x3448)
    Execute query exec [sp_CP_SetPushRequestMachineStatus] 16777221, 2	SMS_CLIENT_CONFIG_MANAGER	10/28/2014 10:58:36 AM	13384 (0x3448)
    Execute query exec [sp_CP_SetLatest] 16777221, N'10/28/2014 14:58:36', 27	SMS_CLIENT_CONFIG_MANAGER	10/28/2014 10:58:36 AM	13384 (0x3448)
    <======End request: "16777221", machine name: "CM-1208-O-CCB2".	SMS_CLIENT_CONFIG_MANAGER	10/28/2014 10:58:36 AM	13384 (0x3448)
    

    So its actually a Error 5..  So, BOTH machine account and "crazycarl" do not have permission to install.  However, "crazycarl" is in the local administrators group on the client.  hmmm

    Thank you Jason, I will suggest putting the Machine Account into the domain admin group or another elevated group we have. 

    Tuesday, October 28, 2014 3:06 PM
  • As Jason states check DNS. Does it resolve correctly for this device. 

    Also ensure you have WMI and File and Print Sharing allowed through the Windows Firewall or relevant ports allowed through firewall device.

    Can you connect to the admin$ via UNC from a Windows\Run?


    Cheers

    Paul | sccmentor.wordpress.com

    Tuesday, October 28, 2014 3:36 PM
  • OK

    check DNS. Does it resolve correctly for this device. 

    YES, it does resolve to DNS name

    Also ensure you have WMI and File and Print Sharing allowed through the Windows Firewall or relevant ports allowed through firewall device.

    All Enabled and firewall is disabled. 

    Can you connect to the admin$ via UNC from a Windows\Run?

    YES

    ---

    Paul, we tried all of those things.  WMI, Fire wall, F&PS are not the issue.  The agent refuses to install on the unless you add the Client Push Install account directly to the admin group on the local pc.  

    However, the account I am using IS a member of a AD Group, which is added to the local administrators group. What gives?

    We also added the SCCM Machine account to the same group as the the installation account.  Which are both members of a local admin account via our AD group.  

    And to recap, you can manually install the agent without a problem.  

    Tuesday, October 28, 2014 9:03 PM
  • Chad,

    I must admit I have not seen this behaviour. I would check that the account has definitely got local admin rights when you add it to the global group by logging in and performing a few admin functions.  I sounds like, for some reason, it hasn't.

    Otherwise I'd use GPO to explicitly state your push account as a local admin rather than a global group and skirt around the issue for now until you can pinpoint the exact cause.


    Cheers

    Paul | sccmentor.wordpress.com

    Wednesday, October 29, 2014 10:38 AM
  • Here is the most recent log.  

    The files copy over now, but nothing happens after that.  There is a WMI error, but I've disabled the firewall, and enabled remote WMI administration.  However, I do not think that is preventing it from installing. 

    ======>Begin Processing request: "16777221", machine name: "CM-1208-O-CCB2"	SMS_CLIENT_CONFIG_MANAGER	10/29/2014 8:04:56 AM	3348 (0x0D14)
    Execute query exec [sp_IsMPAvailable] N'SC1'	SMS_CLIENT_CONFIG_MANAGER	10/29/2014 8:04:57 AM	3348 (0x0D14)
    ---> Trying the 'best-shot' account which worked for previous CCRs (index = 0x0)	SMS_CLIENT_CONFIG_MANAGER	10/29/2014 8:04:57 AM	3348 (0x0D14)
    ---> Attempting to connect to administrative share '\\CM-1208-O-CCB2\admin$' using account 'MCCAD\chad.brower'	SMS_CLIENT_CONFIG_MANAGER	10/29/2014 8:04:57 AM	3348 (0x0D14)
    ---> The 'best-shot' account has now succeeded 15 times and failed 9 times.	SMS_CLIENT_CONFIG_MANAGER	10/29/2014 8:04:57 AM	3348 (0x0D14)
    ---> Connected to administrative share on machine CM-1208-O-CCB2 using account 'MCCAD\chad.brower'	SMS_CLIENT_CONFIG_MANAGER	10/29/2014 8:04:57 AM	3348 (0x0D14)
    ---> Attempting to make IPC connection to share <\\CM-1208-O-CCB2\IPC$>	SMS_CLIENT_CONFIG_MANAGER	10/29/2014 8:04:57 AM	3348 (0x0D14)
    ---> Searching for SMSClientInstall.* under '\\CM-1208-O-CCB2\admin$\'	SMS_CLIENT_CONFIG_MANAGER	10/29/2014 8:04:57 AM	3348 (0x0D14)
    ---> System OS version string "6.3.9600" converted to 6.30	SMS_CLIENT_CONFIG_MANAGER	10/29/2014 8:04:57 AM	3348 (0x0D14)
    Submitted request successfully	SMS_CLIENT_CONFIG_MANAGER	10/29/2014 8:04:58 AM	12600 (0x3138)
    Getting a new request from queue "Incoming" after 100 millisecond delay.	SMS_CLIENT_CONFIG_MANAGER	10/29/2014 8:04:59 AM	12600 (0x3138)
    Waiting for change in directory "C:\Program Files\Microsoft Configuration Manager\inboxes\ccr.box" for queue "Incoming", (30 minute backup timeout).	SMS_CLIENT_CONFIG_MANAGER	10/29/2014 8:04:59 AM	12600 (0x3138)
    ---> Unable to connect to WMI (root\ccm) on remote machine "CM-1208-O-CCB2", error = 0x8004100e.	SMS_CLIENT_CONFIG_MANAGER	10/29/2014 8:04:59 AM	3348 (0x0D14)
    ---> Creating \ VerifyingCopying exsistance of destination directory \\CM-1208-O-CCB2\admin$\ccmsetup.	SMS_CLIENT_CONFIG_MANAGER	10/29/2014 8:04:59 AM	3348 (0x0D14)
    ---> Copying client files to \\CM-1208-O-CCB2\admin$\ccmsetup.	SMS_CLIENT_CONFIG_MANAGER	10/29/2014 8:04:59 AM	3348 (0x0D14)
    ---> Copying file "C:\Program Files\Microsoft Configuration Manager\bin\I386\MobileClient.tcf" to "MobileClient.tcf"	SMS_CLIENT_CONFIG_MANAGER	10/29/2014 8:04:59 AM	3348 (0x0D14)
    ---> Copying file "C:\Program Files\Microsoft Configuration Manager\bin\I386\ccmsetup.exe" to "ccmsetup.exe"	SMS_CLIENT_CONFIG_MANAGER	10/29/2014 8:04:59 AM	3348 (0x0D14)
    ---> Created service "ccmsetup" on machine "CM-1208-O-CCB2".	SMS_CLIENT_CONFIG_MANAGER	10/29/2014 8:04:59 AM	3348 (0x0D14)
    ---> Started service "ccmsetup" on machine "CM-1208-O-CCB2".	SMS_CLIENT_CONFIG_MANAGER	10/29/2014 8:05:00 AM	3348 (0x0D14)
    ---> Deleting SMS Client Install Lock File '\\CM-1208-O-CCB2\admin$\SMSClientInstall.SC1'	SMS_CLIENT_CONFIG_MANAGER	10/29/2014 8:05:00 AM	3348 (0x0D14)
    Execute query exec [sp_CP_SetLastErrorCode] 16777221, 0	SMS_CLIENT_CONFIG_MANAGER	10/29/2014 8:05:00 AM	3348 (0x0D14)
    ---> Completed request "16777221", machine name "CM-1208-O-CCB2".	SMS_CLIENT_CONFIG_MANAGER	10/29/2014 8:05:00 AM	3348 (0x0D14)
    Deleted request "16777221", machine name "CM-1208-O-CCB2"	SMS_CLIENT_CONFIG_MANAGER	10/29/2014 8:05:00 AM	3348 (0x0D14)
    Execute query exec [sp_CP_SetPushRequestMachineStatus] 16777221, 4	SMS_CLIENT_CONFIG_MANAGER	10/29/2014 8:05:00 AM	3348 (0x0D14)
    Execute query exec [sp_CP_SetLatest] 16777221, N'10/29/2014 12:05:00', 48	SMS_CLIENT_CONFIG_MANAGER	10/29/2014 8:05:00 AM	3348 (0x0D14)
    <======End request: "16777221", machine name: "CM-1208-O-CCB2".	SMS_CLIENT_CONFIG_MANAGER	10/29/2014 8:05:00 AM	3348 (0x0D14)
    

    Here is the log from the client machine.  Now it seems it can't find the DP..  Would this have anything to do with not having AD Schema extended or just a DNS problem?

    ==========[ ccmsetup started in process 2020 ]==========	ccmsetup	10/29/2014 8:05:00 AM	4024 (0x0FB8)
    Running on platform X64	ccmsetup	10/29/2014 8:05:00 AM	4024 (0x0FB8)
    Launch from folder C:\windows\ccmsetup\	ccmsetup	10/29/2014 8:05:00 AM	4024 (0x0FB8)
    CcmSetup version: 5.0.7958.1000	ccmsetup	10/29/2014 8:05:00 AM	4024 (0x0FB8)
    In ServiceMain	ccmsetup	10/29/2014 8:05:00 AM	3036 (0x0BDC)
    Running on 'Microsoft Windows 8.1 Enterprise' (6.3.9600). Service Pack (0.0). SuiteMask = 272. Product Type = 18	ccmsetup	10/29/2014 8:05:00 AM	3036 (0x0BDC)
    Ccmsetup command line: "C:\windows\ccmsetup\ccmsetup.exe" /runservice /config:MobileClient.tcf	ccmsetup	10/29/2014 8:05:00 AM	3036 (0x0BDC)
    Command line parameters for ccmsetup have been specified.  No registry lookup for command line parameters is required.	ccmsetup	10/29/2014 8:05:00 AM	3036 (0x0BDC)
    Command line: "C:\windows\ccmsetup\ccmsetup.exe" /runservice /config:MobileClient.tcf	ccmsetup	10/29/2014 8:05:00 AM	3036 (0x0BDC)
    SslState value: 224	ccmsetup	10/29/2014 8:05:00 AM	3036 (0x0BDC)
    CCMHTTPPORT:    80	ccmsetup	10/29/2014 8:05:00 AM	3036 (0x0BDC)
    CCMHTTPSPORT:    443	ccmsetup	10/29/2014 8:05:00 AM	3036 (0x0BDC)
    CCMHTTPSSTATE:    224	ccmsetup	10/29/2014 8:05:00 AM	3036 (0x0BDC)
    CCMHTTPSCERTNAME:    	ccmsetup	10/29/2014 8:05:00 AM	3036 (0x0BDC)
    FSP:    SOURCREAM	ccmsetup	10/29/2014 8:05:00 AM	3036 (0x0BDC)
    CCMFIRSTCERT:    1	ccmsetup	10/29/2014 8:05:00 AM	3036 (0x0BDC)
    Config file:      C:\windows\ccmsetup\MobileClientUnicode.tcf	ccmsetup	10/29/2014 8:05:00 AM	3036 (0x0BDC)
    Retry time:       10 minute(s)	ccmsetup	10/29/2014 8:05:00 AM	3036 (0x0BDC)
    MSI log file:     C:\windows\ccmsetup\Logs\client.msi.log	ccmsetup	10/29/2014 8:05:00 AM	3036 (0x0BDC)
    MSI properties:    INSTALL="ALL" FSP="SOURCREAM" SMSSITECODE="SC1" CCMLOGLEVEL="0" CCMHTTPPORT="80" CCMHTTPSPORT="443" CCMHTTPSSTATE="224" CCMFIRSTCERT="1"	ccmsetup	10/29/2014 8:05:00 AM	3036 (0x0BDC)
    Source List:	ccmsetup	10/29/2014 8:05:00 AM	3036 (0x0BDC)
                      \\SOURCREAM.mccad.mcc.edu\SMSClient	ccmsetup	10/29/2014 8:05:00 AM	3036 (0x0BDC)
                      \\SOURCREAM.MCCAD.MCC.EDU\SMSClient	ccmsetup	10/29/2014 8:05:00 AM	3036 (0x0BDC)
    MPs:	ccmsetup	10/29/2014 8:05:00 AM	3036 (0x0BDC)
                      SOURCREAM.mccad.mcc.edu	ccmsetup	10/29/2014 8:05:00 AM	3036 (0x0BDC)
    MapNLMCostDataToCCMCost() returning Cost 0x1	ccmsetup	10/29/2014 8:05:00 AM	3036 (0x0BDC)
    No version of the client is currently detected.	ccmsetup	10/29/2014 8:05:00 AM	3036 (0x0BDC)
    Folder 'Microsoft\Configuration Manager' not found. Task does not exist.	ccmsetup	10/29/2014 8:05:00 AM	3036 (0x0BDC)
    Updated security on object C:\windows\ccmsetup\.	ccmsetup	10/29/2014 8:05:00 AM	3036 (0x0BDC)
    Sending Fallback Status Point message to 'SOURCREAM', STATEID='100'.	ccmsetup	10/29/2014 8:05:00 AM	3036 (0x0BDC)
    Failed to get client version for sending messages to FSP. Error 0x8004100e	ccmsetup	10/29/2014 8:05:00 AM	3036 (0x0BDC)
    Params to send FSP message '5.0.7958.1000 Deployment '	ccmsetup	10/29/2014 8:05:00 AM	3036 (0x0BDC)
    receiving response with winhttp failed; 80072efe	FSPStateMessage	10/29/2014 8:05:21 AM	3036 (0x0BDC)
    Running as user "SYSTEM"	ccmsetup	10/29/2014 8:05:21 AM	3036 (0x0BDC)
    Detected 211154 MB free disk space on system drive.	ccmsetup	10/29/2014 8:05:21 AM	3036 (0x0BDC)
    Checking Write Filter Status.	ccmsetup	10/29/2014 8:05:21 AM	3036 (0x0BDC)
    This is not a supported write filter device. We are not in a write filter maintenance mode.	ccmsetup	10/29/2014 8:05:21 AM	3036 (0x0BDC)
    Performing AD query: '(&(ObjectCategory=mSSMSManagementPoint)(mSSMSDefaultMP=TRUE)(mSSMSSiteCode=SC1))'	ccmsetup	10/29/2014 8:05:21 AM	3036 (0x0BDC)
    Retrieved 0 MP records from AD for site 'SC1'	ccmsetup	10/29/2014 8:05:21 AM	3036 (0x0BDC)
    Failed to get site version from AD with error 0x87d00215	ccmsetup	10/29/2014 8:05:21 AM	3036 (0x0BDC)
    Sending message header '<Msg SchemaVersion="1.1"><ID>{5CAF943A-27EE-405F-873C-4CBA5D6BE2EB}</ID><SourceHost>CM-1208-O-CCB2</SourceHost><TargetAddress>mp:[http]MP_LocationManager</TargetAddress><ReplyTo>direct:CM-1208-O-CCB2:LS_ReplyLocations</ReplyTo><Priority>3</Priority><Timeout>600</Timeout><ReqVersion>5931</ReqVersion><TargetHost>SOURCREAM.mccad.mcc.edu</TargetHost><TargetEndpoint>MP_LocationManager</TargetEndpoint><ReplyMode>Sync</ReplyMode><Protocol>http</Protocol><SentTime>2014-10-29T12:05:21Z</SentTime><Body Type="ByteRange" Offset="0" Length="186"/><Hooks><Hook3 Name="zlib-compress"/></Hooks><Payload Type="inline"/></Msg>'	ccmsetup	10/29/2014 8:05:21 AM	3036 (0x0BDC)
    MapNLMCostDataToCCMCost() returning Cost 0x1	ccmsetup	10/29/2014 8:05:21 AM	3036 (0x0BDC)
    CCM_POST 'HTTP://SOURCREAM.mccad.mcc.edu/ccm_system/request'	ccmsetup	10/29/2014 8:05:21 AM	3036 (0x0BDC)
    Failed to get site version from MP 'SOURCREAM.mccad.mcc.edu' with error 0x80072efe	ccmsetup	10/29/2014 8:05:42 AM	3036 (0x0BDC)
    SiteCode:         SC1	ccmsetup	10/29/2014 8:05:42 AM	3036 (0x0BDC)
    SiteVersion:      	ccmsetup	10/29/2014 8:05:42 AM	3036 (0x0BDC)
    Only one MP SOURCREAM.mccad.mcc.edu is specified. Use it.	ccmsetup	10/29/2014 8:05:42 AM	3036 (0x0BDC)
    Searching for DP locations from MP(s)...	ccmsetup	10/29/2014 8:05:42 AM	3036 (0x0BDC)
    Current AD site of machine is CM1143A	LocationServices	10/29/2014 8:05:42 AM	3036 (0x0BDC)
    Local Machine is joined to an AD domain	LocationServices	10/29/2014 8:05:42 AM	3036 (0x0BDC)
    Current AD forest name is mccad.mcc.edu, domain name is mccad.mcc.edu	LocationServices	10/29/2014 8:05:42 AM	3036 (0x0BDC)
    DhcpGetOriginalSubnetMask entry point is supported.	LocationServices	10/29/2014 8:05:42 AM	3036 (0x0BDC)
    Begin checking Alternate Network Configuration	LocationServices	10/29/2014 8:05:42 AM	3036 (0x0BDC)
    Finished checking Alternate Network Configuration	LocationServices	10/29/2014 8:05:42 AM	3036 (0x0BDC)
    Adapter {5899829D-895E-430B-B150-63FE6989E4B9} is DHCP enabled. Checking quarantine status.	LocationServices	10/29/2014 8:05:42 AM	3036 (0x0BDC)
    Sending message body '<ContentLocationRequest SchemaVersion="1.00">
      <AssignedSite SiteCode="SC1"/>
      <ClientPackage/>
      <ClientLocationInfo LocationType="SMSPACKAGE" DistributeOnDemand="0" UseProtected="0" AllowCaching="0" BranchDPFlags="0" AllowHTTP="1" AllowSMB="0" AllowMulticast="0" UseInternetDP="0">
        <ADSite Name="CM1143A"/>
        <Forest Name="mccad.mcc.edu"/>
        <Domain Name="mccad.mcc.edu"/>
        <IPAddresses>
    <IPAddress SubnetAddress="10.26.0.0" Address="10.26.2.57"/>
        </IPAddresses>
      </ClientLocationInfo>
    </ContentLocationRequest>
    '	ccmsetup	10/29/2014 8:05:42 AM	3036 (0x0BDC)
    Sending message header '<Msg SchemaVersion="1.1"><ID>{42770D1B-3371-412E-9726-887C2BA3B2EA}</ID><SourceHost>CM-1208-O-CCB2</SourceHost><TargetAddress>mp:[http]MP_LocationManager</TargetAddress><ReplyTo>direct:CM-1208-O-CCB2:LS_ReplyLocations</ReplyTo><Priority>3</Priority><Timeout>600</Timeout><ReqVersion>5931</ReqVersion><TargetHost>SOURCREAM.mccad.mcc.edu</TargetHost><TargetEndpoint>MP_LocationManager</TargetEndpoint><ReplyMode>Sync</ReplyMode><Protocol>http</Protocol><SentTime>2014-10-29T12:05:42Z</SentTime><Body Type="ByteRange" Offset="0" Length="1090"/><Hooks><Hook3 Name="zlib-compress"/></Hooks><Payload Type="inline"/></Msg>'	ccmsetup	10/29/2014 8:05:42 AM	3036 (0x0BDC)
    MapNLMCostDataToCCMCost() returning Cost 0x1	ccmsetup	10/29/2014 8:05:42 AM	3036 (0x0BDC)
    CCM_POST 'HTTP://SOURCREAM.mccad.mcc.edu/ccm_system/request'	ccmsetup	10/29/2014 8:05:42 AM	3036 (0x0BDC)
    GetDPLocations failed with error 0x80072efe	ccmsetup	10/29/2014 8:06:04 AM	3036 (0x0BDC)
    Failed to get DP locations as the expected version from MP 'SOURCREAM.mccad.mcc.edu'. Error 0x80072efe	ccmsetup	10/29/2014 8:06:04 AM	3036 (0x0BDC)
    Sending Fallback Status Point message to 'SOURCREAM', STATEID='101'.	ccmsetup	10/29/2014 8:06:04 AM	3036 (0x0BDC)
    Failed to get client version for sending messages to FSP. Error 0x8004100e	ccmsetup	10/29/2014 8:06:04 AM	3036 (0x0BDC)
    Params to send FSP message '5.0.7958.1000 Deployment '	ccmsetup	10/29/2014 8:06:04 AM	3036 (0x0BDC)
    receiving response with winhttp failed; 80072efe	FSPStateMessage	10/29/2014 8:06:25 AM	3036 (0x0BDC)
    Next retry in 10 minute(s)...	ccmsetup	10/29/2014 8:06:25 AM	3036 (0x0BDC)
    

    Wednesday, October 29, 2014 12:16 PM
  • The first log file above clearly shows that ccmsetup was properly staged and started by the client push process which makes the client push process successful.

    The second log shows an error code of 0x80072efe during DP lookup which means "The connection with the server was terminated abnormally". This is indicative of a network, server, or other environmental issue outside the control of anything that ccmsetup is doing. You'll have to get other folks involved to figure out why the communication is not successful including potentially setting up a network trace.


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

    Wednesday, October 29, 2014 12:43 PM
  • I tried to reach the web address http://sourcream/CCM_CLIENT/  and it cannot be reached that from the client computer.  

    Thanks Jason, I will get with the network guys.  

    Wednesday, October 29, 2014 12:51 PM
  • I believe I got it working.  

    Under Client Installation Settings, I specified install properties.  Because we are opting not to use the SCCM extended AD Schema, ccmsetup would/could not locate the server via AD. 

    Once I put these properties in; it works with client push:

    SMSMP=FQDN SMSSITECODE=yoursitecode FSP=FQDN CCMLOGLEVEL=0 DNSSUFFIX=YOURDNSSERVER

    FQDN = Fully Qualified Domain Name  

    It doesn't have to be the FQDN, but for our organization, I thought it was best to use that.  You can use the Server name, or IP address in those fields.  

    Thanks all for the help



    Wednesday, October 29, 2014 4:33 PM
  • A few side note:

    - DNSSUFFIX is used to help the client locate the MP using DNS so if you haven't added any DNS records for this, this property is meaningless

    - SMSSLP is no longer valid in 2012

    - CCMLOGLEVEL of 0 is excessive IMO. I have never had to enable this to troubleshoot normal issues.


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

    Wednesday, October 29, 2014 4:38 PM
  • One more side question: Why not extend the schema? It's done  by overwhelming majority of folks using ConfigMgr and is completely benign.

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


    Wednesday, October 29, 2014 4:39 PM
  • A few side note:

    - DNSSUFFIX is used to help the client locate the MP using DNS so if you haven't added any DNS records for this, this property is meaningless

    - SMSSLP is no longer valid in 2012

    - CCMLOGLEVEL of 0 is excessive IMO. I have never had to enable this to troubleshoot normal issues.


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

    DNSSUXFIX = I added it because our DNS server is shaky

    SMSLP = will remove. LOL Just following MS Documentation..

    CCMLOGLEVEL = there by default..

    Wednesday, October 29, 2014 4:45 PM
  • One more side question: Why not extend the schema? It's done  by overwhelming majority of folks using ConfigMgr and is completely benign.

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


    I know, and it would have made this so much easier.  But our organization is extremely protective of any kind of changes to AD.  And, there should be some kind of documentation out there, IF you don't use it.  I guess now there is..
    Wednesday, October 29, 2014 4:47 PM
  • For DNSSUFFIX though, it has nothing to do with your DNS server or general DNS usage. As mentioned, its specifically used by the client agent to lookup up a specific locator record in DNS which in turn allows the client to discover an MP. If you haven't published this record, then its useless.

    Someone must have added CCMLOGLEVEL because it is not there by default.


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

    Wednesday, October 29, 2014 5:54 PM
  • Yeah, I believe that the record is published.  At least when I checked it last.  

    Heh, I swear to you that CCMLOGLEVEL was there when I started to configure SCCM and I am the only one who has been working on this project. 

    Again, thank you for the time and information.  It has been extremely helpful in my learning process. 

    Wednesday, October 29, 2014 9:10 PM