A forum for general discussion of any MSP topic.
Just starting a new thread for ongoing enhancements to the RMM Suite.
This is a summary of the updates released between May 1 and November 30, 2019.
The Intelligent Ticket Processing system has received quite a few enhancements and several new features:
New tools as well as enhancements to the core tool set have been deployed. Some changes took effect immediately, while others are optional and may require configuration changes.
One of the most exciting enhancements to the Daily Maintenance tool suite is the ability to respond to Zero-Day Vulnerabilities. No less than 5 of the new features directly support this capability.
We've updated several of the Smart Monitors to eliminate dependencies on external tools, improve security, or accommodate special situations.
While we build all of our tools following enterprise security methods, we're always looking for ways to improve and enhance the tools and our practices.
The WIN-Local Account - Set/Create RMM_Admin Password procedures have been enhanced to allow the MSP/IT team to define the "Friendly Name". In prior versions, this name was fixed as "MSP Admin" and was only displayed when the "simple" logon page was enabled. The name can be defined in the ALL-Set Common Data procedure.
This non-urgent update will be deployed on request or during other updates only. Contact the MSP Builder support team to have this installed.
A set of two procedures and a batch file that support offline workstation deployments and "one-click" ability to join a customer's AD domain from your office, with no direct connectivity to the customer's network. The app is part of the standard toolset and is downloaded automatically by licensed customers.
Our tool will use VSA to locate the customer's domain controller, identify the domain name, and then run a procedure on the domain controller to define the AD object and retrieve the offline-join data file. The data file is returned directly to the agent being joined to complete the process. This works on any Windows host and DC from Windows 7/Server 2008 and higher. No user input is required, allowing this to become part of an automated onboarding process.
This is a feature and can be downloaded & installed by customers from the Products/Downloads/Software page. Our professional Services team can also install it for you by request. It will automatically be part of all new RMM Suite deployments.
A new procedure, updates to ALL-Agent Onboarding - 3 - MSP Customization Tasks, and a new BMS app combine to provide a highly customizable solution for agent onboarding. Using a single, centrally managed configuration file, the tool will call Agent Procedures to perform global as well as customer-specific onboarding tasks, such as application installs, cleanups, and even domain-join operations. Configurations can be deployed to all systems or limited by server or workstation. Customer-specific tasks can be configured to replace generic tasks.
This is a feature that our Professional Services team will deploy. You must review and define the tasks in the configuration file for any automation to be performed. All new RMM Suite deployments will include this feature, and customer platforms are being updated during the next few weeks.
The RMUGET utility has been updated to bypass the applications that are actively in use, specifically the RMMKSE.EXE and RMUGET.BMS. This prevents logging errors that the files cannot be written. These files are updated prior to running the RMUGET, so attempting to update these is redundant. The log now reports these files as being skipped.
This change is automatic - no action is required.
All messages in the user interface can now be displayed in any language, selected as defined in the user's LOCALE Language setting. MSP Builder provides a sample messages file (.LNG extension) that the MSP can customize with any language. Language files will be deployed and loaded on demand - where available - when a user's LOCAL Language ID matches the ID in the file name.
This change to the interface is automatic. The MSP must define and deploy the language file(s) to support alternate languages.
The end user can now submit a standard priority support request directly from the User Interface. The dialog box prompts for the user's name, email, a summary line, and a detailed description. The ticket is submitted and processed by the Intelligent Ticket Processing system and delivered to the MSP's PSA.
This change to the interface is automatic. The MSP must enable the Ticket feature if they so choose via a simple configuration setting.
The User Interface now displays a pair of 4-digit numbers that are unique to the agent and update every 60 seconds. A separate utility, used by the MSP technician, can generate the same security code when the customer's Agent Name is entered. The MSP technician can present the security code to the end user, who can verify that it matches the code displayed on their interface. This can help prevent attacks through social engineering by verifying that the caller is actually from the MSP.
The change to the interface is automatic. The Technician Interface requires a security configuration setting to be performed by MSP Builder's support team.
A new Smart Monitor is being released that will generate Warning Alarms for all changes to User and Group security - both machine-local and in Active Directory.
The Smart Monitor is deployed automatically. The MSP Builder support team will be updating the deployment procedure and monitor set.
All Operation & Configuration guides have been updated to reflect these enhancements.
An extensive set of fixes, enhancements, and new features was released in March of 2021. All existing client platforms were updated automatically, and all new platform installs are being done with this version.
The full details of this upgrade are available on our documentation page. A summary can be found on our Product Notices library.