Jump to content

Search the Community

Showing results for tags 'Discovery'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • Cloud
    • Azure
    • Microsoft Intune
    • Office 365
    • Windows 365
  • General Stuff
    • General Chat
    • Events
    • Site News
    • Official Forum Supporters
    • Windows News
    • Suggestion box
    • Jobs
  • MDT, SMS, SCCM, Current Branch &Technical Preview
    • How do I ?
    • Microsoft Deployment Toolkit (MDT)
    • SMS 2003
    • Configuration Manager 2007
    • Configuration Manager 2012
    • System Center Configuration Manager (Current Branch)
    • Packaging
    • scripting
    • Endpoint Protection
  • Windows Client
    • how do I ?
    • Windows 10
    • Windows 8
    • Windows 7
    • Windows Vista
    • Windows XP
    • windows screenshots
  • Windows Server
    • Windows Server General
    • Active Directory
    • Microsoft SQL Server
    • System Center Operations Manager
    • KMS
    • Windows Deployment Services
    • NAP
    • Failover Clustering
    • PKI
    • Hyper V
    • Exchange
    • IIS/apache/web server
    • System Center Data Protection Manager
    • System Center Service Manager
    • System Center App Controller
    • System Center Virtual Machine Manager
    • System Center Orchestrator
    • Lync
    • Application Virtualization
    • Sharepoint
    • WSUS

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start



Website URL



Found 7 results

  1. System discovery is finding objects in active directory but they aren't showing up in the console under any collections. I have a CAS and 2 primary Sites.
  2. So, I have about 2200 actual PC's that I manage, however it shows about 3500 "all systems" PC's with around 1300 Showing "All Systems - No Client". 98% of these PC's are not ping-able and show no host found in my RCT Recast tools add-on under ping collection. There are no records in AD for these, as well as DNS. As far as I can tell, I have little to none duplicate GUIDS after running every query under the sun. Has anyone seen such a thing? My discovery is set to only discover PC's that have been logged into within 30 days, same with parameters for the automatic aged removal. DNS scavenging is fairly aggressive. I cannot find where these extra systems are coming from if they don't exist anywhere in the environment or AD. I've deleted these extra Systems in SCCM, and they come back during the weekly Delta discovery, but not in the incremental discovery. I can give more specifics if necessary, but I thought I'd see if anyone else has seen something similar first. Thanks,
  3. Hi there, I'm new to SCCM ,I just installed SCCM 2012 and enabled Active DIrectory Group Discovery ,All my users have been imported successfully, howerver the security groups haven't. Is there any particular option for security groups ? Thanks,
  4. Hi, all. Weird thing... Config Manager 2012, SP1. AD discovery and network discovery are both on. We've got a number of computers showing up twice in CM. For each of these, there's one instance that looks all fine and happy with successful deployments, etc; then there's another "bare-bones" kind of version with only a handful of properties actually populated. For the bare-bones copy of these: Some things match the active client, namely - MAC Address; IP Address; subnet; Resource Domain or Workgroup; Name; NETBIOS Name; AD, Agent, CM Assigned, CM Resident sites, Resource type (=System), and Decommissioned (=No) While other stuff differs - Agent Name = "SMS_NETWORK_DISCOVERY" (active client has this along with others) Creation Date is always well after the creation date of the "real" copy Resource ID is way different Resource Names = netbios name and FQDN, where active client only has FQDN here And the rest of the fields are usually empty, but not always. LastLogonTimeStamp is sometimes present - I'm guessing this is a case of the DB updating the field for the wrong instance. E.g. I'm looking at one now where the bare-bones copy has a Last Logon Timestamp of 18 August while the real copy is showing a Last Logon Timestamp back in April, right around the time the bad copy showed up. The real one has a last policy request from less than 10 minutes ago... What am i missing here that's causing these to show up? With only a few dozen, it's not a big deal for me to just go in and get rid of them manually, but I'd rather address the root cause. Pretty sure it's not a case of AD delta discovery+OSD looking for unknowns, which is about all I can google up in regards to duplicates, as these new copies showed up in mostly in July 2014 for systems that were either built from scratch or OSD'd and have been in AD for a year or more.
  5. We need to be able to discover users who have been disabled and update changes made to disabled users. It seems that if a user is disabled in AD, SCCM just ignores them so that it doesn't even update the UAC attribute in the SCCM database. Is there any way to get around this?
  6. I have a problem at work where my new sccm 2012 server discovered way to many users. I had enabled the Active Directory Forest discovery and I thought it was only supposed to discover the forest and possibly add those as boundaries, but now I have 44.000 users from other locations I do not want in the DB. Is there a quick way to clean the DB for these users? The server is not in prod, but don't want to start over for I've already created some tasks and packages. I have since then setup the user discovery from the right ou, but is it safe to just select all -> delete? tried with a few, but its an extremely slow process. I'm going on vacation soon, so if that's what it takes, I can live with it And it's safe to delete users? It's only the users from the sccm db. It will never touch AD? Edit: All the objects that I want to delete has the Agent Name: "SMS_AD_SECURITY_GROUP_DISCOVERY_AGENT"
  7. Hi, This is my first time posting in this forum so please forgive me if i have posted this in the wrong place. I am currently having a new issue (everything was working fine about 3 days ago but is no longer working), were collections dont seem to updating properly when running 'update collection membership'. Couple fo examples; a computer shows as no client installed, i install the client via the manual install (right click on computer and install client). The client installs on the computer but it doesn't show up in the collection that the client is installed. I run the update and refresh and nothing changers. Ill also tried running the software inventory cycle on the client itself but nothing changers. But when i come in the next day the client shows up as being installed. i just dosent seem to refresh during the day. Another example is when i add a security group to a computer for software installation it dosent appear in the collection. I run the 'run full discovery as soon as possible' in the active directory secuirty group discovery and see that it was succesful in the logs but nothing shows up in the collection. Once again overnight tho it seems to work. Both examples were working a couple of days ago. I did have a issue 2 days ago where the discovery was 'blind' to AD which i resolved by restarting the central sever but ever since then it hasnt seem to run properly. Does anyone have an ideas about what might be happening?? If you need any other infomation about this please let me know and ill see what i can get for you. Regards Scottyj82
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.