New Users created on the web console are being created in Active Directory correctly, HOWEVER … the User Logon Name (pre-windows 2000) in Active Directory is being created with the username selected + “_COMPANYNAME” for example.
User logon name: test@testcompany.com
User logon name (pre-windows 2000): domainname\test_testcomp
we would like the pre-windows 2000 name to be created as domainname\test , withtout the _companyname
Please let me know what we need to modify to fix this. thank you in advanced.
If you are on the latest builds you can go to the setup page, click advanced tab and change the sAMAccountName format from 1 to 0. What will happen is if you create a new user named John Doe then the sAMAccountName will be jdoe. If you create another user named Jane Doe, then it will create the sAMAccountName as jdoe1 and increment the number from there.
I would like to point out that bets practice in a multi-tenant environment is for users to use their UserPrincipalName and not the sAMAccountName for logging in.
We are currently running Version: 3.1.1532.0 and not seeing the advanced option. this is happening with all new user accounts created even if there is not a jdoe already. it will create the pre windows 2000 name as jdoe_compan, any way to modify that on the version we are running?
Yes you can modify the settings.xml file and then recycle the CloudPanel application pool. Here is an article showing the differences:
Okay i found the setting in the XML , currently is set to 1, if we set to 0 will users be able to continue using UserPrincipalName to login?
<Advanced>
<CompanyCodeFormat>0</CompanyCodeFormat>
<SamAccountNameFormat>1</SamAccountNameFormat>
<ADCNFormat>1</ADCNFormat>
<AllowDuplicateDomains>0</AllowDuplicateDomains>
</Advanced>
Yes, it won’t change the UserPrincipalName. Also this won’t change the existing users SamAccountName, so that will have to be done manually or left alone.
When there is a duplicate name, will it let us know it had to add the 1 to the samaccountname?
