This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Is any one else seing this alert - Shh/Updater-B False positives

Virus/spyware 'Shh/Updater-B' has been detected in "C:\Program Files\Sophos\Sophos Anti-Virus\Web Intelligence\swi_update.exe". Cleanup unavailable. This is trickling in as alerts but at an alarming rate.

:29723


This thread was automatically locked due to age.
Parents

  • HealthAdmin wrote:

    Hello

    Could you give us an example for the psexec syntax to be fully functional with your FixUpdate.vbs Script please?

    Cause I have error code 1 or incorrect parameter errors.

    For example:

    C:\Users\chaminade-d\Desktop\sophos>psexec \\machinename -u domain\adminaccount -p password -i cscript //nologo \\server\share\scripts\FixUpdate.vbs /fixIssues:true /cid:\\srv-sophos\sophosupdate\cids\s003\savscfxp /updateNow:true

    I get an "incorrect parameter error"

    Thanks


    Hey,

    Not sure about your syntax. If I had to guess PSEXEC is getting confused with the forward and back slashes after your -i switch.

    What you might want to try is calling your VBscript from within a batch script. Then use PSEXEC to push out the batch script.

    psexec @filelist -u domain\adminaccount path-to-your-batch-script.bat

    You can leave the -p switch out and when you hit enter, it will prompt for the password. This way you don't have to make your password visible on the cmd.

    :32171
Reply

  • HealthAdmin wrote:

    Hello

    Could you give us an example for the psexec syntax to be fully functional with your FixUpdate.vbs Script please?

    Cause I have error code 1 or incorrect parameter errors.

    For example:

    C:\Users\chaminade-d\Desktop\sophos>psexec \\machinename -u domain\adminaccount -p password -i cscript //nologo \\server\share\scripts\FixUpdate.vbs /fixIssues:true /cid:\\srv-sophos\sophosupdate\cids\s003\savscfxp /updateNow:true

    I get an "incorrect parameter error"

    Thanks


    Hey,

    Not sure about your syntax. If I had to guess PSEXEC is getting confused with the forward and back slashes after your -i switch.

    What you might want to try is calling your VBscript from within a batch script. Then use PSEXEC to push out the batch script.

    psexec @filelist -u domain\adminaccount path-to-your-batch-script.bat

    You can leave the -p switch out and when you hit enter, it will prompt for the password. This way you don't have to make your password visible on the cmd.

    :32171
Children
No Data