Site Settings - Legacy UI

SECURITY  Permission to manage Site Settings

NAVIGATION  Legacy UI > Sites > click on a site > Settings

Refer to Site Settings in Creating a site.

If you are responsible for implementing Datto RMM in your company, you have probably reviewed your Account Settings - Legacy UI in the legacy UI or Global Settings in the New UI as one of the first steps in implementation. While global settings are fundamental for the optimal running of Datto RMM, they may not apply to all sites in your account, and you may need to modify them for certain sites. Individual site settings may override global settings or complement them with additional information. For information about sites, refer to Sites - Legacy UI in the legacy UI or Sites in the New UI.

To learn how to set up correct permissions to access Site Settings refer to Security levels - Legacy UI in the legacy UI and Security Levels in the New UI.

NOTE  As OnDemand sites cannot access all Datto RMM features, some settings may not be available for them. The settings described below are available for Managed sites.

You can modify basic information about your site by clicking Edit.

Field Description
Name Give your site a meaningful name. By default, you have one site called Managed and one called OnDemand.
ID This is the unique identifier of your site. This field cannot be edited as it is hard-coded.
Description Enter a meaningful description.
Type Choose one of the two available site types:
• Managed
• OnDemand
To learn how the two site types differ, refer to Sites - Legacy UI.

NOTE  This section is only available if you have downloaded the Autotask component from the ComStore. Refer to Autotask Integration.

By default, the Autotask Ticket Integration option is switched ON for all sites. This means that devices are able to create alert tickets in Autotask as per the ticket integration setup. Refer to Configure ticket integration.

If you switch off the Autotask Ticket Integration option in Site Settings, tickets will not be created in Autotask PSA for devices in the site in question, regardless of the monitor configuration.

You can specify the cost and power rating of your devices within the site. Click Edit to change the default wattage of 350W and the default cost.

NOTE  The fields accept numeric values only.

Field Description
Desktop Define the power rating of desktops.
Laptop Define the power rating of laptops.
Server Define the power rating of servers.
Other Define the power rating of any other devices. For ESXi hosts, network devices, and printers, this can be overridden on the Device Summary - Legacy UI page.
Cost per kWh Define the cost per kWh.

NOTE  If you leave the fields blank, the power rating configured in Account Settings - Legacy UI will be applied.

NOTE  With the 11.5.0 release, energy usage calculation based on power rating has been deprecated. Refer to Device Energy Usage deprecation.

If your site requires a proxy server, you can configure the proxy settings.

  1. Click Edit to configure the following:
Field Description
Proxy Type Select the correct proxy type:
• HTTP
• Socks4
• Socks5
• Select None if you do not wish to use any proxy for this site.
Proxy Host Enter the proxy host as required by your proxy server.
Proxy Port Enter the proxy port as required by your proxy server.
Proxy Username Enter the proxy username as required by your proxy server.
Proxy Password Enter the proxy password as required by your proxy server.
  1. Click Save.

NOTE  Site proxy settings will not apply to devices that had already been in the site before the proxy settings were configured. Existing devices with an Agent installed will need to be manually configured for the proxy.

For further information, refer to Proxy settings in Datto RMM - Legacy UI.

This setting enables a Network Node to scan additional subnets at the site level. This is particularly useful if your network consists of multiple VLANs that contain a set of devices of the same device type (for example, one for servers, one for workstations, and one for network devices). Any IP and subnet configured at the site level will be measured against the allowed limits set globally. Refer to Custom Agent Settings in Account Settings - Legacy UI (legacy UI) or Custom Agent Settings in Global Settings (New UI).

To learn how to configure additional subnets in the New UI, refer to Additional Subnets and Network Discovery.

To add a subnet:

  1. Click Add Subnet.
  2. Enter the Start IP Address and the End IP Address.
  3. Click Add.
  4. To add more IP ranges, repeat steps 1-3.
  5. Click the pencil icon to edit the subnet, or the Delete icon to remove it.

