Skip to main content

Remotely Restart the FileWave Windows Client Service with PsExec

What

Use

UsingMicrosoft PsExec to remotely restart the "FileWaveWinClient" Windows service allows you to remotely manage the FileWave client on Windows devices. This can be useful in situations where the client is not functioning properly and needs to be restarted in order to resolve the issue.

When/Why

There may be a variety of reasons why you would need to remotely restart the FileWaveWinClient service on a remote Windows device.device Some common reasons include:

    The service has stopped functioning properly and needs to be restarted in order to resolvewhen the issueClient is not responding through normal FileWave commands.

    The service needs to be restarted in order to apply a configuration change

    The service needs to be restarted as part of a troubleshooting process

    How

    To use PsExec to remotely restart the FileWaveWinClient service,Before you willstart first

    • Download needPsExec tofrom downloadMicrosoft andSysinternals.
    • Use installan PsExecaccount with local administrator rights on the devicetarget fromdevice.
    • Confirm whichthat youyour willWindows befirewall, initiatingadmin shares, and organization security controls permit approved remote administration.
    • Do not put an administrator password in the restart.command PsExecline. canIf bealternate downloadedcredentials fromare required, omit PsExec’s -p value and enter the Microsoftpassword TechNetat websiteits (https://docs.microsoft.com/en-us/sysinternals/downloads/psexechidden ).prompt.

    Open a remote shell

    OnceFrom youan haveelevated PsExecCommand installed,Prompt you can usein the followingPsTools commandfolder, toreplace remotely restart the FileWaveWinClient service:

    psexec \[remote device] -u [username] -p [password] net start "FileWaveWinClient"

    Replace [remote device]computername with the hostnametarget orWindows IPdevice:

    address
    psexec64 \\computername -h cmd

    If your download contains PsExec.exe instead of PsExec64.exe, use that executable name. Type exit when you are finished with the remote device,shell.

    Restart the FileWave Client service

    Run these commands inside the remote shell:

    sc.exe query FileWaveWinClient
    sc.exe stop FileWaveWinClient
    sc.exe start FileWaveWinClient
    sc.exe query FileWaveWinClient

    The final query should report a RUNNING state. Then confirm that the device checks in to FileWave again.

    If the service does not restart

    • If PsExec returns Access is denied, verify the account’s rights and [username] and [password] with the appropriateremote-administration credentialsprerequisites before retrying.
    • If security software blocks PsExec, use your organization’s approved remote-management tool instead of weakening endpoint protection.
    • Review C:\ProgramData\FileWave\fwclient\fwcld.log for the remoteservice device.error.
    • Use qc
      • Microsoft TechNet: PsExec (https://docs.microsoft.com/en-us/sysinternals/downloads/psexec )

      Digging Deeper

      In additionFileWaveWinClient to using PsExec to remotely restartinspect the FileWaveWinClient service, you can also use the "net" and "sc" command-line tools to query and change Windows services.

      To query aconfigured service using "net", you can use the following command:

      net start [service name]

      This will display the status of the specified service.

      To start or stop a service using "net", you can use the following commands:

      net start [service name] net stop [service name]

      To change the startup type of a service using "net", you can use the following command:

      net start [service name] [startup type]

      Valid startup types include: boot, system, auto, demand, disabled

      To query a service using "sc", you can use the following command:

      sc query [service name]

      This will display detailed information about the specified service, including its status, startup type, and binary path.

      ToDo startnot orchange stopthem unless troubleshooting has identified a servicespecific usingconfiguration "sc",problem.

      you

      Related canContent

      use