Environment
NetIQ AppManager 6.x
NetIQ AppManager 7.0.x
NetIQ AppManager 7.0.x
Situation
How does the SvcWaitInterval registry value function?
Resolution
The SvcWaitInterval (HKEY_LOCAL_MACHINE\SOFTWARE\NETIQ\AppManager\4.0\NetIQmc\Config\SvcWaitInterval) registry value works in conjunction with the ServiceDependency (HKEY_LOCAL_MACHINE\SOFTWARE\NETIQ\AppManager\4.0\NetIQmc\ServiceDependency) registry value. The SvcWaitInterval delays the startup of the NetIQ AppManager Client Resource Manager service (NetIQmc) by the X number of seconds for any service listed in the ServiceDependancy list that does not start.
The SvcWaitInterval does not work independent of the ServiceDependency registry value. So if a data value is entered for the SvcWaitInterval registry value, and no services are listed under the ServiceDependency registry value, then nothing will be affected.
Be aware though that if the service does start there is no delay introduced into the start-up of the agent. The wait interval is dependant upon a service in the list not starting, or taking time to start in order to cause the Netiq Client Resource Monitor to delay start-up.
In order to configure the setting so that you will always delay the start of the netiqmc service, you should include in the serviceDependancy list an installed service that is disabled.
If you list SNMP & W3SVC as data values for the ServiceDependency registry value, enter the data value of 20 for SvcWaitInterval registry value, and the SNMP service does not start (for what ever reason) then the NetIQmc service will wait 20 seconds for the SNMP service to start, then check for the W3SVC service. If that service has not started the netiqmc will wait another 20 seconds. If the W3SVC service is already started there is no additional delay.
The SvcWaitInterval does not work independent of the ServiceDependency registry value. So if a data value is entered for the SvcWaitInterval registry value, and no services are listed under the ServiceDependency registry value, then nothing will be affected.
Be aware though that if the service does start there is no delay introduced into the start-up of the agent. The wait interval is dependant upon a service in the list not starting, or taking time to start in order to cause the Netiq Client Resource Monitor to delay start-up.
In order to configure the setting so that you will always delay the start of the netiqmc service, you should include in the serviceDependancy list an installed service that is disabled.
If you list SNMP & W3SVC as data values for the ServiceDependency registry value, enter the data value of 20 for SvcWaitInterval registry value, and the SNMP service does not start (for what ever reason) then the NetIQmc service will wait 20 seconds for the SNMP service to start, then check for the W3SVC service. If that service has not started the netiqmc will wait another 20 seconds. If the W3SVC service is already started there is no additional delay.
Additional Information
Formerly known as NETIQKB717