# Mapping Hostnames to a Group

# Introduction

Configure license-host-mapping to map hostnames to a group.

Apply the configurations shown in the Open iT server.

# Configuring `license-host-mapping`

Open license-host-mapping in the Configuration directory, which is by default in C:\Program Files\OpeniT\Core\Configuration.

Notice that it contains instructions on how to edit the file.
Specify host names with the following syntax:
Mapping Syntax
```
MAP: HostGroupName
Hostname1
Hostname2
```
Empty lines are allowed — any line beginning with # as the first non-whitespace character is considered a comment. Globbing is also supported, allowing you to use several globbing patterns; however, remember that they are slower than exact matches. To make your mapping files more effective and efficient, refer to the Optimize Rules to Speed-up Rename or Mapping page.

In the mapping file, entries are case-insensitive, meaning that capitalization variations, such as 'Hostname' and 'hostname', will be recognized as identical. Also, note that leading and trailing spaces are removed from entries.

Each host can be a member of only one group. A host that appears in multiple mappings will always be mapped to its first occurrence in the file.
Example
```
MAP: HostGroup1    
Host1028
Host0232
```
This example maps Host1028 and Host0232 to HostGroup1.

You can also include custom configurations in this mapping file, such as default mapping, setting date limits on specific mapping entries, or creating nested maps.
Save the changes.

The mapping file will only affect the data collected after configuring. To apply the mapping for historical data, you need to regenerate that data. This process will help ensure that all your information is aligned and accurate.

Open license-host-mapping in the etc directory, which is by default in /var/opt/openit/etc.

Notice that it contains instructions on how to edit the file.
Specify host names with the following syntax:
Mapping Syntax
```
MAP: HostGroupName
Hostname1
Hostname2
```
Empty lines are allowed — any line beginning with # as the first non-whitespace character is considered a comment. Globbing is also supported, allowing you to use several globbing patterns; however, remember that they are slower than exact matches. To make your mapping files more effective and efficient, refer to the Optimize Rules to Speed-up Rename or Mapping page.

In the mapping file, entries are case-insensitive, meaning that capitalization variations, such as 'Hostname' and 'hostname', will be recognized as identical. Also, note that leading and trailing spaces are removed from entries.

Each host can be a member of only one group. A host that appears in multiple mappings will always be mapped to its first occurrence in the file.
Example
```
MAP: HostGroup1    
Host1028
Host0232
```
This example maps Host1028 and Host0232 to HostGroup1.

You can also include custom configurations in this mapping file, such as default mapping, setting date limits on specific mapping entries, or creating nested maps.
Save the changes.

The mapping file will only affect the data collected after configuring. To apply the mapping for historical data, you need to regenerate that data. This process will help ensure that all your information is aligned and accurate.

# Next Steps?

Proceed with data regeneration after configuring all the necessary mapping files to apply the changes in the historical reports:

Data Generation

# Mapping Hostnames to a Group

# Introduction

# Configuring license-host-mapping

# Next Steps?

# Configuring `license-host-mapping`