Main: General
Attribute name |
Description |
Name |
The name of the location item. Mandatory field. |
Short name |
Enter the short name of the location. Note! this field can be used as a variable in package building. See, using package variables. This field is optional. |
Status |
A location item can have following system statuses:
|
Parent |
In case you need to build a hierarchy of your locations define the upper level location here. When the parent is defined for a child location, the inherited settings (regional settings, keyboard layout, time zone, default installation point) are displayed automatically in the form. In case this is the top level location or you don't build a hierarchy of your locations, leave this field empty. This field is optional. |
Responsible |
A person responsible for this location item. This field is optional. |
Description |
You may enter a free description of the location here. This field is optional. |
Location selectable for asset |
Location selectable for asset defines whether it is allowed to assign asset configuration items to the particular location. With the help of this setting, you can prevent assets from being assigned to locations that are only logical nodes in the location hierarchy, but there is no office at that location for example. If the check box is unchecked, then assets cannot be assigned to the location in Miradore Management Console, in the initial installation console, or not even in the Miradore's Self-service portal. However, this setting does not affect to the data that is entered to Miradore Management Suite through integrations or asset data import. By default, assets can be assigned to all locations. |
Location selectable for user |
Location selectable for user defines whether it is allowed to assign user items to the particular location. With the help of this setting, you can prevent users from being assigned to locations that are only logical nodes in the location hierarchy, but there is no office at that location for example. If the check box is unchecked, the user items cannot be assigned to the location in Miradore Management Console, in the initial installation console, or not even in the Miradore's Self-service portal. However, this setting does not affect to the data that is entered to Miradore Management Suite through integrations. By default, users can be assigned to all locations. |
Main: External identification
Attribute name |
Description |
LDAP identification string |
When importing user objects from Microsoft Active Directory, you can assign those to a correct Miradore location by entering an identification string here. On the AD connector item, you can define the AD attributes that are used in the identification process. Attribute values are separated with a comma and combined into a string. This combined string is compared to LDAP identification strings of locations. If the combined string includes the LDAP identification string of a location, the location is set for user. If the combined string matches to several locations, i.e. several LDAP identification strings, the location which has the longest LDAP identification string is selected for the user. An LDAP identification string can be a part of the combined attribute value string, for example (if distinguishedName is used): OU=Paris,OU=France,OU=Users,DC=company,DC=com OU=Paris,OU=France,OU=Users Several LDAP identification strings can be entered for a location by separating them with semicolons, for example: OU=France,OU=Sales,OU=Users;OU=France,OU=Services,OU=Users See Active Directory connector. This field is optional. |
Main: Installation settings
Attribute name |
Description |
Regional settings |
Select here the default operating system regional settings for assets which are assigned to this location. The regional settings (regional settings, keyboard layout, and time zone) are configured to the asset's operating system during the initial installation process. Windows assets will also use the time zone, inherited from the location, to display power management reports. If time zone hasn't been defined for a location, then the reports are displayed with UTC time. See asset configuration item attributes for more detailed descriptions of those attributes. If the settings are inherited from a parent location, they are then greyed out and cannot be edited. A link to the parent location from where the setting is inherited is displayed next to the setting. You can define the regional settings separately for each operating system category on the location. |
DHCP |
Default value for asset configuration items assigned to this location. The DHCP setting is configured to the asset operating system during the initial installation process. Values: Yes/No |
Subnet |
The correct installation point used for package installations is selected based on the subnet information entered here. This field is optional. |
DNS servers |
Default DNS servers for asset configuration items assigned to this location in case DHCP is set as 'No'. The DNS servers are configured to the asset operating system during the initial installation process. |
WINS servers |
Default WINS servers for asset configuration items assigned to this location in case DHCP is set as 'No'. The WINS servers are configured to the asset operating system during the initial installation process. |
Installation points |
Installation points in this location. Only the first (on top of the list) is sent to client. |
Default packages |
Enter the default packages to be installed in initial installation to asset configurations with this location and child locations defined (optional) If the package is inherited from a parent organisation, it is then greyed out and cannot be edited. A link to the parent where from the package is inherited is displayed next to the package. |
Default installation point |
Define the default installation point to be used for assets in this location. The installation point value is read always when distributing packages. If the setting is inherited from a parent location, it is then greyed out and cannot be edited. A link to the parent where from the setting was inherited is displayed next to the setting. |
Max concurrent package installations |
This field defines the maximum number of concurrent package installations for devices in this location. A device's current location is solved by comparing the device's IP address to the subnet information on the location items in Miradore. If the limit is reached, Miradore Management Suite doesn't start any new package distributions. In this case. the package distributions are re-attempted later when the target asset polls Miradore server for the next time. All installation packages are affected by this setting by default, but at the Package item pages, it is possible to separately choose for each installation package whether or not this location-specific setting should be taken into account when starting to distribute the particular package. This limitation can be also skipped when starting new package distributions from the Asset configuration item page. There is a check box for skipping this limitation in the popup, which is used to select the package to be distributed. |
Max bandwidth for file copying (kbytes/s) |
This field defines, in kilobytes per second (KBps), the maximum allowed bandwidth usage for... - the "Copy file/folder" package action for assets in this location at the moment when the package distribution is started. This limitation is ignored if either the source or the destination is not a network file system. - downloading the patch management files to the assets that are currently in this location. - downloading Windows 10 version updates to the assets that are currently in this location. Notice: A device's current location is solved by comparing the device's IP address to the subnet information on the location items in Miradore. Notice that for the package distributions this limitation is distribution-specific, which means that, if you have allowed 5 concurrent package installations and the maximum bandwidth for file copying is set to 200 KBps, then the total maximum bandwidth consumption may raise up to 5 * 200 KBps = 1000 KBps if all five packages are executed at the same time. All installation packages are affected by this setting by default, but at the Package item, it is possible to choose for each installation package separately whether or not this location item's setting should be taken into account when executing the particular package. This limitation can be also skipped when starting new package distributions from the Asset configuration item page. There is a check box for skipping this limitation in the popup, which is used to select the package to be distributed. |
Main: Address information
Attribute name |
Description |
Addresses |
Three types of addresses can be configured for a location: mailing, visit, and delivery. The addresses are inherited to all sublocations. |
Main: Power management
Attribute name |
Description |
Electricity price |
Electricity price is used to calculate an estimate of power costs for devices (asset configuration items) that have been assigned to this location. The electricity price is inherited to all sublocations. Default value for the electricity cost can be defined in Administration > System settings > Main > Power management > Power management settings. The power costs are calculated based on the device power states that are monitored by Miradore client. If the electricity price is changed, any existing electricity costs will not be recalculated. Although location specific electricity prices can be configured, the prices need to be entered in the same currency. The used currency can be defined in Administration > System settings > Main > Power management > Power management settings. |
Main: Additional information
Attribute name |
Description |
Attachments |
You may attach files into this field. About attaching files. This field is optional. |
Comments |
You may add comments related to this location here. This field is optional. |