Scribd
Upload
195 views

Sandboxie Installation and Setup

The document discusses how to configure Sandboxie to make non-multiuser applications multiuser. It provides instructions for setting up shortcuts to sandbox Windows Movie Maker and Kidpix. It also explains how to configure Sandboxie for Success Maker to prevent temp file corruption.

Uploaded by

Alejandro Pons
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
195 views

Sandboxie Installation and Setup

The document discusses how to configure Sandboxie to make non-multiuser applications multiuser. It provides instructions for setting up shortcuts to sandbox Windows Movie Maker and Kidpix. It also explains how to configure Sandboxie for Success Maker to prevent temp file corruption.

Uploaded by

Alejandro Pons
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 5

Sandboxie Installation and Setup

Requirements
OS: Windows XP or Windows Server 2003.
Users must have individual Login accounts for this solution to work.

How Sandboxie works


Once Sandboxie is installed on the Host PC, it does not have to be installed again. Please
purchase and register your Sandboxie software program. Sandboxie is launched when you
launch an application you wish to be sandboxed. See below on how to create the shortcut.
By default Sandboxie will create a sandboxed file store. The software will then copy any files
the application uses, like the exe and dlls and data modules into the sandboxed file store. It
will also create and contain any registry changes, file changes and created files. Thus if you
opened and application that changed a registry setting, you created files with this app and you
opened a virus infected file with this app. All the changes, virus and all would be
trapped/contained in the sandbox file store. To clean this you simply delete the sandbox and it
is like nothing ever happened.
Thus we are leveraging Sandboxie, to make non-multiuser applications, multiuser and have
poked a few holes in the sandboxed file store for our purposes.
The two major holes we have created are.
First to allow any files we create and save to the C:\ drive (example My Documents) to be
saved to the C:\ drive and not the sandboxed file store.
Second is to NOT copy an applications exe, dlls and data modules into the sandboxed file
store. This is for very large applications and or applications that are mapped to a network
drive, to help keep network traffic down. Since the data files are static and not changed by the
student anyway.

To Create a shortcut Icon that will automatically sandbox an application


Create a shortcut on the desktop to movie maker
Right-click the icon and choose properties
Set the target to "C:\Program Files\Sandboxie\Start.exe" "C:\Program Files\Movie
Maker\moviemk.exe"
Set the start in to "C:\Program Files\Sandboxie"
Now you can change the icon by pointing the icon to the program you wish to sandbox.
IE C:\Program Files\Movie Maker\moviemk.exe

To configure Sandboxie Control not to autostart with bootup, but to load


when you run a Sandboxed application.
Choose Start/Programs/Sandboxie/Sandboxie Control
Right-click the yellow kite icon in the systray and choose Open Main Window
Click Options and make sure only Run Sandboxie Control when Sandboxed Program
Runs is the only item with a check mark in front of it.
Choose Function/Exit to close Sandboxie control.
2007 NComputing, Inc

Page 1 of 5

Application 1: Windows Movie Maker


Sandboxie configuration and use for non-multiuser applications, which makes them multiuser and allows the users to save to their created files to C:\Documents and
Settings\(userid)\My Documents. Note: The files created on a Host PC group will only be
available on that Host PC group. See *Note 1 below

Setup:
Install Sandboxie, choose defaults.
Close Sandboxie program via systray icon.
Replace the contents of C:\windows\sandboxie.ini with this.
#### Start of file ####
# Sandboxie Configuration File
# Automatically generated whenever the configuration changes.
# Set ConfigLevel to 99 to prevent the overwriting of this file.
[GlobalSettings]
ConfigLevel=1
BoxRootFolder=%APPDATA%
ForceDisableSeconds=10
FileTrace=.
PipeTrace=.
KeyTrace=.
IpcTrace=.
GuiTrace=.
[DefaultBox]
Enabled=yes
CopyLimitKb=32768
CopyLimitSilent=Yes
OpenPipePath=%Personal%
### the above allows the application user to save any created file to their My
Documents
### example = moviemaker output file or .mov
LingerProcess=acrord32.exe
LingerProcess=jusched.exe
LingerProcess=syncor.exe
BlockDrivers=y
BlockFakeInput=y
BlockWinHooks=y
BoxNameTitle=n
#### END OF FILE ####
Save the changes.

2007 NComputing, Inc

Page 2 of 5

Application 2: Kidpix 4.0


