No, installation will not happen, only the installables will get copied to the end user's machine.

Any software that uses a valid license is termed as commercial. If a license is not required, then it is termed as non-commercial software.

Yes you can, if you know the command line arguments to install them silently.

Yes, you can configure the number of times you want to retry the configuration in case it fails to install.

This can be done using the pre-deployment activities.

It is recommended to use a Distribution server in this case. The data from the RMM Server will be replicated only once to the distribution server and this data is later internally shared to the WAN computers.

When you are creating the Packages from Software templates you need not specify the switches or arguments as they are already available in the templates. If you are creating the packages manually you should specify the silent switches/commands for silent software installation.

No, the entire set up file will not be copied and downloaded again. The download will be resumed from where it ended.

In Self Service portal there is setting to publish all the non-commercial software to "All computer group" for self deployment. Thus the software which are marked as non-commercial will get published to the "All computer group".

For computer configuration under install/uninstall software there is an option "Allow User to interact with the Installation/Uninstallation Window". On enabling this option user will be prompted for installation. Ensure that you do not give any silent switch while creating the EXE package for this option to work.

While adding MSI packages enable the option "Enable Logging for troubleshooting" to enable extra logging for troubleshooting.

If you are using a Distribution File System (DFS) as Network share replication is automatically taken care to local servers in the Remote office.

Yes. If you provide the same location for both the Network share and the HTTP repository, then the Template applications will get downloaded to the same location.

You can choose to clone the configuration with/without the target, and re-use the configuration for deployment. If you would like deploy this configuration only to a specific number of computers, you can also choose to edit the configuration, modify the target and re-deploy them, you should ensure to add a pre-deployment activity to exclude computers if the software already exists. So that the deployment will happen only to the newly added computers.

Automated patch deployment is used to update the patches, whereas when a software/application needs to be upgraded, it should be performed using Software Deployment.

Deployment will happen only based on the timing set on the Deployment settings, even if you choose to deploy immediately. If you want to deploy a software immediately, you will have to modify the deployment to meet your requirement. So, that whenever a computer is reachable, the deployment will begin.

You will have to get the vendors website to fetch the uninstallation switches, once you have the uninstallation switches, you can create a package and deploy it to the target computers.

Based on the scenario, it is clear that the first 5 computers are reachable and the deployment is successful. So, you will have to verify if the remaining 5 computers are reachable from the server. You can verify it by pinging the agent computer. If there is an issue in connectivity, then you will not be able to deploy the software to the target computer. Deployment will begin when the RMM server is reachable from the managed computer.

You can verify the version of the software from the Inventory details. If you want to verify this, before initiating the deployment, you can use pre-deployment activities, to verify the version and choose to proceed or abort the installation.

When a software is installed using self-service portal, it uses the "system account" to install a software for computers and currently logged on user account for user specific software.

Please refer this document.

Enterprise applications can be deployed through RMM. You need to add the package with proper silent install switches as specified by the application vendor. It can be achieved by passing the license key as arguments or by XML files which depend entirely on the product.

Self-Service Portal is only available for Enterprise Edition. You can login to RMM web console and click Licenses at the top pane. You can view the license type as Professional or Enterprise Edition.

Self-service portal can be enabled for all managed computers, users and custom group in RMM.

Yes, it is possible to wake up the computers before deployment. You can configure this from, Software deployment -> settings -> Deployment policies-> Turn on Computers before Deployment.

Software will install in the next refresh policy after the time mentioned in the 'Install After'. Refresh policy is a duration of 90 minutes for the network.

Installable files will be copied inside the 'RMM' agent folder. Files will be deleted once the software is installed successfully.

Schedulers work with reference to the RMM server time.

For Remote Office based network infrastructure, HTTP repository is the recommended approach. This would automatically replicate the deployed packages to the respective Remote Offices. Currently, replication of packages in Network share are not supported. However, if you are using Distributed File System (DFS) replication is automatically taken care.

Using the given 'Proxy', RMM will download files from the external vendors website and store the files in the HTTP software repository.

MSP file format can be used for installation in RMM. Choose "MSIEXEC" as package type and specify the arguments along with its silent switches as shown below: %windir%\system32\msiexec.exe /update "\\share\xyz.msp" /qn.

If the first package fails, it will halt the installation. We have e-mail notifications to notify the admin about failure. We would recommend you to configure the retry option, to increase the success rate.

RMM has a online database of Software Templates to look for silent install switches which you may view here. You can also check with the original software vendors to get the silent switches. Online search is another way to get your switches from user communities, software expert blogs etc.

The latest versions of chrome will be upgraded over the existing one. In general, the uninstall does not need the original package. You can use the uninstall string to uninstall it directly.

If you want to maintain the history of previous configurations, then you will have to create a new configuration for every upgrade, else you can update the same package and configuration.

Currently RMM do not have option to add multiple exit code. However, this can be added to road-map tool.

You can use script to do the registry and use it with pre/post deployment activities of Software Deployment. To give you a quick heads-up, the development team has plans to provide requested features under Collections. (Collection is the combination of multiple configurations in the required order). This would empower you to do multiple configurations like Registry, Environment Variable, File folder Operations, Drive mapping etc., along with "Software Deployment" as a collection.

RMM will attempt to install it on all computers. However, you can follow the below approach to handle this,

1. Using configuration Modify >> save as new >> Without target and add new target computers.
2. Apply the configuration to a 'Custom Group' and later add new computers to custom group so that only the newly added computers will get the configuration.

RMM doesn't support this feature. However the product roadmap has this added in. Please raise those requirements to our product road map.

Create a folder in another computer. Give end-users read and execute permission for that folder. Go to Software Deployment->Software Repository->Network Share. Choose Existing Share. Here, enter the path name for the Network Share that you have created earlier. For example : \\MachineName\ExampleShare