Client push not working on secondary site
Hi Guys, my client push does not apear to be working. What logs etc can I look in for problems with Push?System discovery is enabled on the secondary site along with heartbet discovery. Client push is enabbled & with a valid account(mine). The Software update client installation method is also activated.the guys on that site have reinstalled a few PC's & they have checked over several days & the client dosent get pushed. if I manually install the client from SCCM console it installs fine.any ideas guys?
February 5th, 2010 2:05pm

Hi,Check the ccm.log on the site server. It will tell you if the process begins and if any errors occurs during the process.Kent Agerlund | http://scug.dk/members/Agerlund/default.aspx | The Danish community for System Center products
Free Windows Admin Tool Kit Click here and download it now
February 5th, 2010 2:08pm

dosent apear to like any account. not sure why its a domain admin account & ive deleted it & readded several times now to the client push.---> WNetAddConnection2 failed (LOGON32_LOGON_NEW_CREDENTIALS) using account ebnet\ME (000004b3) SMS_CLIENT_CONFIG_MANAGER 05/02/2010 11:03:43 6048 (0x17A0)---> WNetAddConnection2 failed (LOGON32_LOGON_INTERACTIVE) using account ebnet\ME (000004b3) SMS_CLIENT_CONFIG_MANAGER 05/02/2010 11:03:43 6048 (0x17A0)---> Trying each entry in the SMS Client Remote Installation account list SMS_CLIENT_CONFIG_MANAGER 05/02/2010 11:03:43 6048 (0x17A0)---> Attempting to connect to administrative share '\\192.168.65.92\admin$' using machine account. SMS_CLIENT_CONFIG_MANAGER 05/02/2010 11:03:43 6048 (0x17A0)---> Failed to get token for current process (5) SMS_CLIENT_CONFIG_MANAGER 05/02/2010 11:03:43 6048 (0x17A0)---> ERROR: Failed to connect to the \\192.168.65.92\admin$ share using account 'Machine Account' SMS_CLIENT_CONFIG_MANAGER 05/02/2010 11:03:43 6048 (0x17A0)---> Trying the account stored in the CCR (index = 0x0) SMS_CLIENT_CONFIG_MANAGER 05/02/2010 11:03:43 6048 (0x17A0)---> WNetAddConnection2 failed (LOGON32_LOGON_NEW_CREDENTIALS) using account ebnet\ME (000004b3) SMS_CLIENT_CONFIG_MANAGER 05/02/2010 11:03:43 6048 (0x17A0)---> WNetAddConnection2 failed (LOGON32_LOGON_INTERACTIVE) using account ebnet\ME (000004b3) SMS_CLIENT_CONFIG_MANAGER 05/02/2010 11:03:43 6048 (0x17A0)---> Trying each entry in the SMS Client Remote Installation account list SMS_CLIENT_CONFIG_MANAGER 05/02/2010 11:03:43 6048 (0x17A0)---> Attempting to connect to administrative share '\\192.168.65.92\admin$' using machine account. SMS_CLIENT_CONFIG_MANAGER 05/02/2010 11:03:43 6048 (0x17A0)---> Failed to get token for current process (5) SMS_CLIENT_CONFIG_MANAGER 05/02/2010 11:03:43 6048 (0x17A0)---> ERROR: Failed to connect to the \\192.168.65.92\admin$ share using account 'Machine Account' SMS_CLIENT_CONFIG_MANAGER 05/02/2010 11:03:43 6048 (0x17A0)---> Trying the account stored in the CCR (index = 0x0) SMS_CLIENT_CONFIG_MANAGER 05/02/2010 11:03:43 6048 (0x17A0)
February 5th, 2010 2:13pm

make sure you can connect to admin$ on thise machines. Check firewalls, policies etc.Kent Agerlund | http://scug.dk/members/Agerlund/default.aspx | The Danish community for System Center products
Free Windows Admin Tool Kit Click here and download it now
February 5th, 2010 2:58pm

Hi kent,This machine is one of my problem ones. its switched on. ccm.log shows this i can connect to the admin share from my Pc here on the primary site.---> WNetAddConnection2 failed (LOGON32_LOGON_NEW_CREDENTIALS) using account eastberks.ac.uk\ME (000004b3) SMS_CLIENT_CONFIG_MANAGER 05/02/2010 12:03:39 4852 (0x12F4)---> WNetAddConnection2 failed (LOGON32_LOGON_INTERACTIVE) using account eastberks.ac.uk\ME (000004b3) SMS_CLIENT_CONFIG_MANAGER 05/02/2010 12:03:39 4852 (0x12F4)---> Attempting to connect to administrative share '\\wi104-18.eastberks.ac.uk\admin$' using machine account. SMS_CLIENT_CONFIG_MANAGER 05/02/2010 12:03:39 4852 (0x12F4)---> Failed to get token for current process (5) SMS_CLIENT_CONFIG_MANAGER 05/02/2010 12:03:39 4852 (0x12F4)---> ERROR: Failed to connect to the \\wi104-18.eastberks.ac.uk\admin$ share using account 'Machine Account' SMS_CLIENT_CONFIG_MANAGER 05/02/2010 12:03:39 4852 (0x12F4)---> Trying the 'best-shot' account which worked for previous CCRs (index = 0x0) SMS_CLIENT_CONFIG_MANAGER 05/02/2010 12:03:39 4852 (0x12F4)---> Attempting to connect to administrative share '\\WI104-18\admin$' using account 'ebnet\mark chinery' SMS_CLIENT_CONFIG_MANAGER 05/02/2010 12:03:39 4852 (0x12F4)Submitted request successfully SMS_CLIENT_CONFIG_MANAGER 05/02/2010 12:03:40 4372 (0x1114)
February 5th, 2010 3:49pm

