Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Client Installation issues with SCCM 07

395 views
Skip to first unread message

BDA

unread,
Apr 14, 2008, 10:53:21 AM4/14/08
to

I've rolled out over 2000 sucessful client installs in my environment,
but have about 1% of my machines failing for unknown reasons. The
first issue is around Prerequisite files not being 'MS signed'. I
know this can't be the case as the same files have worked on the other
clients, but my Fallback status point reports this:


Prerequisite file is not MS signed: C:\WINNT\system32\ccmsetup
\wimgapi.msi

I've connected to this machine and have re-installed Windows Installer
to version 3.1 and no luck.

Here is a sample of the local log file:

==========[ ccmsetup started in process 1524 ]========== ccmsetup
4/14/2008 8:39:31 AM 1860 (0x0744)
Version: 4.0.5931.0000 ccmsetup 4/14/2008 8:39:31 AM 1860 (0x0744)
Command line parameters for ccmsetup have been specified. No registry
lookup for command line parameters is required. ccmsetup 4/14/2008
8:39:31 AM 1860 (0x0744)
Command line: "C:\WINNT\system32\ccmsetup\ccmsetup.exe" /runservice /
config:MobileClient.tcf ccmsetup 4/14/2008 8:39:31 AM 1860 (0x0744)
CCMHTTPPORT: 80 ccmsetup 4/14/2008 8:39:32 AM 1860 (0x0744)
CCMHTTPSPORT: 443 ccmsetup 4/14/2008 8:39:32 AM 1860 (0x0744)
CCMHTTPSSTATE: 0 ccmsetup 4/14/2008 8:39:32 AM 1860 (0x0744)
CCMHTTPSCERTNAME: ccmsetup 4/14/2008 8:39:32 AM 1860 (0x0744)
FSP: MTLWSUS ccmsetup 4/14/2008 8:39:32 AM 1860 (0x0744)
CCMFIRSTCERT: 0 ccmsetup 4/14/2008 8:39:32 AM 1860 (0x0744)
Config file: C:\WINNT\system32\ccmsetup\MobileClient.tcf ccmsetup
4/14/2008 8:39:32 AM 1860 (0x0744)
Retry time: 10 minute(s) ccmsetup 4/14/2008 8:39:32 AM 1860
(0x0744)
MSI log file: ccmsetup 4/14/2008 8:39:32 AM 1860 (0x0744)
MSI properties: INSTALL="ALL" SMSSITECODE="IBI"
CCMALLOWSILENTREBOOT="1" FSP="MTLWSUS" SMSCACHESIZE="2048"
CCMHTTPPORT="80" CCMHTTPSPORT="443" CCMHTTPSSTATE="0" CCMFIRSTCERT="0"
ccmsetup 4/14/2008 8:39:32 AM 1860 (0x0744)
Source List: ccmsetup 4/14/2008 8:39:32 AM 1860 (0x0744)
\\mtlsccm01.interlinebrands.com\SMSClient ccmsetup
4/14/2008 8:39:32 AM 1860 (0x0744)
\\MTLSCCM01\SMSClient ccmsetup 4/14/2008 8:39:32 AM
1860 (0x0744)
MPs: ccmsetup 4/14/2008 8:39:32 AM 1860 (0x0744)
mtlsccm01.interlinebrands.com ccmsetup 4/14/2008
8:39:32 AM 1860 (0x0744)
Updated security on object C:\WINNT\system32\ccmsetup\. ccmsetup
4/14/2008 8:39:32 AM 1860 (0x0744)
Sending Fallback Status Point message, STATEID='100'. ccmsetup
4/14/2008 8:39:32 AM 1860 (0x0744)
State message with TopicType 800 and TopicId
{A74479B8-02B0-4277-9221-86E2CDA9230D} has been sent to the FSP
FSPStateMessage 4/14/2008 8:39:32 AM 1860 (0x0744)
Running as user "SYSTEM" ccmsetup 4/14/2008 8:39:32 AM 1636 (0x0664)
Detected 25237 MB free disk space on system drive. ccmsetup 4/14/2008
8:39:32 AM 1636 (0x0664)
DetectWindowsEmbeddedFBWF() Detecting OS Version ccmsetup 4/14/2008
8:39:32 AM 1636 (0x0664)
Client OS is not Windows XP Embedded ccmsetup 4/14/2008 8:39:32 AM
1636 (0x0664)
Ccmsetup is being restarted due to an administrative action.
Installation files will be reset and downloaded again. ccmsetup
4/14/2008 8:39:32 AM 1636 (0x0664)
Successfully ran BITS check. ccmsetup 4/14/2008 8:39:34 AM 1636
(0x0664)
SSL Registry key Software\Microsoft\CCM not found, assuming Client SSL
is disabled. ccmsetup 4/14/2008 8:39:34 AM 1636 (0x0664)
Certificate doesn't have EKU, meaning good for all usages. ccmsetup
4/14/2008 8:39:35 AM 1636 (0x0664)
Select first cert flag is set, choosing the first certificate valid
for ConfigMgr usage. ccmsetup 4/14/2008 8:39:35 AM 1636 (0x0664)
Verified file 'C:\WINNT\system32\ccmsetup\ccmsetup.cab' is MS signed.
ccmsetup 4/14/2008 8:39:35 AM 1636 (0x0664)
Successfully extracted manifest file C:\WINNT\system32\ccmsetup
\ccmsetup.xml from file C:\WINNT\system32\ccmsetup\ccmsetup.cab.
ccmsetup 4/14/2008 8:39:35 AM 1636 (0x0664)
Loading manifest file: C:\WINNT\system32\ccmsetup\ccmsetup.xml
ccmsetup 4/14/2008 8:39:35 AM 1636 (0x0664)
Successfully loaded ccmsetup manifest file. ccmsetup 4/14/2008 8:39:35
AM 1636 (0x0664)
Couldn't get directory list for directory 'http://
mtlsccm01.interlinebrands.com/CCM_Client/ClientPatch'. This directory
may not exist. ccmsetup 4/14/2008 8:39:35 AM 1636 (0x0664)
Adding file 'http://mtlsccm01.interlinebrands.com:80/CCM_Client/i386/
wimgapi.msi' to BITS job, saving as 'C:\WINNT\system32\ccmsetup
\wimgapi.msi'. ccmsetup 4/14/2008 8:39:35 AM 1636 (0x0664)
Adding file 'http://mtlsccm01.interlinebrands.com:80/CCM_Client/i386/
client.msi' to BITS job, saving as 'C:\WINNT\system32\ccmsetup
\client.msi'. ccmsetup 4/14/2008 8:39:36 AM 1636 (0x0664)
Couldn't get directory list for directory 'http://
mtlsccm01.interlinebrands.com/CCM_Client/i386/00000409'. This
directory may not exist. ccmsetup 4/14/2008 8:39:36 AM 1636 (0x0664)
Starting BITS download for client deployment files. ccmsetup 4/14/2008
8:39:36 AM 1636 (0x0664)
Download Update: Connecting to the server. ccmsetup 4/14/2008 8:39:37
AM 1636 (0x0664)
Successfully completed BITS download for client deployment files.
ccmsetup 4/14/2008 8:41:36 AM 1636 (0x0664)
Successfully downloaded client files via BITS. ccmsetup 4/14/2008
8:41:37 AM 1636 (0x0664)
Updated security on object C:\WINNT\system32\ccmsetup\. ccmsetup
4/14/2008 8:41:37 AM 1636 (0x0664)
Can't verify that file 'C:\WINNT\system32\ccmsetup\wimgapi.msi' is
digitally signed. ccmsetup 4/14/2008 8:41:37 AM 1636 (0x0664)
Sending Fallback Status Point message, STATEID='316'. ccmsetup
4/14/2008 8:41:37 AM 1636 (0x0664)
State message with TopicType 800 and TopicId
{4DE48AEB-75B2-4448-83A2-91673A1F407E} has been sent to the FSP
FSPStateMessage 4/14/2008 8:41:37 AM 1636 (0x0664)


