- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-14-2026 03:40 AM - edited 05-14-2026 03:59 AM
Hi Experts,
There are many threads and explanation documentation , but opening a fresh one to understand as what would be the best way to stop discovering Non-operational / Retired servers from cloud.
We have discovery in place but
This consumes license and hence need to restrict .
Is scripting needed here to avoid insert of new CI (retired) or in CI CLASS MANAGER the identification rule resolved this problem.
New to RTE so if anyone can suggest
Thanks
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 weeks ago
@Nisha30 IRE Data Source rule for vmis and for source 'SG Azure' and checkbox 'Insert not allowed' => no vmis will be created via 'SG Azure' => from my understanding not what you want
Before BR on insert with condition
'Discovery Source is 'SG Azure'
In the script write an if statement like:
if(install_status!=1) current.setAbortAction(true);
This should fit your needs
Kind Regards
Thomas
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 weeks ago
@Nisha30 IRE Data Source rule for vmis and for source 'SG Azure' and checkbox 'Insert not allowed' => no vmis will be created via 'SG Azure' => from my understanding not what you want
Before BR on insert with condition
'Discovery Source is 'SG Azure'
In the script write an if statement like:
if(install_status!=1) current.setAbortAction(true);
This should fit your needs
Kind Regards
Thomas
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
a week ago
Thankyou @thomasbueck was trying to avoid scripting but seems needs to be done to restrict. Have created same .