Installing clients SCCM 2012

[BFofana]

I have installed SCCM 2012 on a standalone primary site. I installed the client by push method. In many clients i got errors : the device does not exist on the network. give up. But i ping the clients from the primary site.

 

Received request: "2097152177" for machine name: "PC-MPR26" on queue: "Incoming". SMS_CLIENT_CONFIG_MANAGER 15/04/2013 15:56:32 4000 (0x0FA0)

Stored request "2097152177", machine name "PC-MPR26", in queue "Processing". SMS_CLIENT_CONFIG_MANAGER 15/04/2013 15:56:32 4000 (0x0FA0)

Execute query exec [sp_CP_SetPushRequestMachineStatus] 2097152177, 1 SMS_CLIENT_CONFIG_MANAGER 15/04/2013 15:56:32 4000 (0x0FA0)

======>Begin Processing request: "2097152177", machine name: "PC-MPR26" SMS_CLIENT_CONFIG_MANAGER 15/04/2013 15:56:32 2740 (0x0AB4)

Execute query exec [sp_IsMPAvailable] N'SAS' SMS_CLIENT_CONFIG_MANAGER 15/04/2013 15:56:32 2740 (0x0AB4)

---> Trying the 'best-shot' account which worked for previous CCRs (index = 0x0) SMS_CLIENT_CONFIG_MANAGER 15/04/2013 15:56:33 2740 (0x0AB4)

---> Attempting to connect to administrative share '\\PC-MPR26\admin$' using account 'test\administrateur' SMS_CLIENT_CONFIG_MANAGER 15/04/2013 15:56:33 2740 (0x0AB4)

Submitted request successfully SMS_CLIENT_CONFIG_MANAGER 15/04/2013 15:56:34 4000 (0x0FA0)

Getting a new request from queue "Incoming" after 100 millisecond delay. SMS_CLIENT_CONFIG_MANAGER 15/04/2013 15:56:34 4000 (0x0FA0)

Waiting for change in directory "E:\Program Files\Microsoft Configuration Manager\inboxes\ccr.box" for queue "Incoming", (30 minute backup timeout). SMS_CLIENT_CONFIG_MANAGER 15/04/2013 15:56:34 4000 (0x0FA0)

---> WNetAddConnection2 failed (LOGON32_LOGON_NEW_CREDENTIALS) using account test\administrateur (00000035) SMS_CLIENT_CONFIG_MANAGER 15/04/2013 15:56:35 2740 (0x0AB4)

---> The device PC-MPR26 does not exist on the network. Giving up SMS_CLIENT_CONFIG_MANAGER 15/04/2013 15:56:35 2740 (0x0AB4)

---> Trying the 'best-shot' account which worked for previous CCRs (index = 0x0) SMS_CLIENT_CONFIG_MANAGER 15/04/2013 15:56:35 2740 (0x0AB4)

---> Attempting to connect to administrative share '\\PC-MPR26.test.sn\admin$' using account 'test\administrateur' SMS_CLIENT_CONFIG_MANAGER 15/04/2013 15:56:35 2740 (0x0AB4)

---> WNetAddConnection2 failed (LOGON32_LOGON_NEW_CREDENTIALS) using account test\administrateur (00000035) SMS_CLIENT_CONFIG_MANAGER 15/04/2013 15:56:41 2740 (0x0AB4)

---> The device PC-MPR26.test.sn does not exist on the network. Giving up SMS_CLIENT_CONFIG_MANAGER 15/04/2013 15:56:41 2740 (0x0AB4)

---> Trying the 'best-shot' account which worked for previous CCRs (index = 0x0) SMS_CLIENT_CONFIG_MANAGER 15/04/2013 15:56:41 2740 (0x0AB4)

---> Attempting to connect to administrative share '\\PC-MPR26\admin$' using account 'test\administrateur' SMS_CLIENT_CONFIG_MANAGER 15/04/2013 15:56:41 2740 (0x0AB4)

---> WNetAddConnection2 failed (LOGON32_LOGON_NEW_CREDENTIALS) using account test\administrateur (00000035) SMS_CLIENT_CONFIG_MANAGER 15/04/2013 15:56:41 2740 (0x0AB4)

---> The device PC-MPR26 does not exist on the network. Giving up SMS_CLIENT_CONFIG_MANAGER 15/04/2013 15:56:41 2740 (0x0AB4)

i need your help

[Peter van der Woude]

Are you able to connect to the admin$ of the machine?

[mk.maddin]

Hi,

 

 

was there a resultion to this?

 

I'm having the same problem with many clients here.

All of them I can't ping.

 

I already read this post, but in my opinion there was no solution. :-(

 

 

thank you for help.

 

mk.maddin

[Rocket Man]

All of them I can't ping.

 

 

What is your DNS like??

Try and turn off the firewall on a single machine then ping again to rule out if it is firewall related or not!

 

Had a similar problem with a CM2007 setup a way back. I introduced CM2007 on an already established network........couldnt get most of the clients to install even though the firewall exclusions were created on the local machines via GPO.......turned out to be old outdated DNS enteries....had no DNS scavenging turned on....so basically when I would manually try or let auto-site-wide installs to take place it would fail miserably because several machines had the same IP address according to DNS even though everything else was working fine in terms of ADDS. This seemed to get SCCM confused!!

 

Rocket Man

[mk.maddin]

Turning off the Firewall didn't help anything.

 

But it looks like there is a problem with DNS.

While Devices are connected to Wireless LAN and LAN, the WLAN address is always assigned in DNS.

But Computer uses LAN as primary Network connection.

-> No answer at pinging by name.

 

But what can I do to resolve this?

 

Thank you for fast reply

[Rocket Man]

Are there multiple DNS enteries with the same IP address? i:e

 

ComputerA 192.168.0.55(Out dated)

ComputerB 192.168.0.55(Out dated)

ComputerC 192.168.0.55(Current system holding on to this IP address)

 

You should be able to ping your laptops atleast by IP address once they are connected to your network not unless your WAP does not allow ping.

 

 

Are you able to connect to the admin$ of the machine?

 

Have you also tried what Peter suggested?

 

 

While Devices are connected to Wireless LAN and LAN, the WLAN address is always assigned in DNS.

But Computer uses LAN as primary Network connection.

 

 

Not sure if this matters as I have pushed out CM Agents accross wireless network connections with DNS enteries pointing to wireless IP, just once the IP address matches the current netbios name within DNS and there are no other out dated enteries with same IP address.