Hello Peter,
I had exactly the same problem you described, after some troubleshooting i found that the CCM_client virtual directory on the SCCM machine is causing the problem. I still don't know what the problem is but i found that if you recreate the CCM_Client virtual directory the problem should be gone. It worked for me.
Good luck
Greetz
Aad Noman
Wally, having the exact same problem. we have an environment where half of the systems work with just a plain client push, and the other half work manually when using /noservice switch. Not consistant. Placing the /noservice switch in the ccmsetup push installation properties section does not work. I am perfectly happy using the /noservice switch if you tell me exactly where to put it to make client push work with it. With hundreds of servers it is not feasible to do it manually on every system, it should work via push either way or try both ways automatically. Please provide instructions or a fix. Thanks.
Hey,
I think I have the same problem so would be good to get some reply on this one, thanks!
Anyone?
cheers,
Janne
Tim, there's nothing "broken", so there's nothing to "fix. There is no hotfix for this, as client deployment works fine. You just need to use the correct command line parameters depending on your scenario.
I know in our TAP, we installed many 10's of thoudands of clients successfully - brand new clients, upgrades from SMS 2003. Sometimes you have to use the /noservice switch to no have us change from a user to a service context so clients can access the source files. Not sure how you'd expect us to "fix" this - we may start via a user context, then may switch to a service context (which would be local system). To prevent that, use the /noservice switch.
See this topic for the command line switches: http://technet.microsoft.com/en-us/library/bb680980.aspx
Use /noservice as a switch for the client install properties.
Does anyone have an actual SUPPORTED fix for this. I runing into this issue in 2 seperate(Seperate customers) deployment. Its fails on both XP and W2k3. This is very frustrating and the customers are no beginning to look at different product because this is the 2nd time they've deployed SCCM with this same issue. Please suppply a fix an get a KB or hotfix for this as this seem to be a consistent issue with SCCM.
Thanks
Tim McGilvery
I am a little confused here. From within the SCCM 2007 console you are saying set the /noservice command line option when sending a "client push installation"? How?
I am having a probelm getting the client installed in my environment. I have all the computers, servers, and users in the "collections" under "computer management" so I assume SCCM is communicating with AD correctly.
If the /noservice switch works, why not use it? In a push, it defaults to starting under the service, and then switches to a different account. Here's a dev comment on this from a while ago:
Have they tried using a /noservice switch on the ccmsetup command? Often, the reason ACLs become an issue is because the machine account can’t access the SMB share. If you run /noservice you’ll launch under the context that you spawned the process from. Since they needed the right ACLs just to access ccmsetup.exe from the mp SMB share, it should have the right ACLs to download the content too
Hi All-
This is indeed what is happening to my client when manually installing....the /noservice works. So, this leaves me stumped as to how to rectify the problem when using the push technology. I have assigned an account to the process that has admin rights both on the client and on the SCCM server. Should this account be used to make the network connection on the client (admin$) and the sms_sitecode\client folder? Why the change in security context at the point where data is being copied from a network location? I am missing something and would like to fix the Client Push Installation process and any help would be greatly appreciated. Thanks so much for your help!
Depending on your install method, you may be starting as the user context, and then switching to a service context. In those cases, the service context may not have rights as you are seeing. So you might try the /noservice switch as documented here:
http://technet.microsoft.com/en-us/library/bb680980.aspx
Hi Wally,
While I wholeheartedly agree with you that we should not have to change permissions I ran into the exact same issue while setting up a dev lab. Changing the share and file permissions listed above started the client install process immediately.
I presume that this is a known issue as there are multiple posts around regarding it? What is the proper solution?
Mike
The screen flashing sounds like the remote control agent being installed. When it installs, we install some virtual drivers, and the screen does flash like that.
You absolutely should not have to change any permissions at all. In fact, we'd recommend that you don't. You are granting way too many rights here for this process to complete. The only place a client installation would use is the Client folder under Program Files\Microsoft Configuration Manager. Granting rights to the entire folder listed would allow any user to access your site's files.
Hi,
I have changed 2 things:
Firstly, I have added the SMSPublicRootKey=<key> parameter in the installation properties of the Automatic push install.
Secondly, I have added "Everyone" group with read permission for the SMS_SiteCode share and with read & execute NTFS permissions to the underliyng folder C:\Program Files\Configuration Manager... and child folders.
The second action seems to did the trick, as almost immediately after that all pilot machines started the client installation and reported back to the SCCM server. I am yet to see the HW and SW inventory reporing back, though.
On another note, I have noticed one undocumented behaviour during the SCCM agent manual and automatic installation - if the client computer has a screen extended to a second monitor - both monitors will flash back and forth for a part of a second alternatively. This has happened at least in two cases. The particular HW is Dell laptops + Dell LCD monitors. It is bizarre and worth trying to reproduce, as the SCCM agent is noticable.
Best regards,
Peter
All you need for either automated or manual push is:
* An admin account - you have that, or the process would not have installed Ccmsetup.exe at all
* The resource as a new system resource assigned to the site - you have that, or we wouldn't have started at all
* Appropriate ports open through the firewall (or the firewall disabled) - obviously working, as we tried
* An MP with source files - an MP just need IIS with WebDAV allowed and BITS Server Extensions installed - but we require that, so the MP would not be installed if those were not met
* Access to the source files on the MP - that can be either the computer account (if domain joined) or the Network Access Account - usually we log that the source files were not accessbile if not
I can't think of anything else there that is required.
I'd try a manual install of a client to see if that is the same. However, likely it is the 80004005 error. From what I see, that is listed as an "Unspecified error" from Windows, so no help there.
Hi,
Please note that I am using the same (64-bit) server for all SCCM roles including site server, MP, FSP, DP, database etc.
The workstations with BITS2.5 installed have only this error:
"Failed to successfully complete HTTP request. (StatusCode at WinHttpQueryHeaders: 401"
which seems to be something with server authentication. So the cliewnt machines for some reason cannot authenticate with the SCCM server. Thsi error prevents the insyallation of teh SCCM agent to continue, so no SMS agent is running on the client machines and no CCM folde is created.
Is there any documented (pre-)configuration that should be done on the IIS for the automatic client pus to work?
Regards,
Peter
Hi Wally,
I have changed 2 things:
1. Enabed automatic push installation (so I am not usign the wizard any more)
2. Changed the IP subnet to IP ranges in the site boundairies.
After runnignt the discovery, I was able to see some activities in the ccm.log. A ccmsetup folder is now created but the agent is still not instaleld. Here is the ccmsetup.log
==================================
<![LOG[==========[ ccmsetup started in process 3140 ]==========]LOG]!><time="09:45:07.045+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="3108" file="ccmsetup.cpp:8853">
<![LOG[Version: 4.0.5931.0000]LOG]!><time="09:45:07.045+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="3108" file="ccmsetup.cpp:1913">
<![LOG[Command line parameters for ccmsetup have been specified. No registry lookup for command line parameters is required.]LOG]!><time="09:45:07.045+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="3108" file="ccmsetup.cpp:3937">
<![LOG[Command line: "C:\WINDOWS\system32\ccmsetup\ccmsetup.exe" /runservice /config:MobileClient.tcf]LOG]!><time="09:45:07.045+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="3108" file="ccmsetup.cpp:3946">
<![LOG[CCMHTTPPORT: 80]LOG]!><time="09:45:07.045+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="3108" file="ccmsetup.cpp:7851">
<![LOG[CCMHTTPSPORT: 443]LOG]!><time="09:45:07.045+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="3108" file="ccmsetup.cpp:7866">
<![LOG[CCMHTTPSSTATE: 0]LOG]!><time="09:45:07.045+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="3108" file="ccmsetup.cpp:7884">
<![LOG[CCMHTTPSCERTNAME: ]LOG]!><time="09:45:07.045+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="3108" file="ccmsetup.cpp:7912">
<![LOG[FSP: HFXDBSSOM.CORP.EASTLINK.CA]LOG]!><time="09:45:07.045+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="3108" file="ccmsetup.cpp:7927">
<![LOG[CCMFIRSTCERT: 0]LOG]!><time="09:45:07.061+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="3108" file="ccmsetup.cpp:7969">
<![LOG[Config file: C:\WINDOWS\system32\ccmsetup\MobileClient.tcf]LOG]!><time="09:45:07.061+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="3108" file="ccmsetup.cpp:4341">
<![LOG[Retry time: 10 minute(s)]LOG]!><time="09:45:07.061+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="3108" file="ccmsetup.cpp:4342">
<![LOG[MSI log file: ]LOG]!><time="09:45:07.061+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="3108" file="ccmsetup.cpp:4343">
<![LOG[MSI properties: INSTALL="ALL" SMSSITECODE="PHX" CCMHTTPPORT="80" CCMHTTPSPORT="443" CCMHTTPSSTATE="0" FSP="HFXDBSSOM.CORP.EASTLINK.CA" CCMFIRSTCERT="0"]LOG]!><time="09:45:07.061+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="3108" file="ccmsetup.cpp:4344">
<![LOG[Source List:]LOG]!><time="09:45:07.061+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="3108" file="ccmsetup.cpp:4352">
<![LOG[ \\HFXDBSSOM.corp.eastlink.ca\SMSClient]LOG]!><time="09:45:07.061+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="3108" file="ccmsetup.cpp:4359">
<![LOG[ \\HFXDBSSOM\SMSClient]LOG]!><time="09:45:07.061+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="3108" file="ccmsetup.cpp:4368">
<![LOG[MPs:]LOG]!><time="09:45:07.061+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="3108" file="ccmsetup.cpp:4371">
<![LOG[ HFXDBSSOM.corp.eastlink.ca]LOG]!><time="09:45:07.061+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="3108" file="ccmsetup.cpp:4386">
<![LOG[Updated security on object C:\WINDOWS\system32\ccmsetup\.]LOG]!><time="09:45:07.076+240" date="12-06-2007" component="ccmsetup" context="" type="0" thread="3108" file="ccmsetup.cpp:8692">
<![LOG[Sending Fallback Status Point message, STATEID='100'.]LOG]!><time="09:45:07.076+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="3108" file="ccmsetup.cpp:9169">
<![LOG[State message with TopicType 800 and TopicId {A450B407-619B-4777-B77E-C3352753B58A} has been sent to the FSP]LOG]!><time="09:45:07.326+240" date="12-06-2007" component="FSPStateMessage" context="" type="1" thread="3108" file="fsputillib.cpp:730">
<![LOG[Running as user "SYSTEM"]LOG]!><time="09:45:07.326+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="2600" file="ccmsetup.cpp:2534">
<![LOG[Detected 24292 MB free disk space on system drive.]LOG]!><time="09:45:07.326+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="2600" file="ccmsetup.cpp:465">
<![LOG[DetectWindowsEmbeddedFBWF() Detecting OS Version]LOG]!><time="09:45:07.342+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="2600" file="ccmsetup.cpp:511">
<![LOG[Client OS is not Windows XP Embedded]LOG]!><time="09:45:07.342+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="2600" file="ccmsetup.cpp:548">
<![LOG[Successfully ran BITS check.]LOG]!><time="09:45:08.745+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="2600" file="ccmsetup.cpp:6948">
<![LOG[Failed to successfully complete HTTP request. (StatusCode at WinHttpQueryHeaders: 401)]LOG]!><time="09:45:08.745+240" date="12-06-2007" component="ccmsetup" context="" type="3" thread="2600" file="ccmsetup.cpp:5813">
<![LOG[Sending Fallback Status Point message, STATEID='308'.]LOG]!><time="09:45:08.760+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="2600" file="ccmsetup.cpp:9169">
<![LOG[State message with TopicType 800 and TopicId {3BFABF82-FB74-43FB-8A4A-6DFDEAEAC25C} has been sent to the FSP]LOG]!><time="09:45:08.776+240" date="12-06-2007" component="FSPStateMessage" context="" type="1" thread="2600" file="fsputillib.cpp:730">
==============================================================
There are two red errors I am concerned about:
"Failed to successfully complete HTTP request. (StatusCode at WinHttpQueryHeaders: 401)
and
"Failed to download 'WindwosXP-KB923845-x86-ENU.exe' from http://HFXDBSSOM.corp.eastlink.ca/CCM_Client/i386/BITS25 with error code 0x80004005).
What should I do to resolve these errors?
Thanks,
Peter
You would havve to check the ccm.log. I know you said you "do not see anything helpful" in the log, but if you are doing a push, and the Ccmsetup folder is not created, that means the site server has an issue installing the bootstrap, which would be logged in the ccm.log file. So without knowing what is in there, there is no way to offer any assistance.
For a push, it is ccm.log on the site server until the site server installs the bootstrap. Search on the target computer name.
If that is successful, then you should see the Windows\System32\Ccmsetup\Ccmsetup.log for any install issues locally.
Hello,
I have tried running the Client Push wizard for a single computer or a pilot collection of 8 computers, the result is always
the same - no SCCM client is installed on any computer.
The computers are running 32-bit Windows XP SP2.
The Windows firewall is disabled.
The client push installation account is setup and have domain admin and local admin privileges. Client Push automatic method
is not enabled.
The domain is AD WIndows 2000.
The SCCM server is running Windows 2003 R2 SP2 64bit Standard.
The AD schema has been extended.
MP, and SLP are installed and published. (MP is published in DNS as well.)
FSP is installed.
MP, SLP and FSP are running on the same server.
SQL 2005 server is running locally.
System management container is created and all rights and permissions delegated.
With the Push installation account I can access C$ share on the client computer from the SCCM server.
RPC, Remote registry, WMI services are running on the client machines.
All prerequisites are installed from the client folder on SCCM server- latest BITS 2.5, Windows installer 3.1 and MSXML6.
All computers are in the same IP subnet which is listed in the boundaries.
Yet, the client is not being installed.
No CCMSetup folder is created on the client machines in Windows\System32 folder, so it is really difficult to troubleshoot
what the is the issue. I do not see anything helpful in the ccm.log on the server.
I have tried running the CCMSetup.exe manually on one of the workstations and that was successful and reported back to the
SCCM server / console.
What else I should check / try? I really want to push agents via the wizard.
Thank you,
Peter