Discussion Locked

User Naming Standards

0 helpful
1 reply
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Hi folks,

I have been tasked with coming up with a recommendation for a user naming standard for a government agency. Before I proffer my suggestions I would like to hear what other organizations are doing. There are several issues that need to be addressed, how to handle duplicates (John Doe, Jane Doe, etc), how to handle long last / first names, and how to support multiple vender environments and products and their restrictions/limitations - you know, to support that much sought after single login grail (MS Networks, Mainframe, Unix, MS SQL, Oracle, etc).

Any help would be useful, thanks?

Brett

1 reply

by brainb

At Stark Brothers, because we have several networks we use the abbreviation of the city, the users initials and the day of birth. This way a John Friendly Jones you works in Atlanta and has a birthday of 6/4/1964 has a logon of ATLJFJ04.

This virtually illiminates any duplicates. There are, of course, always exceptions.

Hope this helps

This discussion is closed to new replies.