CMDB Identification and Reconciliation rules | CMDB IRE ServiceNow | Part 1

Поделиться
HTML-код
  • Опубликовано: 20 авг 2024

Комментарии • 19

  • @madhavanmadhan9079
    @madhavanmadhan9079 8 месяцев назад +1

    Really great video
    First time i watched about IRE. I dont knwo IRE.. Now I know crisp and clear about IRE. Hats off bro.. Thanks a lot

  • @mania7217
    @mania7217 18 дней назад

    Clear explanation 👌

  • @ipradiip572
    @ipradiip572 7 месяцев назад +1

    Excellent 🎥video for IRE. 🤗

  • @Ingles4allYou
    @Ingles4allYou 9 месяцев назад +1

    The best IRE ever. Thanks a lot

  • @sndev1400
    @sndev1400 4 месяца назад +1

    great video.

  • @user-of5er8tu9j
    @user-of5er8tu9j 8 месяцев назад +1

    very well explained thanks a lot.

  • @jaganr13
    @jaganr13 8 месяцев назад +1

    Thank you very much for making this video sir ❤

  • @ravigaur583
    @ravigaur583 8 месяцев назад +1

    Thanks a lot, very simple and clear ❤

  • @kirankumarbastawadi1367
    @kirankumarbastawadi1367 Год назад +1

    Awesome presentation 🎉

  • @kirankumarbastawadi1367
    @kirankumarbastawadi1367 Год назад +1

    Very good content 🎉

  • @kirankumarbastawadi1367
    @kirankumarbastawadi1367 Год назад +1

    Awesome 🎉

  • @galshimoni391
    @galshimoni391 14 дней назад +1

    Question regarding the reconciliation from your example: Let's say ServiceNow is updating the computer record (RAM field). Once it is updated, ServiceNow will always be the source of truth. So, aren't we getting stuck at this point? Future updates from BigFix inventory or import sets will always fail. What is the meaning of all this configuration in that case? It seems like a dead end.
    Thanks in advance.

    • @servicenow_universe
      @servicenow_universe  14 дней назад +1

      @@galshimoni391 It's not dead end. If you believe ServiceNow discovery is not a trusted source and Big Fix is the trusted source now, then just change the priority of Big Fix to less than ServiceNow. That will make Big Fix trusted source and the data from Big Fix in next run will update the CI.
      Hope this answers your question.
      Thanks 😊

    • @galshimoni391
      @galshimoni391 14 дней назад +1

      @servicenow_universe thanks 😊 🙏

  • @saivivek-ic3bq
    @saivivek-ic3bq 7 месяцев назад +1

    Thank you for the clear explanation with the examples ❤
    A small doubt that for example
    A data source has the lowest version/ram size with priority 100 & the other data source has the better version/ ram size with 200
    In this scenario which data will get updated?

    • @servicenow_universe
      @servicenow_universe  7 месяцев назад

      Data source with Lowest priority will take precedence and that will update the CI. You can watch part 2 video if you want.

    • @i.mohitchauhan
      @i.mohitchauhan 7 месяцев назад

      System will only focus on the lowest priority data source rather than what value is coming (better RAM size etc). If the data source with the lowest priority (ServiceNow - 100 in our case) has updated the RAM once then the precedence will always be with ServiceNow. System will not take value from any other source but ServiceNow only.

  • @sundharj7034
    @sundharj7034 2 месяца назад

    what if we dont want to create the new Server records