Scheduling Problems

<< Click to Display Table of Contents >>

Navigation:  Using SyncBackPro > Basic Operation > Creating a Schedule >

Scheduling Problems

 

Windows Security

 

Security settings in Windows are very important when it comes to scheduled tasks:

 

oRun only when user is logged on: This option is available for all users.

 

oRun whether user is logged on or not: For this option to be available, you must have the "Log on as a batch job" user right. If you are an administrator user then it is likely you already have this right. However, standard non-administrator users in Windows do not have this access right. You must use the Local Security Policy editor in Windows and assign the right to the appropriate user.

 

oRun whether user is logged on or not (do not store password): For this option to be available, you must have the "Log on as a batch job" user right and also be a Windows administrator.

 

uac Also, if you create a schedule with SyncBack while elevated, then that scheduled task cannot be edited or deleted by SyncBack if it is not run elevated.

 

 

Common Problems

 

The Scheduler Monitor Service detects profiles that are not being run by the Windows Task Scheduler. There are a number of possible reasons why the scheduled task may not run:

 

Check to see what error message is returned from the Windows Task Scheduler. On Windows 10 you can do this by Start > Windows Administrative Tools > Task Scheduler. Expand the tree on the left so it is Task Scheduler (Local) > Task Scheduler Library > 2BrightSparks > SyncBack > [your username].

 

You must use your Windows login password. You cannot use your login PIN or Windows Hello. It must be your Windows login password. This is a requirement of Windows, not SyncBackPro.

 

If you change your Windows login password then you must remember to change the password for your scheduled tasks. You only need to update the password for one schedule. Windows will automatically update the password for all other scheduled tasks using the same Windows account.

 

You are using the wrong username and/or password. You must use your Windows login password.

 

The scheduled task may not be set-up correctly to wake the computer if it is hibernating or in standby mode.

 

The scheduled task may have the option Start the task only if the computer is on AC power enabled (which is the default) and your computer (notebook, laptop, etc.) may be using batteries and not mains power.

 

The scheduler may be stopped or not installed. See your Windows documentation for details on how to start or install it.

 

Profiles are user specific, they are not visible to every user on the computer. This means when you create a profile under a Windows username, and logout and login as a different Windows user, then you will not see the profile created as the other user. When scheduling a profile make sure your scheduled task is being run as the user who created the profile (this is the default when new schedules are created).

 

If you are a member of a domain check that the correct username is being used for the scheduled task. By default your local (machine) username may be used, but it may be that you must use your domain username (domain\username).

 

You should also make sure the user account has the necessary Windows user rights. To do this, run the Local Security Policy control panel applet (in the Administrative Tools section of the control panel). If you are using the home version of Windows then you may not have access to the Local Security Policy control panel applet (Microsoft have removed the feature from home versions of Windows).

 

Make sure that the user account has the following user rights:

 

Act as part of the operating system

Log on as a batch job

Log on as a service

 

Make sure the user account is not listed in the following user rights:

 

Deny logon as a batch job

Deny logon as a service

 

 

All Content: 2BrightSparks Pte Ltd © 2003-2024