UserName/DisplayName/AccountDescription feature in DomainService piece of TechIdManger

New for DomainService version 2.0 (and greater) is the ability to set, on a per domain basis, the format of some of the managed technician’s account information. The user name, the display name, and the account description can all be set from the commandline for DomainService.

New for DomainService version 3.177 (and greater) is the ability to set on a per domain basis the phone and email of the of managed technician’s account.

All of these are set based on the same internal variables:

  1. first – First name from TechClient (not assured to be unique among techs)
  2. last – Last name from TechClient (not assured to be unique among techs)
  3. user – User name from TechClient (assured to be unique among techs)
  4. company – UserNameAddon from ManagementConsole (shared between everyone in the company)
  5. firstinitial – First letter of the First name from TechClient (not assured to be unique among techs)
  6. lastinitial – First letter of the Last name from TechClient (not assured to be unique among techs)
  7. phone – Phone number from TechClient (not assured to be unique among techs)
  8. email – Email from TechClient (not assured to be unique among techs)
  9. blank – nothing. Use to prevent a value from being set.

To set these on the command line for DomainService they need to in curly braces {}. Any text not in curly braces is used as text. Once set from the commandline they will be used from then on. To clear (or go back to the default value) for any of these options use “reset” as the string after the option. When using PowerShell all options need to be in double quotes (“) because PowerShell will interpret the braces and not do what you are probably expecting. You should use DomainService.exe show to confirm you set the options as intended.

For a few examples lets have a few techs who work for a company with UserNameAddOn – SuperTechs. These names are all made up just for the example, and we really suggest you use realistic names that are easy to identity when looking at AD.

The first tech is John

  1. User Name – Tech1
  2. First Name – John
  3. Last Name- Blaze

The second tech is Eric

  1. User Name – Eric
  2. First Name – Eric
  3. Last Name – Burgin

The third tech is Ethan

  1. User Name – Master
  2. First Name – Ethan
  3. Last Name – Bailey

For example: The command line

DomainService.exe username "admin-{user}.{company}"

will create the following three users

  1. admin-Tech1.SuperTechs
  2. admin-Eric.SuperTechs
  3. admin-Master.SuperTechs

For example: The command line

DomainService.exe username "{firstinitial}{lastinitial}.{company}"

will NOT create the following three users. An error will be sent to the ManagementConsole that you can see when looking at the Domain Status.

  1. JB.SuperTechs
  2. EB.SuperTechs
  3. EB.SuperTechs

This is because there is an overlap in usernames. Note how both Eric and Ethan map to the same username. This will result in the DomainService doing nothing until the error is fixed. Users won’t get created and passwords won’t get rotated.

For example: The command line

DomainService.exe username "{first}"

will create, or take over, the following three users. If there are no users with those names on the network already that won’t be a problem. If one of the names exists already then TechIdManager will take over maintenance on that account, and start rotating the password and setting the rights.

  1. John
  2. Eric
  3. Ethan

This has a high likelihood to overlap with existing and future users on the network, so we recommend against it.

The default for the username is {user}.{company} which guarantees that there is never an overlap in the names created, and minimizes the chance for overlap with existing and future users on the network.

All this applies to username, displayname, and accountdescription. If you want to set spaces in the Display Name or the Account Description then make sure to use quotes (“) appropriately on the commandline.

Note: On DomainControllers with DomianService running the managed accounts will be updated to reflect changes in these parameters, as they are changed.

Note: On a non-domain computer with DomianService running, the account names will not be changed when these parameters are changed. The name an account is created with on a non-domain computer is the name it always has. If you manually delete that account a new account will be created based on the current parameters.

3 thoughts on “UserName/DisplayName/AccountDescription feature in DomainService piece of TechIdManger”

Comments are closed.