# Renaming Users

# Introduction

Configure user-rename.map to use a new user name for the users. The new user name will be visible in both the License Monitor and historical reports.

Apply the configurations shown in the Open iT server.

# Configuring `user-rename.map`

Open user-rename.map 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 the username with the following syntax:
Mapping Syntax
```
MAP: New_UserName   
Old_UsernName
```
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 'User' and 'user', will be recognized as identical. Also, note that leading and trailing spaces are removed from entries.
Example
```
MAP: jsmith   
smith
```
This example renames smith as jsmith.

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 user-rename.map 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 the username with the following syntax:
Mapping Syntax
```
MAP: New_UserName   
Old_UsernName
```
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 'User' and 'user', will be recognized as identical. Also, note that leading and trailing spaces are removed from entries.
Example
```
MAP: jsmith   
smith
```
This example renames smith as jsmith.

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.