Hi, I can see the computer in question on the network, but for some reason it isn't showing up in Configuration Manager. How do I add the computer to Configuration Manager?

Hi, Is the computer a member of the Active Directory? If so you can discover it using Active Directory System discovery which will add it to the SCCM DB and then you can push the client to it. All the discovery methods are described here: http://technet.microsoft.com/en-us/library/bb632733.aspx Regards, Jrgen-- My System Center blog ccmexec.com -- Twitter @ccmexec

Hi Jorgen, Yes, the computer in question is currently visible in the "Computers" folder when viewing "Active Directory Users and Computers" Thanks, Jesse

Have you enabled/configured AD system discovery?Torsten Meringer | http://www.mssccmfaq.de

In addition to Torstens reply, make sure you can resolve the computername of the client from the SCCM primary site server, and if you have enabled AD System Discovery make sure you have included the "Computer" container. Regards, Jrgen-- My System Center blog ccmexec.com -- Twitter @ccmexec

In addition to Torstens reply, make sure you can resolve the computername of the client from the SCCM primary site server, and if you have enabled AD System Discovery make sure you have included the "Computer" container. Regards, Jrgen -- My System Center blog ccmexec.com -- Twitter @ccmexec Have you enabled/configured AD system discovery? Torsten Meringer | http://www.mssccmfaq.de Is there a simple how-to on how to accomplish this?

Also wanted to note (working with Jesse), we're trying to push out an update with the hotfix. Ultimately we're setting up an environment to test with, but the product version needs to be 2.1.x instead of 2.0.x (which is default). After grabbing the hot-fixes however, they do not seem to be applying once running the setup.exe. http://www.microsoft.com/download/en/details.aspx?id=26583 So basically, we're running into a couple problems: 1. Client machine is not being detected although clearly in the active directory. 2. Hot fixes do not seem to get applied. 3. Can't seem to deploy the client even on the local machine Any help would be greatly appreciated as this testing is crucial and on that note, we're seeing an SQL version error (this may be the cause).

http://technet.microsoft.com/en-us/library/bb693618.aspxRegards, Bill

http://technet.microsoft.com/en-us/library/bb693618.aspx Regards, Bill Thanks. It looks like we have AD System Discovery correctly configured, and still no luck when checking "All Systems" under Computer Mangement -> Collections

Check adsysdis.log for errors. Remember you will also need to Update Collection Membership / Refresh the All Systems collection as this only happens by default every 1 day.My Microsoft Core Infrastructure & Systems Management blog - blog.danovich.com.au

are the clients using static IP's? Try using network discovery: http://technet.microsoft.com/en-us/library/bb932200.aspxRegards, Bill

How long does the refresh take? There's an option to select run discovery as soon as possible... but generally how long does this take?Regards, Bill

There is no one-fits-all answer. It depends on the number of objects to be discovered, network speed, machine performance etcTorsten Meringer | http://www.mssccmfaq.de

How long does the refresh take? There's an option to select run discovery as soon as possible... but generally how long does this take? Regards, Bill Depends on the size of your environment and if you are using R2 or R3 (delta discovery). Sometimes 5 minutes, sometimes 8 hours+. Once again, monitor adsysdis.log.My Microsoft Core Infrastructure & Systems Management blog - blog.danovich.com.au