locked
Can't install client via push RRS feed

  • Question

  • So I've got SCCM 2007 R3 running.  I'm in the process of upgrading all our users machines.  All of the machines show up in AD and I've assigned them to the exact same groups as their old machines were once I swapped them out.  Now in SCCM for the new clients it shows client=no and approved it shows N/A.  If I right client the client and choose Install Client or choose the Install SCCM Client option I get a CMD window that pops up and it looks like its doing something.  After it goes away the client still shows as no and N/A in the console.  I checked the ccm.log file on the server, but I don't see anything wrong, says The request was completed for the computer I chose.  Any ideas on whats going on?  I'm using mixed mode and auto approve for computers in trusted domain.  Thanks
    Wednesday, February 6, 2013 10:04 PM

Answers

  • The "Install SCCM Client" option is not a real ConfigMgr option and was added by the right-click tools. The reason a command windows pops up is because its just running a script (vis psexec) that directly connects to the remote system and initiates ccmsetup. It can fail for many reasons including permissions.

    As for the real "Install CLient" ConfigMgr option, you need to trace the progress of the client install request using ccm.log and and then ccmsetup.log on the client. In ccm.log, just because it says request completed does not mean everything was OK. Typically, you need to look for a line that says ccmsetup started on the target system.

    The most common issues when using client push are lack of permissions or firewalls.


    Jason | http://blog.configmgrftw.com

    • Proposed as answer by nabin777 Thursday, February 7, 2013 9:23 AM
    • Marked as answer by Yog Li Friday, March 1, 2013 10:16 AM
    Wednesday, February 6, 2013 10:16 PM
  • hello billy

    as Jason said for client push you need to have certain permissions in client machines ,if those condition dont met then there will problem

    first of all check weather u can acess clients with Admin$ share (example: \\clientname\\Admin$) from sccm server, there should be At least one Client Push Installation account must be defined in the Accounts tab of the Client Push Installation Properties dialog box. This account must be a member of the local Administrators group.

    There should be no DNS issue  for more check this out.

    http://blogs.technet.com/b/sudheesn/archive/2010/05/31/troubleshooting-sccm-part-i-client-push-installation.aspx

    • Proposed as answer by nabin777 Thursday, February 7, 2013 9:23 AM
    • Marked as answer by Yog Li Friday, March 1, 2013 10:16 AM
    Thursday, February 7, 2013 9:23 AM

All replies

  • Forgot to mention that if I manually run the ccmsetup on the client it works just fine.  I'm running SEP on the clients, but I even tried to completely remove SEP from the client and push it again and it still didn't work.  Only thing thats worked for me is to manually run the ccmsetup on each client.  Thanks
    Wednesday, February 6, 2013 10:12 PM
  • The "Install SCCM Client" option is not a real ConfigMgr option and was added by the right-click tools. The reason a command windows pops up is because its just running a script (vis psexec) that directly connects to the remote system and initiates ccmsetup. It can fail for many reasons including permissions.

    As for the real "Install CLient" ConfigMgr option, you need to trace the progress of the client install request using ccm.log and and then ccmsetup.log on the client. In ccm.log, just because it says request completed does not mean everything was OK. Typically, you need to look for a line that says ccmsetup started on the target system.

    The most common issues when using client push are lack of permissions or firewalls.


    Jason | http://blog.configmgrftw.com

    • Proposed as answer by nabin777 Thursday, February 7, 2013 9:23 AM
    • Marked as answer by Yog Li Friday, March 1, 2013 10:16 AM
    Wednesday, February 6, 2013 10:16 PM
  • The permissions seems correct, using the exact same admin account I always have in the past.  Again I've removed all firewalls for testing purposes and still get nothing.  Where is the ccmsetup.log file located on the client? 

    One detail that might help is all these computers were ghosted so not sure if that makes a difference or not.

    Wednesday, February 6, 2013 10:25 PM
  • Was the ConfigMgr client installed and assigned on your Ghost image(s)?  If so, then you'll have problems with duplicate guids.  You can find the ccmsetup.log file at

    x86 - c:\windows\system32\ccmsetup

    x64 - c:\windows\ccmsetup


    Nick Moseley | http://t3chn1ck.wordpress.com

    Thursday, February 7, 2013 1:15 AM
  • hello billy

    as Jason said for client push you need to have certain permissions in client machines ,if those condition dont met then there will problem

    first of all check weather u can acess clients with Admin$ share (example: \\clientname\\Admin$) from sccm server, there should be At least one Client Push Installation account must be defined in the Accounts tab of the Client Push Installation Properties dialog box. This account must be a member of the local Administrators group.

    There should be no DNS issue  for more check this out.

    http://blogs.technet.com/b/sudheesn/archive/2010/05/31/troubleshooting-sccm-part-i-client-push-installation.aspx

    • Proposed as answer by nabin777 Thursday, February 7, 2013 9:23 AM
    • Marked as answer by Yog Li Friday, March 1, 2013 10:16 AM
    Thursday, February 7, 2013 9:23 AM
  • The client was not installed prior to ghosting the machines.  They just had the OS and all microsoft updates installed and that was it.  As for the user account I am using the domain administrator account to push the client on all the machines.  It works on some and does not on the others.  I can not get to the \\hostname\Admin$ on any of the computers who do not already have the client installed.  If I manually install the client on the computer I can then access it via the \\hostname\Admin$ from the SCCM server, but not until I install the client.
    Thursday, February 7, 2013 5:28 PM
  • Then you will want to enable the admin share via GPO.  This is a requirement for client push.

    Nick Moseley | http://t3chn1ck.wordpress.com

    Thursday, February 7, 2013 5:33 PM
  • Have you setup boundaries for your environment?

    A good guide for troubleshooting client push problems - http://blogs.technet.com/b/sudheesn/archive/2010/05/31/troubleshooting-sccm-part-i-client-push-installation.aspx

    Saturday, February 9, 2013 2:41 PM
  • Did you get a chance to check thi : http://blogs.technet.com/b/sudheesn/archive/2010/05/31/troubleshooting-sccm-part-i-client-push-installation.aspx
    Tuesday, February 12, 2013 3:18 PM