Modul Auftraege

Tasks - Single scan job 

The New scan job window lets administrators define a single or periodic scan job. A complete job configuration consists of three aspects: Job scheduling, Scanner settings and Analysis scope, each covered by their respective window tabs.

Which options are available on the tabs depends on the type of client that the job is being planned for. For example, when planning a job for an Exchange server (if Exchange Mail Security has been installed), options that deal with threats specific to desktop clients are not available.

Job scheduling

The Job scheduling tab lets you plan the scan job:

• Job name: Specify which name the scan job should have. You can enter meaningful names here such as Archive scan or Monthly scan to clearly label the job so that it can be found again in the table overview.
• Schedule (Periodic scan job): For periodic scan jobs, this option specifies when and at what intervals the virus check should occur. If you select On system startup the scheduling defaults no longer apply and the G DATA software will run the scan each time your computer is restarted. For Daily jobs, you can specify under Weekdays on which specific days of the week the job should be carried out.
• Time: Use this option to set a specific start time. For single scan jobs without start time, the scan job will be started immediately after creation.
• Settings
  • Allow the user to halt or cancel the scan job: Permissions can be granted to the users for pausing or aborting the job via the system tray context menu.
  • Notify the user when a virus has been found: Displays a notification on the client when a virus is found.
  • Report scan progress to the ManagementServer (every 2 minutes): Enable this option to report the status of a scan job to the server.
  • Shut down client after scan job, if no user is logged on: The client can be shut down automatically after the scan job is finished.
  • Run scan job later if a client is not powered up at the scheduled time: If a computer is not switched on at the scheduled time of a periodic scan job, the scan job can be started later by ticking this option.
• User context (optional): If the scan job includes network shares, they should be entered as a UNC path instead of using mapped network drives. If the client's machine account (e.g. Client001$) has no permissions to access a share, enter a User name and Password for an account with the appropriate permissions here.

Scanner

The Scanner tab shows the settings with which the scan job will be executed. The following options are available:

• Use engines: The G DATA software works with two independently operating virus scanning engines (see Client settings > Monitor).
• If an infected file is found: Specify what should happen if an infected file is detected (see Client settings > Monitor).
• Infected archives: Specify here how infected archives are to be treated (see Client settings > Monitor).
• File types: Here you can define the file types G DATA should check for viruses. Please bear in mind that checking all files on a computer can take considerable time.
• Priority scanner: You can use the levels High, Medium and Low to specify whether the virus check should have high priority on the client (in which case the analysis is relatively quick and other applications may run more slowly during the analysis) or low priority (the analysis requires more time, so that other applications can continue to run relatively unaffected). Which priority to choose mostly depends on the point of time at which the virus check will be carried out.
• Settings: Specify the additional virus analyses you want the G DATA software to perform. The default options are the recommended ones, but depending on the type of application, the time gained by omitting these checks may outweigh the slightly reduced level of security. Most of the settings are identical to those found on the panel Client settings > Monitor, but the following ones are specific to scan jobs:
  • Check for rootkits: A rootkit attempts to evade conventional virus detection methods. You can use this function to specifically search for rootkits, without checking all hard drives and files.
  • Use all available CPUs: With this option, you can distribute the virus checking load on systems with multiple processor kernels over all the processors with the result that the virus checking runs considerably quicker. The downside to this option is that less processing power is available for other applications. This option should only be used if the scan job is executed at times when the system is not regularly used (e.g. at night).

Analysis scope

Using the Analysis scope tab, you can limit the scan job to specific directories (when planning a scan job for a client) or mailboxes (when planning a scan job for an Exchange server). The folder selection window allows you to pick folders from both the PC on which Administrator is running and on clients. When including network shares, they should be defined as a UNC path instead of using mapped drives. The Analysis scope can be used to exclude folders, for example those with rarely used archives (which can then be checked in a separate scan job).

Tasks - Periodic scan job

The New scan job window lets administrators define a single or periodic scan job. A complete job configuration consists of three aspects: Job scheduling, Scanner settings and Analysis scope, each covered by their respective window tabs.

Which options are available on the tabs depends on the type of client that the job is being planned for. For example, when planning a job for an Exchange server (if Exchange Mail Security has been installed), options that deal with threats specific to desktop clients are not available.

Job scheduling

The Job scheduling tab lets you plan the scan job:

