We've had a 'Green field' install of SCCM 2007 R2. Out of the 8000 odd computers in our estate, 4500 have now been migrated to the new AD domain. We had / have SMS in the old domains. All computers that have been migrated to the new domain 'should' get the SCCM client through client push. These 4500 odd computers now appear within 'All Systems' in SCCM. We are using AD system discovery. However out of the 4500 computers only 2500 are showing as having the SCCM client. Client push install has been turned on in all th sites with "SMSSiteCode=AUTO". There is a service account (svc-sccm002) that is setup for client push which has local admin rights on all the computers in the estate. This service account is not disabled. I have been trying for last few weeks to find out why client push does not work on half of our estate but havent had much luck. The following entries are from the ccm.log file of one of the secondary sccm servers for one of the computers that hasnt got the sccm client but I am able to unc to the C$ and admin$ share of this computer. ======>Begin Processing request: "10_19_8_61.CENTRA", machine name: "PC-5P1-007869" SMS_CLIENT_CONFIG_MANAGER 26/03/2012 08:58:02 5348 (0x14E4) ---> Trying the 'best-shot' account which worked for previous CCRs (index = 0x0) SMS_CLIENT_CONFIG_MANAGER 26/03/2012 08:58:02 5348 (0x14E4) ---> Attempting to connect to administrative share '\\10.19.8.61\admin$' using account 'centra\svc-sccm002' SMS_CLIENT_CONFIG_MANAGER 26/03/2012 08:58:02 5348 (0x14E4) ---> The 'best-shot' account has now succeeded 1 times and failed 0 times. SMS_CLIENT_CONFIG_MANAGER 26/03/2012 08:58:03 5348 (0x14E4) ---> Connected to administrative share on machine 10.19.8.61 using account 'centra\svc-sccm002' SMS_CLIENT_CONFIG_MANAGER 26/03/2012 08:58:03 5348 (0x14E4) ---> Attempting to make IPC connection to share <\\10.19.8.61\IPC$> SMS_CLIENT_CONFIG_MANAGER 26/03/2012 08:58:03 5348 (0x14E4) ---> Searching for SMSClientInstall.* under '\\10.19.8.61\admin$\' SMS_CLIENT_CONFIG_MANAGER 26/03/2012 08:58:03 5348 (0x14E4) ---> WNetAddConnection2 failed (LOGON32_LOGON_NEW_CREDENTIALS) using account centra\svc-sccm002 (00000035) SMS_CLIENT_CONFIG_MANAGER 26/03/2012 08:58:03 5300 (0x14B4) ---> Lost local access after ImpersonateLoggedOnUser (LOGON32_LOGON_INTERACTIVE) using account centra\svc-sccm002 SMS_CLIENT_CONFIG_MANAGER 26/03/2012 08:58:03 5300 (0x14B4) ---> Trying the 'best-shot' account which worked for previous CCRs (index = 0x0) SMS_CLIENT_CONFIG_MANAGER 26/03/2012 08:58:03 5300 (0x14B4) ---> Attempting to connect to administrative share '\\10.19.12.37\admin$' using account 'centra\svc-sccm002' SMS_CLIENT_CONFIG_MANAGER 26/03/2012 08:58:03 5300 (0x14B4) ---> WNetAddConnection2 failed (LOGON32_LOGON_NEW_CREDENTIALS) using account centra\svc-sccm002 (00000035) SMS_CLIENT_CONFIG_MANAGER 26/03/2012 08:58:03 5300 (0x14B4) ---> Lost local access after ImpersonateLoggedOnUser (LOGON32_LOGON_INTERACTIVE) using account centra\svc-sccm002 SMS_CLIENT_CONFIG_MANAGER 26/03/2012 08:58:03 5300 (0x14B4) ---> The 'best-shot' account has now succeeded 1 times and failed 1 times. SMS_CLIENT_CONFIG_MANAGER 26/03/2012 08:58:03 5300 (0x14B4) ---> Trying each entry in the SMS Client Remote Installation account list SMS_CLIENT_CONFIG_MANAGER 26/03/2012 08:58:03 5300 (0x14B4) ---> Attempting to connect to administrative share '\\10.19.12.37\admin$' using machine account. SMS_CLIENT_CONFIG_MANAGER 26/03/2012 08:58:03 5300 (0x14B4) ---> Failed to connect to \\10.19.12.37\admin$ using machine account (53) SMS_CLIENT_CONFIG_MANAGER 26/03/2012 08:58:03 5300 (0x14B4) ---> The device 10.19.12.37 does not exist on the network. Giving up SMS_CLIENT_CONFIG_MANAGER 26/03/2012 08:58:03 5300 (0x14B4) ---> Trying the account stored in the CCR (index = 0x0) SMS_CLIENT_CONFIG_MANAGER 26/03/2012 08:58:03 5300 (0x14B4) ---> Attempting to connect to administrative share '\\10.19.12.33\admin$' using account 'centra\svc-sccm002' SMS_CLIENT_CONFIG_MANAGER 26/03/2012 08:58:03 5300 (0x14B4) ---> System OS version string "5.1.2600" converted to 5.10 SMS_CLIENT_CONFIG_MANAGER 26/03/2012 08:58:03 5348 (0x14E4) ---> Service Pack version from machine "PC-5P1-007869" is 3 SMS_CLIENT_CONFIG_MANAGER 26/03/2012 08:58:03 5348 (0x14E4) ---> No MP shares. Will not push the mobile client to PC-5P1-007869 SMS_CLIENT_CONFIG_MANAGER 26/03/2012 08:58:03 5348 (0x14E4) ---> Failed to install CCM Client Bootstrap component on client (2) SMS_CLIENT_CONFIG_MANAGER 26/03/2012 08:58:03 5348 (0x14E4) STATMSG: ID=3014 SEV=W LEV=M SOURCE="SMS Server" COMP="SMS_CLIENT_CONFIG_MANAGER" SYS=SRSCCM08 SITE=CE6 PID=2848 TID=5348 GMTDATE=Mon Mar 26 07:58:03.938 2012 ISTR0="PC-5P1-007869" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_CLIENT_CONFIG_MANAGER 26/03/2012 08:58:03 5348 (0x14E4) ---> Deleting SMS Client Install Lock File '\\10.19.8.61\admin$\SMSClientInstall.CE6' SMS_CLIENT_CONFIG_MANAGER 26/03/2012 08:58:03 5348 (0x14E4) Stored request "10_19_8_61.CENTRA", machine name "PC-5P1-007869", in queue "Retry". SMS_CLIENT_CONFIG_MANAGER 26/03/2012 08:58:03 5348 (0x14E4) <======End request: "10_19_8_61.CENTRA", machine name: "PC-5P1-007869". SMS_CLIENT_CONFIG_MANAGER 26/03/2012 08:58:03 5348 (0x14E4) I am desperate to get this sorted ASAP. Any help would be greatly appreciated. Ted

