I wonder if anyone could tell where I am going wrong or is the following a design issue:
Environment: EPO4.5 P4HF1, EEPC6.1,MA4.5P3, Windows AD
I think I got everything working from install, user and computer sync, deploy of clients and upgrade from v5 to v6 to perserving the password from v5. However, our environment operates first name [space] last name for username for AD and we replicate that in v5.
Here's the problem, when you install v6 or upgrade from v5 to v6, v6 user login challenge screen only accepts last name [comma] [space] first name. Otherwise, it will say UNKNOWN user. I can't think of a way short of telling all the existing users of v5 that in order to be recognised they will have to enter last name [comma] [space] first name. I know to me this is not a big deal but users are not going to like it.
Any advice or info would be much appreciate it.
the user name format in eepc6 is set when you create the settings for your AD sync within EPO - you get to set what attributes it uses for the user name, and the displayed name. You can set it to use whatever attribute from your AD you want.
i have the same problem, can you tell me where this is changed as there is nothing in the screen where you register the AD synch, and am having a problem with the usernameset up as (firstname.secondname) but the endpoint encryption user name coming in as (firstname secondname),
The sync is done through Server Tasks. you create a new task and set it for EE LDAP User/Group Synchronisation.
Select your LDAP Server and match the field that you want for:
My setup is:
It might help you out if you use AD Explorer from Sysinternal to view our AD attributes.
yes - easily - just look up "theme" in the help or docs. You need a 1024x768 basic PNG file - open and save it in MSPaint seems to work to strip out all funkly formatting.