Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 48 Next »

 

This section allows a number of aspects of Commander to be configured.

 

License Details

License details for Enterprise Commander & other products from Event Zero are displayed here.

 

System Settings

System Settings allows you to configure the following items.

Authentication

You can configure authentication via Microsoft Active Directory and / or via locally defined users.

Active Directory Authentication

  1. For every domain that you wish to authenticate against install a commander Connector (Installation - Commander Connectors) on a Windows computer in that domain.
  2. Every Connector is capable of authenticating against the domain it is in (you may have installed Connectors for different reasons and so have domains you do not wish to authenticate against). You must select which domains to authenticate against by adding an Authentication Forest. Click Add... and select the forests you wish to authenticate against.

  3. Only users in specific AD groups are authorised to access Enterprise Commander. Click Add... and start typing a group name to add it. 

    Group membership for users is extracted from AD by the connector if you are importing user details from AD. See the Active Directory Connector documentation for details of enabling this.

Local Users Authentication

You can create local users inside Enterprise Commander that can login. Use that section of the page to add and delete users and set their password.

Note that users are not deleted - they are just flagged as deleted and can no longer login. You can 'Undelete' them to restore their access.

 

 

DMA Configuration Properties

DMA Configuration Properties allows you to enable or disable the reporting of Power Actions to your endpoints that are reporting to the Engine Room Server.

Replay History on Reconnect

Replay History on Reconnect is the time period of data that is cached locally on the endpoint by the DMA Client Agent. In the event of the endpoint being offline from the server the DMA Client Agent will then push the cached data through to the server. By default Enterprise Commander is set to only receive 4 hours of history. This can be changed if required but will impact on server performance due to the upload & processing of large quantities of cached data.

Load Balance Configuration

If your Commander standalone instance is behind a load-balancer of some kind (eg bigIP), you have to manually set Client Poll. Set the secure flag (http or https) and the external hostname. The path should remain /dma/clientPoll.

 

 

 

You are also able to enable or disable the Enterprise Commander Deskband. Enabling the Deskband will place an Enterprise Commander search filed onto your Windows task bar enabling direct search access to Enterprise Commander at any stage.

You are able to search on items you would find within enterprise commander as well as items as partial names, partial machine names, contact numbers and even IP Addresses. The results are displayed directly within an Enterprise Commander browser window that open when you enter your search into the Deskband.

Print Discovery Configuration

Print Discovery Configuration allows you to enable to disable the reporting of printers to the Engine Room Server, there is also an option to enable the discovery for directly attached printers (eg. USB Printers)

Notice & Alert Limits

Notice & Alert Limits allows you to set and fine tune the time periods for Enterprise Commander alerts and notices. Enterprise Commander ships with default times but these may not be an accurate reflection of what your environment considers to be best suited for its requirements.

As an example the slow boot time in seconds and the slow boot to log in time can be adjusted to take into consideration the following;

  • A benchmarked average time for boot based on fleet models within your environment.
  • The duration of log in scripts and machine activities that are set to run at log on.
By fine tuning the time periods for both Alerts and Noticies you will be able to get a more precise and accurate picture of events within your envrionment.

System Alert Configuration

System Alert Configuration allows you to enable or disable alerts for specific conditions;

  • Users with locked endpoints.
  • Users with expired accounts.
  • Users with accounts set to expire.
  • Endpoints with not Anti-virus software.

These alerts are displayed on the dashboard pages within Enterprise Commander.

System Notice Configuration

System Notice Configuration allows your to enable or disable system related notices, such as;

  • Endpoints with low disk space.
  • Endpoints with low memory.
  • Endpoints with no firewall.
  • Sites that have a slow network response time.
  • Sites that are open but have no users.

Work Hours

Work Hours allows you to set the work hours for your organisation, this allows for more accurate time related information, such as identification of users active outside of business hours etc.

Mobile Device Management

Allows you to create secure mobile APNS Certificates for your mobile device access to Enterprise Commander. 

Sites

Your site location details are entered here in order to have them appear within the Sites dashboard within Enterprise Commander. Sites are created and subnets of endpoints are allocated to the created sites in order to present accurate location based reporting.

 

Creating A Site

  • To create a site click on Add Site.

 

  • A site information box will appear on screen detailing the required information for the creation of the site, once completed click on Save.

  • The site will now appear in the Site list table on the Sites page within Global Settings.

Adding Subnets

A newly created site will appear in the Site list table on the sites page within Global setting but it will also show that there are 0 subnets associated with that site.

In order to have endpoints reporting to the site correctly we need allocate the endpoint to the site.

  • Click on Add Subnets.

Step 1

  • The first of two steps will appear on screen, you will first need to specify the subnets you are wanting to assign to a site.

  • Once the subnet addresses have been entered you will need to set the Route for the subnet or subnet range, if the subnet / subnet range is being routed through a proxy or another address specify the address from the drop down list.
  • You will then need to select the site from the drop down list that you wish to assign the subnets to.
  • Click Validate to validate the entered information before progressing to step 2.

Step 2

  • Once verified, you will be presented with a summary of the subnet information that was added in step 1 as well as options to add the subnet to the site or to ignore it.

  • Click on Add on the subnet or subnets you wish to allocate to the site.
  • Click on Complete.
  • The subnet has now been allocated to that site.
Adding Additional Subnets to an Existing Site

 

  • If you would like to add a subnet or multiple subnets to an existing site, click on the number of subnets that the site reports it has allocated within the sites table.

  • A window will appear with the subnets allocated to the site with options to add additional subnets.

  • To add additional subnets click on Add Subnets.
  • Enter the subnet or subnets into the text field, select the appropriate Route option & then click on Add Subnets.

  • The new subnets will appear in the subnet window, the window can be closed using the Close button.

 

 

 

  • No labels