Active Directory naming standards/Name Changes

This isn't really an Infor 'issue' but it impacts us with Infor so wanted to reach out to see if anyone would mind sharing what they do for Active Directory and name changes.

We have standard of first initial last name. If that is already 'used' by someone, the next person gets a number at end. jsmith@xxx jsmith2@xx for example.

Then if jsmith changes their name and becomes 'wilson' a bunch of requests kick off internally to change AD (jwilson) and then change in all other systems as well and including email.

I'm sure we are not the only organization that feels like they spend a lot of time due to name changes.

Anyone have any insight?

Find more posts tagged with

Infor Lawson Human Resources Group - Discussion

Comments

unknown

The company I am at used to do something similar. In fact, the prior place did this as well. Both places ended up changing to something that incorporated the employee's id. So if their EMPLOYEE id in Lawson/Infor is 456789 and the company name is Widgets and Gadget Manufacturing then the user id in AD (and all other applications) will be wgm456789. This way, there are no changes needed. The EMPLOYEE ID will not change and upon rehire, they get the same id.

downloadexport530_1.zip

unknown

Thank you. I totally understand that.. using emp id.. as that is the strategy I took for Actors/RMID's in Infor because of that reason. But my concern is if /how that works with communicating 'hey, my email is xyz14333@xyn.com And then from HR perspective of several people having visibility to employee id #'s

unknown

Email can still use firstname.lastname@wgm.com and not use the employee id/user id. It is easier to provide a new email address and still forward email from the old one. Probably best to keep email address different from what users use to log into applications with. Infor applications are the only ones we use the @wgm.com for signing in. It is set up at a thickclient in Infor Security. There is an option to set up SSOP so they will just use their wgm456789 id without the @wgm.com at the end.

unknown

We do what @Tammy Viola said.
Our AD uses the EMPLOYEE number as the SAMA. We authenticate Lawson against an extended attribute in AD, not the SAMA or email or name. Normal Network Authenticates against SAMA. We use Company initials + Employee number in that extended attribute. Email is separately done by the AD admins just like described, avoiding duplicates. I don't know how this is going to work out when we go to ADFS. We think we can get it to work. This isn't hard for our employees because to login to their computer it has been their Employee ID for some time (10+ years). We couldn't get it to work with just the Employee Number as the authentication in 2014/15.

Copyright © 2025 Infor. All rights reserved.