120 views

Description

Duplicate cmdb_print_queue_instance records created each time the "Windows - Printers" sensor run. 

Steps to Reproduce

 

01) Discover a windows server that has multiple Win32_TCPIPPrinterPort with same Name

Workaround

  1. Delete duplicate cmdb_print_queue_instance records
  2. Navigate to sensor discovery_sensor.do?sys_id=e2ca913b0a0a0ba5003efbc5a56431bf
  3. Update query in findPrintQueue() to use both name and addr, final function version as follows

    findPrintQueue: function(name, addr) {
    var gr = new GlideRecord("cmdb_ci_print_queue");
    gr.addQuery("ip_address", addr);
    // Following line added:
    gr.addQuery("name", name);
    gr.query();
    if (!gr.next()) {
    gr.setValue("name", name);
    gr.setValue("ip_address", addr);
    gr.insert();
    }

    return gr.sys_id;
    }


Related Problem: PRB1340775

Seen In

SR - IRM - Advanced Risk - New York 2019 Q3
SR - IRM - GRC Profiles - Madrid 2019 Q2
SR - IRM - GRC Workbench - New York 2019 Q3
SR - IRM - Risk Management - New York 2019 Q3
SR - IRM - SIG Assessment Legacy - Madrid 2019 Q1
SR - IRM - SIG Questionnaire - New York 2019 Q3
SR - IRM - Vendor Risk Management - Madrid 2019 Q1
SR - ITOM - Discovery and Service Mapping - 201908
SR - ITOM - Discovery and Service Mapping - v1.0.35
SR - ITOM - Fundamentals Istanbul Jakarta Kingston r1 - v5.99.6

Fixed In

Orlando

Associated Community Threads

There is no data to report.

Article Information

Last Updated:2020-11-16 09:54:00
Published:2019-04-29