Domain : Virtual Site Server = "SRVCM01" With Win2003SrvEESP2 (Configuration Manager 2007 SP2 and R2, Mixed Mode). Virtual Site System = "PSCM01" With Win2003SrvEESP2 (AD+DNS+DHCP+SQL). Virtual Client = "ClientXP" With Windows XP Pro SP3. Workgroup : Physical Computer = "Black" With Windows Vista Business (Virtual Server 2005 EE R2 SP1). Physical Computer = "LaptopVid" With Windows XP PRO SP3. All computers have the firewall disabled. There are no hardware firewall. STEP 1: Configured Boundaries (IP Subnet). STEP 2 : User configured "Domain" and user "Workgroup" in Push Client. User configured "Domain" in "Computer Client Agent". I have not enabled the Push Client. Step 3 : Network Discovery DHCP (All computers have been discovered with the Client Push off.). Step 4 : Installed "Client Configuration Manager" on "Black" and "LaptopVid" with the Push Client Manual. Step 5 : Enabled Push Client, Only Workstation. Step 6 : Scheduled new Discovery network. (I expected the "Client Configuration Manager " is installed on your computer "ClientXP", but this has not happened). Not Folder "Client Configuration Manager "Present in "c:\windows\system32". The Push Client with Discovey Network, must operate? Thanks. Vid.

What's in ccm.log on the server? John Marcum | http://myitforum.com/cs2/blogs/jmarcum/| In "Ccm.log, there are references only to computers" Black "," SRVCM01 "and" LaptopVid. The "Client Configuration Manager" is present, and was installed by the "Configuration Manager Console" only on computers in Workgroup (Black and LaptopVid). In "Ccm.log" there are no yellow or red lines. Paste this into question the "Ccm.log? Thanks. Vid.

