Endpoint Encryption

Hi,

I'm currently rolling out our SEE client to Windows end-users using a third party application.

We are using Drive Encryption (not Symantec Endpoint Encryption for BitLocker).  

For our Windows client installation settings, under "Registered Users" we have chosen "Using Windows user authentication credentials -
User registration happens in the background after first login."

For some of our Windows laptops that we are rolling out, we will not have users logged in during the install. Is there anyway to add a generic registered user to our installation, which can used by our IT support staff.

I understand we can't add this to the installation package, but I was hoping this could be added via group policy or something similar?

Thanks,

Elana

It sounds like you're after the Client Administrator account here, of which you are forced to create at least one, during client package creation.  These are accounts that exist within SEE alone, and not within Windows, but that allow authentication past the Pre-Boot Environment, as well as other administrative functions on the client.

This old article discusses how to update and distribute client administrator accounts via GPO and should still be applicable:

http://www.symantec.com/docs/TECH161649

This article shows how to use The Client Administrator account at Pre-Boot:

http://www.symantec.com/docs/HOWTO110298

As the name suggests, this account is for administrative purposes, and is not one I would normally recommend sharing with users.  Is that what you were after?

Thanks so much for your help!

This is exactly what I was after.