To be able to deploy an Agent across a LAN, you will need to have a username and a password for the devices you want to install the Agent on. You can save these credentials so that you don't have to enter them when adding new devices. At the time of initiating Agent deployment, you will be prompted to select a set of credentials. Refer to LAN deployment from the web interface.

The credentials entered here will be used in addition to any credential specified in Account Settings. For information on how to add Agent deployment credentials, refer to Account Settings - Legacy UI.

For newly created sites, the option Use Account Level Agent Deployment credentials is set to ON by default. Switch it off if you wish to use the credentials added at the site level only in the legacy UI. This setting does not have an impact on the New UI.

To learn how to save Windows and SSH credentials in the New UI, refer to Windows credentials and SSH credentials.

If you would like to manage SNMP-enabled devices in Datto RMM, you can save their credentials so that you don't have to enter them when adding new devices. Cached SNMP credentials are also used during network discovery. For more information, refer to Managing and monitoring SNMP-enabled network devices and printers - Legacy UI and Network scan process in the legacy UI or Managing and monitoring SNMP-enabled network devices and printers in the New UI.

The credentials entered here will be used in addition to any credential specified in Account Settings. For information on how to add SNMP credentials, refer to Account Settings - Legacy UI.

If you wish to use the SNMP credentials configured at the site level only in the legacy UI, switch off the option Use Account level credentials for SNMP-enabled devices. This setting does not have an impact on the New UI.

To learn how to save SNMP credentials in the New UI, refer to SNMP credentials.

If you would like to manage ESXi devices in Datto RMM, you can save their credentials so that you don't have to enter them when adding new devices. Cached ESXi credentials are also used during network discovery. For information about how to add ESXi devices, refer to Managing and monitoring ESXi devices - Legacy UI in the legacy UI or Managing and monitoring ESXi devices in the New UI.

The credentials entered here will be used in addition to any credential specified in Account Settings. For information on how to add ESXi credentials, refer to Account Settings - Legacy UI.

If you wish to use the ESXi credentials configured at site level only in the legacy UI, switch off the option Use Account level credentials for ESXi hosts. This setting does not have an impact on the New UI.

To learn how to save ESXi credentials in the New UI, refer to ESXi credentials.

This section allows you to specify one or more email recipients and define what type of email notifications they should receive. Email recipients set up here will receive notifications from this site only.

  1. Click Add Email Recipient.
  2. Fill in the required fields:
    3. Field Description
    Name Enter the recipient's name.
    Address Enter the recipient's email address.

    NOTE  The email field accepts the following characters:
    a-z, A-Z, 0-9, @, and !#$%&'`*+-|/=?^_{}~.
    Type Select the preferred email format for this recipient: HTML, Text, or Both.
    Receives Select any of the notification types this recipient should receive: Alerts, Reports, or New Devices.
  3. Click Add.

To delete an email recipient, click the Delete this recipient icon at the end of the row.

NOTE  Email recipients for the entire account can be specified in the Email Recipients section in Account Settings - Legacy UI (legacy UI) or the Email Recipients section in Global Settings (New UI).

NOTE  The notification type ComStore Components is only available for selection in Account Settings - Legacy UI (legacy UI) or Creating a site, Site Settings, and Global Settings (New UI).

IMPORTANT  With the 10.0.0 release, the local cache functionality has been deprecated as part of Datto's continued commitment to security. References to the local cache remain in the UI at present, but will be removed in the future.

NOTE  The Local Caches option is not available for OnDemand sites.

A local cache is a designated device that can be used as a component cache to store components. For more information, refer to (Deprecated) Designate a local cache - Legacy UI.

Once you have nominated your local caches, they will be listed in Site Settings with the following details: Name, Priority, Drive, and Cache type. You can perform the following actions:

  • Drag and drop any of the local caches to re-arrange their order. This allows you to prioritize which local cache your devices should contact first.
  • Hover over one of the local caches and click on the Delete this cache icon to remove it from the list. For more information, refer to Edit or remove a device as a local cache.

