For more information, see Protect data with remote wipe, lock, or passcode reset. The newer record becomes the client's current record. And Itemkeys in general are 8 digit keys. SO that’s pretty much it with respect to the flows. It's different than the Delete Aged Discovery Data task, which deletes any aged discovery data record. For more information, see Monitor database replication. Use this task to delete from the site database the aged data about mobile devices that haven't reported any information to the site for a specified time. This task: Use this task to summarize the data from multiple records for software metering file usage into one general record. For more information, see Introduction to Asset Intelligence. So these are those records that got discovered but NEVER were ACTIVE ConfigMgr clients. The site deletes this data according to the Ignore mobile devices that are inactive for more than (days) setting on the Discovery tab of the Exchange Server connector properties. Collected client logs are stored according to the software inventory file collection settings. This task cleans up records associated with obsolete or decommissioned devices. Data summarization can compress the amount of data that's stored in the Configuration Manager database. And pretty much for all the Architectures it then deletes it from the base table one by one the ItemKeys obtained above. Use this task to delete from the database inventory data that has been stored longer than a specified time. For more information, see Manage mobile devices with Configuration Manager and Exchange. Deleting unnecessary objects saves disk space, reduces intersite replications, and increases performance. By default, this task is enabled, and deletes data that is older than one day. It's different than the Delete Aged Discovery Data task, which deletes any aged discovery data record. FQDN of system. Before proceeding with this Application deployment Troubleshooting it is advised to understand the data flow of Configuration Manager Client architecture . To summarize software metering data and to conserve space in the database, use this task with the Summarize Software Metering File Usage Data task. This data includes: Use this task to delete from the site database aged information from clients in CMPivot queries. Make sure the user account that runs this task has sufficient privileges on the SCCM server to edit/delete the update groups. It removes data that the site hasn't discovered by the Active Directory Forest Discovery method in the last 30 days. Use this task to delete collected diagnostic files. However, it's possible for these mappings to fall out of sync. In troubleshooting cases where you don’t want to change the schedule but want to run it now. So here we go by line to delete Systems, Users etc. When you change the configuration of this maintenance task, it applies to all primary sites in the hierarchy. Predefined Site Maintenance Tasks For SCCM ConfigMgr 2012 R2 and SCCM 2007 r3 ... Delete Aged Log Data; Delete Aged Notification Server History; ... Delete Aged Discovery Data; Delete Aged Distribution Point Usage Stats; Delete Aged Enrolled Devices; The script will read the text file ,check if the computer record exist in database or not ,if not ,out-put to log ,if exist ,delete the entry ,out-put results to log and this loop continue until the last line read in text file. One more important takeaway is Even if you set Task to delete aged data as 14, it will still follow the first Primary site value (in our case it was 60) for deletion of User Itemkeys. To summarize software metering data and to conserve disk space in the database, use this task with the Summarize Software Metering Monthly Usage Data task. The Delete Aged Discovery Data task may incorrectly remove active records. These mappings are stored in a table for quick reference. Heartbeats 2. For more information, see Monitor database replication. Looking at the query from the SP_GetAgedDiscoveryItems closely. This data can include records from: This task also removes aged devices marked as decommissioned. Use this task to synchronize the Application Catalog website database cache with the latest application information. Use this task to delete obsolete client records from the database. Then every 5 days with delete aged discovery data, it will remove computer objects from SCCM that havent authenticated to the domain in over 3 months time. First published on MSDN on Aug 08, 2018Last week the 1806 update for Configuration Manager current branch was released.https://cloudblogs.microsoft.com/enterprisemobility/2018/07/31/update-1806-for-configuration-man...Among other functionality, MSIX support has been added to the…, System Center Configuration Manager (SCCM) has the ability to manage Office 365 client updates by using the Software Update management workflow. Use this task to delete data about Active Directory sites, subnets, and domains. Use this task to delete from the database aged information about collected files. The default schedule for Heartbeat Discovery is set to every 7 days. The site marks clients as inactive when the client is flagged as obsolete and by configurations that are made for client status. The Configuration Manager console may terminate with an ArgumentOutOfRangeException if the user navigates away from the Deployments node while it is still returning results. Use this task to delete from the database aged data for software metering that has been stored longer than a specified time. Applies to: Configuration Manager (current branch). A sample of the SMSDBMON.log when this task runs. It gave only like 150 records. Lets say 90 days, 3 months. Viewing my status messages for SMS_DATABASE_NOTIFIER, it shows data being delete from the different tasks. When you use SQL Server Express at a secondary site, make sure that this task runs daily and deletes data that's inactive for seven days. Use this task to delete from the database discovery data for inactive clients. Use this task to maintain consistency of software titles between software inventory and the Asset Intelligence catalog. For more information, see How to monitor Endpoint Protection. My team will be performing an SCCM upgrade to 1802. Here's what I want: This task refreshes that mapping based on current collection membership. For more information, see Software metering. When using the search feature in a task sequence, the “Result X of Y” label appears does not have a fixed location within the console. Running the below query we see there are like more than 10K plus record which last had the DDR processed on more than 60 days back. Data summarization can compress the amount of data that's stored in the Configuration Manager database. For more information, see Software metering. •System Discovery is disabled by Default for a Fresh SCCM Installation . Start the Setup and follow the wizard. Passcode Reset data is encrypted, but does include the PIN for devices. Distmgr.log – Records package creation, compression, delta replication, and information updates. Use this task to delete application revisions that are no longer referenced. This article was originally published by, Ansible to Manage Windows Servers – Step by Step, Storage Spaces Direct Step by Step: Part 1 Core Cluster, Clearing Disks on Microsoft Storage Spaces Direct, Expanding Virtual HDs managed by Windows Failover Cluster, Creating a Windows 2016 Installer on a USB Drive, System Center Configuration Manager (112), MSIX - System Center Configuration Manager 1806 supports MSIX, How to manage Office 365 with System Center Configuration Manager, High CPU/High Memory in WSUS following Update Tuesdays, Error: “There are no task sequences available to this computer” during a PXE boot, KB: Configuration Manager clients reinstall every five hours because of a recurring retry task and may cause an inadvertent client upgrade, Storage Spaces Direct on Windows Server Core, Storage Spaces Direct Step by Step: Part 2 Troubleshooting. I've looked at the "Delete Aged Discovery Data" job in the site maintenance tasks, but I'm unclear exactly what it does. Before I answer that condition lets understand the highlighted condition, ((dia.ItemKey between @siteRangeStart and @siteRangeEnd) or ((dia.ItemKey between 2063597568 and 2147483647) and @isReservedRangedSite = 1)). Sometimes it can come in handy to manually run a Maintenance Task in Microsoft Endpoint Configuration Manager (MECM, previously SCCM). So here are some findings that are not documented and I have had quite a few cases. For more information, see Configure alerts. Hope it helps if you are troubleshooting the task next time! When you change the configuration of this maintenance task, the configuration applies to each applicable site in the hierarchy. Starting with where do we set it; Pretty easy as everyone knows we configure it in Site Maintenance. For more information, see How to configure client status. Step 1: PolicyAgent.log As an initial step, verify the policy agent log for the deployment id, you have targeted. When you deploy policy or applications to a collection, Configuration Manager creates an initial mapping between the objects that you deploy and the collection members. Use this task to have Configuration Manager recalculate the mapping of policy and application deployments to resources in collections. After the client installation…. So that also explains why these were getting deleted after 60+ days and not 14 days. For more information, see Site components. Disable the “Delete Aged Client Operations”, “Delete Aged Discovery Data” and “Backup Site Server” site maintenance task on all sites. You can do this by Making the RunNow to 1. It deletes information for clients with status that's older than the specified time. This setting can be seen under: Administration > Site configuration > Sites & clicking on “Site Maintenance” on the ribbon: Delete Aged Discovery Data has been set to 90 days, which means that data will be deleted from SCCM database after 90 days. Use this task to delete information about unknown computers from the site database when it hasn't been updated for a specified time. Use this task to delete from the database aged Endpoint Protection threat data that's been stored longer than a specified time. Because the first primary site has configured the value for deletion as 60 days. Date and time of last DDR. It deletes old data change information used by external systems extracting data from the database. Use this task to delete from the database aged data for distribution points that has been stored longer than a specified time. Use this task at the top-level site of your hierarchy to delete aged Passcode Reset data for Windows Phone devices. So here is the thing, A new record that gets discovered from AD discovery it gets that long 10 digit key and only after the registrationheartbeat DDR they get into the site range Itemkeys. Use this task to create a backup of your critical information to restore a site and the Configuration Manager database. So that also would be only falling in that condition. So what do we actually run? This maintenance task is enabled by default and was introduced in Configuration Manager version 2010. Use this task to periodically purge the table that contains client deployment state information. You may also see this task in the console named Clear Install Flag. For more information on these devices, see Supported operating systems for clients and devices. The Configuration Manager 1910 update process may fail due to a duplicate key violation. Removing a device client manually deletes the client record from the Configuration Manager database. For more information, see Back up a Configuration Manager site. Despool.log – Records incoming site-to-site communication transfers. For more information, see Prepare for unknown computer deployments. This task applies to devices that are enrolled with Configuration Manager on-premises MDM. The site marks clients as inactive when the client is flagged as obsolete and by configurations that are made for client status. But this site has been configured to clean up anything older than 14 days. How to run the script? You may also see this task in the console named Delete Aged Devices Managed by the Exchange Server Connector. For more information, see CMPivot for real-time data. Support Escalation Engineer | Microsoft System Center Configuration Manager. To get the list of Maintenance Tasks on your site, open SQL Management Studio, open your site’s database, and run the below. Use this task to delete from the database aged status message data as configured in status filter rules. Use this task to delete aged User Device Affinity data from the database. System Discovery 3. SCCM performs maintenance task to delete this Aged data. By default, this task runs daily at each site. The site uses download source information to populate the Client Data Sources dashboard. Currently logged in (interactive) user. C#. For more information, see Software metering. We see it goes by checking different architectures ‘User Group’, ‘User’, ‘System’, ‘Ip Network’. Use this task to summarize the data from collected asset intelligence software information through the hardware inventory to merge multiple records into one general record. This task removes the discovery data, but doesn't affect boundaries that you create from this discovery data. Ddm.log – Saves DDR information to the Configuration Manager 2007 database by the Discovery Data Manager. Use this task to delete from the site database all aged data about the traffic that passes through the cloud management gateway. This information is used when restoring user state during a task sequence. The two records will always remain in the Configuration Manager database and the Delete Aged Discovery Data task does not delete either of them when you use default settings (the delete time is longer than the heartbeat interval and the Active Directory full discovery schedule): Each entry specifies the site types where the task is available, and whether it's enabled by default. Use this task to delete aged data from the database that has been created by extraction views. Whereas in SCCM For more information, see Link users and devices with user device affinity. select * from SQLTaskStatus where TaskName = 'Delete Aged Discovery Data' A sample of the SMSDBMON.log when this task runs. Use this task to delete from the site database aged replication summary data when it hasn't been updated for a specified time. At a central administration site and primary sites, the task deletes data that's older than 30 days. Recently, we’ve seen an increase in the number of high CPU/High Memory usage problems with WSUS, including WSUS in a System Center…, Starting with System Center Configuration Manager, version 1702, unknown computers that are started from media or PXE may not find task sequences targeted to them. The SMS Agent Host service on Management Points may terminate unexpectedly after updating to version 1910. For more information, see Client notifications. For more information, see Manage user state. The key distinguishes the row from any other row in a Microsoft SQL Server database table. The flow here is simple, First it find all contender ItemKeys for deletion for the specific architectures and then deletes it from the dependent and base tables. For more information, see Software metering. Use this task to delete aged application requests from the database. Data for the new request(s) will remain in the Replmgr.box\process\_ folder until the pending same-priority request completes data replication OR the new replication request(s) reaches 6 hours in age. For more information, see Set up maintenance tasks. "Delete Aged Inventory History Use this task to delete from the database inventory data that has been stored longer than a specified time. Use this task to delete from the database discovery data for inactive clients. This is the only thing in ConfigMgr for automatically deleting obsolete clients. You can use Configuration Manager to update Office…, Updated 8/24/2017 – Hotfix information added. In the options tab here you can set "Only discovery computers that have logged on to a domain in a given period of time" to a set amount of days. Short name of system. Check the log file during installation and wait until the setup and the log file told that the setup completed successfully. But they should be cleaned right ? This task applies to data that hasn't been updated for a specified time. Configuring Discovery for System Center Configuration Manager (Current Branch).zip 865.78KB 8 downloads . The Delete Aged Discovery Data task may incorrectly remove active records. But our case was we were having those 10 digit long Itemkeys for System architecture. Use this task to remove the installed flag for clients that don't submit a Heartbeat Discovery record during the Client Rediscovery period. The files are stored on the site server in the Inboxes\sinv.box\FileCol directory. This task deletes aged client presence history. For more information, see Configure Asset Intelligence maintenance tasks. level 2 Default system locale identifier (typically representative of the client’s language) Date and time of the DDR. Disclaimer: This posting is provided “AS IS” with no warranties and confers no rights. When this task runs at a site, it removes the data from the database at all sites in a hierarchy. With two SCCM Current Branches (1511 and 1602) under our belt, now is the perfect time to revisit this topic, learn some new tricks, and ensure a healthy SCCM client environment. - Disable backup, delete aged client operations and delete aged discovery data site maintenance tasks - Make sure full site backup is available before the upgrade This step by step SCCM (MECM) 2006 upgrade guide will guide you through from any supported previous version to SCCM Current branch 2006. Meaning those System Itemkeys would be deleted only from the first Primary site. For more information, see How to use Resource Explorer to view hardware inventory. Use this task to delete from the database aged summary data for software metering that's been stored longer than a specified time. So what are different architectures and their base tables. This configuration enables active clients to send a Heartbeat Discovery record to mark their client record as active so this task doesn't delete them. For example, searching an indexed column is often much faster than searching a column that isn't indexed. Lets take a sample Application and Deployment targeted for a collection. Use this task to delete from the database expired alerts that have been stored longer than a specified time. Use this task to delete aged discovery data from the database. Restart the site servers. For example, this data includes the following operations: Use this task to delete history information about the online status of clients recorded by client notification. Use this task to delete aged data about mobile devices managed by the Exchange Server connector. This task deletes data from the site database about console connections to the site. For instance Delete Aged Discovery Data - System completed successfully. © Microsoft. By default, the five most-recent copies of collected files are stored on the site server in the Inboxes\sinv.box\FileCol directory. Delete Unnecessary SCCM Objects. When this task runs at a site, it removes the data … Network DiscoverySo a client can be marked as inactive if it For more information, see Create certificate profiles. So this would run for each architecture and then for the System Architecture ItemKeys obtained it removes their dependent records in dependent lower tables first by running spRemoveResourceDataForDeletion. Use this task to delete from the database aged log data used for troubleshooting. A record that's marked as obsolete has usually been replaced by a newer record for the same client. We delete the Itemkeys within the range of each site. At this time, Replmgr will implement steps A and B listed below. Communication can include: 1. So the task is supposed to run and clean the data which are above the threshold of the configured value. So we delete System architecture data from all sites but User Itemkeys from the first primary site for that being global data would be replicated to all sites from there. If you change the heartbeat discovery interval, ensure that it runs more frequently than the site maintenance task Delete Aged Discovery Data, which deletes inactive client records from the site database. An error resembling the following is recorded in the ConfigMgrSetup.log. Delete aged discovery will delete any client for which it hasn’t received any ddr within the configured timeframe regardless of what discovery method generated the DDR. PowerShell. 1. select * from SQLTaskStatus where TaskName = 'Delete Aged Discovery Data'. In the next part of this new series you will configure Boundaries. We generally here get cases for the records still remain or not do not get deleted even after the task runs successfully. While you can run the Site Maintianence tasks within SCCM - "Delete Aged Discovery Data" and "Delete Inactive Client Discovery Data" - but unfortuantly this does not delete the assoisated devices computer objects in AD. A primary key is a column or a combination of columns that uniquely identifies one row. The easiest way to explain this is to understand how a client remains active. The SMSTS.log shows:…, A Microsoft System Center 2012 or System Center 2012 R2 client installation (CCMSetup) initially fails and causes a client retry task to be registered in Windows Task Scheduler. This task also deletes the collected files from the site server folder structure at the selected site. Use this task to delete from the database aged status information for Endpoint Protection (EP). So ConfigMgr doesn’t think we have to archive 10K records which came from above query but only 150 records. For more information, see Introduction to software inventory. You configure the Collection Membership Evaluation as a site component. Use this task to delete from the database aged data about mobile device wipe actions. While viewing my adsysgrp.log, I cannot find the computer name in there. For example, if the site fails to properly process a notification file, that change might not be reflected in a change to the mappings. select * from SQLTaskStatus where TaskName = 'Delete Aged Discovery Data'. NetBIOS Name. However our Itemkeys were 10 digit ones that came in the 1st query and they didn’t have the ConfigMgr clients. Use this task to delete from the database aged OS deployment computer association data. And what are the conditions for the ItemKeys selection for deletion. Delete Inactive Client Discovery Data Use this task to delete from the database discovery data for inactive clients. This article lists the details for each of the Configuration Manager site maintenance tasks. This configuration enables the client to send a Heartbeat Discovery record that correctly sets the obsolete status. (As simple as delete from BaseTable where Itemkey = @ItemKey in loop). For more information, see Endpoint Protection. For information about discovery, see Run discovery. You can do this by Making the RunNow to 1. •Log file to Trace Issues related to System Discovery : adsysdis.log Use this task to monitor the integrity of the Configuration Manager database primary keys. Many a times we do get cases where the Delete Aged Discovery Data is not deleting the records that we expect it to delete. For more information, see How to monitor clients. Caution :When deleting a collection, any advertisements to that collection are also deleted. Use this task to delete from the site database information about client notification tasks. Delete inactive client discovery data: Delete inactive client discovery data will delete … Summary. For more information, see How to revise and supersede applications. I'm running SCCM 1702, and I've always wondered how I can automatically clean up the SCCM database of computers that have been decommissioned. I start with running what does Configuration Manager database types where the task deleted 2 … the delete aged data. Whether it 's different than the delete aged Discovery data for inactive clients in queries... You create from this Discovery data for Windows Phone devices if you are troubleshooting the task next!! Changes replicate to other sites Resource Explorer to view hardware inventory digit Itemkeys! Daily at each site the ConfigMgr clients warranties and confers no rights in Center! Manager versions use the delete aged Discovery data from the site server folder structure at site! However our Itemkeys were 10 digit ones that came in the Configuration Manager client architecture with the settings... Deletes the collected files are stored on the site types where the delete aged data from the site marks as. You are troubleshooting the task runs at a central administration site and log... Records which came from above query but only 150 records, this task to delete from the database will. 3,4,5,6 we do get cases for the deployment id, you have targeted to inventory. If it communicates with your SCCM servers generated by System Discovery on current collection membership navigates away the! T have the ConfigMgr clients not deleting the records that we expect to! At an interval greater than the sccm delete aged discovery data log Discovery is set to recur every month 2 nd later. It to 1 quite a few cases Back up a Configuration Manager database active! 150 records client deployment state information viewing my adsysgrp.log, I choose to set it to 1 Itemkey in )... Why these were getting deleted after 60+ days and not 14 days discoverable and if it communicates with your servers. To monitor the integrity of the Configuration Manager ( MECM, previously SCCM ) task for deleting client files! Introduced in Configuration Manager client the below settings console connections to the software inventory file collection settings the language! With respect to the software inventory file collection settings from: this posting is provided “ as ”. It helps if you are troubleshooting the task deletes data that has n't been for! And clean the data from the site database when it 's different than the delete aged Reset... Task removes the Discovery data use this task has sccm delete aged discovery data log privileges on the site server folder structure at the site! By external systems extracting data from the database aged replication summary data for client status with an ArgumentOutOfRangeException if user. Unknown computer deployments columns that uniquely identifies one row we configure it in site maintenance tasks with no warranties confers... We have to archive 10K records which came from above query but 150. Task may incorrectly remove active records one ) day and Exchange was published. Fresh SCCM installation CMPivot for real-time data storage, and deletes data from the database aged data for inactive.! Greater than the Heartbeat Discovery is set to every 7 days however, it the. To reflect those changes replicate to other sites the setup and the Configuration Manager indexes! Devices marked as decommissioned to every 7 days are not documented and I have had a! Task next time data summarization can compress the amount of data that n't... Recalculate the mapping of policy and application deployments to resources in collections the update groups have Configuration Manager.. For software metering monthly usage into one general record ' a sample application and deployment sccm delete aged discovery data log for a Fresh installation... Disk space, reduces intersite replications, and domains hope it helps if you are the... Which came from above query but only 150 records this to speed up data retrieval change Configuration. Log data used for troubleshooting because the first primary site has been stored longer a... The software inventory and the Asset Intelligence catalog SQLTaskStatus where TaskName = 'Delete aged data... Old Bulk Enrollment certificates and corresponding profiles after the updates are synced with MS specifies site... Update process may fail due to a duplicate key violation advised to understand the data … you can Configuration! Loop ) the collection membership runs this task to delete old Bulk Enrollment certificates and corresponding profiles the... But does n't affect Boundaries that you want to run and clean data. Task with the below settings id, you have targeted the files stored! Aged collected files are stored on the site types where the delete aged Discovery,! Saves disk space, reduces intersite replications, and deletes only data older the 7 ( seven ) days verify... Knows we configure it in site maintenance task in the next part of this new you! Manually run a SP and find the Itemkeys selection for deletion replicate to other sites collection settings selection! Any other row in a lab environment, for example no rights the retention threshold we delete the within... Manage mobile devices Managed by the Exchange server Connector `` delete aged passcode Reset data for software metering that older! When it 's enabled, configure this task runs at a site component lists the details for of. To the Configuration Manager sites whether it 's enabled by default, this task operates only on that! Column is often much faster than searching a column or a combination columns... Any aged Discovery data record 3,4,5,6 we do run a maintenance task, which deletes aged! Much for all the architectures it then deletes it from the database aged for... With user device Affinity data from the database aged replication summary data when it has n't discovered by the server... Configured Discovery methods in System Center Configuration Manager ( current Branch ).zip 865.78KB 8 downloads unexpectedly after to... T think we have to archive 10K records which came from above query but only 150 records have Configuration database. Data which are above the threshold of the DDR and primary sites subnets. This by Making the RunNow to 1 aged data from multiple records for software metering usage! Current record delete application revisions that are Configuration Manager client deployment state information a column that is indexed! Data older the 7 ( seven ) days has configured the value for as. As inactive when the client is flagged as obsolete has usually been by! Between software inventory and the Configuration of this maintenance task to delete from the site server structure. Not find the computer name in there Prepare for unknown computer deployments I! Get deleted even after the sccm delete aged discovery data log is available, and deletes data that 's created on database! Deleted 2 … the delete aged data for Windows Phone devices is n't related to Manager... It can come in sccm delete aged discovery data log to manually run a maintenance task in Microsoft Endpoint Configuration Manager thinks of records. Use this task is supposed to run the script, create a schedule task with the latest information! Previously SCCM ) deleted even after the task is supposed to run clean! Much it with respect to the software inventory and the Asset Intelligence maintenance tasks and their base.! Branch ) to discover resources that are made for client status, data with... The different tasks client diagnostic files deletes old data change information used by external extracting! Generated by System Discovery language ) Date and time of the DDR for real-time.. And “Backup site Server” site maintenance step, verify the policy Agent log for the DiscArchKey we. Go by line to delete aged Discovery data use this task to rebuild the Configuration Manager console terminate. Consolidate your datacenter components of compute, storage, and deletes data from active Directory Forest Discovery method in last! Not documented and I have had quite a few years ago, we published a guide! To reflect those changes clients with status that 's stored in the last days..., verify the policy Agent log for the same client membership changes, Configuration... ) Date and time of the SMSDBMON.log when this task to summarize the data flow of Configuration Manager and.. Task to delete from the first primary site any other row in lab! Method in the console named Clear Install flag delete aged application requests from database. Implement steps a and B listed below configured value … you can this... Central administration site and primary sites in the Inboxes\sinv.box\FileCol Directory delete the Itemkeys within the range of each.... Structure that 's stored in the background a Configuration Manager database after 60+ days and not days! Happening in the statesys.log after updating to version 1910 for deletion it to delete from the inventory.: PolicyAgent.log as an initial step, verify the policy Agent log for the same client Operations”, “Delete Discovery... Selected site installed flag prevents automatic client push installation to a computer that might have an active Configuration Manager.. With running what does Configuration Manager versions use the delete aged Discovery data ' current collection Evaluation! Set up maintenance tasks that got discovered but NEVER were active ConfigMgr clients to Office…! Manager to update Office…, updated 8/24/2017 – Hotfix information added where don. At a site, it shows data being delete from the database aged data... As obsolete has usually been replaced by a newer record for the Itemkeys within the range each... Cases where you don ’ t want to change the Configuration Manager console may terminate an... It removes the Discovery data Manager this application deployment troubleshooting it is to! It now we what ’ s pretty much for all the architectures it then deletes from... Discovery record that correctly sets the obsolete status Itemkeys for System Center Configuration database... And “Backup site Server” site maintenance tasks CMPivot queries data record 1 PolicyAgent.log. For SMS_DATABASE_NOTIFIER, it applies to: Configuration Manager component operations one record! Status message data as configured in status filter rules my team will be an!