• Job name: Specify which name the scan job should have. You can enter meaningful names here such as Archive scan or Monthly scan to clearly label the job so that it can be found again in the table overview.
• Schedule (Periodic scan job): For periodic scan jobs, this option specifies when and at what intervals the virus check should occur. If you select On system startup the scheduling defaults no longer apply and the G DATA software will run the scan each time your computer is restarted. For Daily jobs, you can specify under Weekdays on which specific days of the week the job should be carried out.
• Time: Use this option to set a specific start time. For single scan jobs without start time, the scan job will be started immediately after creation.
• Settings
  • Allow the user to halt or cancel the scan job: Permissions can be granted to the users for pausing or aborting the job via the system tray context menu.
  • Notify the user when a virus has been found: Displays a notification on the client when a virus is found.
  • Report scan progress to the ManagementServer (every 2 minutes): Enable this option to report the status of a scan job to the server.
  • Shut down client after scan job, if no user is logged on: The client can be shut down automatically after the scan job is finished.
  • Run scan job later if a client is not powered up at the scheduled time: If a computer is not switched on at the scheduled time of a periodic scan job, the scan job can be started later by ticking this option.
• User context (optional): If the scan job includes network shares, they should be entered as a UNC path instead of using mapped network drives. If the client's machine account (e.g. Client001$) has no permissions to access a share, enter a User name and Password for an account with the appropriate permissions here.

Scanner

The Scanner tab shows the settings with which the scan job will be executed. The following options are available:

• Use engines: The G DATA software works with two independently operating virus scanning engines (see Client settings > Monitor).
• If an infected file is found: Specify what should happen if an infected file is detected (see Client settings > Monitor).
• Infected archives: Specify here how infected archives are to be treated (see Client settings > Monitor).
• File types: Here you can define the file types G DATA should check for viruses. Please bear in mind that checking all files on a computer can take considerable time.
• Priority scanner: You can use the levels High, Medium and Low to specify whether the virus check should have high priority on the client (in which case the analysis is relatively quick and other applications may run more slowly during the analysis) or low priority (the analysis requires more time, so that other applications can continue to run relatively unaffected). Which priority to choose mostly depends on the point of time at which the virus check will be carried out.
• Settings: Specify the additional virus analyses you want the G DATA software to perform. The default options are the recommended ones, but depending on the type of application, the time gained by omitting these checks may outweigh the slightly reduced level of security. Most of the settings are identical to those found on the panel Client settings > Monitor, but the following ones are specific to scan jobs:
  • Check for rootkits: A rootkit attempts to evade conventional virus detection methods. You can use this function to specifically search for rootkits, without checking all hard drives and files.
  • Use all available CPUs: With this option, you can distribute the virus checking load on systems with multiple processor kernels over all the processors with the result that the virus checking runs considerably quicker. The downside to this option is that less processing power is available for other applications. This option should only be used if the scan job is executed at times when the system is not regularly used (e.g. at night).

Analysis scope

Using the Analysis scope tab, you can limit the scan job to specific directories (when planning a scan job for a client) or mailboxes (when planning a scan job for an Exchange server). The folder selection window allows you to pick folders from both the PC on which Administrator is running and on clients. When including network shares, they should be defined as a UNC path instead of using mapped drives. The Analysis scope can be used to exclude folders, for example those with rarely used archives (which can then be checked in a separate scan job).

Tasks - Backup jobs

Backup is available as an optional module.

Using backup jobs, administrators can plan backup tasks for client data in order to centrally safeguard essential files.

Job scheduling

A Job name for the backup job must be entered. It is recommended that you use a self-explanatory name to make it easier to identify individual backup jobs. You can set up Full backups or Partial backups (differential) at defined times. A partial backup only saves files that have been altered since the last full backup. In this case, the backup job will need less time, but restoring a partial backup takes longer because it needs to be rebuilt from multiple backup files.

Enable Do not run backup when running on battery to prevent burdening mobile computers running in battery mode with a backup job. The backup will be postponed until the client is connected to a power supply. For Daily jobs, you can specify under Weekdays on which specific days of the week the job should be carried out.

Server-side backup storage paths as well as quota notifications can be configured under General settings > Backup.

File/directory selection

The File/directory selection tab lets you select which folders from which clients or groups will be backed up. Under Backup scope, add folders from any of the clients. Exclude files allows you to define files and folders to be excluded from the backup. There are several general options, such as Temporary internet Files and Thumbs.db, but you can also define custom file types by adding their extension to the file type list.

