locked
Can't push install clients in 2012 R2 help pls RRS feed

  • Question

  • Hi,

    I'm at the headache point already :)

    Trying to push install the client, so far i found lots of blogs about checking the account in the Site - Client Installation Settings... witch i tried domain admins, administrators... and yes i added those and the server computer account to the local admins.

    -I also have a distribution points in a group and boundaries in boundary groups (all linked to each other)
    -I have tried to verify and redistribute the client package
    -changed the C:\Windows\System32\inetsrv\config\schema\webdav_schema like mentionned in a thread
    -disabled the firewall on the client and created a GPO that allows in and out for filesharing and wmi
    -successfully tested access to WMI with wmitest.exe
     I still get this:

    ---> Searching for SMSClientInstall.* under '\\MOMSTIN003\admin$\' SMS_CLIENT_CONFIG_MANAGER 2014-05-22 2:37:54 PM 2560 (0x0A00)
    ---> System OS version string "6.3.9600" converted to 6.30 SMS_CLIENT_CONFIG_MANAGER 2014-05-22 2:37:54 PM 2560 (0x0A00)
    ---> Unable to connect to WMI (root\ccm) on remote machine "MOMSTIN003", error = 0x8004100e. SMS_CLIENT_CONFIG_MANAGER 2014-05-22 2:37:54 PM 2560 (0x0A00)
    ---> Creating \ VerifyingCopying exsistance of destination directory \\MOMSTIN003\admin$\ccmsetup. SMS_CLIENT_CONFIG_MANAGER 2014-05-22 2:37:54 PM 2560 (0x0A00)
    ---> Copying client files to \\MOMSTIN003\admin$\ccmsetup. SMS_CLIENT_CONFIG_MANAGER 2014-05-22 2:37:54 PM 2560 (0x0A00)
    ---> Copying file "C:\Program Files\Microsoft Configuration Manager\bin\I386\ccmsetup.exe" to "ccmsetup.exe" SMS_CLIENT_CONFIG_MANAGER 2014-05-22 2:37:55 PM 2560 (0x0A00)
    ---> ForceReinstall flag is set to true SMS_CLIENT_CONFIG_MANAGER 2014-05-22 2:37:55 PM 2560 (0x0A00)
    ---> Updated service "ccmsetup" on machine "MOMSTIN003". SMS_CLIENT_CONFIG_MANAGER 2014-05-22 2:38:10 PM 2560 (0x0A00)
    ---> Started service "ccmsetup" on machine "MOMSTIN003". SMS_CLIENT_CONFIG_MANAGER 2014-05-22 2:38:10 PM 2560 (0x0A00)
    ---> Deleting SMS Client Install Lock File '\\MOMSTIN003\admin$\SMSClientInstall.MOM' SMS_CLIENT_CONFIG_MANAGER 2014-05-22 2:38:10 PM 2560 (0x0A00)
    Execute query exec [sp_CP_SetLastErrorCode] 2097152002, 0 SMS_CLIENT_CONFIG_MANAGER 2014-05-22 2:38:10 PM 2560 (0x0A00)
    ---> Completed request "2097152002", machine name "MOMSTIN003". SMS_CLIENT_CONFIG_MANAGER 2014-05-22 2:38:10 PM 2560 (0x0A00)
    Deleted request "2097152002", machine name "MOMSTIN003" SMS_CLIENT_CONFIG_MANAGER 2014-05-22 2:38:10 PM 2560 (0x0A00)
    Execute query exec [sp_CP_SetPushRequestMachineStatus] 2097152002, 4 SMS_CLIENT_CONFIG_MANAGER 2014-05-22 2:38:10 PM 2560 (0x0A00)
    Execute query exec [sp_CP_SetLatest] 2097152002, N'05/22/2014 18:38:10', 51 SMS_CLIENT_CONFIG_MANAGER 2014-05-22 2:38:10 PM 2560 (0x0A00)
    <======End request: "2097152002", machine name: "MOMSTIN003". SMS_CLIENT_CONFIG_MANAGER 2014-05-22 2:38:10 PM 2560 (0x0A00)

    Any pointers would help... Thx

    Thursday, May 22, 2014 6:39 PM

