SCCM client failed to install on all win7 computers
-
Tuesday, April 10, 2012 4:25 PM
Hi team, we are trying to install (push ) sccm 2007 agent to win7 computers but all failed. xp all fine for a few years. Error on RegTask: Failed to refresh site code. Error: 0x80004005 for the ClientIDManagerStartup.log
I tried running the installation via manually using the ccmsetup.exe. I even tried adding the management point using the argument /mp:hostname.domain.com
It seems that I am able to install the client successfully.
But the client was unable to work till I ran the repair from the Server via Client centre .SCCM client got no error
The Client is showing No. (It is within the same boundary)
any advice please? Thanks
- Moved by Moiz Rassiwala[MSFT]Microsoft Employee Tuesday, April 10, 2012 5:14 PM (From:Configuration Manager General)
All Replies
-
Tuesday, April 10, 2012 5:13 PM
Is firewall disabled on Windows 7 Computers ?
If client push has worked for Windows Xp , I would assume you have client push agent account set which has admins rights to workstations
- Edited by PicSee Tuesday, April 10, 2012 5:14 PM
-
Tuesday, April 10, 2012 5:16 PM
First, one quick note: /mp does not set the MP. /mp is a switch for the ccmsetup bootstrap program that tells ccmsetup to download the required client
installation files using BITS from the MP.Are there any other errors in the log files like ccmexec.log, locationservices.log, or clientlocation.log?
Jason | http://blog.configmgrftw.com | Twitter @JasonSandys
-
Wednesday, April 11, 2012 9:45 AMpush install succeeded. we tried manual install too, same result. it has to be repaired . otherwise it just not working. client status shows no. any advice please? admin right.no error found in log files.
-
Wednesday, April 11, 2012 2:19 PM
Client status = no just means the client has never contacted the server and has nothing to do with installation success or failure.
How were these systems deployed? Were they deployed with an agent already on them?
Can you zip up and post your (client) log files directory on a file sharing service? There has to be an error.
Jason | http://blog.configmgrftw.com | Twitter @JasonSandys
-
Thursday, April 12, 2012 9:28 AM
Hi,
It seems like client reporting issue.
Error on RegTask: Failed to refresh site code. Error: 0x80004005
Upon error may happen with incorrect client installation properties specified.
Such as: SMSSITECODE=ABC,SMSCACHESIZE=1000
SCCM will not validate the site code setting, since there's a comma but no space, anything specified after SMSSITECODE= is considered to be the site code. As a result, the installation command line will be incorrect.
Check the ccmsetup.log to verify client setup properties, it should be something like:
MSI PROPERTIES are REINSTALL=ALL REINSTALLMODE=vmaus INSTALL="ALL"
SMSSITECODE="ABC" "SMSCACHESIZE=1000" CCMHTTPPORT="80" CCMHTTPSPORT="443"
CCMHTTPSSTATE="0" CCMFIRSTCERT="0"
SMSPUBLICROOTKEY=<...key...>For client reporting issue troubleshooting details, you should read this blog carefully:
Troubleshooting issues where clients are not reporting
Also take a look at this technet blog, it maybe help:
Troubleshooting SCCM ..Part I (Client Push Installation )
Thanks
-
Thursday, April 12, 2012 10:38 AM
Thanks . the client configuartion manager properties show this information:
conifgmgr client version : 4.00.6221.1000
configmgr connection type: Unknown
FQDN: NBhost.domain.com
IP: 192.1.1.111
Logon user: domain\someone
Login domain: abc.com
MAC: F0:xxxxxxx....
Site Mode: Unknown
Advanced:
Currently assigne to site code: S02
temperaroy program download folder: c:\windows\syswow64\cache
component-- all shows "Installed"
ANy advice please?Thanks!
-
Thursday, April 12, 2012 10:50 AM
Hi, Please check that all require services are running. what happens when you manually discovers site code from SCCM client? If it is successful try to initiate action "Machine policy retrieval & evaluation cycle" & monitor the logs file. Hope you already configured firewall settings.Prashant Patil
- Marked As Answer by Sabrina ShenModerator Monday, April 30, 2012 4:07 AM
-
Thursday, April 12, 2012 11:50 AMModerator
Any chance that the client is stuck in provisioning mode? http://blogs.technet.com/b/configurationmgr/archive/2010/09/13/solution-after-a-configmgr-2007-osd-task-sequence-completes-the-client-may-not-automatically-pull-down-policy.aspxSite Mode: Unknown
Torsten Meringer | http://www.mssccmfaq.de
- Marked As Answer by Sabrina ShenModerator Monday, April 30, 2012 4:07 AM

