KACE
AppDeploy

Spybot Search and Destroy 1.x
Company: PepiMK Software
Setup Type: Legacy setup with no known support
Package Difficulty Rating: Easy (1) [ Rate It or View Ratings ]
Most Commonly Reported Method: Repackaged (EXE)
Record Created On: 3/8/2004
Number of Views: 28,374
 
  
 
Software Knowledge Base: The software knowledge base contains details on over 60,000. The closest record matching this software package is displayed here. Browse the Software KB directly to find similar records.

No record in the Software KB was found to match this package.

Download the AppDeploy Scanner   Browse the Software KB
 
 
Command Lines: Command line details for installation and removal of this software. Details may include available command line arguments and/or public properties.

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.

Above Entry Provided on 2/11/2004 by francisg 		Rate It
 Rating
119

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

goto Scan

:Install
T:\Scripts\spybot\spybotsd13.exe /silent /nocancel /noicons
copy "T:\Scripts\spybot\Default configuration.ini" "c:\Program Files\Spybot - Search & Destroy"

:Scan
"c:\Program Files\Spybot - Search & Destroy\SpybotSD.exe" /autoupdate /autocheck /autofix /autoclose /immunize

"C:\Program Files\Spybot - Search & Destroy\unins000.exe" /silent

:End

Above Entry Provided on 6/15/2004 by jparekh 		Rate It
 Rating
2

Unins000.exe can uninstall silently.

C:\Program Files\Spybot - Search & Destroy\unins000.exe /silent
will show a reboot dialog and let user choose to reboot or not.

C:\Program Files\Spybot - Search & Destroy\unins000.exe /verysilent
will uninstall and auto-reboot.

Above Entry Provided on 2/7/2008 by graywalker 		Rate It
 Rating
120
Add an Entry
 
 
Notes: Shared "notes from the field" covering how to handle the automated installation of this software.

You can customize almost everything for this software in the DEFAULT CONFIGURATION.INI file found in the installation directory.

Above Entry Provided on 2/11/2004 by francisg 		Rate It
 Rating
118

I edited code from fparekh -

'Automatic install, scan and deinstall of SpyBot
' Martin Zugec
' 22.6.2004
' Supported parameter are /scan, /install and /runonce

Option Explicit

Dim objShell, objFSO, objNamed
Dim strLocalPath, strInstallPath

Set objNamed = WScript.Arguments.Named
Set objShell = Wscript.CreateObject("Wscript.Shell")
Set objFSO = CreateObject("Scripting.FileSystemObject")

strInstallPath = Left(WScript.ScriptFullName,Len(Wscript.ScriptFullName) - Len(WScript.ScriptName + "n"))
strLocalPath = "C:\Program Files\Spybot - Search & Destroy\"

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.

Above Entry Provided on 6/22/2004 by Soulin 		Rate It
 Rating
117

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.

Above Entry Provided on 9/16/2004 by EarlyMorningHours 		Rate It
 Rating
117
Add an Entry
 
 
Virtualization: Information regarding how to work with this software in creating a virtual deployment package for products like Altiris SVS and Microsoft SoftGrid.

No information at this time. Discuss this package in the forum or click here if you have something to contribute!

 
 
Terminal Services: Notes on how to address problems working with this software in a Terminal Services session as with Citrix shared environments.

No information at this time. Discuss this package in the forum or click here if you have something to contribute!

 
 
Related Links: Additional resources to reference in regards to the deployment and configuration of this software.
 
Security Information: Details covering which files, directories and/or registry entries must be opened to standard users for operation in a locked down environment.

No information at this time. Discuss this package in the forum or click here if you have something to contribute!

 
 
Discussion threads: Discussion topics in the AppDeploy message boards that have been linked as relevant information to this entry.
 

 


Report a problem
  Printer Friendly Version