This content has been marked as final. Show 3 replies
i don't think it will work if a user has truely never logged on. If this is in a corporate environment, what a lot of IT staff do is log onto A N Other laptop using the client, both pre-boot and windows, then sync up the SSO details to the server.
Then any machine that sync's (regardless of who is logged on) will get those SSO cred's. A password reset by the helpdesk, using "force change at next log-on" would then force user to change password upon first entry to windows and then the passwords should sync themselves back up.
Are you talking about WINDOWS profiles? The password is not stored in the users profile - it's stored in the SafeBoot File System (SbFS). The only thing that is a hindrance to you is perhaps that because no one has logged into the system, the client hasn't brought down the user accounts yet --- but if that was the case, then encryption shouldn't have started.
If you have another password sync utility for your Active Directory domain, you can create an external call that sets the MEE password and SSO information through the API.