0 votes

I recently upgraded to version 2013.1 and since then a create user action on my help desk website no longer adds the @domainname.com to the User logon name field. You can see from the screenshot below what I'm actually talking about. Notice how the box next to the User logon name is blank. if I click it I can select the domainname.com from the dropdown, but I don't know why it's not being set automatically anymore. This is in turn messing up our account creation process because without the proper suffix there Exchange will not create the mailbox.

Any help with this issue is appreciated. Thanks

by (520 points)

1 Answer

0 votes
by (215k points)


A possible reason for such behavior is that you are using a modified Create User Web Interface form that does not contain the User Logon Name field. In such a case, when User Logon Name is not specified explicitly, the User Logon Name property is generated by Adaxes automatically basing on the Property Pattern for the User object. Since the value generation template for the property is set by default to %saAMAccountName% in the builtin User Pattern, the generated User Logon Name does not include the UPN suffix.

To remedy the issue, you need to modify the Property Pattern that is used for User objects. To do this:

  1. Open Adaxes Administration Console.
  2. In the Console Tree, Navigate to the Property Pattern that is used for User objects (by default, this is the builtin User Pattern) and select it.
  3. Double-click the User Logon Name property.
  4. In the Generate default value field, modify the template for the property to include the domain name, for example, %saAMAccountName%@domain.com.
  5. Click OK and save the Property Pattern.

Another possible reason is that you use a certain script for username generation that sets only the User Logon Name (pre-Windows 2000) property (SamAccountName), but does not set the User Logon Name property. Or the script may set the User Logon Name property without the UPN suffix. An example of such a script is the script that adds a digit to the end of the username if it is not unique from our Validate/Modify User Input Using a Script Tutorial. If this is the case, you need to modify the script so that it sets the User Logon Name property correctly. If you need help with modifying the script, we can help you.


That was it. I had created a customized form and didn't have the User Logon Name field on it anywhere. Instead of changing the Property Pattern I just added it to the form. Created a couple of test users and they all worked perfectly.

Thanks very much for the help.

Related questions

0 votes
1 answer

It is possible to automatically create the logon name based on eg %firstname% and %lastname%, however I want to achieve the following: logon name = first letter FirstName, first ... account where that field is used for. How to achieve this? With regards, Remco

asked Nov 21, 2013 by RTiel (780 points)
0 votes
1 answer

Due to some of the systems we have, we must limit our logon names to 8 characters. When I set the Value Length to Maximum 8, the result when creating a new account ... get a popup "Invalid Value Length". Is there a way to autopopulate with only 8 characters?

asked Mar 18, 2013 by Kikaida (1.1k points)
0 votes
1 answer

Unfortunately, the logon names are not set automatically when a user is created. For the Full Name attribute everything is working fine. Where did I make a mistake here? Greetings, Robin

asked Apr 26 by robin.christmann (80 points)
0 votes
1 answer

Hello, our users have to login to the Adaxes web service by using their username and password, no SSO is used. I have configured the option in the web interface ... /access control, but after some weeks/months this happens again. Thank you Regards, Thorsten

asked Jun 4, 2014 by techman26 (240 points)
0 votes
1 answer

Hello, We are currently allowing users to submit requests for new user accounts within the domain. By default, the logon name is being formatted as %firstname%.%lastname% However this ... pre-Windows-2000 user logon name. Is there a way to work around this?

asked Dec 11, 2020 by sirslimjim (400 points)
2,757 questions
2,491 answers
1,468,884 users