Most do not have a client. This particular machine does have the old sms client. I used ccmclean.exe and removed the client and rebooted. Then I asked SCCM 2007 to push the client again and now it seems to have taken the client. Register; Sign In; Client Center for ConfigurationManager. Failed to install CCM Client BootStrap Component. I' m going through my ccm.log to begin identifying any failed client. Network Steve Forum)SCCM Client installation error: failed (6. I have clients in my sites which are failing to install client using SCCM console.
I recently installed SCCM 2012 on a server and set it up based on this website: I have ran into a problem where I am having problems pushing out the client to the computers. It does install as a service but it does not communciate with the server. I have tried to push it out from the server, use a GPO from group policy, and a manual install by going to the shared drive on the SCCM server. I did notice that doing it the manually way, it would install the service but would not start. It would report that the service started and then stopped.
It would do this everytime when I used the switches with the command to add the sitecode. If I just typed ccmsetup.exe to install, then the service started fine but there was no communication with the server. I then decided to just focus on pushing it out from the server and reviewed the logs.
I am at a point where it is pushing the client out as a service and it starts fine but no communicaton with the server. There is 1 error in the CCM log showing 'Unable to connect to WMI (roomt/CM) on remote machine'. I already have a GPO in place to make sure the ports are open. I have already turned off the firewall on the server and client as a test but there was no change.
I am unsure what to check next. Below is the log from CCM on the server for the 'testcomputer' that I am testing the client on: Received request: ' for machine name: 'TESTCOMPUTER' on queue: 'Incoming'. $$ Stored request ', machine name 'TESTCOMPUTER', in queue 'Processing'.
$$ Execute query exec spCPSetPushRequestMachineStatus, 1 $$ Begin Processing request: ', machine name: 'TESTCOMPUTER' $$ Execute query exec spIsMPAvailable N'503' $$ - Trying the 'best-shot' account which worked for previous CCRs (index = 0x0) $$ - Attempting to connect to administrative share ' TESTCOMPUTER admin$' using account 'TYLERCON resa5' $$ - The 'best-shot' account has now succeeded 1 times and failed 0 times. $$ - Connected to administrative share on machine TESTCOMPUTER using account 'TYLERCON resa5' $$ - Attempting to make IPC connection to share $$ - Searching for SMSClientInstall. under ' TESTCOMPUTER admin$ ' $$ - System OS version string '6.1.7601' converted to 6.10 $$ - Unable to connect to WMI (root ccm) on remote machine 'TESTCOMPUTER', error = 0x8004100e. $$ - Creating VerifyingCopying existence of destination directory TESTCOMPUTER admin$ ccmsetup. $$ - Copying client files to TESTCOMPUTER admin$ ccmsetup. $$ - Copying file 'C: Program Files Microsoft Configuration Manager bin I386 MobileClient.tcf' to 'MobileClient.tcf' $$ - Copying file 'C: Program Files Microsoft Configuration Manager bin I386 ccmsetup.exe' to 'ccmsetup.exe' $$ - Created service 'ccmsetup' on machine 'TESTCOMPUTER'.
$$ - Started service 'ccmsetup' on machine 'TESTCOMPUTER'. $$ - Deleting SMS Client Install Lock File ' TESTCOMPUTER admin$ SMSClientInstall.503' $$ Execute query exec spCPSetLastErrorCode, 0 $$ - Completed request ', machine name 'TESTCOMPUTER'. $$ Deleted request ', machine name 'TESTCOMPUTER' $$ Execute query exec spCPSetPushRequestMachineStatus, 4 $$ Execute query exec spCPSetLatest, N' 13:11:26', 23 $$ Any suggestions what to try next? There are several things that need to be done. Verify the account used to push software. In the SCCM Console navigate to Administration Overview SiteConfiguration Sites. Right click on your Site and choose Configure Site Components Software Distribution.
![Bootstrap Bootstrap](http://2.bp.blogspot.com/_dvyYK8VndcE/TGMKOksy_zI/AAAAAAAACr4/nL6q9mN88Ls/s400/sccm_client.jpg)
Click Network Access Tab. Validate the account you specified here. Make a group in AD called SCCMAdmins. In this group add the account mentioned above in this group. Now push this group to the local admin group of the client PC. SCCM requires this account to be local admin on the PC in order to install the client and get it working.
It needs this control also to perform tasks on the client. With the two steps above completed the installation should go through ok. For the manual install package gather the client files and make a.bat file in that same folder. Use this text in the batch file to perform a manual install. '%dp0ccmsetup.exe' /mp:YourSCCMServer smssitecode=XXX FSP=YourSCCMServer Replace 'Your SCCM Server' with the FQDN name of your SCCM server. There are several things that need to be done. Verify the account used to push software.
In the SCCM Console navigate to Administration Overview SiteConfiguration Sites. Right click on your Site and choose Configure Site Components Software Distribution.
Click Network Access Tab. Validate the account you specified here.
Make a group in AD called SCCMAdmins. In this group add the account mentioned above in this group. Now push this group to the local admin group of the client PC. SCCM requires this account to be local admin on the PC in order to install the client and get it working. It needs this control also to perform tasks on the client. With the two steps above completed the installation should go through ok. For the manual install package gather the client files and make a.bat file in that same folder.
Use this text in the batch file to perform a manual install. '%dp0ccmsetup.exe' /mp:YourSCCMServer smssitecode=XXX FSP=YourSCCMServer Replace 'Your SCCM Server' with the FQDN name of your SCCM server.
Hmm, About all I get is 3 warnings, The assignment of application SMS Client Setup Bootstrap from policy SCCM Client - Install failed. The error was:%%1274 Failed to apply changes to software installation settings. The installation of software deployed through Group Policy for this user has been delayed until the next logon because the changes must be applied before the user logon. The error was:%%1274 The Group Policy Client Side Extension Software Installation was unable to apply one or more settings because the changes must be processed before system startup or user logon. The system will wait for Group Policy processing to finish completely before the next startup or logon for this user, and this may result in slow startup and boot performance. Hi Anoop, Surely the fact the ccmsetup.msi does kick off, and begin the process of downloading and running ccmsetup.exe, not mean that the Group Policy side of things is working as it should be? At this point ccmsetup.exe takes over the installation and then it fails after or during client.msi download.
I did run RSOP.MSC and it is my SCCM client install policy is producing the error. I also tried deleting the registry entry in the link you send me and got another error The install of application SMS Client Setup Bootstrap from policy SCCM Client - Install -failed. The error was:%%1603 which is just a generic windows installer failure. On another note I read this yesterday, but cant see why it needs it?
On my tests nothing is blocked on the client on File and Print Ports. Client Installation using Group Policy In order to successfully use Group Policy to install the Configuration Manager 2007 client, you must add File and Printer Sharing as an exception to the Windows Firewall Many thanks in advance.