The user name in windows has to match the one used in eepc if you have the machine general policy "must match" turned on?
If you turn it off thn it won't care if the users names match or not.
Did you mean to create your users with fqdns?
The users's were automatically sync'd from AD in the FQDN format. Maybe I should just turn off the the "must match" requirement? I'm not sure how the EEPC account gets linked to the correct AD account then.
Whoever the first windows user to login after a Pre boot login will get linked, that's all there is to it.
How are you creating the users? Whoever set that up picked upns, the default is always the SAMAccountName.
1 of 1 people found this helpful
Oops. I thought that was changed in the product some versions ago! My mistake. I guess the implementation team were just changing it for customers when they went on site.
Anyway, the name format has to match if you want to use the "must match option". If you turn that off, then you can have user "simon" linked to windows creds for "administrator"' or whatever you like.
in case some else runs into this, this was all caused by me not using the correct client file settings. Here are the steps I missed:
- In EEM go to the System tab
- Right click Endpoint Encryption File Groups and choose Update file groups. This apparently loads the files into EEM from the file system.
- Under the Machines tab, open your machine properties or machine group properties if the machines are managed at the group level.
- go to the Files area
- Make sure you have EEPC52 Option: EE Password Change Notification Plugin Files, EEPC52 Theme213: EE for PC McAfee Theme, EEPC52: EE 5.2.8 Client Files selected.
- Update your installation set and deploy.
Somehow I didn't have the right set of client files available to be deployed to my machines.
This resolved the problem for me.