The NVDD Configuration File234 Client NamingUpdating ClientName from ClientWhen a client name has been set using the NVD protocol, it can beupdated from the client side. At shutdown time the client sends amessage to the NVDD server in which the client’s name is embed-ded. If the client name has changed or does not exist, the NVDDserver can then record this name in the nvdd configuration file. Thisfeature can be disabled using the save_name property of the clientobject so that unauthorized clients cannot actually change theirname.If you set the default global property default_save_name to falseand the property everybody.save_name to true, this has the resultthat unknown clients (not identified by a unique MAC or IP address,belonging to “everybody” subnet), can store their name on the NVDserver, but then this name cannot be changed unless the configura-tion file is modified so that the client has its save_name property setto true.If existing clients (identified by a unique IP or MAC address) do nothave their own save_name property, their default behaviour is ruledby the value of the global parameter default_save_name.For example, if the client name has changed (using a Windows Sys-tem applet or by manipulating the registry), and if the propertysave_name is set to true for the client (or IP range if the client is notuniquely defined), the new name can be stored on the server side sothat it will be used at next boot (standard Windows behaviour). Thiswill also be the case if the global parameter default_save_name isset to true and the client has a unique definition but no save_nameproperty.Note: The property save_name is set to false by default.The property is NOT propagated. This means that, though every-body.save_name is set to true, a client that does not have the prop-erty save_name explicitly set to true will not be able to change itsname from the client side (even if that client is a member of thegroup everybody), unless the global parameter default_save_nameis set to true.
