Client PUSH Installation ( not working )
Hi Wally, As promised, I'm starting a new thread. I have been trying to install clients using client push installation but have failed to do so after so many attempts.For one test PC i get this error in CCM.log file Attempting to connect to administrative share '\\pckhiitd775.ppl.com.pk\admin$' using account 'pplnet\sms_client' WNetAddConnection2 failed (LOGON32_LOGON_NEW_CREDENTIALS) using account pplnet\sms_client (00000775) LogonUser failed (LOGON32_LOGON_INTERACTIVE) using account pplnet\sms_client (00000775) Attempting to connect to administrative share '\\pckhiitd775.ppl.com.pk\admin$' using machine account. Failed to connect to \\pckhiitd775.ppl.com.pk\admin$ using machine account (5) ERROR: Failed to connect to the \\pckhiitd775.ppl.com.pk\admin$ share using account 'Machine Account' Whileforthe other test PC i get this in this log file. Attempting to connect to administrative share '\\PCKHIITD689.ppl.com.pk\admin$' using account 'pplnet\sms_client' WNetAddConnection2 failed (LOGON32_LOGON_NEW_CREDENTIALS) using account pplnet\sms_client (0000052e) LogonUser failed (LOGON32_LOGON_INTERACTIVE) using account pplnet\sms_client (0000052e) Attempting to connect to administrative share '\\PCKHIITD689.ppl.com.pk\admin$' using machine account. Failed to connect to \\PCKHIITD689.ppl.com.pk\admin$ using machine account (5) ERROR: Failed to connect to the \\PCKHIITD689.ppl.com.pk\admin$ share using account 'Machine Account' While going through one of the post I found you out saying. """ Error 52e is unknown user or bad password, so it is an account issue. What I always do to test is: * Start a Command Prompt* Type: "net use l: \XPclient\admin$ /u:testserver2003\test password" """" I tried the same with obviously my test computer names and user passwords and was able to successfully run this command on CLIENT PCs as well as on the SCCM server. I also checked the account sms_client and its present in the administrator group of both tests PCs. Now, I have no idea what to do as you see its not an issue of user access or bad password. Plus the other computer is giving error 775 which is something quiet strange. Your prompt and helpful reply is eagerly awaited. Regards,
March 7th, 2008 8:44am

Hi, here in my vm network with 3 primary sites in one AD the client push function works. I usedthe local Administrator as the account. Do you specify the account with password in the push client mask?
Free Windows Admin Tool Kit Click here and download it now
March 7th, 2008 5:28pm

Error 775 is 1909, which is the account referred to is locked out. Pretty self explanatory for account: pplnet\sms_client And the 52e is the 1326 error - unknown user or bad password. These are errors that the OS gives us when we're trying things, we don't make them up. So, that account is locked out on pckhiitd775, and is invalid on PCKHIITD689. I'd venture a guess that you didn't do the: net use l: \\PCKHIITD689\admin$ /uplnet\sms_client successfully, as the OS wouldn't allow us to use that account. That's what I'd check out, given the errors listed in the log.
March 8th, 2008 9:31pm

