RE: SCCM Client Installer Mystery

Hi William

I've been having similar problems... but I didn't go as far as disabling the
firewalls ;)
I can shed a little light on what is happening, as advised to me by a
friendly SMS expert.

The error code you are getting is because the WMI name space that is created
by the SCCM client is NOT there until you have installed a client. Notice
that it does start the install process. So this error can safely be ignored.

The logs on the client machine that will tell you what is going on / wrong
are in c:\windows\system32\ccmsetup\
you should find all the information that you need in there. You probably
want to look at ccmsetup.log but maybe the other ones will be needed.

Furthermore I can advise that you can run with the firewall on for windows
XP. You need the File and Print sharing enabled and also Remote
Administration. These can both be set with group policy or manually. To set
Remote admin on XP use:
netsh firewall set service remote admin enable
This also works on Server2008 and will need to be done on any server that
has a role in the SCCM configuration. N.B. on Server2008 this will create
extra rules in the firewall Domain profile.

Hope this helps.

"William Anderson" wrote:

Alrighty, I have a test server that I've configured and installed SCCM2k7 on.
I also have a virtual client (XP on Virtual Server2005) that I'm trying to
install the client on using the push method. The CCMSetup installer fails
immediately with the following in the log:

==========[ ccmsetup started in process 1848 ]========== ccmsetup 8/13/2008
12:09:05 PM 1144 (0x0478)
Version: 4.0.6221.1000 ccmsetup 8/13/2008 12:09:05 PM 1144 (0x0478)
Command line parameters for ccmsetup have been specified. No registry
lookup for command line parameters is required. ccmsetup 8/13/2008 12:09:05
PM 1144 (0x0478)
Command line: "C:\WINDOWS\system32\ccmsetup\ccmsetup.exe" /runservice
/config:MobileClient.tcf ccmsetup 8/13/2008 12:09:05 PM 1144 (0x0478)
CCMHTTPPORT: 80 ccmsetup 8/13/2008 12:09:05 PM 1144 (0x0478)
CCMHTTPSPORT: 443 ccmsetup 8/13/2008 12:09:05 PM 1144 (0x0478)
CCMHTTPSSTATE: 0 ccmsetup 8/13/2008 12:09:05 PM 1144 (0x0478)
CCMHTTPSCERTNAME: ccmsetup 8/13/2008 12:09:05 PM 1144 (0x0478)
FSP: MW2K8EVAL.MW2K8.TEST ccmsetup 8/13/2008 12:09:05 PM 1144 (0x0478)
CCMFIRSTCERT: 0 ccmsetup 8/13/2008 12:09:05 PM 1144 (0x0478)
Config file:
C:\WINDOWS\system32\ccmsetup\MobileClient.tcf ccmsetup 8/13/2008 12:09:05
PM 1144 (0x0478)
Retry time: 10 minute(s) ccmsetup 8/13/2008 12:09:05 PM 1144 (0x0478)
MSI log file: ccmsetup 8/13/2008 12:09:05 PM 1144 (0x0478)
MSI properties: INSTALL="ALL" SMSSITECODE="MWT" CCMHTTPPORT="80"
CCMHTTPSPORT="443" CCMHTTPSSTATE="0" FSP="MW2K8EVAL.MW2K8.TEST"
CCMFIRSTCERT="0" ccmsetup 8/13/2008 12:09:05 PM 1144 (0x0478)
Source List: ccmsetup 8/13/2008 12:09:05 PM 1144 (0x0478)
\\MW2K8EVAL.MW2K8.TEST\SMSClient ccmsetup 8/13/2008
12:09:05 PM 1144 (0x0478)
\\MW2K8EVAL\SMSClient ccmsetup 8/13/2008 12:09:05 PM 1144
(0x0478)
MPs: ccmsetup 8/13/2008 12:09:05 PM 1144 (0x0478)
MW2K8EVAL.MW2K8.TEST ccmsetup 8/13/2008 12:09:05 PM 1144
(0x0478)
Updated security on object C:\WINDOWS\system32\ccmsetup\. ccmsetup 8/13/2008
12:09:05 PM 1144 (0x0478)
Sending Fallback Status Point message, STATEID='100'. ccmsetup 8/13/2008
12:09:05 PM 1144 (0x0478)
State message with TopicType 800 and TopicId
{5BF19854-AF27-4958-8279-0440522EC415} has been sent to the
FSP FSPStateMessage 8/13/2008 12:09:06 PM 1144 (0x0478)
Running as user "SYSTEM" ccmsetup 8/13/2008 12:09:06 PM 368 (0x0170)
Detected 38264 MB free disk space on system drive. ccmsetup 8/13/2008
12:09:06 PM 368 (0x0170)
DetectWindowsEmbeddedFBWF() Detecting OS Version ccmsetup 8/13/2008 12:09:06
PM 368 (0x0170)
Client OS is not Windows XP Embedded ccmsetup 8/13/2008 12:09:06 PM 368
(0x0170)
Ccmsetup is being restarted due to an administrative action. Installation
files will be reset and downloaded again. ccmsetup 8/13/2008 12:09:06 PM 368
(0x0170)
Successfully ran BITS check. ccmsetup 8/13/2008 12:09:06 PM 368 (0x0170)
Failed to successfully complete HTTP request. (StatusCode at
WinHttpQueryHeaders: 403) ccmsetup 8/13/2008 12:09:06 PM 368 (0x0170)
Sending Fallback Status Point message, STATEID='308'. ccmsetup 8/13/2008
12:09:06 PM 368 (0x0170)
State message with TopicType 800 and TopicId
{441D45A5-86A4-4E47-B8CE-7C362EFE023B} has been sent to the
FSP FSPStateMessage 8/13/2008 12:09:06 PM 368 (0x0170)

