Windows 7 not being discovered by SCCM 2007 Server
Issue: Windows 7 not being discovered Server: Windows Server 2003x64 SP2, SCCM2007 R2 Mixed. Win7: I can manually install the client. Firewall is off.
September 28th, 2010 11:09pm

Discovery and client installation are two different things. Can you please clarify what issue you are experiencing, what your goal is, some basic configuration info, and what troubleshooting you have already done. If you are refering to discovery, have you reviewed your AD System Discovery and its log: adsysdis.log? If client discovery, have you reviewed ccm.log on the server and ccmsetup.log on the client?Jason | http://myitforum.com/cs2/blogs/jsandys | http://blogs.catapultsystems.com/jsandys/default.aspx | Twitter @JasonSandys
Free Windows Admin Tool Kit Click here and download it now
September 29th, 2010 12:23am

Thank you for your response Jason. The story is that the Windows 7 machines are not appearing in any collections. I have to manually install the client from the Windows 7 machine. The Win7 machines are within the boundaries. The SCCM server is set to automatically approve clients that are assigned to the site. Client push installation is enabled to install to assigned resources. I created a collection for Win7 resources. As the clients are installed manually on the Windows 7 machines, they show up correctly.
September 29th, 2010 4:16pm

What about your discoveries? How are they configured?Jason | http://myitforum.com/cs2/blogs/jsandys | http://blogs.catapultsystems.com/jsandys/default.aspx | Twitter @JasonSandys
Free Windows Admin Tool Kit Click here and download it now
September 29th, 2010 4:34pm

All the are enabled except for Network Discovery. Path is LDAP://DC= domainexample,DC=domainext. Set to include all groups. System Discovery Attributes are all set to "yes"
September 29th, 2010 4:43pm

Have you examined adsysdis.log on the site server to see if the known Windows 7 clients are listed? Are you manually updating the collection or waiting for its update interval: collections are not dynamically updated, they are only updated on a defined schedule. Thus, if discovery runs, you won't see new systems added to a collection until that collection is updated either manually (by right-clicking and choosing update) or automatically at the scheduled time (once a day by default).Jason | http://myitforum.com/cs2/blogs/jsandys | http://blogs.catapultsystems.com/jsandys/default.aspx | Twitter @JasonSandys
Free Windows Admin Tool Kit Click here and download it now
September 29th, 2010 5:17pm

In the Adsysdis.log, the widows 7 PC was not found. In the Adsysgrp.log the windows 7 PC was found.
September 29th, 2010 8:21pm

For the second part of the question. I have manually updated and refreshed the collection(s).
Free Windows Admin Tool Kit Click here and download it now
September 29th, 2010 8:24pm

That doesn't make any sense if the two discoveries are configured the same. Are your Win 7 systems in a unique OU? Are there other errors in adsysdis.log?Jason | http://myitforum.com/cs2/blogs/jsandys | http://blogs.catapultsystems.com/jsandys/default.aspx | Twitter @JasonSandys
September 29th, 2010 8:44pm

It does not make any sense. I do not have them in their own OU in AD they are in with other workstations. I am getting this error "WARN: Could not get property (domain) for system (0x80005010)"
Free Windows Admin Tool Kit Click here and download it now
September 29th, 2010 9:00pm

That's a known issue and is ignorable. Does it say anything else? Please post the relevant section of the log file.Jason | http://myitforum.com/cs2/blogs/jsandys | http://blogs.catapultsystems.com/jsandys/default.aspx | Twitter @JasonSandys
September 29th, 2010 11:39pm

Jason, I was able to get the Win7 resources to show by removing the CCRs on the CCRRETRY.box folder. And running the AD System Group Discovery. I am very thankful for you assistance.
Free Windows Admin Tool Kit Click here and download it now
September 30th, 2010 2:59pm

CCRs have nothing to do with discovery (they may get generated after a resource has been discovered, but not impact the other way round).
September 30th, 2010 3:44pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics