You can configure Patch Cleanup Settings, which will automatically remove superseded/unused patches from the patch repository.

It is recommended to use "Test and Approve" feature, which can test the patches on lab machine and then approve it automatically before deployment. We also have patch removal/roll back option, which can be used to handle these situations.

We do not have an option to schedule the reboot, however, you can customize the deployment to a specific time interval and configure a reboot to meet your requirement.

You can create a separate "Deployment Policy" for such requirements and get them deployed automatically.

It depends on the number of computers. Usually in an enterprise, it is done at least once in a week using Automated Patch Deployment (APD) task.

Managed computers can use regular user accounts, since the agent is running in the system account it would have the privilege to install the patches.

RMM will automatically detect the language based on the operating system.

RMM will retry to install the patch during the subsequent deployment window and the installation status would be updated.

It is about testing the patches before deployment. You can choose to approve the patches automatically or manually. We also have the feasibility to test the patches before approving them automatically. The tested patches can be approved automatically after a specified number of days if no failures are found. Alternatively, you can manually approve it based on the result.

RMM will allow you to automate the complete process. You can create an APD task, which will automatically scan computers, detect missing patches, automatically download the required patches and deploy it to the target computers. You can configure "Patch Clean up settings", to delete the unwanted patches automatically.

Yes, you can. You can target machines based on system type such as laptops and desktops. You can also create a custom group with system type as criteria.

You can create separate APD task for scanning and downloading the patches. You will find different options such as scan, download, draft and deploy. You can choose any of them based on your requirements.

You can configure notification settings for the APD task which can send you the status report multiple times based on the different status including scanning, downloading and deployment of patches Yes, RMM supports them.

RMM maintains a single patch store for all the patches, including Windows, Mac Linux and 3rd party patches. You can customize it from Patch Mgmt -> Downloaded Patches -> Settings -> Download Settings.

Deployment Policy can be used to schedule the patch and reboot/shutdown. However, if you want to shut down after reboot, you can use the remote shutdown/reboot tool to perform this operation.

Patch database will be synchronized automatically as per built-in-scheduler Patch Mgmt -> Patch Database Settings -> Enable Schedule. You can verify the latest sync time from, Patch Mgmt -> Update Vulnerability DB -> last updated time. However, you can sync it manually, using “sync now” option.

You can disable auto-updates from WSUS and install RMM agent on the computers to be managed, scan the computers and start deploying the patches.

Yes, you can pull local agent logs from remote computers and upload it to support for analysis from, Support -> Create Support File.

You can create a custom group and test the patches before deploying them to all computers in the company using the "Test and deploy" feature.

JRE update from 1.7 to 1.8 is considered as an upgrade and not as an update, which means, both the versions can co-exist. You can use software deployment to install JRE 1.8 and uninstall JRE 1.7.

You can customize the count of computers displayed. The changes you make will persist only for the technician and the view.

You can achieve this by using the “deploy immediately option”, whenever you deploy a patch configuration. This will wake up the target computer on-demand, to perform the task initiated by RMM.

You can view the status of the “Automate Patch Deployment Task” from, Patch Mgmt -> Automated Patch Deployment Tasks. You can also generate reports of these tasks and schedule it.

You can deploy definition updates using RMM from, Patch Mgmt -> Automate Patch Deployment -> Schedule Anti-Virus Task.

You can create a dynamic custom group and choose to decline the patches for a specific application like JRE. By doing this, you can maintain multiple versions of the JRE in your network.

Refer to this article to find the list of domains, which need to be excluded.

Automated patch tasks are not regular configurations. You can view the status of the "Automate Patch Deployment Task -> System View". You can also configure the notification settings, Patch Mgmt -> Automate Patch Deployment -> Notification Settings, to receive email updates, whenever there is any change in the status of the task.

This can be achieved by configuring the deployment policy and excluding servers from reboot, Patch Mgmt -> Deployment Policies -> Create Deployment Policy ->Deployment Window -> Reboot Policy -> Exclude Servers from Reboot.

This can be achieved by configuring the deployment to happen after the encryption time window. You can configure it from, Patch Mgmt -> Deployment Policies -> Create Deployment Policy -> Deployment Window.

You can wake up the computers and deploy the patches by configuring, Patch Mgmt -> Deployment Policies -> Create Deployment Policy -> Turn on computers before deployment.

“Mark As” - option, will be available only when you choose to approve patches. Manually, Patch Mgmt-> Settings -> Approval settings - > Approve Patches -> Manually. If you have chosen to approve all patches automatically, all the patches will be marked as approved by default.

Both Windows 10 and Microsoft Office 2016 are supported by RMM. You should ensure that your Patch Database is successfully synchronized in the recent past. Verify it from, Patch Mgmt -> Update Vulnerability DB -> Last update time.

ANSWER

You can, create a report from, Patch Mgmt -> All Patches -> Missing Patches Tab -> Computer View and create a filter based on the “Release Date”

You can use the File Folder operations, configuration, software deployment, custom script configuration to update the definition updates and engine upgrades. We are also looking into the possibility of including this in the Patch Management section.

It is currently not available in cloud. However, we are looking at cloud based solution.

Yes, when you create an APD task, under scheduler select the monthly option and choose 3rd Sunday.

Dynamic custom groups are evaluated on the client side during deployment based on the criteria you have defined.

The new UI is developed based on the usage. When you have more number of computers, you can move it to a group or an OU and add them as target.

Yes, under Patch Mgmt->Disable Automatic Updates, choose templates and disable.

You might need to create 2 separate APD tasks as below to achieve this:

• Create the first task to just scan the computers and schedule this at 10 AM. This will complete by 12 noon and you will get the list of missing patches, which you can choose and approve.
• Create a second task scheduled to run at 3PM (assuming that you would approve the patches by then). For this task, define a Deployment policy with o Deployment Window with start and end times as required, say start at 8 PM o Select this option “Download Patches/Software during subsequent Refresh Cycle”.The second task will start at 3 PM and scan the computers again and download the necessary patches to the agents. Assuming that all the target computers are up, this will complete and keep things ready for deployment by 6 PM. The deployment will begin at the scheduled deployment window, 8 PM.

When these computers connect to the network via VPN, the deployment will be initiated during the next refresh cycle (90 minutes).

Yes, Ubuntu flavors are supported. The update will be made available next month for existing users.

Yes, most patches that have a download URL will be supported.

We usually support within 24 hours.

This is a feature pack; not supported in patch. You can use Software Templates - > Search with Microsoft .NET Framework 4.6.1 and create package and deploy.

It depends on the number of systems and patches that are maintained, maybe up to 1 GB. It is recommended to configure patch cleanup settings to remove older patches automatically. This will also clean up the distribution server.

It will automatically be downloaded and installed.

Patch inter-dependencies and sequencing will be automatically be taken care by RMM.

No, agent should be deployed before scanning. You can define SoM Sync Policy to automatically identify new computers added to Active Directory and install agents on them.

Under Configuration Templates, we have a template to disable windows10 creep update (Disable Windows 10 Notification.)

Yes, it is technically possible if all the remote offices use the same agent and if all the remote office computers can reach the Distribution Server.

Yes, the ideal way to do this is go to the All Systems View, select the computer and install all missing patches to this computer.

No, this is not feasible as download URL to this update is not publicly available.

Yes, the agents will contact the server to post the failure messages. However, no deployment can happen.

Go to Patch Mgmt->Settings->Cleanup Settings->Settings. Against Patch Repository Location, enter the new Patch Repository's location. For example, \\machine_name\example_patch_repository