OSU75

I ran a dsquery in order to move all computer accounts that have not been logged onto in 4 months to an OU where they were disabled. These accounts will be eventually deleted the problem I'm running into like so many others is how to purge these accounts from the configuration manager database. I have ran the site maintenance task delete obsolete client discovery data. Of course this did not work I also thought about creating a collection looking for user account control number 4098. However, that can't be done because when I ran the system discovery nothing was updated so all computer accounts are showing 4096. So my only option is to create a collection where client install equals no or maybe a powershell script that can clean the disabled computer accounts from the configuration manager database. I am thinking about turning off the system discovery method and just using the heartbeat data. So my question is how would you guys handle this?

This was a db permissions problem when I installed the product I ran the installer under my account which I should have used a service account it actually had my user account as the owner of the config db. After I thought about this I remember that I actually moved the config db files to a new set of drives after the db was created so that could have also complicated things. So I created an account named smsadmin I than made it an admin of the configuration manager server and added it to the configmgr_collectedfilesaccess and smsadmins group. After I opened config manager and made smsadmin a full administrator than went over to the sql server and made the account sysadmin also I made it owner of the database at that point I did a refresh and all the data came into the configuration manager console. However, I would like to ask does the smsadmin account have to be a sysadmin on the sql server or can it just be dbowner for the config manager database?

I pulled this from ddm.log DDM LOG ~Updated inbox def 27, Discovery Data Manager (Registration) $$<SMS_DISCOVERY_DATA_MANAGER><03-30-2014 22:38:22.262+300><thread=2776 (0xAD8)> ~Updated inbox def 49, Discovery Data Manager (Notification) $$<SMS_DISCOVERY_DATA_MANAGER><03-30-2014 22:38:22.268+300><thread=2776 (0xAD8)> DDM is configured to synchronize the network config data (NCF) files at startup and every 15 minutes thereafter. $$<SMS_DISCOVERY_DATA_MANAGER><03-30-2014 22:38:22.268+300><thread=2776 (0xAD8)> CreateUnknownSystemDDRs: already created~ $$<SMS_DISCOVERY_DATA_MANAGER><03-30-2014 22:38:22.270+300><thread=2776 (0xAD8)> Processing file adu12vfh.DDR $$<SMS_DISCOVERY_DATA_MANAGER><03-30-2014 22:38:22.377+300><thread=2776 (0xAD8)> *** Exec spGetNextIDInARange N'NextIds_G', N'NextUserID', N'User_DISC', 2063597568, 2080374783, N'ItemKey' $$<SMS_DISCOVERY_DATA_MANAGER><03-30-2014 22:38:22.388+300><thread=2776 (0xAD8)> *** [42000][33009][Microsoft] [sql Server]The database owner SID recorded in the master database differs from the database owner SID recorded in database 'CM_789'. You should correct this situation by resetting the owner of database 'CM_789' using the ALTER AUTHORIZATION statement. : spGetNextIDInARange_internal $$<SMS_DISCOVERY_DATA_MANAGER><03-30-2014 22:38:22.388+300><thread=2776 (0xAD8)> WARNING - GetNextIDInARange() failed to execute $$<SMS_DISCOVERY_DATA_MANAGER><03-30-2014 22:38:22.389+300><thread=2776 (0xAD8)> CDiscoveryDataManager::ProcessDDR - could not get next available item key. $$<SMS_DISCOVERY_DATA_MANAGER><03-30-2014 22:38:22.389+300><thread=2776 (0xAD8)> CDiscoverDataManager::ProcessUserDDRs_PS - SQL problem detected. Will retry later. $$<SMS_DISCOVERY_DATA_MANAGER><03-30-2014 22:38:22.389+300><thread=2776 (0xAD8)> CDiscoverDataManager::THREAD_ProcessUserDDRs - Failed to manage files in inbox. Will retry in at least 60 seconds $$<SMS_DISCOVERY_DATA_MANAGER><03-30-2014 22:38:22.390+300><thread=2776 (0xAD8)>

Guys I am running configuration manager 2012 R2 the problem I'm having is I can't get any of the discovery methods to work. I've ran user, group, and machine discovery several times and no data is pulled into config manager from active directory. I have tried this with the configuration manager computer account and even a regular ad user account still nothing. If you look at the below log snippet looks like the DDRS are actually being created. I have waited up to 60 minutes for the DDRS to be processed still nothing. Also if I go to the config manager db and do a select on views _RES_COLL_SMS00001, _RES_COLL_SMS00002, _RES_COLL_SMS00003, _RES_COLL_SMS00004 there is no data at all.So has anyone else here had this problem before? INFO: discovered object with ADsPath = 'LDAP://DC1.example.COM/CN=Tran\, Phuoc,OU=GN2,OU=Testou,DC=example,DC=com'~ $$<SMS_AD_USER_DISCOVERY_AGENT><03-30-2014 22:39:46.795+300><thread=1860 (0x744)> INFO: DDR was written for user 'example\jdoe' - C:\Program Files\Microsoft Configuration Manager\inboxes\auth\ddm.box\userddrsonly\adu2e0r1.DDR at 3/30/2014 22:39:46.~ $$<SMS_AD_USER_DISCOVERY_AGENT><03-30-2014 22:39:46.797+300><thread=1860 (0x744)>