Following are few important Use Cases or Scenarios where this article would come in handy-
- When there is a need to modify the CFG file located at C:\inSync4\users\username folder, the inSync service needs to be stopped and started for the changes to take effect.
- When there is a client db corruption and C:\inSync4 folder needs to be renamed. In this scenario, the running inSync processes needs to be killed manually from task manager.
- When inSync agent sometimes doesn't launch and existing process needs to be killed.
The processes for inSync client are as follows-
All the above binaries are located at C:\Program Files (x86)\Druva\inSync
- From the remote machine, open services console.
- Click on Action tab - Connect to another computer.
- Browse and select the desired client machine - click on OK.
- If the connectivity is fine, then it should open up the services console for the other machine.
- You can then stop/start the Druva inSync Client service easily.
You can stop the services remotely using command line utility named PsExec.
Download Link: https://technet.microsoft.com/en-us/sysinternals/psexec.aspx
Usage: psexec [\\computer[,computer2[,...] | @file]][-u user [-p psswd][-n s][-r servicename][-h][-l][-s|-e][-x][-i [session]][-c [-f|-v]][-w directory][-d][-<priority>][-a n,n,...] cmd [arguments]
Force Close inSync processes remotely
To force close any running inSync processes after stopping the service (inSyncCPHwnet64.exe),
Connect using command
Tasklist /S remote system (name or IP address) /U username /P password
once connected, you should see all the processes running on the remote machine.
You can kill the inSync processes using the command
Taskkill /S remote system /U username /P password /IM Process
Example: Taskkill /S remote system /U username /P password /IM inSyncAgent.exe