Hi,

 I am unable to install the client on all computers. Please help to resolve the issue. The process beings but it doesn't complete and there is no error messages.

Thanks.

 

There are ALWAYS error messages. make sure client push is enabled. Not just the check mark box at the top of client push. That will auto install the cleint and you may not want that. Add the domain\user to the account. Make sure your Network Access Account is the same and push to a client. Look at the ccm.log file on the server and you should see it connect. Verify the ccmsetup folder on the client and read the logs. Look for the CCM folder in System32 and review the logs for errors. Something is misconfigured...

I seem to be having the same issue, I have all the settings configured on the sccm server,

I have no errors in my component status and site site systems status, wsus is being syncronized from another server and everything seems to be working,

I have all detected all the user and group membership accounts aswell as computers within the domain.

The only issue that Im currently experiencing is that when I push out the sccm client to the computers , non of them get installed after several days.

 I have checked the log for the intended pc. This is the ccmsetup.log .

Version: 4.0.5931.0000 ccmsetup 3/17/2008 5:33:10 PM 1724 (0x06BC)
Command line parameters for ccmsetup have been specified.  No registry lookup for command line parameters is required. ccmsetup 3/17/2008 5:33:10 PM 1724 (0x06BC)
Command line: "C:\WINDOWS\system32\ccmsetup\ccmsetup.exe" /runservice /config:MobileClient.tcf ccmsetup 3/17/2008 5:33:10 PM 1724 (0x06BC)
CCMHTTPPORT:    80 ccmsetup 3/17/2008 5:33:10 PM 1724 (0x06BC)
CCMHTTPSPORT:    443 ccmsetup 3/17/2008 5:33:10 PM 1724 (0x06BC)
CCMHTTPSSTATE:    0 ccmsetup 3/17/2008 5:33:10 PM 1724 (0x06BC)
CCMHTTPSCERTNAME:     ccmsetup 3/17/2008 5:33:10 PM 1724 (0x06BC)
FSP:     ccmsetup 3/17/2008 5:33:10 PM 1724 (0x06BC)
CCMFIRSTCERT:    0 ccmsetup 3/17/2008 5:33:10 PM 1724 (0x06BC)
Config file:      C:\WINDOWS\system32\ccmsetup\MobileClient.tcf ccmsetup 3/17/2008 5:33:10 PM 1724 (0x06BC)
Retry time:       10 minute(s) ccmsetup 3/17/2008 5:33:10 PM 1724 (0x06BC)
MSI log file:      ccmsetup 3/17/2008 5:33:10 PM 1724 (0x06BC)
MSI properties:    INSTALL="ALL" SMSSITECODE="xxx" CCMHTTPPORT="80" CCMHTTPSPORT="443" CCMHTTPSSTATE="0" CCMFIRSTCERT="0" ccmsetup 3/17/2008 5:33:10 PM 1724 (0x06BC)
Source List: ccmsetup 3/17/2008 5:33:10 PM 1724 (0x06BC)
                  \\TEST.TEST.com\SMSClient ccmsetup 3/17/2008 5:33:10 PM 1724 (0x06BC)
                  \\TEST\SMSClient ccmsetup 3/17/2008 5:33:10 PM 1724 (0x06BC)
MPs: ccmsetup 3/17/2008 5:33:10 PM 1724 (0x06BC)
                  TEST.TEST.com ccmsetup 3/17/2008 5:33:10 PM 1724 (0x06BC)
