Hello,
I completely disabled Windows Firewall on the client, and then ran the test:
RUN-->WBEMTEST-->CONNECT-->TYPE \\ipaddress\root\cimv2 THEN CLICK CONNECT
I received the error:
Number: 0x80070057
Facility: Win32
Description: The parameter is incorrect.
Any suggestions?
I'm stuck with same issue....followed all above steps, but client is not getting downloaded to local machine.
I don't see anything in ccm.log file on server
please help me..
this is the latest log file update
************** Client Config Manager main thread starting ************** SMS_CLIENT_CONFIG_MANAGER 12/08/2012 12:00:49 AM 3168 (0x0C60)
This site: "BLM". SMS_CLIENT_CONFIG_MANAGER 12/08/2012 12:00:49 AM 3168 (0x0C60)
This machine: "BLMSCCMSR". SMS_CLIENT_CONFIG_MANAGER 12/08/2012 12:00:49 AM 3168 (0x0C60)
The Site Control File has changed, parameters will be reread. SMS_CLIENT_CONFIG_MANAGER 12/08/2012 12:00:49 AM 3168 (0x0C60)
Updating Site Parameters SMS_CLIENT_CONFIG_MANAGER 12/08/2012 12:00:49 AM 3168 (0x0C60)
MP Ports: 80 SMS_CLIENT_CONFIG_MANAGER 12/08/2012 12:00:49 AM 3168 (0x0C60)
MP SSL Ports: 443 SMS_CLIENT_CONFIG_MANAGER 12/08/2012 12:00:49 AM 3168 (0x0C60)
IISPreferedPort: 80 SMS_CLIENT_CONFIG_MANAGER 12/08/2012 12:00:49 AM 3168 (0x0C60)
IISSSLPreferedPort: 443 SMS_CLIENT_CONFIG_MANAGER 12/08/2012 12:00:49 AM 3168 (0x0C60)
Default MP: BLMSCCMSR SMS_CLIENT_CONFIG_MANAGER 12/08/2012 12:00:49 AM 3168 (0x0C60)
SSL State: 0 SMS_CLIENT_CONFIG_MANAGER 12/08/2012 12:00:49 AM 3168 (0x0C60)
Certificate Selection Criteria: SMS_CLIENT_CONFIG_MANAGER 12/08/2012 12:00:49 AM 3168 (0x0C60)
Certificate Store: SMS_CLIENT_CONFIG_MANAGER 12/08/2012 12:00:49 AM 3168 (0x0C60)
Select First Certificate: 0 SMS_CLIENT_CONFIG_MANAGER 12/08/2012 12:00:49 AM 3168 (0x0C60)
Checking configuration information for server: BLMSCCMSR. SMS_CLIENT_CONFIG_MANAGER 12/08/2012 12:00:49 AM 3168 (0x0C60)
Checking configuration information for server: BLMSCCMSR. SMS_CLIENT_CONFIG_MANAGER 12/08/2012 12:00:49 AM 3168 (0x0C60)
Fallback Status Point: BLMSCCMSR.LNTIES.COM SMS_CLIENT_CONFIG_MANAGER 12/08/2012 12:00:49 AM 3168 (0x0C60)
Install on DC: False SMS_CLIENT_CONFIG_MANAGER 12/08/2012 12:00:49 AM 3168 (0x0C60)
Site account information has been refreshed SMS_CLIENT_CONFIG_MANAGER 12/08/2012 12:00:49 AM 3168 (0x0C60)
Retrieving properties from the site control file. SMS_CLIENT_CONFIG_MANAGER 12/08/2012 12:00:49 AM 3168 (0x0C60)
Security Mode Option - CCR buffering disabled. SMS_CLIENT_CONFIG_MANAGER 12/08/2012 12:00:49 AM 3168 (0x0C60)
Default Client Type: -1 SMS_CLIENT_CONFIG_MANAGER 12/08/2012 12:00:49 AM 3168 (0x0C60)
Ignoring unrecognized property "Bootstrap Download Timeout" SMS_CLIENT_CONFIG_MANAGER 12/08/2012 12:00:49 AM 3168 (0x0C60)
Ignoring unrecognized property "Bootstrap Retry Interval" SMS_CLIENT_CONFIG_MANAGER 12/08/2012 12:00:49 AM 3168 (0x0C60)
Advanced Client Command Line: SMSSITECODE=BLM SMS_CLIENT_CONFIG_MANAGER 12/08/2012 12:00:49 AM 3168 (0x0C60)
Ignoring unrecognized property "Advanced Client Command Line Default" SMS_CLIENT_CONFIG_MANAGER 12/08/2012 12:00:49 AM 3168 (0x0C60)
Hi All,
Have faced same issue ,Have done below things its working fine.
To use client push to install the System Center 2012 Configuration Manager client, add the following as exceptions to the Windows Firewall:
INBOUND RULE EXCEPTION
OUTBOUND RULE
ENABLE ONLY File and Printer Sharing.
ONCE THE ABOVE THINGS ARE DONE Test following things
RUN-->WBEMTEST-->CONNECT-->TYPE \\CLIENTNAME\root\cimv2 THEN CLICK CONNECT
THE ABOVE THING IS NOT WORKING MEANS CLIENT WONT GET INSTALL.
Regards,
vasanth
http:\\vasanthsccm.wordpress.com
I have met the same problem,all of systems cannot install client agent! both 'client push' and 'install client'! why?
The /noservice switch will not resolve the client push issue.
To resolve the;
<![LOG[Failed to successfully complete HTTP request. (StatusCode at WinHttpQueryHeaders: 401
I granted IUSR read permission on the CCM_Client VD and IUSR read permission NTFS to the Program Files\Microsoft Configuration Manager\client directory.
Abdul,
I remember reading that you cannot use the CCMSetup.exe properties in the "Installation properties:" box under:
Site Mgmt -> Site name -> Site settings -> Client Install Methods -> Client Push Installation Properties -> Client Tab
(My reference is the second Note: at: http://technet.microsoft.com/en-us/library/bb680938.aspx)
I believe the installation happens via the Client.msi file, which has a different set of installation properties. Instead look at the list of properties under "Client.msi Properties" at:http://technet.microsoft.com/en-us/library/bb680980.aspx.
Apparently, the Fallback Service Point and the Management Point are automatically applied under Client Push Installation.
Hope that helps,
Aaron
HI Wally,
Please go through this with me.
To add the /noservice switch, I need to do the following:
Site Mgmt -> Site name -> Site settings -> Client Install Methods
properties of Client push installation, click on the client tab and add /noservice in addition to :
smssitecode=xyz FSP=siteserver name.
Please advise if the above is correct. The reason I ask is because I had the /mp: siteserver and got an error when trying to install the clients before.
Now when I add the /noservice, I get the following errors on the log of client machines (ccmsetup.log). See below
Invalid argument: /noservice ccmsetup 05/11/2008 05:17:55 AM 448 (0x01C0)
Invalid ccmsetup command line: "C:\WINDOWS\system32\ccmsetup\ccmsetup.exe" /runservice /config:MobileClient.tcf ccmsetup 05/11/2008 05:17:55 AM 448 (0x01C0)
I am obviously missing someting...
I have my wsus and sccm installed on the same server and have one site. my sccm db is on a seperate sql server. I am in mixed mode.
When I try to install the clients manually, they install and report correctly.
Regards
Abdul
I have the push client configured and automatic approval set for machines in a trusted domain so my expectation is this is all I need an POOF the client should be installed?
I am looking at the /noservice as well as the firewall issues BUT is there way to say to the system :evaluate the clients now for client push” so I can speed up my testing and not wait X amount of cycles to see if it worked? How often does it evaluate clients to see if they should automatically get the client? If it evaluates them one will it do it again without any changes to the client?
Please make it an X then Y then Z answer for a meer mortal
There is no fix, as there is nothing broken here. We don't automatically try using the service method, and then if fails, go to the user only method. You have to configure it to use that method if you want.
I've never had to use the /noservice switch for a push. If you allow us to set the permissions on the directories and use this push method, I don't know why you would have to use it.
I have had to use this method if I manually run ccmsetup.exe from the site server using the
\\smsserver\c$\Program Files\Microsoft Configuration Manager\Client folder to keep it from using the service account however.
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!