FAQShop.com : "SMS Client Configuration Manager (CCM) has made 25 unsuccessful attempts to install SMS..."

"SMS Client Configuration Manager (CCM) has made 25 unsuccessful attempts to install SMS..."

OK, I'm still working on my SMS 2003 RTM lab. I have 2003 loaded and Active Directory discovery has found all the machines in my lab appropriately and assigned them to collections.

Now, I have my service account set up with the same credentials in AD and in SMS's client account setup for the Client Push Installation method. My service account is actually an Enterprise Admin in my domain. The Site Server computer account is also a domain admin.

However, the Client Bootstrap fails to install. In reviewing the CCM.LOG file, I see the machine connect without a problem. Then I see several 'Unable to see this or that' type statements (probably due to no client on the system). The log then says that it's going to install the Advanced Client, then I get the failure to install the client bootstrap.

I've also seen Error 2 from the CCM, the system cannot find the file specified, which they suggest point to the service accounts inability to log into the client box (even though I've done it directly with complete success using the service account) And the machines are on the network...so I'm not sure what else we're looking for..

I know SMS isn't supposed to be NetBIOS reliant for a truly homogeneous Windows 2000 environment, but my thoughts gravitate that way.

Thoughts anyone?

Contributed By: Rick Butler on the SMS 2003 Forum
In the past 168 hours, SMS Client Configuration Manager (CCM) has made 25 unsuccessful attempts to install SMS on client "TEST06". CCM will continue to attempt to install this client. The operating system reported error 2: The system cannot find the file specified.

Possible cause: The client is not accessible.
Solution: Verify that the client is connected to the network and that the SMS Service account or (if specified) the SMS Client Remote Installation account have the required privileges, as specified in the SMS documentation.

This does correlate to some of the errors I'm seeing in the CCM.LOG.

Well, we play, we struggle, we learn.

Seems that my problems may have been caused by having SUS and SMS on the same machine.

Both of these programs use IIS. SUS is built around it, the Management Point requires IIS and BITS on the system before you turn on the MP.

And you need the MP in place to manage Advanced Clients...

Not 100% if this was the problem I was having, but after tearing it down and installing it an another box, my problem went away.

Finally, a side note:

When installing on Windows Server 2003, remember these things:

1) Make sure you have IIS installed, configuring the server as an application server.

2) Make sure you have ASP support turned on.

3) Make sure BITS is set up. Be sure to install BITS server (instll option in IIS)

4) THEN, configure your management point.

To see other SMS 2003 Troubleshooting FAQs click here.