Setup

Click on  button in the top right corner of the screen. 

The 'Setup' area of the console settings will be displayed. (Click on the 'expand' arrow if required)Drop-down TitleDrop-down Title

You can manage Sites that you have created in the Devices area.

A Site will only be displayed in this area if an IP range has been configured for the Site.

If two or more Sites have overlapping IP ranges then the order that they are displayed in this list will determine which site manages any overlapping IP addresses.

The Up/Down arrow buttons allow you to change the list order. You may also click 'Export' to export the list of ranges to CSV.

Check our  Video about Site Configuration for Discovery.

Inventory archive points are created whenever a device successfully sends inventory data up to the cloud console.

This enables you to compare two sets of inventory data via the Inventory History feature, any hardware or software changes between the archive points will be highlighted.

It is possible to delete records older than the period selected from the drop-down menu.

 If you click on 'Delete ALL archive data' all historical data will be deleted and the Inventory History feature will no longer function.

If you require any emails that the console sends to be sent using a particular account, then the account details can be entered here.

 You do not have to configure this setting for the console to send emails. Emails are automatically sent from the console's default domain.

Configure the date format and time zone using this area of the console.

All dates are stored within the Syxsense database with UTC time but are then converted to the configured time zone when being displayed in the console.

Devices can be automatically archived into the 'Archived Devices' area of the console using this option.

If a device remains out of contact with the console for 'X' days, it will be archived.

If an archived device contacts the console it will be returned to the Managed Devices section.

 Auto Archive is switched off by default.

Create exclusion rules the prevent devices that meet any of the rules from being discovered using the 'Discovery Task' process.

Exclusions can be based on operating system name, IP address, device name, etc.

 The exclusion rules will not prevent a new device from appearing in the console if an agent is manually installed on the device. Furthermore, if a device already has an agent installed adding the device name to the exclusion list will not prevent the device from appearing in the console. The agent must be removed from the device, the device must then be deleted from the console.

This option allows cleaning up old tasks. Set the period in which the task is considered old, and it will be permanently deleted.

The out-of-date tasks are determined by the following categories:

StartTime, LastStart, EndTime, LastUpdate, CreatedDate, LastTargetRefresh, PausedUntil.

If at least one of these categories do not run into the set period, the task will not be deleted.

Example: If you enable cleaning the tasks that are older than 10 days and there is a particular task which is more than 10 days old (was created earlier) but has its start time set to a date in a future, than such task will not be deleted.

Identify devices with duplicate 'Device IDs'.

This section allows you to input the 'cloned' device GUID, so that if additional devices check in with the same GUID, the additional devices will re-generate the GUID to show up as unique devices.

 This happens if you clone a device that already has a client installed.  Please contact our helpdesk if you detect duplicate devices. 

Check our  Video to learn how to exclude a device ID.

Rules based on IP address ranges can be created which restrict the logged-on user's permissions within the console.

Countries can be configured to allow or deny access to the console from that country.

The 'End User Access' portal can also be switched to on/off based on the Location Security Settings.

This area of the console allows you to leverage any external identity provider for Single Sign-On (SSO).

Simply enable the option and input the required SAML2.0 Metadata; however, be sure that the users are already created in the console under 'User Accounts' and that the email addresses match.

Identity Providers Supported (click for instructions, if applicable):

• Okta
• Azure AD

You may disable the forced Syxsense 2FA option by clicking the checkbox 'Disable two-factor authentication when logging in with External Authentication'.