HI Wally, I definately had tried the net use command that you had mentioned and I was able to map drives using the same command on both PCs which means account is neither LOCKEd nor it isINVALID. Further more I have checked the account and I have been using the same account to distibute Patches and Softwares on my working Client. I was able to install client on PCKHIITD689 using the same account with client push method and i have made another post about the HTTP issue ( also mentioned towards the end of this post )I m facing for that client. ( waiting for your answer to that post ) It mightinterest you that when i try installing the client using ccmsetup.exe with parameters ccmsetup.exe /mp:<MP name> SMSSITECODE=<code> SLP=<SLP name> from command prompt on client PCKHIITD314, I get this in the ccmsetup.log file on client: --->downloading file client.msi --->determining source location --->source \\pplkhiho09\smsclient\I386 is inaccessible (5) --->failed to find accessible source. waiting for... Now, I have checked this source location and its sharing and everything is ok. I tried to access the share from the same client machine using the same user account as used by SCCMand was able to do that successfully. This issue has taken up3 days now and is still unresolved. Anyway, Here is the CCM.log file on server when i try to do a client push installation on a pc named PCKHIITD314. Everytime I am being provided by a new sort of error. ccm.log Waiting for change in directory "D:\Program Files\Microsoft Configuration Manager\inboxes\ccr.box" for queue "Incoming", (30 minute backup timeout). ======>Begin Processing request: "URFMWMOU", machine name: "PCKHIITD314"---> Trying the 'best-shot' account which worked for previous CCRs (index = 0x1)---> Attempting to connect to administrative share '\\PCKHIITD314.ppl.com.pk\admin$' using account 'pplnet\ap_operator'---> The 'best-shot' account has now succeeded 2 times and failed 0 times.---> Connected to administrative share on machine PCKHIITD314.ppl.com.pk using account 'pplnet\ap_operator'---> Attempting to make IPC connection to share <\\PCKHIITD314.ppl.com.pk\IPC$>---> Searching for SMSClientInstall.* under '\\PCKHIITD314.ppl.com.pk\admin$\'CWmi::Connect(): ConnectServer(Namespace) failed. - 0x800706ba---> Unable to connect to WMI on remote machine "PCKHIITD314", error = 0x800706ba.---> Deleting SMS Client Install Lock File '\\PCKHIITD314.ppl.com.pk\admin$\SMSClientInstall.KHI'Retry request id for "URFMWMOU" set to "PCKHIITD314_ppl_com_pk"Stored request "PCKHIITD314_ppl_com_pk", machine name "PCKHIITD314", in queue "Retry".<======End request: "PCKHIITD314_ppl_com_pk", machine name: "PCKHIITD314". One more thing is thatonceI somehowsuccessfully install the client manually, then I am usually provided by this error in policyagent.log file upon distributing any patches. Cleaning policy for 'SMS:KHI' in '\\PCKHIITD314\ROOT\ccm\Policy\S_1_5_21_2049651388_11092402_1330272300_6125\RequestedConfig' () Failed in WinHttpReceiveResponse API, ErrorCode = 0x2f78 [CCMHTTP] HTTP ERROR: URL=http://PPLKHIHO09/SMS_MP/.sms_pol?{6b9109cc-e36d-415c-85ba-3cb9fc3febf3}.3_00, Port=80, Protocol=http, SSLOptions=0, Code=12152, Text=ERROR_WINHTTP_INVALID_SERVER_RESPONSE Raising event: instance of CCM_CcmHttp_Status{ClientID = "GUID:F6C26131-4B60-45DB-9877-30E82B05EC86";DateTime = "20080311035526.670000+000";HostName = "PPLKHIHO09";HRESULT = "0x80072f78";ProcessID = 1344;StatusCode = 0;ThreadID = 3980;}; HTTP download of http://PPLKHIHO09/SMS_MP/.sms_pol?{6b9109cc-e36d-415c-85ba-3cb9fc3febf3}.3_00 failed: 999 Unknown It seems that both these errors are related.I have checked and taken every possible actionI could think of regarding the network access and authorization of the used accounts but I have been UNSUCCESSFUL. I hope You can provide me with some solid solution and the detail steps to resolve this issue. NAweed
Free Windows Admin Tool Kit Click here and download it now
March 11th, 2008 1:23pm

