Here is a list of command line parameters that the Spybot-S&D main executable (spybotsd.exe) supports:
/taskbarhide
Runs Spybot-S&D completely hidden (no window, no taskbar icon), so make absolutely sure you use it only in combination with /autoclose (otherwise it would remain in memory sitting idle). Useful only in combination with /autocheck, /autoupdate or /autoimmunize, as it cannot be controlled when completely invisible.
/minimized
Starts the window minimized.
/uninstall
Uninstalls Spybot-S&D. This command line parameter is very outdated - unins00.exe should be used instead!
/blinduser
Starts with support for blind users (special menus).
/autoupdate
Does an update after starting the program.
/autocheck
Starts scanning immediately.
/autofix
Fixes problems after scan.
/autoclose
Closes program after it has scanned or updated.
/autoimmunize
Runs the immunization at program start.
/onlyspyware
Fixes only spyware (red) entries with /autofix, leaving all usage tracks as they are.
/easymode
Starts with easier interface for newbies.
And here is a list of command line parameters that the Spybot-S&D installer (spybotsd12.exe) supports:
/silent
Will display the progress during installation, but not the wizard.
/verysilent
Even the progress will not be shown. Errors etc. would still be shown.
/nocancel
Disables the Cancel and Close button. Useful with /silent.
/dir="x:\dirname"
Installs into that directory instead of the default one.
/group="folder name"
Installs into a program group of that name instead of the default one.
/noicons
Avoids creation of any icons for the installed softwae.
/components="comma separated list of component names"
Installs the given components instead of the default ones. Components are main, blind (icons for blind users), language (all language files) and skins.
If Not objFSO.FileExists(strLocalPath & "spybotSD.exe Then objShell.Run Chr(34) & strInstallPath & "\spybotsd13.exe" & Chr(34) & " /silent /nocancel /noicons", 1, True
objFSO.CopyFile strInstallPath & "\Default configuration.ini", strLocalPath & "Default configuration.ini", True
End If
If objNamed.Exists(LCase("Scan")) Then objShell.Run Chr(34) & strLocalPath & "SpybotSD.exe" & Chr(34) & " /autoupdate /autocheck /autofix /autoclose /immunize", 1, True
If objNamed.Exists(LCase("RunOnce")) Then objShell.Run Chr (34) & strLocalPath & "unins000.exe" & Chr(34) & " /silent"
Set objShell = Nothing
Set objFSO = Nothing
This script can be run with two parameters -/scan and /runonce. /scan means after install system will be automatically scanned for spyware (of course after machine is updated) and immunized, /runonce means after running script SpyBot will be uninstalled.
Spybot - Search & Destroy V1.3 repacked with InstallShield Repackager.
With a little bit of fine tuning, Spybot can be packaged up real nice into an msi for GPO deployment. Use the "Installation Monitoring" method.
Run the setup and after it completes, run the program. Do an on-line update to get the new definitions. Configure all of the settings as you'd like them to be. Consider your target audience when doing this as Spybot has a lot of automation and silent features.
My preference is to set the program to download updates, autoscan, autofix, autoinnoculate, and then autoclose when the program is run. Make sure the options for using System Restore are disabled (as you should really disable System Restore anyway). After you finish making your settings, close Spybot. Open the file Configuration.ini found at the path \Documents and Settings\All Users\Application Data\Spybot - Search & Destroy. These are the settings you just made. If you would like to have these settings apply to new users, transfer the appropriate entries to the file Default configuration.ini found at the path \Program Files\Spybot - Search & Destroy.
In your repack directory, edit the file Updated.isr. There should be a significant amount of registry entries. If any of them are complete SIDs (ie actual users), delete them. Make sure to keep the entries for HKEY_USERS\.DEFAULT, HKEY_USERS\S-1-5-19, HKEY_USERS\S-1-5-20. These will "innoculate" the Default user and system accounts.
Finally, in the repack directory, edit your .inc file. You will need to modify the .ini file section to reflect the settings discussed above. Now you can build.
If you would like to schedule Spybot to run on all of your computers after the GPO deployment, you can use this as a startup script or plug it into an existing startup script.
Option Explicit
Dim strComputer, objWMIService, colScheduledJobs
strComputer = "."
Set objWMIService = GetObject("winmgmts:" & "{impersonationLevel=impersonate}!\\" & strComputer & "\root\cimv2")
Set colScheduledJobs = objWMIService.ExecQuery("Select * FROM Win32_ScheduledJob")
'**********************************************************************
'** Subroutine; Spybot Scheduling Routine **
'**********************************************************************
Sub SchedSpybot
Dim objService, objNewJob, SpybotRun, JobID
Set objService = GetObject("winmgmts:\\" & strComputer)
Set objNewJob = objService.Get("Win32_ScheduledJob")
SpybotRun = """C:\Program Files\Spybot - Search & Destroy\SpybotSD.exe "" & /taskbarhide /autoupdate /autoimmunize /autocheck /autofix /autoclose"
objNewJob.Create SpybotRun, "********003000.000000-240", True , 1 OR 2 OR 4 OR 8 OR 16 OR 32 Or 64, , , JobID
objNewJob.Create SpybotRun, "********011000.000000-240", True , 1 OR 2 OR 4 OR 8 OR 16 OR 32 Or 64, , , JobID
objNewJob.Create SpybotRun, "********017000.000000-240", True , 1 OR 2 OR 4 OR 8 OR 16 OR 32 Or 64, , , JobID
End Sub
'**********************************************************************
'** Schedule Spybot **
'**********************************************************************
If colScheduledJobs.Count = 0 Then SchedSpybot
I've been using this with some clients for some time now and it works beautifully. The scheduling of Spybot in this fashion is especially nice since Spybot will run under the credentials of the System, eliminating any problems with non-administrators being logged in.
Using the command lines above, the following batch file can be used to install and start a automatic scan of the PC and uninstall. On a installed PC, modify the Default configuration.ini so Legals=1. Then place that file in the source so it can be copied to the destination.
cls
@Echo off
title Installing and Running SpyBot
color f1
echo Checking to see if it's installed
if not exist "c:\Program Files\Spybot - Search & Destroy\SpybotSD.exe" goto install
Reviews related to PepiMK Software Spybot Search and Destroy
This website uses cookies.
By continuing to use this site and/or clicking the "Accept" button you are providing consent
Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our
websites or when you do business with us. For more information about our
Privacy Policy and our data protection
efforts, please visit
GDPR-HQ