Anyone have any ideas on how to troubleshoot beyond what I've done?

Message has been deleted
Message has been deleted
Message has been deleted

jan...@avanade.com

unread,
Apr 15, 2008, 5:39:23 AM4/15/08
to
Hi,

BITS is used to download the required files from the Management
Point.
Check BITS with the bitsadmin.exe tool for queued jobs or backlogs.
Bitsadmin.exe commands are:

bitsadmin.exe /list /allusers (showe queued jobs)
bitsadmin.exe /reset /allusers (deletes all the jobs)
Restart the ccmsetup service

Other thing to look for is that the i386 folder from C:\Program Files
\Microsoft Configuration Manager\Client still exists.

Hope this helps, regards,


Jannes Alink

BDA

unread,
Apr 15, 2008, 9:08:23 AM4/15/08
to
Thanks Jannes.

There are 0 jobs waiting when running the Bitsadmin /list /allusers -
I assume you meant from the SCCM site server.

Also, the \i386 directory is in place.

As I said, most clients continue to install without issue. There is
however, several who cannot get past the following issues:

"Prerequisite file is not MS Signed"
Failed to download file over WINHTTP at address
Can't verify that prerequisite file is MS signed:
Client.msi installation failed with MSI error:

Any more suggestions?

jan...@hotmail.com