Well, I can tell you that we don't make up these errors, we use the underlying network services to establish the connections - so there could have been other issues. Anyway, you got your client installed. Comments I have are: SLP= should be SMSSLP= so right now you are NOT using an SLP. The connection issue is that we don't share the Client folder, so not sure why yours says \\pplkhiho09\smsclient\I386. We did create that smsclient share in SMS 2003, so if this is an upgraded site, that would explain it. For Configuration Manager, we don't share the folder, and you need to run ccmsetup from the \Program Files\Microsoft Configuration Manager\Client folder (not I386). You might also need to add the /useronly switch, as otherwise, we might switch to a service context, which woudl be the client computer account, which might not have access. Finally, error 12152 can mean a ton of different things - IIS accounts, permissions, lack of SQL access, etc. Here's a list of things from SMS 2003 that you would need to validate: Run http://<MP name>/sms_mp/.sms_aut?mplist This returns a blank screen. Run http://<MP name>/sms_mp/.sms_aut?mpcert This returns a long list of numbers and letters. Verify that the DTS Service is enabled. Verify that the Task Scheduler is enabled. Verify that the Windows Management Instrumentation service is running. Verify that the SMS Agent Host service is running. Verify that the World Wide Web Publishing Service is running. Verify that the MP machine account has been added to the SMS_SiteSystemToSQLConnection_<site_code> group. Verify that the SQL Server has named pipes enabled. Update MDAC on the server. Review Q820910 for details. http://support.microsoft.com/default.aspx?scid=kb;en-us;820910 SQL boxes that are running under a user account, instead of system, need the SPN updated in AD. Review Q829868 for additional details. http://support.microsoft.com/default.aspx?scid=kb;en-us;829868 Crossing domain boundaries between MP and SQL may also need the SPN updated in AD. Review Q829868 for additional details. http://support.microsoft.com/default.aspx?scid=kb;en-us;829868 IIS Lockdown Tool If you are using the IIS lockdown tool on your IIS 5 servers be sure to apply the SMS server template from the SMS 2003 toolkit. http://www.microsoft.com/smserver/downloads/2003/tools/toolkit.asp Deinstall the MP and IIS, then reinstall IIS and the MP. Remove the MP role on the server. Disable IIS. Remove completely. Reboot the server. Verify that the DTS Service is enabled. Verify that the Task Scheduler is enabled. Verify that the Windows Management Instrumentation service is running. Enable BITS, enable WEBDEV and install IIS. Verify that the World Wide Web Publishing Service is running. Verify that the MP machine account has been added to the SMS_SiteSystemToSQLConnection_<site_code> group. Enable MP role on the server.
March 12th, 2008 4:30am

Thanks Wally for your reply. I infact used SMSSLP=" " so i think that is workign fine. I have just joined this company and they have informed me that they tried to upgrade their SMS2003 site but when they were unable to do that they installed the SCCM from scratch and hence according to them its not an upgradation of SMS2003 but its a fresh SCCM2007 site. Now if you can help me telling the way to check if its an upgraded site or its a fresh install, that be of great help. Secondly, when I installed a client on a PC today it copied file from the configuration manager folder mentioned below: ---> Copying file "D:\Program Files\Microsoft Configuration Manager\bin\I386\MobileClient.tcf" to "\\PCKHIITD510\admin$\system32\ccmsetup\MobileClient.tcf" ---> Copying file "D:\Program Files\Microsoft Configuration Manager\bin\I386\ccmsetup.exe" to "\\PCKHIITD510\admin$\system32\ccmsetup\ccmsetup.exe" and the installation went fine. The only thing wrong in the ccm.log file is ---> CWmi::Connect(): ConnectServer(Namespace) failed. - 0x8004100e ---> Unable to connect to WMI (r) on remote machine "PCKHIITD510", error = 0x8004100e. After showing this error, it copies the file as mentioned above from the given folder, starts the ccmsetup service and installs the client as well. Now, I restarted the WMI service, deleted the reposiroty and started the service again as mentioned in some post to get this WMI issue resolved, but its still the same. Can you please tell me how can I fix this issue. Regarding HTTP error, I noticed one thing today that the error mentioned below is also present in the PolicyAgent.log of one client PC, but still I'm ABLE to install all updates and softwares on this PC. But the same updates and software packages do not show on the other PCs with the same error. Now what do you think is wrongwith those PCsthat they are not able to dowbload the policies. The logs of PC successfully downloading updates is as follows: Failed in WinHttpReceiveResponse API, ErrorCode = 0x2f78 [CCMHTTP] HTTP ERROR: URL=http://PPLKHIHO09/SMS_MP/.sms_pol?{6b9109cc-e36d-415c-85ba-3cb9fc3febf3}.3_00, Port=80, Protocol=http, SSLOptions=0, Code=12152, Text=ERROR_WINHTTP_INVALID_SERVER_RESPONSE Raising event: instance of CCM_CcmHttp_Status{ClientID = "GUID:BA3AA2CD-084D-4DD6-9E44-F42F92C1B91E";DateTime = "20080312093619.848000+000";HostName = "PPLKHIHO09";HRESULT = "0x80072f78";ProcessID = 1756;StatusCode = 0;ThreadID = 1012;}; HTTP download of http://PPLKHIHO09/SMS_MP/.sms_pol?{6b9109cc-e36d-415c-85ba-3cb9fc3febf3}.3_00 failed: 999 Unknown Another interesting thing to mention is that the PCs which are unable to downlaod updates are missing ContentTransferManager.log file in their C:\WINDOWS\system32\CCM\Logs folder. how come this file is not present in those PCs. I hope you can help me through this. Naweed
Free Windows Admin Tool Kit Click here and download it now
March 12th, 2008 12:56pm

