Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 302
  • Last Modified:

sccm 2012

I have sccm 2012.i run the discovery all options but sccm is not discovering the new clients.then i went to client and manually installed the agent on client machine.but still it is not appearing in the sccm console.
0
kastro Abbasi
Asked:
kastro Abbasi
1 Solution
 
David Johnson, CD, MVPOwnerCommented:
which discovery methods have you enabled?  there are many methods that are available.
AD System Discovery, Heartbeat, Network Discovery
0
 
kastro AbbasiAuthor Commented:
except Forest Discovery i have enabled all the others.there are more than 200 servers there which it discovered before.but now for any new client it is not discovering them
0
 
Vaseem MohammedCommented:
Have you checked under the system discovery option the DN from where SCCM is looking for computer accounts?
If your servers are in a specific OU in AD and the DN for only that OU is defined, I don't think other systems will be discovered.
0
[Webinar On Demand] Database Backup and Recovery

Does your company store data on premises, off site, in the cloud, or a combination of these? If you answered “yes”, you need a data backup recovery plan that fits each and every platform. Watch now as as Percona teaches us how to build agile data backup recovery plan.

 
kastro AbbasiAuthor Commented:
what do u mean by DN we have defined the boundries for the specefied network .and sccm will discover the computer with in this boundry and more over some the computer in the same OU are already discovered previously but not all.
ofcourse for each discovery method we have also defined the specefic OUs for discovery.
i checked the logs of the client which i have installed manually and find in the logs of ClientIDManagerStartup

Client registration is pending. Sending confirmation request for GUID:60A86EDDC0E51 ...]LOG]!><time="11:39:22.690-180" date="10-27-2014" component="ClientIDManagerStartup" context="" type="1" thread="2452" file="regtask.cpp:1721">
<![LOG[[RegTask] - Sleeping for 3840 seconds ...]LOG]!><time="11:39:22.814-180" date="10-27-2014" component="ClientIDManagerStartup" context="" type="1" thread="2452" file="regtask.cpp:1420">
0
 
Vaseem MohammedCommented:
what does adsysdis.log says? have you checked it?
0
 
Vaseem MohammedCommented:
Delta discovery and schedule of AD system discovery?
Also check the database drive space, Site status, Component status.
0
 
kastro AbbasiAuthor Commented:
there is lot of space available databse drives

site status is showing some crtical error and component status ok.

please tell me if u have any other idea
0
 
Vaseem MohammedCommented:
If site status is showing critical error, check the site system role error message and accordingly try to pin down what is causing the problem.
0
 
kastro AbbasiAuthor Commented:
Again i have resolved the issue any ways thanks for ur effort

It was just matter to update the membership
0
 
kastro AbbasiAuthor Commented:
i resolved it my self
0
 
John JankowskiSCCM SMECommented:
Have you set boundaries? I would also start with just the heartbeat discovery. If you  use the others like ad you will get stale systems in you database.
0

Featured Post

Upgrade your Question Security!

Your question, your audience. Choose who sees your identity—and your question—with question security.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now