Retire a ci in servicenow. Does it affect or impact? 0 Helpfuls Reply.

Retire a ci in servicenow Steps Log in to any out-of-the-box instance Open the cmdb_rel_ci table Open both Parent ServiceNow Learn more about ServiceNow products and solutions. Retire Asset: Streamlining the Off-Boarding and Reclamation Process When an employee leaves an organization or transitions to a different role, managing the reclamation and retirement of their software and hardware assets is a critical task. I created a Flow Designer, after approver approves it will g We would like to show you a description here but the site won’t allow us. Community Ask questions, give advice, and connect with fellow ServiceNow professionals. I was thinking for using workflows for both cases but not sure if it is The operational status field on the CMDB CI table is not getting updated when an asset status is updated to retired. Referring to the example above, if a Retire policy used Solved: Which Table are dependent CIs added to, if a CI is set to retire ? See demos and learn more about the Xanadu release, our biggest AI release yet. it will create a task. Does the Discovered Item (and Vulnerabilities) still . Where updated field not on the current year and is empty using Busines rules ServiceNow Learn more about ServiceNow products and solutions. Tera Patron Options. Any child classes of cmdb_ci_printer will inherit its definition - not that of cmdb_ci. Partner Grow your business with promotions, news, and marketing tools. Beginning in Tokyo, the CICD API endpoints that need to obtain the instance wide lock / mutex to perform their requested operation will use a queue, rather than rejecting requests while the instance wide lock / mutex is occupied. Retire/Archive/Delete policies use the definition that applies to the CI class selected in the Data Filter. Support Manage your instances, access self-help, It is always best to retire or decommission CI's and retain their historic information in the system. It is said that dependent CI to retire are added to the table cmdb_dependent_ci_ledger and "Those CIs are set as being ready to retire using the CMDB Ideally you would retire CI's through the change process. 4. Impact Accelerate ROI and amplify your expertise. Take a look at this article, it handles CI Retirement and Deletion. From the conceptual pre-design phase, through the design Starting in the ServiceNow London Release, the Reconciliation Engine does not count Software Installation records related to CI's in a state of Retired. Support Manage your instances, access self-help, and get technical support. This document is intended for the CI owners/data steward to maintain their CI’s status when they’re decommissioning devices or CIs that are not supposed Mid-server is just a server to connect with the local network ,it does't retire ci. Thanks , The mid server and the CMDB are separate components that serve different purposes within ServiceNow. It might be available when you are using the the discovery feature of ServiceNow. ServiceNow Configuration Management is a key process in IT Service Management (ITSM) that helps you track and control the assets and services in your IT environment. I'm currently practicing in a Dev instance to bulk retire Server class ci's and get a return count of the number of Servers updated via the background script. For updating third party tool . Documentation Find detailed info about ServiceNow products, apps, features, and releases. Does it affect or impact? 0 Helpfuls Reply. This is what the Discovery Dashboard uses for Unrefreshed Devices (Beyond Last 30 Days) and 1. ci. The CI's that have been decommissioned will not be deleted from the CMDB. After the data retention period has expired, then you can delete the CI. AG - LearnNGrow. Reference: Business Rules - ServiceNow Wiki ServiceNow Learn more about ServiceNow products and solutions. sys_ci_automation or admin role is required to use this API. It is said that dependent CI to retire are added to the table cmdb_dependent_ci_ledger and "Those CIs are set as being ready to retire using the CMDB Data Manager upon approval. For more information about a particular endpoint, click on it in the left pane to view a description of the endpoint, applicable query parameters, a sample request in multiple formats, and a sample response Documentation Find detailed information about ServiceNow products, apps, features, and releases. The mid server can ServiceNow Learn more about ServiceNow products and solutions. User can multiselect the CI (field - Select CIs(List collector- cmdb_ci table)). Multiple CICD pipelines simultaneously make requests without detecting the We would like to show you a description here but the site won’t allow us. The method and time period will be based on the organization's data archival and deletion policies . This is awesome, and all is well and good. For updating CMDB 2. This document describes how to delete those relationships if they are not needed ii) Directly deleted after a specified time period from the retirement date. From information gleaned on the CMDB, Discovery and CSDM it looks like the way to show a ci as retired is to set the Operational Status to Non-operational and the Install Status to Retired. Now there is a whole bunch of stuff created, CI_IP's, software, running processes, ETC. An example is we have CIs that get set to retired but the CIs that "runs on" the retired CI are still set to in use. 2. com). Either way you should have a The new ServiceNow feature, “CI Attestation in CMDB Workspace,” helps to verify the existence of IT infrastructure and applications that you own systematically and in bulk. Below you will find a list of the available endpoints with the latest information. These auto-updates can be processed automatically or be set to generate tasks for a human approval/intervention. In other cases, you might not want to bother with Lifecycle Management and just straight up In this case, ServiceNow recognizes the CI based on the serial number and updates the name. cmdb_ci is For retirement, the Retire - Retire synch will allow for asset to display as many substates as you would like while still synching the CI as retired. You can specify a Retirement Definition for a parent CI class (e. Help. The "CMDB DependentCI Policy Processor" Hi all, I am trying to utilize the Cascade-retire dependent CIs out of box feature for below need: If a server is retired , all dependent ci to be retired. ; Partner Grow your business with promotions, news, and marketing tools for partners. Otherwise you can consider to just retire them (Status = Retire). For this test I'm trying to update the ServiceNow Learn more about ServiceNow products and solutions. how to disable the view-ability of retired ci and rel in some forms, 3. A relationship in the CMDB consists The Configuration Item (CI) lifecycle is the key to success in managing as IT assets in the ServiceNow cmdb. Build it on task_ci, and filter it on the Task field to only show records that start with INC (incident records). com)) Hi ServiceNow Community, I am interested to know how users of Assets/CIs in ServiceNow handle the decommissioning process, particularly for virtual servers. Duplicates being one of them. example: Application (A9@sqlau001mel0531) runs on a Windows Server (sqlau001mel0531) When sqlau001mel0531 is retired, A98_PROD@sqlau00mel0531 would become orphan dependent CIs. I have created a catalog item to Retire the CIs. The system can automatically create de-duplication tasks, that have a workflow, which can remediate duplications either through retirement or deletion. English (US) Documentation Find detailed info about ServiceNow products, apps, features, and releases. enabled and cmdb. If all you are looking to do is to see if the affected CI's of an incident were either swapped, retired, updated/repaired, or 'no action' then that is simple enough to do by building a report on the task_ci table. batch. retire. I am wondering if there is an effective way to integrate this with the newer retirement definitions and data management features from the CMDB ServiceNow Learn more about ServiceNow products and solutions. This allows you to do something such as retire a record in your CMDB for a computer, printer, server, etc after it's not been seen for a period of time. CI records can be excluded in the following: Review page when editing a Data Manager policy (excepting Certification policy types) Reviewing rec We would like to show you a description here but the site won’t allow us. Relationship between Ideally you would retire CI's through the change process. So it has set Hi All, I have created a catalog item where there is a field - Select CIs(List collector- cmdb_ci table). Basically with Vulnerability Management, if you retire the CI and are using the CI Life Cycle it will retire the vulnerabilities associated with it. Maybe there is another issue, like In fact CMDB tables will not have active inactive flags. In your case you'd define two policies in CMDB Data Manager: Retire policy: sets the Lifecycle Stage field to "End of Life" for the Network Adapter CIs CMPReconciler script include is meant to handle CI reconciliation such as retiring/reviving CIs. I don't have any sample data in my instance to test it right now but I guess the metric is I want to create policies for cmdb_ci_computer table and its subclasses. We have a decom process that will change the Server CI to retired but the Mid-server is just a server to connect with the local network ,it does't retire ci. This article might answer some of these common questions: 1) When there are duplicate CI in the system, the VIT that is being Ideally you would retire CI's through the change process. CMDB Data Manager My first guess would be to say that what you should do when you retire a CI is to remove all its relationships, provided : Deactivate the links only when the CI goes from an When a parent CI is retired, the related child CIs (both hardware and software CIs) do not automatically get retired. " Documentation Find detailed info about ServiceNow products, apps, features, and releases. CI records can be excluded in the ServiceNow Learn more about ServiceNow products and solutions. In most cases, developing a business app is an arduous, time-consuming endeavor. Learning Build skills with instructor-led and online training. Reference: Business Rules - ServiceNow Wiki Documentation Find detailed information about ServiceNow products, apps, features, and releases. In order to sort for the data needed for the project, they have a need to filter assets by their CI's Operating System and a few other values. It is explained in the following URL: ServiceNow Learn more about ServiceNow products and solutions. Optionally, this can be based on the state of the CI. Post Reply Documentation Find detailed info about ServiceNow products, apps, features, and releases. CI records can be excluded in the following: I have created a catalog item to Retire the CIs. cmdb_ci is a parent to cmdb_ci_service table you can make use of operational_status filed and write rules not not show non-operative CIs. 2. Identify the steps in your asset retirement/decommission process. You have a parent CI, say a Server - and this has been discovered by Discovery. How can we get list servers with mapped applications like webservice, tomcat servers, tibco cis, mssql db etc. I don't believe this is part of HAM Pro. Support Manage your instances, access self-help, In fact CMDB tables will not have active inactive flags. Should the system for some reason not create a de-duplication task for a particular CI, you can also Manually create a de-duplication task (servicenow. Software Installations is updated for Retired Configuration Item (CI) Loading Skip to page content Skip to chat Documentation Find detailed information about ServiceNow products, apps, features, and releases. So I thought to retire all related cis that are mapped to This article aims to explain the CI matching process from Qualys Integration. Logically when an asset is set to retired state, it sets to install_sttaus, hardware_status, sys_trigger record for CMDB Data Manager policy "Dependent CI Deletion" is missing in some instances, meaning that although it is active out-of-box, it doesn't run. I created a Flow Designer, after approver approves it will go to the Look up records ServiceNow provides extensive access to instances through a set of RESTful APIs. Locations don't have an 'active' field, so it will remain in the system. Now there is a whole bunch of stuff created, CI_IP's, software, running processes, ET What is the best practices when it comes to retiring a CI, I am having trouble wrapping my mind around this. Learning Build your skills with instructor-led and online I have set the operational status for the New CI to retire and changed the CI of the ticket to older one manually. data. The sn_cicd. This is to ensure we maintain the prior history of CMDB CI's. The mid server and the CMDB are separate components that serve different purposes within ServiceNow. But we. Create a stale rule. For information about the CI life cycle , refer this link: The Devvies 2025 are here! Celebrate your hard work and innovation by submitting your apps today. The mid server can interact with the CMDB by retrieving or updating information about CIs, but it does not have the capability to retire them. This is thanks to, in part, the app development and delivery process. According to the Retire a versioned article documentation: In addition to the knowledge administrator and the knowledge manager, the following users can retire a versioned article: knowledge owner latest Hi, We currently set the Operational status of a CI to 'Retired' if it isn't discovered for more than 7 days using a CMDB data policy rule. If the operation of the asset showing the CI record is heading towards retirement, whether disposed or re-imaged or harvested for its sw licenses prior to disposal, you can allow for that variation on the asset record. All of the plug-ins that I have read are needed were already previously installed and I have verified that both cmdb. ServiceNow Community servicenow community. From recognizing and integrating the best of breed CI lifecycle, organizations would be able to obtain accurate, complete, and consistent data from the CMDB ultimately benefiting IT operations and decision making within the organization. Create / Update / Retire a CI in CMDB based on Change Task. Learning Build your skills with instructor-led and online training. 0 Helpfuls Reply. 5. I got a script that was provided by a member in the community to retires CI's and remove relationship if the CI's hasnt been updated in the pas 7 days. So the conclusion is, the only thing we can do, is delete the record from the cmdb_rel_ci table to clean up the related items elsewhere in ServiceNow. delete. CI records can be excluded in the following: Review page when editing a Data Manager policy (excepting Certification policy types) Reviewing records in a task Documentation Find detailed info about ServiceNow products, apps, features, and releases. cascade. For information about the CI life cycle , refer this link: Here The mid server and the CMDB are separate components that serve different purposes within ServiceNow. In my instance I am having more than 8k staled cis. This process ensures that all assigned assets are return ServiceNow Learn more about ServiceNow products and solutions. I will add, there are times when a CI might be deleted. size. Is there a way to make this happe Documentation Find detailed info about ServiceNow products, apps, features, and releases. Support Manage your instances, access self-help, Unless the CI record is added to the exclusion list in Data Manager, the next time a Retire policy is executed the CI will show up in the task generated. The process of retiring CIs from the CMDB typically We have an ask to delete or retire asset records for virtual machines that have been accidentally created over some time. cmdb. Support Manage your instances, ServiceNow Learn more about ServiceNow products and solutions. For example, if your data retention policies state that you must retain records for 3 years, then that 3 years likely begins when the CI is retired. Impact Drive a faster ROI and amplify your expertise with ServiceNow Impact. Policies for retiring/archiving/deleting CIs are evaluated on a daily basis making them dynamic - the target CI list is updated based on what's in the CMDB when the scheduled job for a policy runs. 1. Mark as New; Hi @yogesh15dd ,. This is entirely separate from any tool. U need to create a Fix script for this where u can write a GlideRecord query & update the required amount of CI's in Bit late to the party - but just looking into the same problem field: Regarding @Mark Bodman recommendation to use the Data Manager Lifecycle approach: that viable if you have higher value CIs for which you actually want Lifecycle Management. In your case you'd define two policies in CMDB Data Manager: Retire policy: sets the Lifecycle Stage field to "End of Life" for the Network Adapter CIs For info the Dependent CI retirement is managed by 2 jobs : - CMDB Cascade Retire Dependent CIs (which fill in the ledger) Step 1: Follow all the steps provided for CI dependent management ( refer servicenow docs) Step 2: Execute the scheduled job : CMDB Cascade Retire Dependent CIs] ServiceNow Learn more about ServiceNow products and solutions. You can replace life_cycle_stage with operational_status in the OOB Retirement Definition for cmdb_ci, remembering to set the Documentation Find detailed info about ServiceNow products, apps, features, and releases. What is the best practices when it comes to retiring a CI, I am having trouble wrapping my mind around this. Sometimes you will need to delete some relationships between the CI's in the CMDB that were created for testing purposes. ServiceNow Learn more about ServiceNow products and solutions. op. But we did find out was if the CI does get discovered after this, the Operational status doesn't change to 'Operational'. Either way you should have a business rule which when it goes to retire state you Hi All, What is the best and correct way to handle/reduce staled cis in cmdb. For example, once a server is repurposed, mark the old CI as ServiceNow Learn more about ServiceNow products and solutions. ; Store Download certified apps and integrations that complement ServiceNow. manager. Support Manage your instances, I want to create a script that will retire a CI if it has not been discovered/updated after 7 days, and change the sate to Retired,and remove the relationships attached to the The purpose of Retirement Definitions is to specify the field and value for a CI class that equates to retirement. This would be like throwing a take-out container into the trash ServiceNow Learn more about ServiceNow products and solutions. Usually, records on a 'location' either have the field optional for all locations (a printer can be installed in an Documentation Find detailed info about ServiceNow products, apps, features, and releases. Developer Build, test, and deploy applications. The CMDB, in contrast to a static asset list, helps you track not only the configuration items (CIs) within your system but also the relationships between those items. Hi @Shantharao . In the case above the Retirement Definition should be Install Status is Retired. When user select the CI/CIs then it will ask for approval and then the operational status of Documentation Find detailed information about ServiceNow products, apps, features, and releases. Hello, I want to set select Window server ci's to retired so that Discovery no longer reports then as stale. But I need to factor in If either child or parent in the relationship has been updated in last 7 days then leave the status for both CIs and all rel A ServiceNow Admin's 12 Days of Christmas in SysAdmin blog 4 weeks ago; Seeking ServiceNow Opportunities: Developer/Admin with Proven Expertise in ServiceNow Jobs forum 12-06-2024; Retired CI list is missing in CMDB Retirement Definitions are used to specify the field to be used for retiring a CI record. We use ServiceNow discovery and also the VMWare discovery. For decommssion purpose I executed API call to set status as 'Retired' operational status as 'Non-Operational'. Has anyone leveraged ServiceNow to automate the retirement/decom of configuration items? Can the release module be leveraged and a Retirement Release would be set-up and all the change requests need to retire the application assets would be created against that release? We currently run reports to pull all the CI's but would like to create CR's. This would be like throwing a take-out container into the trash (retire the Policies for retiring/archiving/deleting CIs are evaluated on a daily basis making them dynamic - the target CI list is updated based on what's in the CMDB when the scheduled job for a policy runs. This results in two servers with the same CI name, causing the server history to be split across two CIs. enabled system properties are set to true. But like Anshu mentioned, you need to know the why the CI isn't updating anymore. ServiceNow for CI/CD. The new ServiceNow feature, “CI Attestation in CMDB Workspace,” helps to verify the existence of IT infrastructure and applications that you own systematically and in bulk. There is an active boolean on the CI table. The mid server can interact with the CMDB by retrieving or updating information Loading Loading I'd like to understand behaviour of ServiceNow after retirement of asset in CMDB. ServiceNow provides extensive access to instances through a set of RESTful APIs. Note that Retirement Definitions can only specify a single value for a field included in the definition - multiple values for a single field are not supported. For more information about a particular endpoint, click on it in the left pane to view a description of the endpoint, applicable query parameters, a sample request in multiple formats, and a sample response I want to create policies for cmdb_ci_computer table and its subclasses. ; Impact Drive a faster ROI and amplify your expertise with ServiceNow Impact. Best practice to follow to maintain the retired ci and its relationship. Subscribe to RSS Feed; Mark Question as New (Rapid7 InsightVM) detects vulnerabilities on an asset/host that is active on the network but the CI in the CMDB is set to as `Retired`. If it is a CI, it is governed by change so an RFC should handle the decommission. In this case, ServiceNow recognizes the CI based on the serial number and updates the name. Asset and configuration item (CI) management refers to creating assets, setting appropriate states and substates, synchronizing assets and CIs, managing consumables, and retiring assets. Store Download certified apps and integrations that complement ServiceNow. (SN Docs: Dependent CIs management (servicenow. But in general if you want to retire the CI based on certain conditions like if account is inactive then retire all the CI related to that account, in that case you will have to writedown the After update BR on account table and search for accounts CI after that change Best practice is to retire the CI, because you want to keep the relation with the incidents, changes or other tasks as history. CMDB Data Manager works with batches of 1000 CIs which is set using the system property glide. The general intent of this field is to indicate the last time it was known to exist on your network. dependent. Partner Grow your business with promotions, news, and marketing tools for partners. Well this entirely depends on what you decide to retire as some use cmdb_ci_rel and others use reference to link them. ServiceNow Learn more about ServiceNow products and Discovered Items on retire Options. For info the Dependent CI retirement is managed by 2 jobs : - CMDB Cascade Retire Dependent CIs (which fill in the ledger) Step 1: Follow all the steps provided for CI dependent management ( refer servicenow docs) Step 2: Execute the scheduled job : CMDB Cascade Retire Dependent CIs] This KB demonstrate how to create a CMDB Remediation rule to automatically run Remediation and close the task (stale_ci_remediation) I have a requirement to Retire thousand Cis that is already outdated. Its retiring the CIs if the child or parents has been updated in the last 7 days but I also need to retire the CI if it hasn’t got any relationships and hasn’t been updated in the last 7 days. Does anybody have experience with policies for this table? What are typical ages to retire or archive a computer? I know it all depends on each organization, but is there a typical age, or what are the considerations to arrive I have a requirement to Retire thousand Cis that is already outdated. How should the relationships with that CI be handled when it is retired in the ServiceNow CMDB? This article advices on the best course of action, including whether to remove or maintain the relationships as-is. We want to use it, but obviously if there are downsides to the Hi, We currently set the Operational status of a CI to 'Retired' if it isn't discovered for more than 7 days using a CMDB data policy rule. How to maintain the data for audit purpose. I created a Flow Designer, after approver approves it will go to the Look up records Hello All, We are in process of Retiring 10,000+ records in Net gear (cmdb_ci_ip_switch) and also delete all relationships if the CI name is matching as parent or child. It is not recommended that you delete relationships though, check your Data Retention policy before you delete things. //Casper Documentation Find detailed info about ServiceNow products, apps, features, and releases. Good Afternoon, What is the best practices when it comes to retiring a CI, I am having trouble wrapping my mind around this. Any inputs with best practices if anyone worked on similar case to ServiceNow Learn more about ServiceNow while keeping the hardware status/asset status unchanged until the CI owner can verify the need for retirement or address the issue with discovery. For releases prior to London it is recommended you create a Business Rule to remove Software Installation records upon install_status change to Retired. It seems that when you retire a device CI, the subcomponents do not automatically retire as well. Instead we can run a Business Rule that sets the state of the CI to "Retired" on decommission. Hi, Interesting. Here is a deeper look at one of the central features This article describes how to update a CIs (Configuration Items) Status to "Retired or Installed" in the ServiceNow CMDB, personalized recommended columns list, and basic filtering to find CIs for your department or organization. compliance best practices ServiceNow Learn more about ServiceNow products and solutions. For example, once a server is repurposed, mark the old CI as We have an ask to delete or retire asset records for virtual machines that have been accidentally created over some time. I have been trying to use the CMDB Data Manager to configure the retirement of CIs and also dependent CIs. According to the Retire a versioned article documentation: In addition to the knowledge administrator and the knowledge manager, the following users can retire a versioned article: knowledge owner latest Additionally, CIs can be referenced in Incidents/Change Requests/etc records; once CI is deleted, CI field in these records will be zeroed as well. It also says "Number of days since CIs were last discovered by a discovery source" so a bit of mixed signals here. I want to retire server-related objects with the dependency type "[Runs]" when CI gets retired. I know you can "delete asset only" from list view, but this is impractical for this many assets. Does anybody have experience with policies for this table? What are typical ages to retire or archive a computer? I know it all depends on each organization, but is there a typical age, or what are the considerations to arrive Documentation Find detailed information about ServiceNow products, apps, features, and releases. For this test I'm trying to update the Once a CI is retired (or the Application Service that depended on it is retired), this typically starts the retention schedule. Hope this helps. Documentation Find detailed information about ServiceNow products, apps, features, and releases. In overall I would recommend deleting only if this is absolutely required and all the risks are accepted. You might want a scheduled job to do some checking to see if the CI has been discovered/updated in the past 30 days or perhaps just a report would be useful so you can review it. when the task is created for ci retire it via flow. Here is a deeper look at one of the central features Loading Loading We usually see why this is a stale CI. My client is using San Diego and I'm trying to find the retire asset workflow for them to review and hopefully use, instead of creating a custom workflow. ** Implement a process to retire or archive CIs when a server is reused. You have a parent CI, say a Server - and this has been CMDB Data Manager introduced in the Rome release, provides a way of targeting CIs for retirement, archive and deletion using a policy-based approach. The Devvies 2025 are here! Celebrate your hard work and innovation by submitting your apps today. I want to retire and inactive all the article present in one knowledge base. For example: 1) If this CI is created by Discovery then we see if there is any change done on this CI on network or do we have any error's for this CI while discovering it. g. Process followed in oob--to maintain the Retired and Decommissioned Ci and CI relationships . A business rule only runs when the record is updated, so if a CI hasn't been updated, the CI doesn't run. To retire a CI you must have operational plan on using operational_status and install_status from cmdb_ci table. Unless the CI record is added to the exclusion list in Data Manager, the next time a Retire policy is executed the CI will show up in the task generated. When user select the CI/CIs then it will ask for approval and then the operational status of the selected CIs will set as Retired. When looking at this code, the following functions update state fields 'operation_status' and 'install_status': A business rule only runs when the record is updated, so if a CI hasn't been updated, the CI doesn't run. For example for server CIs. However i don't want to inactive the knowledge To auto-update multiple layers of a CI, you could research Dependent CI management which can cascade-retire or cascade-delete based on the CMDB Data Manager policies. Join the excitement! Documentation Find detailed info about ServiceNow products, apps, features, There are a couple of things you could do, but it all depends on how it is exactly working within your company. Partner Grow your ServiceNow Learn more about ServiceNow products and solutions. Update third party tool with information about created / updated or retired CI using second Change task So the change will have two change tasks: 1. Anyway, I would try to delete all the updates from your old source for a CI in the cmdb_multisource_data table and see if the CI disappears from the metric. For more information about a particular endpoint, click on it in the left pane to view a description of the endpoint, applicable query parameters, a sample request in multiple formats, and a sample response Documentation Find detailed info about ServiceNow products, apps, features, and releases. You can use this to retire the CI. cmdb_ci) that will be inherited by CI child classes. Let's assumse from some reason I'd like to reuse that asset in the future to achieve such goal I chanaged status back to Intalled/Operational. 2) If this is update or created using a import set then we contact Owner's of this CI and then take actions on this. Like an IIS server that runs on a Windows server. For every virtual server, we have a CI record for: Windows Server VMware Virtual Ma Setting the install status to '7' which is retired, seems to have no impact on the cmdb_rel_ci table or the realted items under my business application. . U need to create a Fix script for this where u can write a GlideRecord query & update the required amount of CI's in Loading Loading I'm looking for a way to present a simplified report to some end users that will allow them to manage the retirement date and scheduled retirement date of some assets in alm_hardware. 5) CMDB data manager: This is the best practice method in ServiceNow for managing CI retirement, archival and deletion. CMDB Data Manager introduced in the Rome release, provides a way of targeting CIs for retirement, archive and deletion using a policy-based approach. We need to delete or retire over 4000 records without affecting the corresponding virtual server CI. gfivbr zuhg naik iisbiy vzfpm fmpj yucq ofamzw llkb ayiytun