What’s new this week:
Admin level custom filtering rules
It’s now possible to create filtering rules at admin level (that apply to all domains linked to that admin, including indirectly). To do this, simply use the “Admin Rules” tab and select the appropriate admin when creating the rule.
Admins also have a new “Inherited Rules” tab, where they can see (but not edit) rules that have been created by higher level admins. Domain-level users are able to see, but not edit, the rules that are applied to their mail (on the “Admin Rules” tab). If a domain-level user opts out of using the default rules, they are opted out of using the admin rules as well.
LDAP authentication using remote username
If you have configured the LDAP mailbox sync to sync the (remote) username associated with the mailbox, then this can now be used when authenticating against an LDAP server. This is useful when your usernames and email addresses do not necessarily match, e.g. the username may be jsnow but the email address is [email protected]. Authentication will first be attempted using the mailbox entered on the log in page, and if authentication fails, then if there is a remote username set for the mailbox, authentication will be attempted using that.
Front-end / GUI:
- Resolved: fixed inconsistencies when using both the deprecated and current quarantine page (MMA-1255)
- Resolved: fixed an issue with retrying delivery on all outgoing messages matching a search (MMA-1327)
- Changed: the links to the deprecated queue & quarantine pages have been removed from the queue & quarantine pages (b3ba5f44c9).
- Changed: it is no longer possible to add a mailbox alias that has the same name as a mailbox (MMA-1298)
- Improved: the username from the LDAP mailbox sync can be used (rather than the email address) when authenticating against an LDAP server (MMA-193)
- Improved: custom filtering rules may now be applied at the admin level (MMA-535)
In addition, there’s a new GA Agent for Windows, v10.8.10. It means the improvements provided with 10.8.9 RC are now available for rolling out across customers, together with an update to better detect user activity when agents are uninstalled directly on the endpoint. We’re also pleased to release a new RC Agent, v10.9.1, with support for upcoming enhancements to Remote Background Management.
The new agents will be released to the RMM territories in the next few days.
Summary for Service Release
– Patch Management engine upgrade, new Windows agents
– Dashboard v2019.05.22
– Windows Agent 10.8.8 GA, 10.9.1 RC
BUGFIX: Solve issue preventing bulk adding tasks to Mac workstations
Agent 10.9.1 RC
UPDATE: Support for Remote Background enhancements (future feature update)
Agent 10.8.10 GA
UPDATE: Improved end-user detection for manual agent uninstalls
Windows Agent 10.8.10 includes the updates since the current production Agent v10.8.8:
Agent v10.8.9 Release Candidate
UPDATE: Ensure disabling TLS 1.0 and 1.1 has no adverse effect on agent communication
UPDATE: Ensure default agent branding is up to date
What’s new this week:
Addition of Admin Aliases for login
A new page has been added “Manage Admin Aliases”. This page is used to configure multiple user/password credentials to log in as the same admin. For example, if you have three users that manage the same set of domains, then you can create an admin alias for each of them, rather than sharing the same set of admin credentials.
When an admin alias is used to log in, the user has the same permissions as the primary admin. You can see in the top bar the name of the main admin, and actions taken by the user will be logged against the admin alias for auditing purposes.
- Resolved: under some circumstances the archiving soft-quota warning message would fail to be sent (MMA-1282)
- Resolved: in some cases, the ‘welcome’ message for automatic Email Scout Reports would not be sent (MMA-1241)
Front-end / GUI:
- Resolved: fixed an issue where archive message content searching could incorrect return no results (MMA-1248)
- Resolved: when using OAuth/OpenID Connect, the user’s language selection would not always be applied correctly (MMA-1287)
- Improved: the LDAP authentication method now works when the authenticating email address is at a domain alias, rather than the primary domain (MMA-1289)
- Added: an admin may be added as alias, having all permissions of the parent admin (MMA-194, MMA-959)
· We’ve added an option that allows you to restore a deleted service item. This should help with those instances where you didn’t really want to delete a service item, but mark it inactive instead.
We’ve also fixed the following issues:
· Asset not exporting from N-central to MSP Manager with a 400 error.
· Slow Customers selector in access groups.
· Rate names not being updated for Hour Retainer/Flat Fee
· Error importing N-central customer to MSP Manager
· Company dashboard not updating
· Recurring Ticket Schedule creating multiple tickets
· SLA report showing breached tickets for some that are not breached
· Error occurring when editing a customer program level
· Xero exporting whole quantities rather than fractions of hour
· Hours worked rounding displaying excessive decimal places
· Ticket created near midnight appears in next month’s billing batch
· Can’t export customer to QBD if a deleted customer with the same name exists
· Ticket export timeout
· Ticket export not respecting filter settings
· User within access group can see all contacts
· Failure when closing tickets created by RMM outage
· Unable to add customer contact as “cc” to a ticket
We’re always grateful for your feedback, so let us know how we’re doing, and keep the ideas coming! [email protected]
We’re delighted to introduce our latest release for Solarwinds Take Control: 7.00.06
In this release, we have the pleasure of not only introducing our latest feature, Take Control Mobile, we have also lined up a series of enhancements to our Secrets Vaults tool, showcasing several Admin Area usability enhancements.
All the details…
We’re pleased to let you know that this week’s RMM release introduces a new ‘Added and Deleted Devices’ report, making it easier to see which devices are being added and removed in a single overview. It now also shows who the logged-in user was when the RMM agent was uninstalled on the endpoint (requires latest v10.9.0 RC agent). In addition, the release contains an update to Managed Antivirus Bitdefender with improvements to the Site Concentrator and file downloads.
The new report is currently available in the English speaking regions, and will be enabled next week for our partners in the non-English territories.
A new ‘Added and Deleted Devices’ report
Last week we introduced a new ‘Deleted Devices’ alert, a much-requested feature that gives you the option to receive a notification when the RMM monitoring agent is removed directly on the endpoint. This week, we’re following this up with a new ‘Added and Deleted Devices’ report, to make it easier to see device additions and removals Continue reading
What’s new this week:
Option to require delivery using TLS
The normal behavior for mail delivery is that a secure (TLS) connection is established whenever both the sending and receiving servers support it; all our servers support TLS, so a TLS connection will be used as long as the server on the other side has support. If a secure connection is required (ie. if one cannot be established delivery should fail) then the best way to handle this is to use DANE. However, DANE cannot require a TLS connection only for specific mailboxes, and can be complicated to configure, as it requires DNSSEC.
This release adds a new option to address these limitations. The incoming “Filter settings” page has a new “Require TLS settings” section, where you can configure requirements for a TLS connection for mail from senders to the filtering servers, and/or for mail from the filtering servers to your destination servers.
If you have specific requirements, you may either require that all mail for the domain is transmitted over a TLS connection, or that mail for specific recipients or from specific senders must be transmitted over a TLS connection. Note that doing so introduces the risk that some servers will no longer be able to send mail to your mailboxes in case of TLS issues.
Front-end / GUI:
- Resolved: fixed an issue that could prevent the bandwidth overview working correctly (MMA-1281)
- Changed: the ability to see the history of failed delivery attempts, which was removed in the 20190416 build, has been restored.
- Added: the incoming filter settings page now includes the option to require use of TLS (MMA-330)