---> No MP shares. Will not push the mobile client to PC-5P1-007869 SMS_CLIENT_CONFIG_MANAGER 26/03/2012 08:58:03 5348 (0x14E4) Is there a MP installed on the site where you initiated the push from? Check mpsetup.log if the installation was successful. Also make sure that name resolution is working (error 53) in ccmsetup.log. Using "SMSSiteCode=AUTO" will only work if there are no overlapping between boundaries (SMS/ConfigMgr).Torsten Meringer | http://www.mssccmfaq.de

MP is not setup on this secondary SCCM server. There is only one MP setup which is on our central site server. There are no overlapping boundaries.

do a push from central site serverSyed Kasif

There are several possible reasons to cause this issue: 1. Client admin$ doesnt share 2. The account doesnt have the permission to access to this file share. Please make sure that ADMIN$ is enabled in the client: 1. From the server to the client there are no DNS issue 2. Account Specified for client push is correct and have permission to connect to the share Also, please check if the ports were blocked by firewall. Windows Firewall Settings for Configuration Manager Clients Ports that are Used with Client Push InstallationSabrina TechNet Community Support

Thanks for all your suggestions. It turns out that that all the subnets havent been defined in AD and hence we are having this issue!! We are going through the list of subnets that we support and adding them to AD if it is not already done. So far we have 700+ new computers that are managed and hopfully we should have the rest of the 2000 odd computers managed soon.

while we thought we fixed the issue with adding the subnets that were missed out from AD, we are stuck with 30% of our estate not being managed as client push is not working. I have looked at a cross section of these 30% computers. All of them are XP SP3 and belong to subnets that have been defined in AD. They have received the group policy which added a service account with local admin privileges that used for client push. I have checked if I can ping from the SCCM Client central site server and do a reverse lookup. One interesting thing is that all the computers that have received the client seems to be getting it from the Central Site Server. None of the computers have received the client from any of the secondary SCCM servers. Any suggestions on what to look for in the above scenario?

I have come to a point where I am thinking of pushing the client manually using a start up script as we are not having much luck with troubleshooting the client push issues. Any thoughts on this. Ted

yep we have great startup script made by great man Jason http://blogs.catapultsystems.com/jsandys/archive/2010/12/30/updated-configmgr-startup-script.aspx use this ref : http://social.technet.microsoft.com/Forums/en-US/configmgrsetup/thread/8412005a-f1c8-4f29-877f-04c793561ef0 Syed Kasif

thank you Syed for the links I have skimmed through Jason's script and had the following question will this install the SCCM client on the existing SMS client? I ran the following line as a start up script but it did not install the sccm client as it says client already present \\sccm01\client\ccmsetup.e xe /mp:sccm01 /logon SMSSITECODE=AUTO I have now edited this to remove the /logon switch and the client install is happening successfully \\sccm01\client\ccmsetup.exe /mp:sccm01 SMSSITECODE=AUTO however since i am testing the above as a start up script, it will run every single time a computer is rebooted and hence I do not want this.

While I test Jason's startup script I thought i might tell you guys how our infrastructure is designed at the moment and if any of you see anthing inherently wrong with the design that might be causing the client push to fail We have a clustered Primary site (3 servers - 1 MP and 2 DPs), 6 secondary servers with only one of them having the MP and DP role while the other 5 only have the DP role. I have activated Client push with a service account having local admin rights on each of the above sites. However all the clients which are managed are only showing CE1 (which is the site code of the clustered central site servers. As far as the boundaries are concerned the clustered central site has all the 19 boundaries which is an overlap of individual boundaries on the secondary sites. Do you believe the above setup is alright or do you see anything that might cause the client push to fail on secondary site servers?