unread,
Apr 15, 2008, 10:32:37 AM4/15/08
to
Hi,

You can check if any firewall device is blocking the WebDAV requests
that are sent during the installation of the client. WebDav also have
to be allowed at the sites.

Other thing to try is adding the 'Authenticating Users' group to the
local Users group of the SCCM server.

If you push your client with additonal commandline switches like the /
mp this error could also be generated. Try only the switch
SMSSITECODE=

Regards,
Jannes Alink

BDA

unread,
Apr 16, 2008, 10:54:22 AM4/16/08
to
On Apr 15, 10:32 am, jan...@hotmail.com wrote:
> Hi,
>
Thanks again Jannes.
The WebDAV service is running as I checked this in IIS Manager. I
would have thought that since this is a service on my server and not
on each client that it would have failed for all clients? Unless
there is a WebDAV config for the clients as well and I'm just missing
it? Remember, 99% of our clients are installing the client.msi via
push without issue.

Authenticated Users was alreday in the local Users group.

Have run the CCMsetup.exe without parameters with the same issue.

shashi salimath

unread,
Feb 9, 2011, 3:57:27 AM2/9/11
to
Hi understood u r problem, solution for this is to use new sccm client. Might be the machines which are facing this issue are in SCCM 2007 Sp2. please use latest sccm client.


>> On Wednesday, April 16, 2008 6:57 AM jannes wrote:

>> Hi,
>>
>> BITS is used to download the files from the management point. So check
>> BITS with BITSadmin.exe to see if there is a backlog of jobs. Commands
>> are:
>>
>> bitsadmin.exe /list /allusers (this showes jobs that are queued)


>>
>> bitsadmin.exe /reset /allusers (deletes all the jobs)
>>
>> Restart the ccmsetup service
>>

>> Hope this helps, regards,
>>
>> Jannes Alink


>>> On Wednesday, April 16, 2008 6:57 AM jannes wrote:

>>> Killed the ccmsetup.exe process in task manager (stopping the service
>>> did not work)
>>>
>>> Started the ccmsetup service


>>>> On Wednesday, April 16, 2008 6:57 AM jannes wrote:

>>>> Hi,
>>>>
>>>> BITS is used to download the required files from the Management Point.
>>>> Check BITS with the bitsadmin.exe tool for queued jobs or backlogs.
>>>> Bitsadmin.exe commands are:
>>>>
>>>> bitsadmin.exe /list /allusers (showe queued jobs)
>>>>
>>>> bitsadmin.exe /reset /allusers (deletes all the jobs)
>>>>
>>>> Restart the ccmsetup service
>>>>

>>>> Hope this helps, regards,
>>>>
>>>> Jannes Alink


>>>>> On Wednesday, April 16, 2008 6:57 AM jannes wrote:

