CMDB Simulator Task 09: Configure Reconciliation Rule
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-11-2022 07:03 PM
I have been working through the self-paced CMDB Fundamentals course on NowLearning, I am stuck on the Configure the CMDB Simulator (Rome) > Task 09: Configure Reconciliation Rule.
It appears i may not be understanding something simple or there just isn't enough information given (which might be rather unlikely).
The requirement states:
Being part of the Cloud Dimensions CMDB implementation team, using CI Class Manager, you are tasked to update the Windows Server class with a reconciliation rule that achieves the following:
- Windows Server record in CMDB with discovery source LANDesk CAN be updated by discovery source ServiceNow
- Windows Server record in CMDB with discovery source ServiceNow CANNOT be updated by discovery source LANDesk
I have made rules where servicenow has priority over landesk to update all attributes where discovery source is servicenow OR landesk
I have created rules where landesk has priority over servicenow to update all attributes where discover source is NOT landsek.
I have taken each bullet above literally and made a rule specifically for what each says.
I have spent a total of almost three hours on this one simple little thing coming up with rules for everything in between and including the above. nothing appears to validate correctly. I don't know what i'm missing.
Can someone help me out. I don't necessarily want the answer, just help understanding what requirements are asking.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-03-2025 05:16 PM
Rule 1: ServiceNow has priority over Landesk when the Discovery Source is ServiceNow OR Landesk.
Rule 2: Landesk has priority over ServiceNow when the Discovery Source is NOT Landesk.If both rules reference Landesk vs. NOT Landesk, there might be an overlap or unintended exclusions.Try modifying
Rule 2 to cover scenarios where Discovery Source is explicitly defined, instead of using "NOT Landesk.
Believe ServiceNow processes rules based on priority ranking. Ensure the rule you want to take precedence has a lower priority number (e.g., Rule 1: Priority 100, Rule 2: Priority 200)
I would check if any other active rules might be conflicting.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-06-2025 03:36 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-04-2025 07:36 AM
sorted this step due to CIS-FD, but clearly the wording of this step is confusing.
also, I couldn't find in the documentation exact words how to NOT allow update.. why not to include this simple example into documentation and make everyone's life easier.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
4 weeks ago
Keep both conditions in single rule.
