Microsoft: Exchange Server v102 PowerPack Release Notification
We are pleased to announce that the Microsoft: Exchange Server v102 PowerPack has been released. The download for this release can be found on the Support Portal under the PowerPack filename: https://support.sciencelogic.com/s/release-version/aBu0z000000XZLHCA4/microsoft-exchange-server Enhancements and Issues Addressed The following enhancements and addressed issues are included in this release: Resolved an issue to ensure continued data collection for the "Microsoft: Exchange TPS Transport Database Performance" and "Microsoft: Exchange MBS Database Performance" Dynamic Applications by adding a "- ErrorAction SilentlyContinue" flag in the PowerShell script to suppress errors. (Case: 00342636) Added the "Microsoft: Exchange Server Transport Queues" Dynamic Application to the PowerPack. Updated the PowerPack to support dcm creation so that you have the option to switch between dcm mode and discovery objects mode. Please refer to the Microsoft: Exchange Server v102 PowerPack File Details in the PowerPacks section of the Support Portal for all information pertaining to the Microsoft: Exchange Server v102 PowerPack Support Status, Minimum SL1 Version, Solution Information, and Pricing Information. The Microsoft: Exchange Server v102 PowerPack Release File Details also contains links to the Release Notes, Manual, and PowerPack Info Report. Issues Addressed in the Microsoft: Exchange Server v102 PowerPack Release can be found in the Release Notes5Views0likes0CommentsMicrosoft Teams SyncPack v2.0.0 and Microsoft Teams Automation PowerPack v200
Hello, We are pleased to announce the GA release of the Microsoft Teams v2.0.0 SyncPack and the Microsoft Teams v200 Automation PowerPack integrations for PowerFlow. These releases represent a complete re-architecture of the Teams integration and was driven by a change by Microsoft to the ways Teams works, as detailed in this blog post last fall. Essentially, Microsoft 365 Connectors have been retired, and Microsoft Power Automate was introduced as a replacement. Our new packs make use of Microsoft Power Automate. Please read the release notes and manual carefully, as we have included important details you will need to know before configuring your integration. Here are some highlights from the release notes: Updated the "Create Channel For Event" application to trigger event notification in Microsoft Teams based on the "ms_teams_webhook_url" configuration option, which is a webhook URL generated from Microsoft Teams. When acknowledging an event in Teams, the username of the user who acknowledged the event message is now displayed in SL1. When an event occurs and the event message is posted to Teams, you have three options for handling the event message: Add Note Acknowledge Resolve Added the "enable_existing_channel" configuration option to the "Create Channel For Event" application to allow event notifications to post to an existing Teams channel specified in the "channel_id" configuration option. Updated the "Delete Event From SL1" step name to "Resolve Event From SL1". The Microsoft Teams PowerPack will now create events and event notifications for both major and critical events. Removed the "Major Event Notification to MS Teams" application from the SyncPack. The PowerPack now handles both Critical and Major event notifications using the "Create Channel for Event" application. Removed the "Outage" and "Create Channel Event Notification" applications from the SyncPack. Previously, a refresh token was used to gather user information from adaptive card reactions. The refresh token was removed, and now the user ID is retrieved directly from the workflow using authentication through the Microsoft Authentication Library (MSAL). Optimized the "Microsoft Teams Power Automate" application by reducing API permissions to ensure minimal permission exposure while maintaining essential functionality. This enhancement improves security and aligns with best practices for access control. Microsoft is changing its API policy and the way to use it for adaptive cards. As a result, ScienceLogic has upgraded this SyncPack with the Microsoft authentication library, which is the new way to interact with Microsoft applications in a more authenticated process. For more information, see Microsoft's documentation on MSAL . NOTE: Group calling is not available currently with these packs. Thank you, Release Management14Views0likes0CommentsCisco: Wireless v105 Py3 PowerPack Release Notification
We are pleased to announce that the Cisco: Wireless v105 Py3 PowerPack has been released. The download for this release can be found on the Support Portal under the PowerPack filename: https://support.sciencelogic.com/s/release-version/aBu0z000000XZMBCA4/cisco-wireless Enhancements and Issues Addressed The following enhancements and addressed issues are included in this release: The PowerPack was updated for Python 3.6 compatibility. The Collector Affinity was set to Root device collector in all the Dynamic Applications. The "Cisco: WLC AP Config" Dynamic Application was updated to address an issue in which the MAC Addresses collection objects stored using a space instead of semicolon. Please refer to the Cisco: Wireless v105 Py3 PowerPack File Details in the PowerPacks section of the Support Portal for all information pertaining to the Cisco: Wireless v105 Py3 PowerPack Support Status, Minimum SL1 Version, Solution Information, and Pricing Information. The Cisco: Wireless v105 Py3 PowerPack Release File Details also contains links to the Release Notes, Manual, and PowerPack Info Report. Issues Addressed in the Cisco: Wireless v105 Py3 PowerPack Release can be found in the Release Notes11Views0likes0CommentsAzure monitoring and integration with CMDB
When gathering information from cloud stuff, or actually doing whatever with cloud staff you most often need the object's ID, that long hexastring. That same ID is also most used identifier and required information when trying to sync those cloud "devices" into ServiceNow CMDB. The issue is that SL1 Azure PP does not gather that information too much, one device class that we have so far found it is those actual VMs in cloud. But one could say that those are the only "devices" where it is easily found. So my question is, how you have planned, or done, the CMDB integration of Azure cloud stuff. Or have you done any automation from SL1 to Azure, because also there one always(?) need that object ID. I could have written also an Idea for this, but at least for me, Nexus does not support my ideas.Solved118Views1like2CommentsCisco Unified Communications Manager 14 EOL and 15 Upgrade tips slides from Cisco Live
Hello all! I'm sure some of you are at Cisco Live NAM right now, but if you aren't, there was a great presentation on CUCM. CentOS is being swapped out, CUCM 15 appears to be switching to Python 3, along with other security changes. They've announced an EOL date for CUCM 14 as well. Take a look at the slide deck as it's very interesting. Their product team also informed me that the API is unchanged from v12.5 through CUCM 15, so our integration should continue to work. Please let us know if you have any issues with the latest version of our PowerPack and CUCM 15.Solved1.4KViews2likes1CommentDell EMC: Unity v103 Py3 PowerPack Release Notification
We are pleased to announce that the Dell EMC: Unity v103 Py3 PowerPack has been released. The download for this release can be found on the Support Portal under the PowerPack filename: https://support.sciencelogic.com/s/release-version/aBu0z000000XZWoCAO/dell-emc-unity Enhancements and Issues Addressed The following enhancements and addressed issues are included in this release: Updated the PowerPack for Python 3.6-compatibility using Snippet Framework. Added the "Dell EMC: Unity Example SF" universal example credential. Removed the following "Dell EMC: Unity LUN Discovery" Dynamic Application collection objects, as the "Dell EMC: Unity LUN Config" Dynamic Application collects the same information: Current Owner Default Owner Health State LUN Size LUN Type Thin Tiering Policy Updated the Collector Affinity to assigned collector in all Dynamic Applications. Updated the "Dell EMC: Unity Classify Root Device Class" run book action so that it no longer uses the "EM7 Central Database" credential. NOTE: After you update the PowerPack to version 103, ScienceLogic recommends that you edit the "Dell EMC: Unity Classify Root Device Class" run book action to change the Snippet Credential field to None. Please refer to the Dell EMC: Unity v103 Py3 PowerPack File Details in the PowerPacks section of the Support Portal for all information pertaining to the Dell EMC: Unity v103 Py3 PowerPack Support Status, Minimum SL1 Version, Solution Information, and Pricing Information. The Dell EMC: Unity v103 Py3 PowerPack Release File Details also contains links to the Release Notes, Manual, and PowerPack Info Report. Issues Addressed in the Dell EMC: Unity v103 Py3 PowerPack Release can be found in the Release Notes10Views0likes0CommentsDatacenter Automation Utilities v201 PowerPack Release Notification
We are pleased to announce that the Datacenter Automation Utilities v201 PowerPack has been released. The download for this release can be found on the Support Portal under the PowerPack filename: https://support.sciencelogic.com/s/release-version/aBu0z000000XZiBCAW/datacenter-automation-utilities The following enhancements and addressed issues are included in version 201 of the "Datacenter Automation Utilities" PowerPack: Addressed an issue that was preventing the run book actions in this PowerPack from working properly with the SL1 agent. The updates for this issue are supported on SL1 12.3.1 or later. NOTE: If this is a new installation of this PowerPack, you will need to enable all automation policies in the PowerPack before you can use them. NOTE: The Monitoring Guide needed no update from previous v200 so v200 is included here. Please refer to the Datacenter Automation Utilities v201 PowerPack File Details in the PowerPacks section of the Support Portal for all information pertaining to the Datacenter Automation Utilities v201 PowerPack Support Status, Minimum SL1 Version, Solution Information, and Pricing Information. The Datacenter Automation Utilities v201 PowerPack Release File Details also contains links to the Release Notes, Manual, and PowerPack Info Report. Issues Addressed in the Datacenter Automation Utilities v201 PowerPack Release can be found in the Release Notes11Views1like0CommentsLinux SSH Automations v107 Py3 PowerPack Release Notification
We are pleased to announce that the Linux SSH Automations v107 Py3 PowerPack has been released. The download for this release can be found on the Support Portal under the PowerPack filename: https://support.sciencelogic.com/s/release-version/aBu0z000000XZipCAG/linux-ssh-automations Enhancements and Issues Addressed The following enhancements and addressed issues are included this release: Made updates to make the PowerPack compatible with Python 3, including updates to the libraries and execution environments for Python 3.6. The PowerPack now includes the following automation policies, and each Policy Type was updated to Active Events/User Initiated: Linux SSH: Illicit Process Remediation Linux SSH: Process Restart Remediation Linux SSH: Run CPU Diagnostic Commands Linux SSH: Run File System Diagnostic Commands Linux SSH: Run Interface Error/Discard Diagnostic Commands Linux SSH: Run Interface Utilization Diagnostic Commands Linux SSH: Run Memory/Swap Diagnostic Commands Linux SSH: Run System-Storage Diagnostic Commands NOTE: All automation policies in the PowerPack are disabled by default and must be enabled for use. NOTE: All automation policies in this PowerPack require the target device to be part of the "Linux Automation" device group. The PowerPack now includes the following run book actions: Linux CPU Diagnostic Commands Linux File System Diagnostic Commands Linux Illicit Process Remediation Linux Interface Error/Discard Diagnostic Commands Linux Interface Utilization Diagnostic Linux Memory Dmidecode Command Linux Memory/Swap Diagnostic Commands Linux Process Restart Remediation Linux System-Storage Diagnostic Commands Linux Tcpdump Command Added the following parameter to the "Execute Shell Commands" action type (version 2.2): dynamic_app_guid:Specifies the globally unique ID number (GUID) assigned to the Dynamic Application by SL1. You can specify multiple Dynamic Application IDs, separated by commas. If the credential_id parameter is not specified, SL1 will use the dynamic_app_guid parameter to determine the credential. If this value is not specified, or if it is an empty string, SL1 runs a query against the database to get the credential details. The default value for this parameter corresponds to the GUID value in the "Linux: Configuration Discovery" Dynamic Application. Enabled passwordless sudo access on the client being monitored to ensure that run book automations that use sudo in the commands work as expected. For more information, see the "Configuring Linux Devices" topic in the Linux SSH Automations PowerPack manual. Removed the write_password_after_command parameter from the "Execute Shell Commands" custom action type. Please refer to the Linux SSH Automations v107 Py3 PowerPack File Details in the PowerPacks section of the Support Portal for all information pertaining to the Linux SSH Automations v107 Py3 PowerPack Support Status, Minimum SL1 Version, Solution Information, and Pricing Information. The Linux SSH Automations v107 Py3 PowerPack Release File Details also contains links to the Release Notes, Manual, and PowerPack Info Report. Issues Addressed in the Linux SSH Automations v107 Py3 PowerPack Release can be found in the Release Notes10Views1like0CommentsJuniper Mist v100.1 PowerPack Release Notification
We are pleased to announce that the Juniper Mist v100.1 PowerPack has been released. The download for this release can be found on the Support Portal under the PowerPack filename: https://support.sciencelogic.com/s/release-version/aBuVL0000000b1B0AQ/juniper-mist The following enhancements and addressed issues are included this release for Juniper Mist: Added support for collection using a proxy to the PowerPack. For more information about using a proxy, see the Juniper: Mist manual.. Added a divide by zero check to the "Memory Utilization" presentation object in the "Mist: AP Statistics" Dynamic Application. Please refer to the Juniper Mist v100.1 PowerPack File Details in the PowerPacks section of the Support Portal for all information pertaining to the Juniper Mist v100.1 PowerPack Support Status, Minimum SL1 Version, Solution Information, and Pricing Information. The Juniper Mist v100.1 PowerPack Release File Details also contains links to the Release Notes, Manual, and PowerPack Info Report. Issues Addressed in the Juniper Mist v100.1 PowerPack Release can be found in the Release Notes14Views0likes0CommentsPossible deprecation of legacy HPE Edge Connect authentication
Hello all! We are working on an update to the HPE Edge Connect PowerPack that converts the dynamic applications to use the snippet framework. This will improve supportability, simplify troubleshooting, improve performance, and make it easier to customize the collections to suit your needs. As part of this, we are considering dropping support for "cookie" auth and requiring users to use API keys to connect SL1 to the Edge Connect Orchestrator. If you have a use case that precludes using an API key for this integration, please reach out and help us understand your parameters. Thanks!Solved30Views0likes1Comment