So...I check on the server's ccm log and get the following:
Received request: "P0OX1VMY" for machine name: "VIRTUALXP" on queue:
"Incoming". SMS_CLIENT_CONFIG_MANAGER 8/13/2008 12:10:03 PM 3720 (0x0E88)
Stored request "P0OX1VMY", machine name "VIRTUALXP", in queue
"Processing". SMS_CLIENT_CONFIG_MANAGER 8/13/2008 12:10:03 PM 3720 (0x0E88)
======>Begin Processing request: "P0OX1VMY", machine name:
"VIRTUALXP" SMS_CLIENT_CONFIG_MANAGER 8/13/2008 12:10:03 PM 4368 (0x1110)
---> Trying the 'best-shot' account which worked for previous CCRs (index =
0x0) SMS_CLIENT_CONFIG_MANAGER 8/13/2008 12:10:03 PM 4368 (0x1110)
---> Attempting to connect to administrative share
'\\virtualxp.MW2K8.TEST\admin$' using account
'MW2K8\MW-SCCMInst' SMS_CLIENT_CONFIG_MANAGER 8/13/2008 12:10:03 PM 4368
(0x1110)
---> The 'best-shot' account has now succeeded 162 times and failed 0
times. SMS_CLIENT_CONFIG_MANAGER 8/13/2008 12:10:03 PM 4368 (0x1110)
---> Connected to administrative share on machine virtualxp.MW2K8.TEST using
account 'MW2K8\MW-SCCMInst' SMS_CLIENT_CONFIG_MANAGER 8/13/2008 12:10:03
PM 4368 (0x1110)
---> Attempting to make IPC connection to share
<\\virtualxp.MW2K8.TEST\IPC$> SMS_CLIENT_CONFIG_MANAGER 8/13/2008 12:10:03
PM 4368 (0x1110)
---> Searching for SMSClientInstall.* under
'\\virtualxp.MW2K8.TEST\admin$\' SMS_CLIENT_CONFIG_MANAGER 8/13/2008 12:10:03
PM 4368 (0x1110)
---> System OS version string "5.1.2600" converted to
5.10 SMS_CLIENT_CONFIG_MANAGER 8/13/2008 12:10:03 PM 4368 (0x1110)
---> Service Pack version from machine "VIRTUALXP" is
3 SMS_CLIENT_CONFIG_MANAGER 8/13/2008 12:10:03 PM 4368 (0x1110)
CWmi::Connect(): ConnectServer(Namespace) failed. -
0x8004100e SMS_CLIENT_CONFIG_MANAGER 8/13/2008 12:10:04 PM 4368 (0x1110)
---> Unable to connect to WMI (r) on remote machine "VIRTUALXP", error =
0x8004100e. SMS_CLIENT_CONFIG_MANAGER 8/13/2008 12:10:04 PM 4368 (0x1110)
---> Creating \ VerifyingCopying exsistance of destination directory
\\VIRTUALXP\admin$\system32\ccmsetup. SMS_CLIENT_CONFIG_MANAGER 8/13/2008
12:10:04 PM 4368 (0x1110)
---> Copying client files to
\\VIRTUALXP\admin$\system32\ccmsetup. SMS_CLIENT_CONFIG_MANAGER 8/13/2008
12:10:04 PM 4368 (0x1110)
---> Updated service "ccmsetup" on machine
"VIRTUALXP". SMS_CLIENT_CONFIG_MANAGER 8/13/2008 12:10:04 PM 4368 (0x1110)
---> Started service "ccmsetup" on machine
"VIRTUALXP". SMS_CLIENT_CONFIG_MANAGER 8/13/2008 12:10:04 PM 4368 (0x1110)
---> Deleting SMS Client Install Lock File
'\\virtualxp.MW2K8.TEST\admin$\SMSClientInstall.MWT' SMS_CLIENT_CONFIG_MANAGER 8/13/2008 12:10:04 PM 4368 (0x1110)
---> Completed request "P0OX1VMY", machine name
"VIRTUALXP". SMS_CLIENT_CONFIG_MANAGER 8/13/2008 12:10:04 PM 4368 (0x1110)
Deleted request "P0OX1VMY", machine name
"VIRTUALXP" SMS_CLIENT_CONFIG_MANAGER 8/13/2008 12:10:04 PM 4368 (0x1110)
<======End request: "P0OX1VMY", machine name:
"VIRTUALXP". SMS_CLIENT_CONFIG_MANAGER 8/13/2008 12:10:04 PM 4368 (0x1110)
Submitted request successfully SMS_CLIENT_CONFIG_MANAGER 8/13/2008 12:10:05
PM 3720 (0x0E88)
Getting a new request from queue "Incoming" after 100 millisecond
delay. SMS_CLIENT_CONFIG_MANAGER 8/13/2008 12:10:05 PM 3720 (0x0E88)
Waiting for change in directory "E:\Microsoft Configuration
Manager\inboxes\ccr.box" for queue "Incoming", (30 minute backup
timeout). SMS_CLIENT_CONFIG_MANAGER 8/13/2008 12:10:05 PM 3720 (0x0E88)