Updated security on object C:\WINDOWS\system32\ccmsetup\. ccmsetup 3/17/2008 5:33:10 PM 1724 (0x06BC)
A Fallback Status Point has not been specified.  Message with STATEID='100' will not be sent. ccmsetup 3/17/2008 5:33:10 PM 1724 (0x06BC)
Running as user "SYSTEM" ccmsetup 3/17/2008 5:33:10 PM 2776 (0x0AD8)
Detected 9725 MB free disk space on system drive. ccmsetup 3/17/2008 5:33:10 PM 2776 (0x0AD8)
DetectWindowsEmbeddedFBWF() Detecting OS Version ccmsetup 3/17/2008 5:33:10 PM 2776 (0x0AD8)
Client OS is not Windows XP Embedded ccmsetup 3/17/2008 5:33:10 PM 2776 (0x0AD8)
Ccmsetup is being restarted due to an administrative action. Installation files will be reset and downloaded again. ccmsetup 3/17/2008 5:33:10 PM 2776 (0x0AD8)
Failed to successfully complete HTTP request. (StatusCode at WinHttpQueryHeaders: 404) ccmsetup 3/17/2008 5:33:10 PM 2776 (0x0AD8)
A Fallback Status Point has not been specified.  Message with STATEID='308' will not be sent. ccmsetup 3/17/2008 5:33:10 PM 2776 (0x0AD8)
The language specific BITS version wasn't found (Failed to download 'WindowsXP-KB923845-x86-ENU.exe' from 'http://TEST.TESTcom/CCM_Client/i386/BITS25' with error code 0x80004005). ccmsetup 3/17/2008 5:33:10 PM 2776 (0x0AD8)

After checking this log,  It looks like it failing to successfully the http request.

Apperently its failing to download some update from the WSUS server.

I have IIS working fine and BITS is installed aswell.

Can someone please help me resolve this issue.

Gabe ,

As per log this client is not able to contact to your management point as its http request is getting failed.

client.msi will get download via management point .

Pl. check flow chart of Advanced Client Installation with the Client Push Installation Wizard  (This flow chart is for SMS 2003)

I have read information on fallback site server role,

it states that basically it assist client computers failing to communicate with the MP site server to be able to connect to the Fallback site server role.

It also states that you cannot install this site role on the MP site server, sccm. 

Now my question is could I install it on the WSUS server that is sperate from my Main site SCCM site server role.
 

 

Read what experts says about it... http://www.blogcastrepository.com/blogs/kim_oppalfenss_systems_management_ideas/archive/2007/06/27/thing-you-might-want-to-know-about-the-sccm-2007-fallback-status-point.aspx

Note: The Fallback Status Point cannot be installed on a system that already has a Site System role installed that requires https for its communication protocol.

The above note might influence your Fallback Status Point decision quite a bit. This obviously only impacts sites that operate in Native Security Mode, but you might still want to consider it in your designs to minimize the impact of security mode upgrades in the future. The reason that they cannot be co-located is that Configmgr 2007 installs all Site System roles in the same website. Configmgr 2007 has the option of installing in a different website than the default website, but this is a site wide setting, meaning that all Site Systems would then install their websites in this new “SMSWEB” website, which doesn’t solve our http/https problem. Although you could have separate virtual directories with different http/https settings this is generally not accepted as a good security practice. Conclusion, the Fallback Status Point is generally best installed on a machine separate from the Management Point, Software Update Point or Distribution Point which might increase the cost of having the Fallback Status Point locations based on your administrative model.

Ok So this only applies to Native Mode configuration of SCCM not Mixed.,

I am currently running mixed mode and dont plan to deploy native mode at all.

I will dismiss this option for any of the site servers.  

Now I need to figure out why is it that the computers dont get installed since is not becuase of this,  

Thanks Abbi for the article. 

I believe that the fact why Im not being able to deploy the clients to the desktops and server is because I have not deployed a group policy on the

OU that those computers and servers are. I have been reading documentation that states that they are required in order to deploy to clients.

I have been trying to install the client without the group policy objects that point to the wsus servers.

Now Im not sure if anyone has done it in a different way but if you have please let me know.

I think that currently Im going to setup the group policy object on a test OU and then point it to the wsus server and then deploy the client.  

Hi Gabriel

 

1. It looks a parameter is specified in your ccmsetup.exe "Command line parameters for ccmsetup have been specified". try to remove this or try manual installation.

 2. The ccmsetup.exe is trying to download some prequest like BITS 2.5....the path which pointed out in the log seem issue...

 

Have u extended ur schema?
Has the System Container been populated with objects pertaining to your SCCM Site?

No Shanxindia, I have never extended the schema, I dont want to either.

 

Brij,

   I had this same problem on some of my systems. I found that the DCOM was not enabled, as well as not having the correct security for my remote users.

BillDat