Hi Vid, I would configure AD System discovery instead of Network discovery (not that it's related to this problem, just a good idea). On top of that, as John is ssaying check the ccm.log file on the site server. It records information about client push, and might give you a clue to what's wrong. Kent Agerlund | My blogs: http://blog.coretech.dk/author/kea/ and http://scug.dk/ | Twitter @Agerlund | Linkedin: /kentagerlund I had thought to check if the "Enable Client Push"works with an AD Discovery, but I have not tried it, because I do not see errors in the "Ccm.log. So I thought the problem was another. What do you advise me to discover the problem? Thanks. Vid.

If there are no errors in ccm.log, then please verify c:\windows\system32\ccmsetup\ccmsetup.log on the client systems. Do you did not find ccmsetup.log, then the client is not pushed properly and you need to verify ccm.log. Are you trying to push client to WORKGROUP client? Regards, Madan Hi Mohan Step 6 : Scheduled new Discovery network. (I expected the "Client Configuration Manager " is installed on your computer "ClientXP", but this has not happened). Not Folder "Client Configuration Manager "Present in "c:\windows\system32". Step 4 : Installed "Client Configuration Manager" on "Black" and "LaptopVid" with the Push Client Manual. I installed the "Client Configuration Manager" with "Install Client" on the two computers ("Black " and "LaptopVid") in the working group. SCCM Console ---> Collection -> Windows XP -> Select "PC Name" discovered ---> Right click -> Install Client. The operation was successful. The prerequisites for doing this are: The Workgroup Accounts Configured in the "Client Push Installation Properties, Tab Accounts-->Client Push Installation Accounts" and parameters MP, SiteCode, SLP and FSP in "Tab Client-->Installation Properties. " My problem is another. The Client Push Installation does not start automatically on ClientXP located in the Dominion. On ClientXP there is no folder or file Client Push Installation. So no one ccmsetup.log. On the server log Ccm.log there are no references as ClientXP. In Ccm.log I only found the following anomalies: ADM: NtBrowser: Failed to retrieve OS info from device ClientXP, error 5. Thanks.

Error 5 = access denied Can you open \\ClientXP\admin$\ from your SCCM server using the account that is configured as client push instillation account? ADM: NtBrowser: Failed to retrieve OS info from device ClientXP, error 5. Regards, Madan

Error 5 = access denied Can you open \\ClientXP\admin$\ from your SCCM server using the account that is configured as client push instillation account? ADM: NtBrowser: Failed to retrieve OS info from device ClientXP, error 5. Regards, Madan Check. Thanks. Vid.

Error 5 = access denied Can you open \\ClientXP\admin$\ from your SCCM server using the account that is configured as client push instillation account? ADM: NtBrowser: Failed to retrieve OS info from device ClientXP, error 5. Regards, Madan Check. Thanks. Vid. Access to "\\clientxp\admin$" is successful from "SRVCM01 (SiteServer) to ClientXP. then this warning in the log is bogus? Thanks. Vid.

If there are no errors in ccm.log, then please verify c:\windows\system32\ccmsetup\ccmsetup.log on the client systems. Do you did not find ccmsetup.log, then the client is not pushed properly and you need to verify ccm.log. Are you trying to push client to WORKGROUP client? Regards, Madan

No, the connection attempt that is getting error 5 is trying to use the SCCM machine account. When you manually connect that's using the logged in user. If you machine account does not have admin rights to your PC's (which I suggest it should) then you need to supply a client push install account that does have admin rights. John Marcum | http://myitforum.com/cs2/blogs/jmarcum/|

Delete both workgroup computers from the database (using the admin console). Start network discovery. Watch netdisc.log using trace2 to see if those objects get rediscovered. And watch ccm.log if the automatic push is starting as soon as they are discovered (and make sure that automatic client push is enabled at all). The "network user account" (and I guess you were talking abount "network access account") does not have to be a local admin. It is not used for client push (that would be the client push installation account though). I deleted from the collections, the two computer workgroup. manually uninstalled the "Client Configuration Manager" from the computer. remove the client from the workgroup database sql? how do I? client push is enabled on workstations and servers. I removed the "network access account" by the local administrators group of all computers. network access account: you're right, I misunderstood how it works. I read the technet library. Client Push Installation Accounts, I have configured in network discovery. I plan the discovery and control trace2. Thanks. Vid.

No, the connection attempt that is getting error 5 is trying to use the SCCM machine account. When you manually connect that's using the logged in user. If you machine account does not have admin rights to your PC's (which I suggest it should) then you need to supply a client push install account that does have admin rights. John Marcum | http://myitforum.com/cs2/blogs/jmarcum/| hi John, Ok, understood. But I think the problem is not that. The Computer, Client and Server are correctly detected by the "Network Discovery". The Client Configuration Manager installation does not start automatically. Ccm.log Server is not registered in any event to start installing Configuration Manager Client. Over Computers do not create any folder "ccmsetup" and no process "ccmsetup.exe begins. it seems like the "Network Discovery" is not sent any input to start the installation of "Client Configuration Manager ". There can be no errors in the settings of the "Client Push Installation" and "Computer Client Agent", because using the wizard "Install Client", the "Client Configuration Manager is installed correctly on your computer on the domain and workgroup computers. On the Domain Computers, within the local group "Administrators" is set both the SCCM server's machine account, and the "network user account. " I can not understand why the automatic installation of the "client configuration manager" does not work. Logs "Ccm.log"and "netdisc.log". Installation, "Client Configuration Manager, does not start automatically. Log "ccmsetup.log" when manually (Wizard) install "Install Client" on a computer in the domain. What can I even check? Thanks. Vid.

Delete both workgroup computers from the database (using the admin console). Start network discovery. Watch netdisc.log using trace2 to see if those objects get rediscovered. And watch ccm.log if the automatic push is starting as soon as they are discovered (and make sure that automatic client push is enabled at all). The "network user account" (and I guess you were talking abount "network access account") does not have to be a local admin. It is not used for client push (that would be the client push installation account though).

Hi Torsten, Clients are discovered again, but the client installation does not start. Ccm.log not happen in almost anything. Netdiag.log. something is wrong. Thanks. Vid.

STEP 1: Configured Boundaries (IP Subnet). Which boundary did you add? How does a client's IP and subnet mask look like?

STEP 1: Configured Boundaries (IP Subnet). Which boundary did you add? How does a client's IP and subnet mask look like?

STEP 1: Configured Boundaries (IP Subnet). Which boundary did you add? How does a client's IP and subnet mask look like? I configured the "boundaries " for "IP Subnet". 192.168.0.0. I examine one of the Client. IP: 192.168.0.200 Subnet Mask: 255.255.0.0 Gateway: 192.168.0.10 and 192.168.0.201 DHCP: 192.168.0.10. DNS1: 192.168.0.10 DNS2: 192.168.0.201. also changing the boundaries in IP Range, the problem persists. I did a test: with the same boundaries, if I make a discovery on AD, puch the client computer starts successfully covering the domain. Network Discovery Push Client starts automatically? Thanks. Vid.

STEP 1: Configured Boundaries (IP Subnet). Which boundary did you add? How does a client's IP and subnet mask look like? I configured the "boundaries " for "IP Subnet". 192.168.0.0. I examine one of the Client. IP: 192.168.0.200 Subnet Mask: 255.255.0.0 Gateway: 192.168.0.10 and 192.168.0.201 DHCP: 192.168.0.10. DNS1: 192.168.0.10 DNS2: 192.168.0.201. also changing the boundaries in IP Range, the problem persists. I did a test: with the same boundaries, if I make a discovery on AD, puch the client computer starts successfully covering the domain. Network Discovery Push Client starts automatically? Thanks. Vid. So. I still have not grim confirmation and response to my question last. Upon reflection, the only thing that comes to mind, and that the problem may be in the configuration of boundaries or the DHCP server configuration. Reflecting on the overall process of discovery, I'm thinking: Discovery Data Manager does not automatically generate a CCR file for client computers that do not reside within its own site boundaries. But what confuses me, and discovered that the computers are assigned to the site, and the boundaries seem to be configured correctly. But if I change the method of discovery, from network to AD, the installation of the client configuration manager, automatically. so I think the problem is in the configuration of network discovery. my reasoning is correct? Thanks. Vid.