Hi guys, I have a new installation of SCCM2007 and try to install first client agent to a WinXP machine. After I start push installation to this PC nothing happening, there's even no CCm log on client pc. I have following lines in C:\Program Files (x86)\Microsoft Configuration Manager\Logs\ccm.txt on SCCM server: Attempting to connect to administrative share '\\<FQDN of client PC>\admin$' using account '<domain account>'~ $$<SMS_CLIENT_CONFIG_MANAGER><Tue Dec 28 16:30:58.233 2010 Russian Standard Time><thread=2904 (0xB58)> ---> WNetAddConnection2 failed (LOGON32_LOGON_NEW_CREDENTIALS) using account <domain account> (0000052e) $$<SMS_CLIENT_CONFIG_MANAGER><Tue Dec 28 16:31:13.405 2010 Russian Standard Time><thread=2904 (0xB58)> ---> LogonUser failed (LOGON32_LOGON_INTERACTIVE) using account <domain account> (0000052e) $$<SMS_CLIENT_CONFIG_MANAGER><Tue Dec 28 16:31:28.406 2010 Russian Standard Time><thread=2904 (0xB58)> I have the same account <domain account> at Client Push Installation Properties and Local Administrators group on client PC. And can open admin$ share from SCCM server on client PC with no problem. Any ideas?

Hi, Can you access to the xp admin$ share using \\computername\admin$ with the user account configured for the client push installation ? Is that user account added in the local admin group on the xp machine, have you checked that ? Did you type the password correctly on the client push installation properties ? Bechir Gharbi | http://myitforum.com/cs2/blogs/bgharbi/

Just to add to Bechir's comments (I totally consur with his line of thinking): just because you can access a share, doesn't mean the account you've specified in the client install properties can. The account you specify must have local admin privileges on the client to access the admin$ administrative share, a normal domain account will not suffice.Jason | http://myitforum.com/cs2/blogs/jsandys | http://blogs.catapultsystems.com/jsandys/default.aspx | Twitter @JasonSandys

Hi, 0000052e means that the account unknown or password incorrect, so I suggest that you check that you type your password and account correctly in SCCM console client push installation properties. Julien

Hi, 0000052e means that the account unknown or password incorrect, so I suggest that you check that you type your password and account correctly in SCCM console client push installation properties. Julien

Hi, 0000052e means that the account unknown or password incorrect, so I suggest that you check that you type your password and account correctly in SCCM console client push installation properties. Julien

Hello - Also check whether Firewall is enabled on XP pc.....Anoop C Nair

Hi, Follow the below step to find the culprit. 1. Push the client on some other machine without changing the Account specified for client push. If failed = that means the account configured for push is incorrect (Change the Password for client push) If succeeded = Follow the below step (that means account configured for client push is working fine) 2. Go to the client machine and make sure that account used for client push is the member of local admin group on the XP machine If not then add the account to the local administrator group of XP machine. 3. As anoop said please check your firewall setting. 4. Also make sure that XP client falls under the boundary specified.

Hi, Follow the below step to find the culprit. 1. Push the client on some other machine without changing the Account specified for client push. If failed = that means the account configured for push is incorrect (Change the Password for client push) If succeeded = Follow the below step (that means account configured for client push is working fine) 2. Go to the client machine and make sure that account used for client push is the member of local admin group on the XP machine If not then add the account to the local administrator group of XP machine. 3. As anoop said please check your firewall setting. 4. Also make sure that XP client falls under the boundary specified.

Hi, As this thread has been quiet for a while, we assume that the issue has been resolved. At this time, we will mark it as "Answered" as the previous steps should be helpful for many similar scenarios. In addition, we’d love to hear your feedback about the solution. By sharing your experience you can help other community members facing similar problems. Thanks,Yog Li -- Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.