Add a task to push third party software

You can add a task to push software onto devices. This enables you to have N-able N-central download and launch software to ensure all devices have a specific or common set of software.

When you add a Push Third-Party Software task, you can select the software from any of the following locations:

• The N-able N-central repository
• Your local system
• A network share

Third-party software must use InstallShield, MSI, or Wise installers. N-able N-central can access the install software from its repository, your local computer, or a network share.

Requirements

If you use filters for a task, N-able N-central uses a snapshot of the filter for the targeted devices to include in the task. This avoids potential unexpected behavior when running tasks in the future. If you need to apply a task to devices, it is best to use a scheduled task profile. This enables a task to apply to the devices using a rule.

• When selecting the location of the third-party software, the file must be in the root of the UNC path listed in the default network share or use a custom network path that has the file in the root of that UNC path.

• Ensure that the Scheduled Tasks option enabled on the device. To verify, select the device and click the Settings > Properties tab and check the Enable Scheduled Tasks option.

• When N-able N-central pushes software or runs a script, the ADMIN$ share is used as a location to place the installer or script before execution. If Windows File Sharing is not enabled, this can prevent the task from sending the file.

• The agent and probe must have access to the ADMIN$ share on the system to transfer the required script or installer. Domain Admin account typically has the required access.

How to add a task to push third party software

This procedure can only be performed at the Service Organization level or Customer level.

File names for installers or scripts cannot contain spaces.

1. Click Configuration > Scheduled Tasks > Add/Delete.
2. Click Add > Push Third Party Software.
3. Enter a Task Name.
4. Details

   Select the Credentials used to push third party software:

   • Use LocalSystem Credentials: use existing system level credentials to run the task.
   • Use Device Credentials: use existing device credentials to access the device for running the task.
   • Custom Credentials: specify a user name and password to use for this task.
     If N-able N-central cannot login using the configured device credentials, it defaults to the LocalSystem credentials.

   Select the Location of the software, locate or select the install files and enter any additional parameter required to use during the installation.

   Command line parameters for MSI installers must be in the format of: <filename> </i or /u> </additional parameters>. For example, MyInstaller.msi /i /qn. The following examples are invalid: MyInstaller.msi /qn or /i MyInstaller.msi /qn.

5. Task Handler

   Select how N-able N-central manages the task using probes and agents:

   • Use Agent where available: local agents can used to run the task wherever they are available (otherwise the best available probe will be used).

   • Use probe only: specify a probe to run the task.

6. Targets

   Restrict the list of devices on which the task will be run based on filter and/or device:

   • Filters: Use the filters to target a group of devices.

   • Specific Devices: Select specific devices.

   Devices will not be displayed in the list if they cannot be configured as targets for the task. Other factors that may prevent devices from being targets include the device class or if the device is in a scheduled downtime.

7. Schedule

   Set a time when N-able N-central runs the task:

   • Type: Select Now, Once or Recurring task type.

   • Execution Timeout: Define how long (in hours) before the task will be considered to have timed out.

   In the Missed Executions options configure how far in the future N-able N-central should take action on a device that is currently offline, and how long it should wait, once the device powers on, before running the scheduled task.

   • Time to run: Define whether the task should only be run at the specified time or if it can be run as soon as possible if the device is offline at the scheduled time.

   • Settings for running task as soon as possible: If the device is offline, you can also define how many days after the original scheduled time that attempts will be made to run the task.

8. Notifications

   Configure N-able N-central to send a notification upon the successful completion of the task, or if the task fails to complete.

   Specify whether a notification will be sent to a Recipient based on one of the following:

   • Success: if the task is successful.

   • Failure: if the task is unsuccessful.

9. Click Save.

The scheduled task is saved to the repository. N-able N-central runs the task at the configured time. When complete, and if configured to do so, N-able N-central sends a notification to the selected recipients in the format defined by their user profile.

If you choose to edit the task, the edits may not be applied to the task if it has been initiated. Edits are applied to completed tasks only if they are recurring tasks.

When you run the task it runs under the Local System in the background; any user prompts will not be seen by the user. If the script or application requires user input, the task will timeout.

N-able N-central will not verify if the files to be installed are harmful to the target devices. Test any third party software before associating them with a scheduled task.

Considerations

• N-able N-central does not verify syntax and command line parameters of scripts or MSI/EXE installers to ensure that they are correct. You must validate scripts and MSI/EXE installers before using them in scheduled tasks to ensure that they will function properly.

  Command line parameters for MSI installers must be in the format of: <filename> </i or /u> </additional parameters>. For example, MyInstaller.msi /i /qn. The following examples are invalid: MyInstaller.msi /qn or /i MyInstaller.msi /qn.

• If you are installing an MSI file that contains transforms stored in a MST file, the command line parameters must be in the following format:

  <filename> </i or /u> </additional parameters> TRANSFORMS=<parameter file name>
  For example, MyInstaller.msi /i /qn /norestart TRANSFORMS=filename.mst

• If the installation of software requires user input, it must be specified in the Command Line Parameters field when the task is created.
• If restarting your computer is required after the installation of software, you must do this manually or specify it in a script.
• N-able N-central provides a combined total of 500 MB of storage for the script and software repositories.