>>>>> Hi,
>>>>>
>>>>> BITS is used to download the required files from the Management
>>>>> Point.
>>>>> Check BITS with the bitsadmin.exe tool for queued jobs or backlogs.
>>>>> Bitsadmin.exe commands are:
>>>>>
>>>>> bitsadmin.exe /list /allusers (showe queued jobs)
>>>>> bitsadmin.exe /reset /allusers (deletes all the jobs)
>>>>> Restart the ccmsetup service
>>>>>
>>>>> Other thing to look for is that the i386 folder from C:\Program Files
>>>>> \Microsoft Configuration Manager\Client still exists.
>>>>>
>>>>> Hope this helps, regards,
>>>>>
>>>>>
>>>>> Jannes Alink


>>>>>> On Wednesday, April 16, 2008 6:57 AM BDA wrote:

>>>>>> Thanks Jannes.
>>>>>>
>>>>>> There are 0 jobs waiting when running the Bitsadmin /list /allusers -
>>>>>> I assume you meant from the SCCM site server.
>>>>>>
>>>>>> Also, the \i386 directory is in place.
>>>>>>
>>>>>> As I said, most clients continue to install without issue. There is
>>>>>> however, several who cannot get past the following issues:
>>>>>>
>>>>>> "Prerequisite file is not MS Signed"
>>>>>> Failed to download file over WINHTTP at address
>>>>>> Can't verify that prerequisite file is MS signed:
>>>>>> Client.msi installation failed with MSI error:
>>>>>>
>>>>>> Any more suggestions?
>>>>>>
>>>>>>

>>>>>> On Apr 15, 5:39=A0am, jann...@avanade.com wrote:


>>>>>>> On Wednesday, April 16, 2008 6:57 AM jann3 wrote:

>>>>>>> Hi,


>>>>>>>
>>>>>>> You can check if any firewall device is blocking the WebDAV requests
>>>>>>> that are sent during the installation of the client. WebDav also have
>>>>>>> to be allowed at the sites.
>>>>>>>
>>>>>>> Other thing to try is adding the 'Authenticating Users' group to the
>>>>>>> local Users group of the SCCM server.
>>>>>>>
>>>>>>> If you push your client with additonal commandline switches like the /
>>>>>>> mp this error could also be generated. Try only the switch
>>>>>>> SMSSITECODE=
>>>>>>>
>>>>>>> Regards,
>>>>>>> Jannes Alink


>>>>>>>> On Saturday, April 19, 2008 1:01 AM BDA wrote:

>>>>>>>> On Apr 15, 10:32=A0am, jan...@hotmail.com wrote:
>>>>>>>> Thanks again Jannes.
>>>>>>>> The WebDAV service is running as I checked this in IIS Manager. I
>>>>>>>> would have thought that since this is a service on my server and not
>>>>>>>> on each client that it would have failed for all clients? Unless
>>>>>>>> there is a WebDAV config for the clients as well and I'm just missing
>>>>>>>> it? Remember, 99% of our clients are installing the client.msi via
>>>>>>>> push without issue.
>>>>>>>>
>>>>>>>> Authenticated Users was alreday in the local Users group.
>>>>>>>>
>>>>>>>> Have run the CCMsetup.exe without parameters with the same issue.


>>>>>>>>> On Tuesday, July 20, 2010 7:21 PM Dan Spec wrote:

>>>>>>>>> I was getting failed client installations. Turned out a few of my distribution points had 2 year old ccmsetup files. I updated my distribution points - uninstalled, then was able to reinstalled successfully.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Below is the error that was in my Client Deployment Failure Report:


>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Prerequisite file is not MS signed:
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>

>>>>>>>>> C:\Windows\system32\ccmsetup\{4CD82FBB-0AFC-4864-A089-15364DF0000}\client.msi


>>>>>>>>> Submitted via EggHeadCafe
>>>>>>>>> Creating Google Motion Charts from Excel data
>>>>>>>>> http://www.eggheadcafe.com/tutorials/aspnet/86599bca-edda-4204-af15-7a1cf901a071/creating-google-motion-charts-from-excel-data.aspx

0 new messages