All replies

  • Hi

    A few entries from a log file doesn´t really help. You should examine the ccm.log file on the site server and post it here when you have performed a client push. You will find it in Drive:\Program Files\Microsoft Configuration Manager\Logs Where Drive is the drive you have installed ConfigMgr

    Just paste in from the ccm.log from where it starts with:

    ======>Begin Processing request: "2097152002", machine name: "Name of Computer you are tryiung to push the client to"

    You should also look on the client and check to see weather the ccmsetup.log log file exists in C:\Windows\ccmsetup

    If it does exist then it will include information why the client installation failed.

    Thursday, May 22, 2014 6:53 PM
  • Client push was able to create the ccmsetup service on the client according to the log you posted. Next: examine ccmsetup.log on the client.

    Torsten Meringer | http://www.mssccmfaq.de

    Friday, May 23, 2014 6:32 AM
  • Also, what's the target operating system on the client?

    Friday, May 23, 2014 6:52 AM
  • ---> System OS version string "6.3.9600" converted to 6.30


    The target OS is already listed in the log ...

    Torsten Meringer | http://www.mssccmfaq.de

    Friday, May 23, 2014 6:56 AM
  • Copying client files to \\MOMSTIN003\admin$\ccmsetup. SMS_CLIENT_CONFIG_MANAGER 2014-05-22 2:37:54 PM 2560 (0x0A00)
    --->Copying file "C:\Program Files\Microsoft Configuration Manager\bin\I386\ccmsetup.exe" to "ccmsetup.exe"

    ---> Completed request "2097152002", machine name "MOMSTIN003". SMS_CLIENT_CONFIG_MANAGER 2014-05-22 2:38:10 PM 2560 (0x0A00)
    Deleted request "2097152002", machine name "MOMSTIN003" SMS_CLIENT_CONFIG_MANAGER 2014-05-22 2:38:10 PM 2560 (0x0A00)

    The log file shows the client agent has been installed. Is it not showing up in the CM Console ?


    Prajwal Desai, http://prajwaldesai.com

    Friday, May 23, 2014 6:59 AM
  • Alright thx all for the answers,

    So what i did here was to create a new application from my new server pointing to the share of our old server, and it worked.   so the problem is either with the share, distribution point or package i guess??

    i have to get rid of the old server of course so this has to work

    Here are the logs on my pc before i pushed from our old server:

    <![LOG[Received reply body '<ContentLocationReply SchemaVersion="1.00"><ContentInfo PackageFlags=""><ContentHashValues/></ContentInfo><Sites><Site><MPSite SiteCode="MOM" MasterSiteCode="MOM" SiteLocality="LOCAL" IISPreferedPort="" IISSSLPreferedPort=""/><LocationRecords/></Site></Sites><ClientPackage FullPackageID="MOM00003" FullPackageVersion="1" FullPackageHash="55E1F6C3CFA20792F65363CEF017C1377AF84C6920F1D508A47BF74211014B55" MinimumClientVersion="5.00.7958.1000" RandomizeMaxDays="7" ProgramEnabled="false" LastModifiedTime="30373068;4140815872" SiteVersionMatch="true" SiteVersion="5.00.7958.1000" EnablePeerCache="true"/><RelatedContentIDs/></ContentLocationReply>']LOG]!><time="09:36:53.754+240" date="05-22-2014" component="ccmsetup" context="" type="0" thread="6752" file="siteinfo.cpp:221">
    <![LOG[Failed to get DP locations as the expected version from MP 'PAD-I13.montfort.corp.on.ca'. Error 0x87d00215]LOG]!><time="09:36:53.754+240" date="05-22-2014" component="ccmsetup" context="" type="2" thread="6752" file="ccmsetup.cpp:11261">
    <![LOG[MP 'PAD-I13.montfort.corp.on.ca' didn't return DP locations for client package with the expected version. Retrying in 30 minutes.]LOG]!><time="09:36:53.754+240" date="05-22-2014" component="ccmsetup" context="" type="2" thread="6752" file="ccmsetup.cpp:11087">
    <![LOG[Next retry in 30 minute(s)...]LOG]!><time="09:36:53.754+240" date="05-22-2014" component="ccmsetup" context="" type="0" thread="6752" file="ccmsetup.cpp:8835">
    <![LOG[Current AD forest name is montfort.corp.on.ca, domain name is montfort.corp.on.ca]LOG]!><time="10:06:54.001+240" date="05-22-2014" component="LocationServices" context="" type="1" thread="6752" file="lsad.cpp:842">
    <![LOG[Domain joined client is in Intranet]LOG]!><time="10:06:54.002+240" date="05-22-2014" component="LocationServices" context="" type="1" thread="6752" file="lsad.cpp:1047">
    <![LOG[Current AD site of machine is MONTFORT]LOG]!><time="10:06:54.105+240" date="05-22-2014" component="LocationServices" context="" type="1" thread="6752" file="lsad.cpp:770">
    <![LOG[DHCP entry points already initialized.]LOG]!><time="10:06:54.114+240" date="05-22-2014" component="LocationServices" context="" type="0" thread="6752" file="ccmiputil.cpp:75">
    <![LOG[Begin checking Alternate Network Configuration]LOG]!><time="10:06:54.114+240" date="05-22-2014" component="LocationServices" context="" type="0" thread="6752" file="ccmiputil.cpp:1095">
    <![LOG[Finished checking Alternate Network Configuration]LOG]!><time="10:06:54.116+240" date="05-22-2014" component="LocationServices" context="" type="0" thread="6752" file="ccmiputil.cpp:1172">
    <![LOG[Adapter {E8115CFD-EB6B-470C-916C-E6ACC2E63EE2} is DHCP enabled. Checking quarantine status.]LOG]!><time="10:06:54.120+240" date="05-22-2014" component="LocationServices" context="" type="0" thread="6752" file="ccmiputil.cpp:436">
    <![LOG[Adapter {F861C18F-9AA6-4FA3-86DF-606457577BA7} is DHCP enabled. Checking quarantine status.]LOG]!><time="10:06:54.121+240" date="05-22-2014" component="LocationServices" context="" type="0" thread="6752" file="ccmiputil.cpp:436">
    <![LOG[Adapter {26B5AE9A-831C-49A3-A4E9-7A05053E8CF1} is DHCP enabled. Checking quarantine status.]LOG]!><time="10:06:54.121+240" date="05-22-2014" component="LocationServices" context="" type="0" thread="6752" file="ccmiputil.cpp:436">
    <![LOG[Adapter {2177D51C-0191-447C-8898-73D4E9B6C680} is DHCP enabled. Checking quarantine status.]LOG]!><time="10:06:54.121+240" date="05-22-2014" component="LocationServices" context="" type="0" thread="6752" file="ccmiputil.cpp:436">
    <![LOG[Sending message body '<ContentLocationRequest SchemaVersion="1.00">

    Friday, May 23, 2014 10:40 AM
  • So what i did here was to create a new application from my new server pointing to the share of our old server, and it worked.   so the problem is either with the share, distribution point or package i guess??

    What has creating an application to do with client push? Where's the connection?

    Plus the logfile does not contain an error.


    Torsten Meringer | http://www.mssccmfaq.de

    Friday, May 23, 2014 11:35 AM
  • The application i created IS the client, and the default client IS an application.

    Friday, May 23, 2014 3:18 PM