SCCM 2007 Installing Clients

Tech-Archive recommends: Fix windows errors by optimizing your registry

I have setup SCCM and pushed out the client to all of my discovered
collections. I have found that about 50% of the machines I have discovered
would not take the client. I can see them, I can logon to their admin shares
but the client will not install. Here is a snip of logs reflecting the issue:

---> Attempting to connect to administrative share '\\172.16.7.194\admin$'
using account '--ADMIN\ACCOUNT--'~ $$<SMS_CLIENT_CONFIG_MANAGER><Fri Feb 20
14:53:58.433 2009 Pacific Standard Time><thread=2076 (0x81C)>
---> Connected to administrative share on machine 172.16.7.194 using account
'--ADMIN\ACCOUNT--'~ $$<SMS_CLIENT_CONFIG_MANAGER><Fri Feb 20 14:53:58.464
2009 Pacific Standard Time><thread=2076 (0x81C)>
---> Attempting to make IPC connection to share <\\172.16.7.194\IPC$> ~
$$<SMS_CLIENT_CONFIG_MANAGER><Fri Feb 20 14:53:58.464 2009 Pacific Standard
Time><thread=2076 (0x81C)>
---> Searching for SMSClientInstall.* under '\\172.16.7.194\admin$\'~
$$<SMS_CLIENT_CONFIG_MANAGER><Fri Feb 20 14:53:58.464 2009 Pacific Standard
Time><thread=2076 (0x81C)>
---> WNetAddConnection2 failed (LOGON32_LOGON_NEW_CREDENTIALS) using account
--ADMIN\ACCOUNT-- (000004b3) $$<SMS_CLIENT_CONFIG_MANAGER><Fri Feb 20
14:53:58.543 2009 Pacific Standard Time><thread=1300 (0x514)>
---> WNetAddConnection2 failed (LOGON32_LOGON_INTERACTIVE) using account
--ADMIN\ACCOUNT-- (000004b3) $$<SMS_CLIENT_CONFIG_MANAGER><Fri Feb 20
14:53:58.558 2009 Pacific Standard Time><thread=1300 (0x514)>
---> Trying the 'best-shot' account which worked for previous CCRs (index =
0x0)~ $$<SMS_CLIENT_CONFIG_MANAGER><Fri Feb 20 14:53:58.558 2009 Pacific
Standard Time><thread=1300 (0x514)>
---> Attempting to connect to administrative share '\\172.16.7.153\admin$'
using account '--ADMIN\ACCOUNT--'~ $$<SMS_CLIENT_CONFIG_MANAGER><Fri Feb 20
14:53:58.558 2009 Pacific Standard Time><thread=1300 (0x514)>
---> WNetAddConnection2 failed (LOGON32_LOGON_NEW_CREDENTIALS) using account
--ADMIN\ACCOUNT-- (000004b3) $$<SMS_CLIENT_CONFIG_MANAGER><Fri Feb 20
14:53:58.558 2009 Pacific Standard Time><thread=1300 (0x514)>
---> WNetAddConnection2 failed (LOGON32_LOGON_INTERACTIVE) using account
--ADMIN\ACCOUNT-- (000004b3) $$<SMS_CLIENT_CONFIG_MANAGER><Fri Feb 20
14:53:58.574 2009 Pacific Standard Time><thread=1300 (0x514)>
---> The 'best-shot' account has now succeeded 0 times and failed 1 times.
$$<SMS_CLIENT_CONFIG_MANAGER><Fri Feb 20 14:53:58.574 2009 Pacific Standard
Time><thread=1300 (0x514)>
---> Trying each entry in the SMS Client Remote Installation account list~
$$<SMS_CLIENT_CONFIG_MANAGER><Fri Feb 20 14:53:58.574 2009 Pacific Standard
Time><thread=1300 (0x514)>
---> Attempting to connect to administrative share '\\172.16.7.153\admin$'
using machine account.~ $$<SMS_CLIENT_CONFIG_MANAGER><Fri Feb 20
14:53:58.574 2009 Pacific Standard Time><thread=1300 (0x514)>
---> Failed to get token for current process (5)
$$<SMS_CLIENT_CONFIG_MANAGER><Fri Feb 20 14:53:58.574 2009 Pacific Standard
Time><thread=1300 (0x514)>
---> ERROR: Failed to connect to the \\172.16.7.153\admin$ share using
account 'Machine Account' $$<SMS_CLIENT_CONFIG_MANAGER><Fri Feb 20
14:53:58.574 2009 Pacific Standard Time><thread=1300 (0x514)>

I have tried using a login script to pick up the rest but have been
unsuccessful. Any thoughts would be helpful.

.

Relevant Pages

  • Re: VPN tunnel with XP Home on remote end cant connect to server in App Mode
    ... MSLicensing registry key, rebooted, installed VPN client (Watchguard) ... Administrator seemed to get the license properly. ... I did not config these machines prior to this so there could have been ... Pro and obviously have a valid license. ...
    (microsoft.public.win2000.termserv.clients)
  • Re: A case for windows firewall
    ... Renewing SAV for definitions on 50 machines is significantly cheaper than buying a newer version and 50 licenses. ... I'm not saying a client should stick with SAV v4. ... I use the Windows firewall, but I cannot help but ask, "Where was the antivirus software that should have stopped the virus?" ...
    (microsoft.public.windows.server.sbs)
  • Re: 1058 and 1030 errors revisited
    ... Are you sure about the symptoms ie when the11th or 12th user logs ... Does the issue occour only on some machines? ... We have four servers to ... There are about sixty client ...
    (microsoft.public.windows.group_policy)
  • Re: XP Client cant connect (or ping) Host XP machine over wired L
    ... Internet is working fine from the stubborn XP client. ... I believe all machines (Host & Client) have XP pro installed but am unsure. ...
    (microsoft.public.windowsxp.network_web)
  • Re: Kerberos errors
    ... You talk about imaged machines, are your images prepared with sysprep? ... This posting is provided "AS IS" with no warranties, ... pre-authentication errors. ... Client Address: x.x.x.x ...
    (microsoft.public.windows.server.active_directory)