CMDB Simulator Task 09: Configure Reconciliation Rule

[MGHandy]

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.

 

[MGHandy]

@Maik Skoddow Thank you for the attempt at helping I do appreciate it, what you gave was mostly correct I found out what was wrong.

I had someone from work help me out and it turned out to be as simple as I thought it was. He told me to take out the filters and it worked.

He explained that the order alone should take care of it without the need for filters. It was the one thing I thought of but didn't actually try because I was overthinking it and thought it would require filters.

I left it as ServiceNow > Priority 100 and LANDesk > Priority 200 with no filters.

[JanWinther]

Hi @MGHandy,

I faced the same struggle, and in the end came up with this, which passed validation:

The rule has no conditions, and applies to all fields. It works as intended, but I will say that the task is at best extremely poorly worded.

[Joao Ortiz]

Thank you so much!
The wording for this task is just...bananas.

- 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

What???
We just need to add a reconciliation rule that:

• has 2 discovery sources (servicenow =100; LandDesk = 200), and
• apply to all attributes

That's it.

[YashKumarV]

Thanks for the solution. I have one doubt: in this case, how is it determined that the ServiceNow discovery source will not be updated by the LANDesk discovery source?

[cdlopez]

Hi @JanWinther 

Thank you for sharing the solution. It worked.