So I checked online and ensured the following:
-Firewall on Client and Server is disabled.
-Fallback Status Point is Configured.
-Server can access client through WMI (WBEMTEST).
-Client can access server through WMI (WBEMTEST).
-DCOM on client has Anonymous remote access enabled.(DCOMCNFG)
-Net Access and Installation Accounts are in the Local Client Administrators
Group.
-Net Access and Installation Accounts are in the SMS Admins Group.
-SMS Admins group has full priveledges in SMS.
-Client is Windows XP Pro SP3.

Do you guys know what I'm missing? My forehead is getting flatter by the
minute!

Thanks as always!
.

Relevant Pages

  • Re: Client End Firewalls
    ... it doesn't matter if the email client can't be tricked when the ... control such things on a Windows 98 box. ... > than getting the client firewall properly configured. ... > additional costs for configuration and configuration-changes? ...
    (Security-Basics)
  • Re: Client End Firewalls
    ... depending on the firewall's configuration). ... Even if a client side firewall was to block just one ... Using a firewall with password protection is a must. ... >> connections. ...
    (Security-Basics)
  • Re: Client Installation failure
    ... messages for Client Configuration Installation Manager do you see any status ... Let me reiterate that the advanced client install is ... > that it is a local lookup, the admin$ share is completely accessible. ...
    (microsoft.public.sms.setup)
  • Re: Client End Firewalls
    ... since Windows provides far too many ways to work around it. ... Even if a client side firewall was to block just one ... The configuration is a big key. ...
    (Security-Basics)
  • RE: [fw-wiz] Cisco VPN Client "Stateful Firewall (Always On)"
    ... of attack before and after the VPN client is used. ... Need some opinions on a firewall solution for our notebook computers. ... configuration. ... or not the "Stateful Firewall " feature of the Cisco VPN ...
    (Firewall-Wizards)
Loading