heungwing Posted March 13, 2009 Report post Posted March 13, 2009 the system status is normal, and i close the firewall for my client-pc(vista business).but i push install to the client-pc, there is not any response. Quote Share this post Link to post Share on other sites More sharing options...
anyweb Posted March 13, 2009 Report post Posted March 13, 2009 you client push install account are you using ? under site settings, client installation methods, check client push installation and see if you have configured an account there, that user must be a member of Local Administrators Group on the client you are trying to install on... cheers anyweb Quote Share this post Link to post Share on other sites More sharing options...
heungwing Posted March 13, 2009 Report post Posted March 13, 2009 yes, i use the SMSadmin Quote Share this post Link to post Share on other sites More sharing options...
anyweb Posted March 13, 2009 Report post Posted March 13, 2009 verify that your SMSadmin user is a member of Local Administrators on the target client computer, if this user is a domain admin (for testing only) then that is sufficient if your client still fails to install verify you've created a package from definition and that its correctly distributed to a DP and update the dp... cheers Quote Share this post Link to post Share on other sites More sharing options...
heungwing Posted March 13, 2009 Report post Posted March 13, 2009 more information~ the client-pc(vista2)is available. ---> WNetAddConnection2 failed (LOGON32_LOGON_NEW_CREDENTIALS) using account main\SMSadmin (00000035) $$<SMS_CLIENT_CONFIG_MANAGER><Fri Mar 13 06:08:50.087 2009 Pacific Daylight Time><thread=3296 (0xCE0)> ---> LogonUser failed (LOGON32_LOGON_INTERACTIVE) using account main\SMSadmin (0000052e) $$<SMS_CLIENT_CONFIG_MANAGER><Fri Mar 13 06:08:50.087 2009 Pacific Daylight Time><thread=3296 (0xCE0)> ---> The 'best-shot' account has now succeeded 178 times and failed 152 times. $$<SMS_CLIENT_CONFIG_MANAGER><Fri Mar 13 06:08:50.087 2009 Pacific Daylight Time><thread=3296 (0xCE0)> ---> Trying each entry in the SMS Client Remote Installation account list~ $$<SMS_CLIENT_CONFIG_MANAGER><Fri Mar 13 06:08:50.087 2009 Pacific Daylight Time><thread=3296 (0xCE0)> ---> Attempting to connect to administrative share '\\vista2.ive.com\admin$' using account 'main\SMSadmin'~ $$<SMS_CLIENT_CONFIG_MANAGER><Fri Mar 13 06:08:50.087 2009 Pacific Daylight Time><thread=3296 (0xCE0)> ---> WNetAddConnection2 failed (LOGON32_LOGON_NEW_CREDENTIALS) using account main\SMSadmin (00000035) $$<SMS_CLIENT_CONFIG_MANAGER><Fri Mar 13 06:08:50.102 2009 Pacific Daylight Time><thread=3296 (0xCE0)> ---> LogonUser failed (LOGON32_LOGON_INTERACTIVE) using account main\SMSadmin (0000052e) $$<SMS_CLIENT_CONFIG_MANAGER><Fri Mar 13 06:08:50.102 2009 Pacific Daylight Time><thread=3296 (0xCE0)> ---> Attempting to connect to administrative share '\\vista2.ive.com\admin$' using machine account.~ $$<SMS_CLIENT_CONFIG_MANAGER><Fri Mar 13 06:08:50.102 2009 Pacific Daylight Time><thread=3296 (0xCE0)> ---> Failed to connect to \\vista2.ive.com\admin$ using machine account (53) $$<SMS_CLIENT_CONFIG_MANAGER><Fri Mar 13 06:08:50.102 2009 Pacific Daylight Time><thread=3296 (0xCE0)> ---> The device vista2.ive.com does not exist on the network. Giving up~ $$<SMS_CLIENT_CONFIG_MANAGER><Fri Mar 13 06:08:50.118 2009 Pacific Daylight Time><thread=3296 (0xCE0)> ---> Trying the 'best-shot' account which worked for previous CCRs (index = 0x0)~ $$<SMS_CLIENT_CONFIG_MANAGER><Fri Mar 13 06:08:50.118 2009 Pacific Daylight Time><thread=3296 (0xCE0)> ---> Attempting to connect to administrative share '\\VISTA2\admin$' using account 'main\SMSadmin'~ $$<SMS_CLIENT_CONFIG_MANAGER><Fri Mar 13 06:08:50.118 2009 Pacific Daylight Time><thread=3296 (0xCE0)> Quote Share this post Link to post Share on other sites More sharing options...
anyweb Posted March 13, 2009 Report post Posted March 13, 2009 is the vista pc joined to the domain ? Quote Share this post Link to post Share on other sites More sharing options...
heungwing Posted March 13, 2009 Report post Posted March 13, 2009 yes, vista is joined to the domain and the network discover is on. ======>Begin Processing request: "OBBMNIOZ", machine name: "VISTA2" $$<SMS_CLIENT_CONFIG_MANAGER><Fri Mar 13 07:56:45.834 2009 Pacific Daylight Time><thread=2820 (0xB04)> ---> Trying the 'best-shot' account which worked for previous CCRs (index = 0x0)~ $$<SMS_CLIENT_CONFIG_MANAGER><Fri Mar 13 07:56:45.834 2009 Pacific Daylight Time><thread=2820 (0xB04)> ---> Attempting to connect to administrative share '\\vista2.ive.com\admin$' using account 'main\SMSadmin'~ $$<SMS_CLIENT_CONFIG_MANAGER><Fri Mar 13 07:56:45.834 2009 Pacific Daylight Time><thread=2820 (0xB04)> ---> The 'best-shot' account has now succeeded 508 times and failed 303 times. $$<SMS_CLIENT_CONFIG_MANAGER><Fri Mar 13 07:56:47.538 2009 Pacific Daylight Time><thread=2820 (0xB04)> ---> Connected to administrative share on machine vista2.ive.com using account 'main\SMSadmin'~ $$<SMS_CLIENT_CONFIG_MANAGER><Fri Mar 13 07:56:47.538 2009 Pacific Daylight Time><thread=2820 (0xB04)> ---> Attempting to make IPC connection to share <\\vista2.ive.com\IPC$> ~ $$<SMS_CLIENT_CONFIG_MANAGER><Fri Mar 13 07:56:47.538 2009 Pacific Daylight Time><thread=2820 (0xB04)> ---> Searching for SMSClientInstall.* under '\\vista2.ive.com\admin$\'~ $$<SMS_CLIENT_CONFIG_MANAGER><Fri Mar 13 07:56:47.538 2009 Pacific Daylight Time><thread=2820 (0xB04)> CWmi::Connect(): ConnectServer(Namespace) failed. - 0x80070005~ $$<SMS_CLIENT_CONFIG_MANAGER><Fri Mar 13 07:56:47.616 2009 Pacific Daylight Time><thread=2820 (0xB04)> ---> Unable to connect to WMI on remote machine "VISTA2", error = 0x80070005. $$<SMS_CLIENT_CONFIG_MANAGER><Fri Mar 13 07:56:47.616 2009 Pacific Daylight Time><thread=2820 (0xB04)> ---> Deleting SMS Client Install Lock File '\\vista2.ive.com\admin$\SMSClientInstall.WIN'~ $$<SMS_CLIENT_CONFIG_MANAGER><Fri Mar 13 07:56:47.616 2009 Pacific Daylight Time><thread=2820 (0xB04)> Retry request id for "OBBMNIOZ" set to "vista2_ive_com" $$<SMS_CLIENT_CONFIG_MANAGER><Fri Mar 13 07:56:47.616 2009 Pacific Daylight Time><thread=2820 (0xB04)> Stored request "vista2_ive_com", machine name "VISTA2", in queue "Retry". $$<SMS_CLIENT_CONFIG_MANAGER><Fri Mar 13 07:56:47.631 2009 Pacific Daylight Time><thread=2820 (0xB04)> <======End request: "vista2_ive_com", machine name: "VISTA2". $$<SMS_CLIENT_CONFIG_MANAGER><Fri Mar 13 07:56:47.631 2009 Pacific Daylight Time><thread=2820 (0xB04)> Submitted request successfully $$<SMS_CLIENT_CONFIG_MANAGER><Fri Mar 13 07:56:47.835 2009 Pacific Daylight Time><thread=1072 (0x430)> Getting a new request from queue "Incoming" after 100 millisecond delay. $$<SMS_CLIENT_CONFIG_MANAGER><Fri Mar 13 07:56:47.835 2009 Pacific Daylight Time><thread=1072 (0x430)> Waiting for change in directory "C:\Program Files (x86)\Microsoft Configuration Manager\inboxes\ccr.box" for queue "Incoming", (30 minute backup timeout). $$<SMS_CLIENT_CONFIG_MANAGER><Fri Mar 13 07:56:47.835 2009 Pacific Daylight Time><thread=1072 (0x430)> Quote Share this post Link to post Share on other sites More sharing options...
Tobie Posted March 13, 2009 Report post Posted March 13, 2009 ---> Unable to connect to WMI on remote machine "VISTA2", error = 0x80070005. i't seems that you ConfigMgr site have some difficulties to connect to the computers WMI Repository. Error messages like 0x80070005 is always (9/10 times) Access Denied. Or, the WMI Repository is damaged. Check that you have DCOM rights on that machine. Fallow the instructions below. Try running dcomcnfg and right click on My Computer and then select Properties. Check the Default Properties and COM Security tabs and see if anything looks 'not right'. The best way to verify what the setting should be would be to run on a computer where this works and compare the results to one that does not. Unfortunately, I think that this utility must be run locally on each computer. Our you can repair or re-registering your WMI repository on that machine. Go to your Vísta machine and fallow the steps below. Click Start, Run and type CMD.EXE Note: In Windows Vista, you need to open an elevated Command Prompt window. To do so, click Start, click All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator. Type this command and press Enter: net stop winmgmt Using Windows Explorer, rename the folder %windir%\System32\Wbem\Repository. (For example, %windir%\System32\Wbem\Repository_bad). %windir% represents the path to the Windows directory, which is typically C:\Windows. Switch to Command Prompt window, and type the following and press ENTER after each line: net start winmgmt EXIT Wait a couple of minutes and try to push out the client again. If you still have problem, try to install the ConfigMgr client manually to see if you get any diffrence. Good Luck /Tobias Quote Share this post Link to post Share on other sites More sharing options...