can you manually connect to the computer using the eastberks.ac.uk\ME account?Kent Agerlund | http://scug.dk/members/Agerlund/default.aspx | The Danish community for System Center products
Free Windows Admin Tool Kit Click here and download it now
February 5th, 2010 3:53pm

im logged in under that account & can access the \\wi104-18.eastberks.ac.uk\admin$ share..im going to get another domain admin to enter his account to see if that works.
February 5th, 2010 3:58pm

another domain adimn account but same issue. looks like there must be an issue with my secondary site as there is no problem acccessing the admin$ on the network with these accounts.---> Attempting to connect to administrative share '\\WI203C-01\admin$' using account 'ebnet\Account2' SMS_CLIENT_CONFIG_MANAGER 16/02/2010 03:38:28 5348 (0x14E4)---> WNetAddConnection2 failed (LOGON32_LOGON_NEW_CREDENTIALS) using account ebnet\Account2 (000004b3) SMS_CLIENT_CONFIG_MANAGER 16/02/2010 03:38:28 5348 (0x14E4)---> WNetAddConnection2 failed (LOGON32_LOGON_INTERACTIVE) using account ebnet\Account2 (000004b3) SMS_CLIENT_CONFIG_MANAGER 16/02/2010 03:38:28 5348 (0x14E4)---> Attempting to connect to administrative share '\\WI203C-01\admin$' using machine account. SMS_CLIENT_CONFIG_MANAGER 16/02/2010 03:38:28 5348 (0x14E4)---> Failed to get token for current process (5) SMS_CLIENT_CONFIG_MANAGER 16/02/2010 03:38:28 5348 (0x14E4)---> ERROR: Failed to connect to the \\WI203C-01\admin$ share using account 'Machine Account' SMS_CLIENT_CONFIG_MANAGER 16/02/2010 03:38:28 5348 (0x14E4)---> Trying each entry in the SMS Client Remote Installation account list SMS_CLIENT_CONFIG_MANAGER 16/02/2010 03:38:28 5348 (0x14E4)
Free Windows Admin Tool Kit Click here and download it now
February 16th, 2010 6:21pm

Hi All Is this issue resolved for anyone ??? I am also getting the same issue with the Client Deployment. ccm.log in server ---> Attempting to connect to administrative share xxxxxxxxxxxxxxxxxx using account xxxxxxxxxxxxxxxx ---> WNetAddConnection2 failed (LOGON32_LOGON_NEW_CREDENTIALS) using account xxxxxxxxxxxxxxx ---> Failed to get token for current process (5) when i look in the ccmsetup.log in Client i notice that the client installation succeeded. but in the configmgr console Client Status is NO, Assigned Status is Yes and Approved Status is N/A. Please help ....
April 12th, 2010 9:36am

The client installation seems to be successful. See ClientRegistration.log, ClientLocation.log and LocationServices.log on the client (if you already updates the collection membership and refreshed the console afterwards).
Free Windows Admin Tool Kit Click here and download it now
April 12th, 2010 12:51pm

The clients I was having issues with I done a WMI repair on (stop service, delete repositry, start service) & that seemed to resolve the issue.
April 12th, 2010 1:25pm

Thanks Torsten and chiners for your reply. Please clarify on one thing, The present setup we are using SLP and AD Schema is not Extended. Do we need to have an entry of SMS_SLP in WINS, in that scenario we have multiple locations with 4 Primary Sites configured with respective Site Boundaries and Discovery Methods. we could see that only 20% is Clients are installed. Few systems when i logon remotely to check the issue, i notice that the Client is installed and in the Client > Configuration Manager > Advanced Tab....there is no Site Code, in the server the Client Status is 'NO'. I checked the Locationservices.log and found errors for assignment. Assigning to site '***' LSVerifySiteVersion : Verifying Site Version for <***> LSGetSiteVersionFromAD : Failed to retrieve version for the site '***' (0x80004005) Attempting to retrieve SLPs from AD Failed to resolve 'SMS_SLP' to IP address from WINS LSGetSLP : Failed to resolve SLP from WINS, is it published LSGetSiteVersionFromSLP : Unable to get the list of SLPs LSVerifySiteVersion: Failed to get Site Version from AD and SLP Won't send a client assignment fallback status point message because the last assignment error matches this one. In this Case if i need to add an entry in WINS server, do i need to add all the SLP Servers. Please clarify..... Manoj Batchu
Free Windows Admin Tool Kit Click here and download it now
April 13th, 2010 12:37pm

Hi Chiners If i need to do WMI Repair for more than 100+ systems, what is the best way. Please suggest. Manoj Batchu
April 13th, 2010 12:39pm

Manoj, if you have that many machines it might not be WMI. Try this on a couple of machines as a test to see if it fixes it. As you are deleting the WMI repostry you cannot perform this via a remote session. You have to physically have to run this on the PC. 1. Login, 2. run batch file 3. reboot PC here is the contents of my batch file @ECHO OFF ECHO. ECHO Stopping Windows Managment Instrumentation (WMI) Service... net stop "winmgmt" ECHO. ECHO Service stopped. ECHO. ECHO. ECHO Deleting WMI Repository... RMDIR c:\windows\system32\wbem\repository /s /q ECHO. ECHO Repository Deleted ECHO. ECHO. ECHO Starting WMI Service... net start "winmgmt" ECHO. ECHO Service Started ECHO. ECHO. ECHO WMI Repair Completed pause exit
Free Windows Admin Tool Kit Click here and download it now
April 13th, 2010 1:40pm

Yes, you have to make sure that the clients are able to resolve the SLP from WINS: http://technet.microsoft.com/en-us/library/bb632567.aspx. Those errors you mentioned above have nothing to do with WMI issues.
April 13th, 2010 2:14pm

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

Other recent topics Other recent topics