Sandboxie configuration and use for KidPix, making it multi-user and allows the users to save
to their created files to the default file store for KidPix. Which is C:\Documents and
Settings\All Users\Application Data\The Learning Company\Kid Pix\Users\(userid in KidPix)
Note: The files created on a Host PC group will only be available on that Host PC group. See
Note 1 below

Setup:
Install Sandboxie, choose defaults.
Close Sandboxie program via systray icon.
Replace the contents of C:\windows\sandboxie.ini with this.
#### START OF FILE ####
# Sandboxie Configuration File
# Automatically generated whenever the configuration changes.
# Set ConfigLevel to 99 to prevent the overwriting of this file.
[GlobalSettings]
ConfigLevel=1
BoxRootFolder=%APPDATA%
ForceDisableSeconds=10
FileTrace=.
PipeTrace=.
KeyTrace=.
IpcTrace=.
GuiTrace=.
[DefaultBox]
Enabled=yes
CopyLimitKb=32768
CopyLimitSilent=Yes
OpenPipePath=C:\Documents and Settings\All Users\Application Data\The Learning
Company\Kid Pix
### the above is to allow any files the children create and save to be save to the
default
### kipix file store location on the Host PC.
LingerProcess=acrord32.exe
LingerProcess=jusched.exe
LingerProcess=syncor.exe
BlockDrivers=y
BlockFakeInput=y
BlockWinHooks=y
BoxNameTitle=n
#####END OF FILE #####
Save the changes.

2007 NComputing, Inc

Page 3 of 5

Application 3: Success Maker


Sandboxie configuration to use a Mulituser application that stores temp files on the C:\ drive;
that are then imported into the applications database to record a score or test result. Thus the
temp files are getting corrupted as all the users of our software/hardware solution share and
use this C:\ drive location. This will allow sandboxie to place the temp files in the sandbox
file store, thus making them safe from being over written by another student using the same
application at the same time on the same Host PC group.
While not placing the actual application files in the sandbox file store. Thus not causing
undo/unwanted network traffic; possibly coping large amount of data/files that are not
changed. Like the applications exe and data modules.

Setup:
Install Sandboxie, choose defaults.
Close Sandboxie program via systray icon.
Replace the contents of C:\windows\sandboxie.ini with this.
#### START OF FILE ####
# Sandboxie Configuration File
# Automatically generated whenever the configuration changes.
# Set ConfigLevel to 99 to prevent the overwriting of this file.
[GlobalSettings]
ConfigLevel=1
BoxRootFolder=%APPDATA%
ForceDisableSeconds=10
FileTrace=.
PipeTrace=.
KeyTrace=.
IpcTrace=.
GuiTrace=.
[DefaultBox]
Enabled=yes
CopyLimitKb=32768
CopyLimitSilent=Yes
OpenFilePath=LOGIN.EXE,T:\ResultsManager
## where login.exe is the applications exe and T:\path is the path the application
resides,
## this will prevent sandboxie from coping the data modules across the network thus
## saving network traffic.
LingerProcess=acrord32.exe
LingerProcess=jusched.exe
LingerProcess=syncor.exe
BlockDrivers=y
BlockFakeInput=y
BlockWinHooks=y
BoxNameTitle=n
#####END OF FILE #####
Save the changes.
2007 NComputing, Inc

Page 4 of 5

*Note 1 : This will only work per Host PC group. Thus is Johnny uses Host PC group 1 and
saves his creation. Then he can only access the created file from any Terminal or the Host PC
in that Group. But he logs into KidPix on Host PC group 2, KidPix will create a file store for
him, but this saved file remains on Host PC group 1. It is the same for any files created by a
user, unless his/her My Documents is to a mapped network drive.
For more information about Sandboxie.ini setup file, go to.
http://www.sandboxie.com/index.php?SandboxieIni
For general Sandboxie help go to
http://www.sandboxie.com/index.php?HelpTopics
Other Quick Notes on the sandboxie ini file:
Edit Sandboxie.ini which resides in C:\Windows, and add the statement below in the
[DefaultBox] section
OpenPipePath=%Personal%
This will disable the sandboxing of the user's My Documents, and any files saved
there, or below that folder, thus bypassing the sandboxed file store and be saved to the
real folder.
or you can open the parts as you specify the path.
OpenPipePath=C:\Program\files\applicationX
or look in your registry at
[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Shell
Folders]

Anything that is listed there can be a %item% or you can create your own as needed.

2007 NComputing, Inc

Page 5 of 5

You might also like