These are the possible causes:
1. pdm_configure has been run.
2. NX.env has been manually edited.
3. pdm_options_mgr has been run.
4. the Service Desk Manager service has been restarted.
5. the Service Management installer has been run.
6. the information in the Options table of the mdb has been changed.
Release : 17.2
Component : SERVICE DESK MANAGER
Whenever pdm_configure is run, the values get regenerated from a combination of the Options table and the $NX_ROOT\pdmconf\NX.env_nt.tpl file.
It is possible, although not recommended, to edit the NX.env file and the NX.env_nt.tpl files directly.
It is possible to cause changes to the NX.env file by running the "pdm_options_mgr" command with either "-a pdm_option.inst" or "-a pdm_option.deinst" AND without the "-t" parameter. Likewise, it is possible to change the NX.env_nt.tpl file by running the pdm_options_mgr command with either "-a pdm_option.inst" or "-a pdm_option.deinst" AND with the "-t" parameter.
It is possible to cause changes to the NX.env file by running the "pdm_options_mgr" command without any parameters.
When the Service Management installer is run, the user must enter various parameters for the installer to proceed, once the "Install" button is pressed, values in the Options table of the mdb, in the $NX_ROOT\NX.env file, and in the $NX_ROOT\pdmconf\NX.env_nt.tpl may be updated; as well, the pdm_options_mgr may get run by the installer.
It is possible, although not advisable, that the Options table could be updated via pdm_extract/pdm_load or directly via a DBMS tool.