NOTE  The Assigned Resource for Tickets option is not available for OnDemand sites.

Select a user with Administrator permission to be the default assigned resource for tickets of this site. The setting applied at the site level will override the setting applied at the account level.

IMPORTANT  If No default user is selected, tickets will be assigned to the Administrator selected in the Assigned Resource for Tickets section in Account Settings - Legacy UI. If no Administrator is selected in Account Settings, tickets will be assigned to the user who registered the account.

NOTE  The Variables section is not available for OnDemand sites.

You can specify variables that can be used when writing custom components. The variables can be defined with a specific value that the Agent will use when executing the script. How you refer to the variables in your script will be defined by the scripting language you apply (for example, in batch scripts, you can refer to a variable in the format of %VariableName%).

NOTE  Site variables used in components will be passed to jobs and monitors and will override any global variables of the same name. For a site variable to successfully override an existing global variable, the site variable information entered must perfectly match the original global variable information, including the letter case of the name and value. You can specify global variables in the Variables section in Account Settings - Legacy UI in the legacy UI and in the Variables section in Global Settings in the New UI. You can also update multiple sites' variables in bulk using a CSV template. Refer to the Update Site Variables section of Account Settings - Legacy UI in the legacy UI or the Import Site Variables section of Global Settings in the New UI.

  1. Click Add Variable.
  2. Enter a Variable Name. Make sure there is no space in the name of the variable.
  3. Specify the Variable Value. Variable value limit: 20,000 characters.
  4. Check Mask value if you would like to hide the value of the variable.

    5. IMPORTANT  When extended logging is activated for log components, masked variables will be visible in clear text in the log file. Refer to Adding extended logging to Datto RMM.

  5. Click Add.
  6. Repeat steps 1-5 to add more variables.

You can save a credential to be used by components for this site. Caching credentials for components is useful if you want to run a single component against multiple sites, and each site needs a different credential. If the component you want to run is configured to require credentials, the credentials saved for the individual sites will be used at run time. To learn how to configure a component to require credentials, refer to This component requires site credentials in Creating a component - Legacy UI.

To save a credential, follow these steps:

  1. Click Edit.
  2. Select Use the following credentials for this site.
  3. Enter a Username and a Password.
  4. Click Save.

NOTE  To learn how to create and manage credentials used by components in the New UI, refer to Component credentials in Creating a credential.

This area allows you to override the label of the 30 user-defined fields (UDFs) configured in the User-Defined Fields section in Account Settings - Legacy UI (legacy UI) or the User-Defined Fields section in Global Settings (New UI). The UDFs can be populated with information that is not picked up in the device audit to provide additional targeting for jobs and policies. You can enter and edit UDF information manually on the Device Summary - Legacy UI page in the legacy UI and the Device Summary page in the New UI, or it can be populated by the Datto RMM Agent. For further information, refer to User-defined fields - Legacy UI.

To rename the default UDF labels, follow these steps:

  1. Hover over one of the rows and click the pencil icon.
  2. Rename the Site Label field.

NOTE  UDF labels have a limit of 22 characters.

NOTE  UDFs have a limit of 255 characters.

  1. Click the green check mark to save the changes.

NOTE  This section is only available if you have downloaded the Webroot Endpoint Security component from the ComStore. Refer to Webroot Endpoint Security Integration - Legacy UI.

By default, the option Activate Security Management is turned ON if you have a Webroot policy configured for the site.

Turning the setting OFF will deactivate all the currently active Webroot security management policies of the site. Turning the setting ON will activate all the Webroot security management policies that have previously been deactivated for the site.

NOTE  The Activate Security Management setting will automatically be turned OFF if you remove all Webroot policies configured for the site.

For more information about Webroot, refer to Webroot Endpoint Security Integration - Legacy UI.