# November 20, 2023 – ConnectWise PSA Assets and Documentation Synchronization and Configurations, DHCP Requests Discovery, and Serial Number Inventory. We have exciting new features, custom scripts, pre-configured SNMP templates, and improvements available on Domotz. This month’s exciting new updates include the improved integration with ConnectWise PSA platforms (both in terms of Tickets and Configurations), a discovery mechanism based on DHCP listener, faster access to Serial Numbers through the Inventory Dashboard, Microsoft Exchange monitoring, Dell iDRAC additional data and more. **Here’s what’s new and improved on Domotz this month.** We are always improving Domotz and welcome your feedback. Please contact our support team at [support@domotz.com](mailto:support@domotz.com) for help or suggestions. ## **New features** ### Assets and Documentation Synchronization with ConnectWise PSA Firstly, we introduced a new integration with ConnectWise PSA, expanding its compatibility just like with IT-Glue, Syncro, and other leading platforms (Hudu, Halo PSA, Liongard, IT Portal, CloudRadial, etc). With this integration, you can synchronize your discovered assets within Domotz with the "Configurations" in ConnectWise PSA. The integration ensures a seamless two-way synchronization, allowing critical data such as MAC Address, Serial Number, IP Address, Notes, Location, Room, Device Model, Device Vendor, and more to remain in sync between Domotz and ConnectWise PSA. Matching Domotz and ConnectWise PSA Fields 1. In the "Match Fields" section, you can align properties between Domotz and ConnectWise PSA. 2. For each property, select the desired synchronization direction: "Domotz to ConnectWise" or the reverse. 3. The table lists Domotz Fields like Name, Type, Make, Model, Current Status, MAC Address, and IP Address. 4. Each field is matched to a corresponding ConnectWise PSA Field, such as Name, Type, Manufacturer, Model Number, Status, Mac Address, and IP Address. 5. Use the toggle switches to enable or disable synchronization for each field. A green switch indicates synchronization is enabled, while a pink switch indicates it is disabled. Furthermore, this feature automatically creates "Configurations" in ConnectWise PSA whenever new devices are discovered through Domotz scans. This synchronization ensures that Managed and Technology Service Providers leveraging ConnectWise PSA always have an up-to-date and comprehensive asset list within their platform. Please refer to the [ConnectWise PSA Integration User Guide](https://help.domotz.com/integrations/connectwise-psa-documentation/) for more detailed information. ### **ConnectWise PSA Tickets Linked to Configurations** Additionally, we released an enhancement to the integration with ConnectWise PSA. When alerts are raised in Domotz that generate tickets in ConnectWise PSA, these tickets are automatically linked to the corresponding configurations. This association between tickets and configurations allows a more cohesive and organized workflow within ConnectWise PSA. By linking the tickets directly to configurations, Managed Service Providers (MSPs) and Technology Service Providers (TSPs) can efficiently manage and track issues, ensuring that relevant alerts and resolutions are accurately tied to the specific configurations within ConnectWise PSA. This will also help streamline the billing process through the ConnectWise PSA platform, giving the accounting department visibility of the "Configurations" that had tickets created and managed through the Domotz integration. This new mechanism can be configured in the ConnectWise PSA - Ticketing system configuration panel: Connect ConnectWise PSA Account Settings 1. Enter the "Company Login" information. 2. Provide the "Manage Site" URL. Make sure it is the correct API endpoint. 3. Input the "Public Key" required for API access. 4. Enter the "Private Key" for authentication. 5. Select the option to open tickets in a specific service by choosing from the "Domotz is opening tickets in" dropdown. 6. Enable "Automatically close tickets, if possible" by checking the appropriate box. 7. Ensure "Try to link ConnectWise Configurations to tickets" is checked to facilitate automatic linking. 8. Set the "Closed Ticket status" by selecting from available options. 9. Use "Filter your companies based on" to apply company-specific filters. When configuring the integration between Domotz and ConnectWise PSA for the ticketing system part, selecting the “Try to link ConnectWise Configurations to tickets” option will prompt Domotz to attempt linking the ticket to the ConnectWise Configuration based on matching criteria such as Serial Number, MAC Address, or IP Address between Domotz devices and ConnectWise Configurations (Assets). For more details, refer to the [ConnectWise PSA User Guide](https://help.domotz.com/integrations/connectwise-psa/). ### Serial Number in the Inventory Dashboard Inventory Management Interface Highlighting Serial Numbers. 1. Navigate to the "Inventory" section under "Sites Explorer" from the left-hand menu. 2. The main table displays device details such as Site, Device Name, Status, Type, Make/Model, IP, MAC Address, Serial Number, Location/Zone, and Tags. 3. The "Serial Number" column is emphasized, showing unique identifiers for each device. 4. Use the filter option above the Serial Number column to search or sort devices by their serial numbers. 5. This can be useful for identifying and managing specific devices quickly within the list. We are thrilled to introduce the inclusion of Serial Number information directly into the Inventory Dashboard. This enhancement is part of our ongoing efforts to provide you with comprehensive device information at a glance. This addition allows you to conveniently search and categorize devices based on your respective Serial Numbers. The Serial Number info is retrieved automatically by Domotz through various protocols (SNMP, UPnP, Bonjour, Telnet/SSH, etc.). It can also be synchronized with external platforms like ConnectWise PSA, IT Glue, Syncro, Hudu, and more. Additionally, you have the flexibility to edit the Serial Number manually. Quickly view and manage the Serial Numbers across all monitored networks within the Inventory Dashboard, providing a comprehensive overview of your device landscape. ### DHCP Discovery Last but not least, we are glad to introduce a DHCP discovery mechanism that identifies physical devices attempting to connect to the network via DHCP requests. This feature detects devices even if they fail to receive or utilize an IP address assigned by the DHCP server. Devices discovered through this mechanism will be listed in the device list with their MAC address. Due to their nature, these devices will not display an IP address. This capability is now enabled by default on all new Agents and can be managed via the 'Device Auto-Discovery' menu in the Device List. You have control over turning this feature on or off. Device List and Auto Discovery Settings 1. In the "Device List" section, view a list of network devices, including their names, online status, and IP addresses. Examples include "CloudFlare," "Primary WAN Connection," and "API - Domotz." 2. Filter devices using text input or predefined filters like "All Devices" and "Online" status. 3. Access "Manage Devices and Subnets" options on the right, such as "Add Dummy Devices" and "Configure VLAN." 4. In "Monitoring Settings," ensure "Device Auto Discovery" is active to automatically detect devices on the network. Use the toggle to enable or disable this feature. 5. Check additional monitoring settings like "Device Blacklist" and "Device RTD" for managing and monitoring network devices. Enabling Device Discovery via DHCP in Domotz 1. Navigate to the "Device Auto Discovery" section in Domotz. 2. Locate the toggle switch labeled "Device Discovery via DHCP." 3. Ensure the toggle switch is set to "Active" to enable the feature. 4. Enabling this option allows Domotz to monitor DHCP requests and identify devices attempting to request an IP address. Additionally, Domotz will provide insights into the number of DHCP requests per hour to indicate network performance. This feature is currently in Beta Testing. Interested in trying it out? Contact support for access: support@domotz.com. For more information, users can refer to the [user guide](https://help.domotz.com/monitoring-management/automated-discovery-inventory/#6). ## **New Custom Scripts** You can use the custom scripts to monitor and manage network-connected devices, cloud services, and web applications. By using standard network protocols, these scripts will allow you to retrieve valuable data and execute actions on the monitored devices and services. This month, we released the following: - MS Exchange on-prem monitoring (series) - General Stats - Database Fault Rate - Database Stats - RPC Average Latency - LDAP Read Time and Search Time - Current Connections - Message Queued for Delivery - Dell iDrac PSU Monitoring ### MS Exchange on-prem monitoring (series) With this script, you will be able to monitor the following: - OWA (Outlook on the Web) – User Count - OWA (Outlook on the Web) – Requests/s - Availability Service – Requests/s - MapiHttp Esmsdb – User Count - Autodiscover – Requests/s _[Image: MS exchange general stats]_ ### Ms Exchange - Database Fault Rate With this script, you will be able to monitor the database fault rate and statistics on the following components: - Edgetransport - Information store - Information store – exdb1 - Information store – exdb2 _[Image: MS exchange fault rate information]_ ### Ms Exchange - RPC Average Latency With this script, you will be able to monitor the RPC Average Latency on the following components: - Total - Exdb1 - Exdb2 MS Exchange Server Status and Latency Overview 1. The MS Exchange server is shown as "online" with a specific IP address. 2. The status of the server is "RUNNING" with a sample period of 15 minutes. The metrics consumed are listed as 0. 3. A section titled "Variables" displays a table with columns for Name, Value, and Last change. 4. The table lists variables such as "_total", "exdb1", and "exdb2", all with a value of 0 and a last change time of "a minute ago." 5. An option to download the data as a CSV file is available. ### Ms Exchange - LDAP Read and Search Time With this script, you will be able to monitor the LDAP read and search time on your DCs: _[Image: MS Exchange custom scripts ]_ ### Ms Exchange - Current Connections With this script, you will be able to monitor the connection count on the following components: - Total - Default Website - Exchange Backend Monitoring Microsoft Exchange Current Connections 1. The status of Microsoft Exchange is "RUNNING" and it is online. 2. The sample period for monitoring is set to 5 minutes. 3. Metrics consumed are currently at zero. 4. Under the "Variables" section, three entries are listed: - "_total" with a value of 12, last changed 2 minutes ago. - "default web site" with a value of 0, last changed 2 minutes ago. - "exchange back end" with a value of 12, last changed 2 minutes ago. ### Ms Exchange - Messages Queued for Delivery With this script, you will be able to monitor the message queue for delivery based on their priority: - Total - Hi Priority - Low Priority - None Priority - Normal Priority - Total - Excluding Priority None Monitoring MS Exchange Message Queue 1. The server is labeled as "MS Exchange" with an "online" status indicated by a green icon. 2. The section "MS Exchange Messages Queued" has a status labeled as "RUNNING." It shows a sample period link labeled "5 Minutes" and "Metrics Consumed: 0." 3. Below, a table titled "Variables" lists different message priorities under the "Name" column, including _total, high priority, low priority, none priority, normal priority, and total excluding priority n. 4. Each priority level in the "Value" column shows "0 message." 5. The "Last change" column states all entries were updated "6 minutes ago." ### Dell iDrac PSU Monitoring This script allows you to monitor the Power Supply Units on a Dell Server equipped with Dell iDrac. You will be able to gain insights on the following data: - Power Supply Description - Primary Status - Total Output Power - Input Voltage - Redundancy Status - Part Number - Model - Manufacturer Dell iDRAC Power Supply Status Overview 1. The screen displays the status of a Dell iDRAC Power Supply Unit. 2. The system's status is labeled as "RUNNING." 3. The sample period is noted as "5 Minutes." 4. Metrics consumed are marked as "16." 5. Under "PSU Info," details are given for two power supply units: - For "psu.slot.1," the description is "Power Supply 1," with a primary status of "OK," total output power of "750 W," and input voltage of "122 V." - For "psu.slot.2," the description is "Power Supply 2," with a primary status of "Unknown," total output power of "0 W," and input voltage of "0 V." 6. There is an option to "Download CSV" for data export. Dell iDRAC Power Supply Unit Status and Information 1. The identifier "idrac-2Z46WW1" and the status "online" indicate the server is operational, with an IP address partially visible. 2. The Power Supply Unit (PSU) status shows "RUNNING," indicating normal operation. The sample period is set to 5 minutes, with 16 metrics consumed. 3. Under "PSU Info," key details include: - Input Voltage: Shows 122 V for the first entry and 0 V for the second. - Redundancy Status: Displays "Unknown" for both entries. - Part Number: First entry shown as "06W2PWA00"; second entry is blank. - Model: Displays "PWR SPLY,750..." for the first entry; second is blank. - Manufacturer: Listed as "Dell" for the first entry; second is blank. 4. There is an option to download the information as a CSV file for further analysis. ## **New SNMP templates** ### Cisco  - CPU and Memory Utilization With this SNMP template, you will be able to monitor a Cisco appliance's CPU and Memory usage: Cisco CPU and Memory Utilization Overview 1. The section displays CPU and memory usage statistics for Cisco devices. 2. "CPU Usage" shows a current usage of 9%, with indicators suggesting performance trends or alerts. 3. "Memory Usage" indicates 68% usage, accompanied by similar indicators for trend analysis or alerts. 4. Use these metrics to monitor device performance and set alerts for specific thresholds if needed. ### Cisco - Power Supply (CISCO-ENTITY-FRU-CONTROL-MIB) With this SNMP template, you will be able to monitor a Cisco appliance Power Supplies, which rely on the CISCO-ENTITY-FRU-CONTROL-MIB mib: FRU PSU Status Table Overview 1. The table displays three columns: "PSU Index," "Administrative," and "Operational Status." 2. Each column header includes a sorting option and filter dropdown set to "All." 3. Under "PSU Index," entries "470" and "471" are listed. 4. In the "Administrative" and "Operational Status" columns, the status for both entries is "on." 5. A "Download CSV" option is available in the upper right corner for exporting the data. ### Cisco - Fan (CISCO-ENTITY-FRU-CONTROL-MIB) With this SNMP template, you will be able to monitor a Cisco appliance Fan, which relies on the CISCO-ENTITY-FRU-CONTROL-MIB mib: FRU Fan Status Dashboard 1. The dashboard displays a table with two columns: "Fan Index" and "Operational Status." 2. Under "Fan Index," numbers like 534, 539, and 540 are listed. 3. Corresponding to each fan index number, the "Operational Status" shows the status as "up." 4. Above the table, there are dropdown menus labeled "All" for filtering both "Fan Index" and "Operational Status." 5. A "Download CSV" link is available at the top-right corner for exporting the table data. ## **Improvements** **Retry Action for External Services Failure** You can now retry connecting to Meraki Cloud and Unifi Controllers in case of a connection is marked as "failed". With this functionality, you can initiate a retry action for failed connections without reconfiguring the settings from scratch. Users can easily re-establish connections to these external services when the failure is temporary. This is one of the most important benefits of this feature. Troubleshooting Connection Issues with Ubiquiti Unifi Controller 1. Navigate to the "Devices External Services" section, which allows you to manage available systems on the network. 2. Look for the section titled "Ubiquiti Unifi Controller." 3. Note the error message: "Connection failed. The integration has stopped working due to failure in communicating with the Ubiquiti Unifi Controller." 4. Disconnect Unifi Controller Sync and set it up again to resolve the issue. 5. Click on "Retry now" to attempt re-establishing the connection. 6. Review the available sites listed under "Sites" for changes. This enhancement streamlines the reconnection process and ensures smoother operations providing a quick and convenient method to rectify temporary connection issues. ### **Access to Automation and Scripts Library from Monitoring Dashboards** Entering the Monitoring Dashboard section and adding a new table, you can now directly explore the comprehensive library of scripts, including those provided by Domotz and custom-created. This new functionality allows browsing the entire collection of scripts available, facilitating the easy selection and addition of scripts to the monitoring tables. Monitoring Dashboards: Script Selection Interface 1. Navigate to the "Monitoring Dashboards" by selecting it from the menu on the left side of the interface. 2. In the "Scripts" section, browse the available script options for monitoring different devices and metrics, such as "Sophos Firewall Policies," "APC UPS - Battery Replacement Date," and "Hardware Sensors." 3. Use the search bar at the top to filter scripts by typing relevant metrics or keywords. 4. Below, expand your monitoring capabilities with additional scripts categorized under various sections like "HTTP Monitoring," "SSL Certificates," and "Physical Disks Info." 5. Each script tile provides information on the number of devices currently monitored and the protocols supported, such as SNMP or SSH/WMI. 6. Use the "Add Scripts from Library" option to enhance your dashboard with additional data and tailored monitoring solutions. Moreover, you can create new scripts directly from this section, enhancing the customization and extensibility of your monitoring setups. This improvement simplifies the process of script selection and creation. Seamlessly integrate diverse automation and scripts into your monitoring dashboards. ## **Fixes** Additionally, we’ve fixed the following issues: - Pre-configured SNMP: the issue of an incorrect Waste Toner level has been fixed. - IP Change Alert shows the same IP Address for Previous and Current IP Addresses. This issue has been fixed. - ConnectWise PSA Ticketing system integration: The company status filter was not properly used and saved. - Remote Connections requiring access to SSH handshakes were not working on some platforms hosting the Domotz Agent. - Cisco CBS-350 Missing Configuration management unlocks the option in the access manager. - The issue that was causing the UniFi integration to keep falling over with the connection has been fixed. - Incorrect device detection for HP OMEN 17 Laptop. - Domotz Box - Main interface ignored after restart (eth0 in DHCP mode). - The install first agent modal does not close automatically when the first agent is found. - Clicking on the Actions button on the monitoring dashboard should not drag the table. - Users with expired SAML certificates could not update it without disabling the configuration. - Dell EMC Switch model N2048 - Configuration Management Missing. - IT-Glue integration: Fix the following issues: - Error when attempting to create a new configuration for a device - Asset creation fails if there are bound assets deleted - Error while creating a new configuration - Error on user field mapping ## **Known limitations** - No data from the GlassWire For Business (GW4B) Application is available centrally on the Domotz Platform. However, in the next few months, we will add more and more stats about the remote endpoint into the Domotz App/WebApp. - You cannot remove the alerts for IP Conflict without removing the default custom filter for all the Agents. - There is no central repository for all the SNMP pre-configured, OS Monitoring, and Custom Integration script sensor alerts. - Downgrading the GlassWire For Business endpoint amount purchased is impossible without contacting Domotz Support. - Monitoring Dashboards are currently limited to Monitoring Tables as Widgets. - Luxul Router-based Agents do not support VPN on demand. To elaborate, we’ll add this capability as soon as Luxul’s team provides us with the required API. - You can’t configure the static IP address on the Domotz Box before configuring the Agent. - Lastly, you can’t leverage DHCP on additional VLANs on the Domotz Box. These release notes cover the changes, including Domotz Pro Cloud, Domotz Agent, and Domotz Pro App. Learn more about our software on our[ website](https://www.domotz.com/) or read our[ blog](https://blog.domotz.com/) to stay updated with modern network and IT Infrastructure monitoring and management.