Sorry, I don't know how to fix the WMI issue, it is a WMI issue however (from all indications). If a rebuild of the repository doesn't do it, then my only suggestion would be a reinstall of the client. As to the HTTP error, I don't know either. If other clients are able to download policies and install software or updates, then the MP is working fine, but this client is having an issue. Again, that points to a client issue. ContentTransferManager.log is used to download content to the client Cache. If the client can't access the MP to get policies, then it can't find any policies with content to download, so no need to do any downloads.
March 13th, 2008 7:46am

Thank you so much Wally, Well, I once again checked the CAS.log file on the clients which are not getting updates and I found out this common error on the clients which are not downloading updates. they show Software Distribution Site Settings for the client are missing from WMI. CacheConfig::InitializeFromWmi - GetSWDistSiteSettings failed with 0x80004005. Default site settings will be used GetLogonUserSid failed at GetTokenSids 0x800704dd This is the common error code on all clients. the CAS.log file do not show anything else. Can you please help me with this 0x800704dd & 0x80004005 errors..? About the WMI issues I found something related on this link. http://www.poweradmin.com/help/enableWMI.aspx But I wanted to confirm two things. Firstly should I try this...? Secondly, if this is the fix for the issue..how can i do this in a production environment with more than thousand PCs. I mean going to each PC and do all this is not realistic...Can there be any other work around...? Regards NAweed
Free Windows Admin Tool Kit Click here and download it now
March 18th, 2008 6:43am

I can't tell you whether or not the link is applicable, it is not ours. If it works, then great. You do see that entry in the client logs IF the client has not retrieved policies, so it doesn't know to enable the Advertised Programs Client Agent. However, 0x80004005 is: Unspecified error And 0x800704dd is: The operation being requested was not performed because the user has not logged on to the network. The specified service does not exist. By the way, you can look all these errors up on your own. Download and install the Configuration Manager Toolkit, start the SMS Trace (Trace32 tool) and use the Error Lookup function.
March 19th, 2008 4:28am

Hello Naweed, I have been also receiving the similar error. Did you manage to resolve this issue? Please advise. ---> CWmi::Connect(): ConnectServer(Namespace) failed. - 0x8004100e ---> Unable to connect to WMI (r) on remote machine "BICOR1", error = 0x8004100e ---> Creating \ VerifyingCopying exsistance of destination directory \\BICOR1\admin$\ccmsetup. ---> Copying client files to \\BICOR1\admin$\ccmsetup. ---> Updated service "ccmsetup" on machine "BICOR1" ---> Started service "ccmsetup" on machine "BICOR1" ---> Deleting SMS Client Install Lock File '\\BICOR1.corp.bitscape.com\admin$\SMSClientInstall.BIT' ---> Completed request "PCP1UYV5", machine name "BICOR1" Deleted request "PCP1UYV5", machine name "BICOR1" <======End request: "PCP1UYV5", machine name: "BICOR1". Submitted request successfully NOTE: I have ports 1035-5000 (TCP/UDP) open for my internal network for "All Users". Please help!Sumeet Khokhani
Free Windows Admin Tool Kit Click here and download it now
October 2nd, 2010 7:30am

Sumeet, The log text above show that the client DID install, why do you think that it didn't install?http://www.enhansoft.com/
October 3rd, 2010 12:55am

I have the same situation as Sumeet. But I do not have anything new installed in programs and features on the client machine. And in the configuration manager console, the client column still says no. I have system center essentials running in the environment still as we are working towards replacing that. If there is a mom 2007 r2 agent from SCE would that cause issues with the client deployment for Configuration Manager? Thanks, Jesse
Free Windows Admin Tool Kit Click here and download it now
March 28th, 2011 5:29pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics