In order for scheduled tasks to run while a user is logged out, the user must
have batch logon privileges. The simplest way set this up is to add the user to
the 'Backup Operators' group. Steps for how to accomplish this are as follows:
- As the Administrator - open Computer Management which can be found in Programs --> Administrative Tools
- Navigate to Local Users and Groups --> Groups
- Right click the 'Backup Operators' group and select Properties
- At the bottom of the 'Backup Operators' Properties window, click Add
- Enter the user who will be running the batch mode backup and then click OK
- Click OK to close 'Backup Operators' Properties and close the Computer Management
- Next - open Task Scheduler which can be found in Programs --> Accessories --> System Tools --> Task Scheduler
- Open the Task Scheduler Library folder located on the left
- In the top pane, right click on any open space and select 'Create New Task'
- Enter a name and description (for example: SpiderOak Batchmode)
- Under Security Options, select 'Run whether user is logged on or not.'
- Please make sure that "When running the task, use the following user account:" specifies the user which will perform the backup. Typically, this will be the user you are adding the task with and should be set automatically.
- On the 'Triggers' tab, add a trigger for when you want the task to run
- On the 'Actions' tab, add an Action to start a program. For the Program/script, enter the following:
For 32-bit Systems:
For 64-bit Systems:
C:\Program Files (x86)\SpiderOak\SpiderOak.exe
IMPORTANT NOTE: Include the quotes for the above scripts as they are important.
- In the 'Add arguments (optional)' box, enter: --batchmode
- You may alter the settings on the 'Conditions' and 'Settings' tabs but they do not require adjustment.
- Click OK and you will be then prompted for the credentials of the user that will run the task
IMPORTANT NOTE: The instructions above were created for Windows Server 2008 R2.
Windows Server 2008, Windows 7, and Windows Vista may be similar but have not
been tested fully. Windows Server 2003 and Windows XP will likely be different
but the same principles will most certainly apply.