Evaluation settings - where exactly are they populated?

Coordinator
Jun 7, 2007 at 1:02 AM
Edited Jun 7, 2007 at 1:35 AM
The EFS Assistant Administrator's Guide states the following:

"Note that when you install the Evaluation Settings feature, certain configuration settings are written to the area of the registry that is used by Group Policy. However, the Group Policy editor is not aware of these settings and does not display them—despite the fact that some options were configured."

  • Does this mean that the installer actually writes these values to HKLM\Software\Policies\Microsoft\EFS Assistant\ ?
  • Would these values not be wiped out the next time the Group Policy client refreshes its cache of settings?
  • I.E. has this been tested in a scenario where the EFS Assistant is installed, the user waits 16 hours (to ensure the Group Policy client performs the full "overwrite" refresh) and then tries to launch EFS Assistant? Do the evaluation settings still take effect after this time period has elapsed?

I'd hate to think that "evaluation settings" are only intended to be used for one day and then wiped out By Design. Most software vendors allow at least 30 days for evaluation of their software products...
Coordinator
Jun 10, 2007 at 5:19 PM
The evaluation settings are pushed directly into the registry by the installer. You are correct that Group Policy could stomp on these settings, but only if the local or AD-based group policy is set to configure that setting. As long as the GP is not enabled for a particular setting, the values pushed into the registry by the installer will sit there unmolested. We have verified this behavior on many machines.

We do understand that this will cause some confusion when the evaluator goes into the local group policy editor and does not see the evaluation settings configured. We have tried to make clear exactly what is happening in the documentation, and may not have succeeded. The problem was that pushing the evaluation settings into the local group policy itself would have required a custom installer action that was really outside the scope of the project.