If the generated backup should be saved in a particular directory prior to transmission to the ManagementServer, this can be indicated under Cache. If the option Use client standard path is enabled and an absolute path is indicated, the backup will be buffered in the specified directory. If this option is not enabled, G DATA Security Client will always buffer the backup on the partition containing the most free disk space. The directory G DATA\Backup will be created in the root directory of the
partition.

Tasks - Restore jobs

Backup is available as an optional module.

Restore jobs can be planned in several ways. In the Tasks menu, select New > Restore job to plan a new restore job. The Restore job toolbar button opens the same window, allowing you to select a backup to restore. Alternatively, you can look up the backup in the list of backup jobs. Right click a job and click Restore backup to open the Restore backup window.

The Restore backup window shows some basic information about the selected backup job. It contains one or more backups, depending on how often the job was run. For every backup, the list shows Backup time, Client, Type of backup, Number of files and Size (in MB). In the Restore on client dropdown, you can select the client to which the backup should be restored (this does not need to be the client from which the files were backed up). Select the appropriate backup and click OK to open the Restore settings window.

The restore settings can be configured on two tabs. File selection allows you to browse through the backup. Click Only restore selected files from the archive to enable the folder tree in which you can select the files to be restored. Click Restore all files within the archive to disable the folder tree and restore all files instead. The Options tab lets you configure restore job settings. You can add a descriptive title to the restore job under Job name. Files can be restored to the directory they were backed up from if you select Restore files to original directory, or to another directory if you select one under Target directory. Finally, you can decide what should happen to file conflicts under Overwrite existing files. Upon confirming the recovery settings, a restore job will be added to the Tasks module. It will be carried out immediately.

Tasks - Patch applicability jobs

PatchManager is available as an optional module.

Patch applicability jobs can be planned to check if one or more patches are applicable to clients or groups.

Patch applicability jobs can be scheduled using the following options:

• Execution: Decide when the patch applicability job should be run:
  • Scheduled: Run the patch applicability job according to a Schedule, which can be defined using one of the following parameters: Immediately, Once, Hourly, Daily, Weekly, Monthly or On Internet connection.
  • As soon as available: Run the patch applicability job each time a new patch is released.

To select the patches for which applicability should be checked, use one of the two Scope options:

• Specific patch: Choose one or more patches from a list.
• Using attributes: Use Attributes to select a range of patches using keywords. To add a specific attribute (Vendor, Product name, Urgency, Language) as a filter criterium, tick the checkbox and enter a keyword. This way you can check applicability for patches from a specific publisher or only for specific versions. Wildcards like ? and * can be used. Enable the option Patches only if the job should not check full software packages and upgrades for applicability.

Select Automatically install applicable patches to make sure that each time a patch is found to be applicable, it is installed automatically.

If the Patch applicability job is being planned from PatchManager's Status overview module, the job applies to the patch and clients that were selected there. If it is being planned from the Patch configuration module, you need to select the client(s) for which applicability should be checked. If it is being planned from the Tasks module, you need to select the patch(es) for which applicability should be checked - the job will be run on the currently selected group or client.

Tasks - Software distribution jobs

PatchManager is available as an optional module.

To distribute applicable patches to clients or groups, you can define a software distribution job. Software distribution jobs can be managed and scheduled using the Planning options:

• Immediately: The software distribution job will be run immediately.
• Immediately after the boot process: The software distribution job will be run after the nextboot.
• Immediat ely after logging in: The software distribution job will be run after the next time anend user logs in to the client.
• Only load at specified time: Schedule the job to be run at a specific time (the other scheduling options will not come into effect until this point in time has been reached).
• Load with delay: Schedule a delay in starting the job. That way, the boot process and distribution job won't influence client performance at the same time.

If the Software distribution job is being planned from PatchManager's Status overview module, the job applies to the patch and clients that were selected there. If it is being planned from the Patch configuration module, you need to select the client(s) on which the patch should be installed. If it is being planned from the Tasks module, you need to select the patch(es) that need to be installed - they will be installed on the currently selected group or client.

Tasks - Rollback jobs

PatchManager is available as an optional module.

Using rollback jobs you can uninstall previously deployed patches. Right-click the respective distribution job in the Tasks overview and choose Rollback. Alternatively, select the specific client and patch in PatchManager's Status overview panel and choose Rollback from the context menu.

The Update rollback window lets you enter a Job name to easily identify the rollback job. After entering the name, click OK to add the job to the Tasks list. It will be executed immediately.