Skip to main content
Question

Auto-start services when OS starts and LiveSync

  • March 12, 2026
  • 0 replies
  • 11 views

Forum|alt.badge.img+5

Hi,

In the CommServe LiveSync (11.40) environment on the active server, the “Auto-start services when OS starts” option is grayed out.

Only after entering the following commands can the checkbox be selected:


gxadmin.exe -consoleMode -enableautostartoption true

gxadmin.exe -consoleMode -setsvcstartmode Automatic

 

...but after some time the checkbox becomes inactive again.

 

The following article contains that this option is managed by failover.

https://documentation.commvault.com/11.40/software/enabling_or_disabling_commserve_livesync.html

“After you enable the CommServe LiveSync feature, the Auto-start services when OS starts option in process manager is disabled and controlled by the CSLiveSync feature.”

 

During failover, it disables all services on one Commserve and enables them on the other, then does the opposite during failback. It also reverses live sync replications and a few other things.

However, shouldn't this checkbox be checked in such a normal scenario? Shouldn't it be checked and grayed out (preventing manual changes)?

This description from the documentation refers more to the fact that this checkbox is “greyed out” - not whether it should be checked or unchecked.

 

Is this a bug or intentional behavior?

 

Regards,

Michał

Forum|alt.badge.img+4
  • Vaulter
  • March 12, 2026

Hi Michal,

 

As you noted, per the article, when CSLiveSync is enabled the box is greyed out and then service management is handled by the CSLiveSync feature.

 

Checking this box in a normal configuration just sets the services in the Windows service control manager to start Automatically as opposed to manually. 

 

Therefore, I believe what you’re seeing makes sense for a LiveSync environment, as Commvault does not want Windows to make decisions about which services should and should not be started.

 

We need to ensure only one set of Commserve services are running as when the Commserve services are running on both nodes it can lead to undesired behaviour.

 

I believe that the second instance on both Commserves can be set to start automatically, as Instance002 is running the sync operation, Instance001 is the Commserve.

 

I hope this answers the question.

 

Regards,
David Dwyer