SCCM 2007 Client Install Failure on Select PC's

We are in the process of pushing out the client for SCCM 2007 via group policy. It has installed successfully on probably 60-70% of our pc's. I have attached the end of the ccmsetup.log file from one of the clients on which the install is failing. It is failing sporadically on both Vista and XP machines.

I appreciate any help and advise!
<![LOG[==========[ ccmsetup started in process 2156 ]==========]LOG]!><time="08:38:00.208+240" date="05-22-2009" component="ccmsetup" context="" type="1" thread="2160" file="ccmsetup.cpp:8849">
<![LOG[Version: 4.0.6221.1000]LOG]!><time="08:38:00.397+240" date="05-22-2009" component="ccmsetup" context="" type="1" thread="2160" file="ccmsetup.cpp:1907">
<![LOG[Command line parameters for ccmsetup have been specified.  No registry lookup for command line parameters is required.]LOG]!><time="08:38:00.447+240" date="05-22-2009" component="ccmsetup" context="" type="1" thread="2160" file="ccmsetup.cpp:3932">
<![LOG[Command line: "C:\Windows\system32\ccmsetup\ccmsetup.exe" /runservice /config:MobileClient.tcf]LOG]!><time="08:38:00.447+240" date="05-22-2009" component="ccmsetup" context="" type="1" thread="2160" file="ccmsetup.cpp:3941">
<![LOG[Invalid argument: WC-SMS2]LOG]!><time="08:38:00.489+240" date="05-22-2009" component="ccmsetup" context="" type="3" thread="2160" file="ccmsetup.cpp:4647">
<![LOG[CcmSetup::GetValueForMSIParam - MSI param is malformed.]LOG]!><time="08:38:00.489+240" date="05-22-2009" component="ccmsetup" context="" type="3" thread="2160" file="ccmsetup.cpp:5255">
<![LOG[Invalid ccmsetup command line: "C:\Windows\system32\ccmsetup\ccmsetup.exe" /runservice /config:MobileClient.tcf]LOG]!><time="08:38:00.489+240" date="05-22-2009" component="ccmsetup" context="" type="3" thread="2160" file="ccmsetup.cpp:4405">
<![LOG[Sending Fallback Status Point message, STATEID='100'.]LOG]!><time="08:38:00.489+240" date="05-22-2009" component="ccmsetup" context="" type="1" thread="2160" file="ccmsetup.cpp:9165">
<![LOG[State message with TopicType 800 and TopicId {B2577985-952D-42DE-98B5-8BFFFEE896B7} has been sent to the FSP]LOG]!><time="08:38:00.708+240" date="05-22-2009" component="FSPStateMessage" context="" type="1" thread="2160" file="fsputillib.cpp:730">
<![LOG[Sending Fallback Status Point message, STATEID='307'.]LOG]!><time="08:38:00.708+240" date="05-22-2009" component="ccmsetup" context="" type="1" thread="2160" file="ccmsetup.cpp:9165">
<![LOG[State message with TopicType 800 and TopicId {D279291C-27E5-40AF-80B1-29FB5BE90DD3} has been sent to the FSP]LOG]!><time="08:38:00.732+240" date="05-22-2009" component="FSPStateMessage" context="" type="1" thread="2160" file="fsputillib.cpp:730">

Open in new window

whitcotAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

HayesJupeCommented:
invalid command line agreument - "Invalid argument: WC-SMS2"  - can you post the command line your using ?
0
whitcotAuthor Commented:
HayesJupe,

This is the line from GP setting:
SMSSITECODE=WC0 SMSSLP=WC-SMS2 FSP= WC-SMS2

Thanks!
0
HayesJupeCommented:
try
SMSSITECODE=WC0 SMSSLP=WC-SMS2.domain.com SMSMPP=WC-SMS2.domain.com FSP= WC-SMS2
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Cloud Class® Course: Microsoft Azure 2017

Azure has a changed a lot since it was originally introduce by adding new services and features. Do you know everything you need to about Azure? This course will teach you about the Azure App Service, monitoring and application insights, DevOps, and Team Services.

whitcotAuthor Commented:
HayesJupe,

Thanks for the advise. I will try it right now.

A lot of the computers in my org. are powered off since this is a three-day, holiday weekend. But I will still monitor it over the weekend and closely as the work week begins.

Thanks again!
0
schristeCommented:
An alt method would be to push the client or make a separate install package for these clients then advertise it to them or let the push method install them. Otherwise using the FQDN as stated above should work is it's having an issue with that.

-Cheers-
0
whitcotAuthor Commented:
Looking at it this morning, it appears that 12 additional pc's have installed the client. The one from which I got the log in my first post still has not installed it.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Server OS

From novice to tech pro — start learning today.