CA Service Desk Manager (CA SDM) Version Control does not seem to function in Advanced Availability environment. An example would be that an Option was installed on the Background Server per the recommended approach/steps, but the application server never seems to get that option.
In the stdlogs within Service Desk, version control should write messages similar to the following when it runs correctly:
Ver_CTRL 6312 SIGNIFICANT pdm_ver.c 743 Version Control starting as TARGET SERVER
pdm_ver 6312 SIGNIFICANT pdm_ver.c 811 Version control running as RFBroker (pdm_rfbroker_nxd)
pdm_ver 6312 SIGNIFICANT pdm_ver.c 936 Fast channel connection made to Version Server
In some cases there is an NX.env variable, @NX_RF_OVERRIDE_LINKED, that causes a different set of log entries to be written instead similar to these:
01/06 22:23:45.20 servername Ver_CTRL 4628 SIGNIFICANT pdm_ver.c 743 Version Control starting as TARGET SERVER
01/06 22:23:45.20 servername pdm_ver 4628 SIGNIFICANT pdm_ver.c 811 Version control running as RFBroker (pdm_rfbroker_nxd)
01/06 22:23:45.20 servername pdm_ver 4628 SIGNIFICANT pdm_ver.c 852 Override server linked attribute set
01/06 22:23:45.20 servername pdm_ver 4628 SIGNIFICANT pdm_ver.c 855 TARGET SERVER version control completed successfully
01/06 22:23:45.20 servername proctor_servername 3860 SIGNIFICANT pdm_process.c 923 Process stopped D:/Program Files (x86)/CA/SERVIC~2/bin/pdm_ver -s -r return: 0
01/06 22:23:45.20 servername proctor_itsdprd1a 3860 SIGNIFICANT pdm_process.c 932 Stopped: D:/Program Files (x86)/CA/SERVIC~2/bin/pdm_ver -s -r
01/06 22:23:45.71 servername pdm_d_mgr 4692 SIGNIFICANT daemon_obj.c 1798 Transient process (appserver_ver_ctl) finished with return (0)
There are no other indications as to why version control is not running, however the server will not have any files updated by version control upon startup.
Deinstall the option RF_OVERRIDE_LINKED via pdm_options_mgr (Refer to http://www.ca.com/us/support/ca-support-online/product-content/knowledgebase-articles/tec612988.aspx for details on how to deinstall this option)
Once this is done, you can also manually verify that it was uninstalled in each server's NX.env file. When it is uninstalled, it should look similar to this:
! @NX_RF_OVERRIDE_LINKED= Deinstalled <date>
Note: If this option is installed/enabled on one server (and version control pushes it to other servers), those other servers will not regain version control if the option is uninstalled on the original server (since version control would be the process removing this variable).