Best Practices - HP t5630 - Thin Client Using Manual

Best Practices

HP recommends the following best practices when configuring the HP DHCP Settings Update
Client.
Best Practice
If you apply a computer name change,
the Shutdown option in XpePrep should
equal Shutdown or Reboot, and the
CommitEWF option should be set to
Yes.
If you select Yes for CommitEWF, the
Shutdown option should be set to Reboot
or Shutdown.
If you select No for CommitEWF, then
you should not set the Shutdown option
to Reboot or Shutdown. The
recommended setting is None.
If you do not specify a SettingsVersion,
or the SettingsVersion is set to 0, then
you should not set the Shutdown option
to Reboot or Shutdown. The
recommended setting is None.
If you change the password on the
Administrator account, then the computer
name changes will only be applied when
users with administrative privileges logon
to the machine.
In order to process the CommitEWF or
Shutdown options, other settings must be
specified.
Explanation
Changing the computer name requires a reboot in
order to take effect. If you apply a computer name
change and do not commit the change to the EWF
protected volume, the name change will be lost
during the reboot.
Data in the EWF overlay is not committed to the
protected volume until the system shuts down. Any
changes made to the system after the HP DHCP
Settings Update Client runs (and commits the EWF
overlay) will be saved.
If the EWF Overlay is not committed to the protected
volume, then the client will not preserve the
SettingsVersion. This will cause the client to
process the settings and apply the Shutdown option
every time a user logs in. This would put the system
in an endless loop of booting, logging-in, and
rebooting.
Not specifying the SettingsVersion, or setting it
equal to 0 will cause the client to always apply the
settings and process the Shutdown option. This
would put the system in an endless loop of booting,
logging-in, and rebooting.
Changing the computer name requires
administrative access. The client depends on
impersonating the Administrator account in order to
apply computer name changes when running as a
"Guest" user. For security reasons, a method of
communicating a password change to the client has
not been established.
These options will not be processed unless other
settings have been specified. This is done to ensure
that there are no unnecessary reboots or writes to
the flash storage media.
7