# 10. Automated Synctool synchronization using Windows Task Scheduler

## Introduction

This document explains how to automate synchronizations with the Zivver Synctool via the Windows Task Scheduler. The Synctool has no built-in feature to run automatically, therefore the Task Scheduler must be used to automate synchronizations.

## Setting up Windows Task Scheduler

01. Open Task Scheduler from the Windows menu.
02. In the right pane, click **Create Basic Task...**.
03. Enter a name.

_For example: Zivver Synctool_
04. Click **Next >**.
05. Select **Daily**.
06. Click **Next >**.
07. Select a time that is convenient.

_Zivver recommends to select a time outside of office hours._
08. Click **Next >**.
09. Select **Start a program**.
10. Click **Next >**.
11. Browse to the Synctool folder and double-click the `Zivver.Synctool.App` executable.
12. At **Add arguments (optional):** enter the following parameters:

`-s`

_This will run the Synctool in the background (Silent Mode). This parameter is required to run the Synctool automatically._

`-p "Full-path-and-file-name"`

_Open the Synctool profile, go to **Profile** \> **Profile Details** and copy and paste the entire string under **Profile location**._

`-p "c:\zivver\configuration\account-synchronisation.xml"`

Tip

The argument field for running the Synctool will usually look something like this:

`-s -p "c:\zivver\configuration\account-synchronisation.xml"`

13. Click **Next >**.
14. Click **Finish**.

Tip

If you want to run multiple synchronization profiles, then you should create a new **Action** in the scheduled task for each synchronization profile you wish to run.

## How do you know it worked?

You can find the task in the **Task Scheduler Library** and run it manually to verify the task works. If the task works correctly you will either see newly created accounts in the Zivver admin portal or find logs in the configured logs and events folder.

### Security options

Open **Properties** of your Synctool task by double-click it from the Task Scheduler Library. At **Properties** you can specify if you want to run the task whether the user is logged in or not. Zivver recommends enabling this feature. If you do not turn on this property, Zivver accounts will not be updated automatically when the user assigned to execute the task is not logged in.

Note

The service account running this task needs to have the _Log on as batch job_ rights to be able to run the task while the account is not logged in.

Follow the steps in the section below to give the service account the _Log on as batch job_ rights.

#### Enable Log on as batch job rights

The steps below describe how you can enable the _Log on as batch job_ rights for the service account.

01. Press the `Win + R` keys on your keyboard to open the Run dialog.
02. In the Run dialog, type `secpol.msc`.
03. Press `Enter` to open the Local Security Policy Editor.
04. In the Local Security Policy window, locate the **Local policies** folder in the left-hand menu.
05. Expand **Local policies** by clicking on the arrow next to it.
06. Click on **User Rights Assignment** to display the available policies in the right-hand pane.
07. In the list of policies on the right, scroll down to locate **Log on as batch job**.
08. Double-click on **Log on as batch job** to open its properties.
09. In the policy dialog box that appears, click the **Add User or Group...** button.
10. In the dialog box that appears, click **Advanced...** to open advanced search options.
11. Click **Find Now** to see a list of available accounts.
12. Select the service account from the list, or manually type the account name (e.g., `Domain\AccountName` for domain accounts or `.\LocalAccountName` for local accounts).
13. Click **OK** to confirm the selection and close the dialog.
14. In the **Select Users, Computers, Service Accounts, or Groups** dialog box, click **OK**.
15. In the policy dialog box, click **Apply** to save the changes.
16. Click **OK** to close the dialog box.
17. Once the changes are saved, close the Local Security Policy Editor window.

_Depending on your system configuration, the changes might require a restart to take effect._
18. If necessary, restart the server to ensure the policy is applied.

Updated on 2025-11-10