Introduction to tasks in upKeeper

In this topic, you’ll learn what you need to know before start working with tasks in upKeeper.

What is a task?

Tasks in upKeeper is defined functions that can be scheduled or executed instant. Each function is designed to address different needs. Some functions is simple executions and some are more of the type policy. Tasks can be added to groups or directly to a single computer or multiple computers. We recommend that task is added to groups so that you achieve more management effect.

Task can be scheduled to execute ones, on a specific day or date and in a defined interval. You can set offset time in minutes on scheduled tasks, this will randomly spread execution within specified time starting at specified time.

Tasks that are removed from groups or computers will not reverse or in other way affect what the function has done. Removed tasks will simply stop execution and disappear from clients.

Tasks are saved locally on each client that have a task added directly or via inheritance from group. This means that tasks is execute regardless if client is connected to upKeeper or not.

Task functions

Restart – Restart will force computers to restart regardless if users is logged in and working or computers are started and not used. Keep in mind that users will have little or no time to save ongoing work if restart is executed on a computer. Computers will automatically start on default selected operating system after shutdown.

Restart to SOS – Restart will fore computers to restart regardless if there are users logged in or not. Keep in mind that users have little or no time to save ongoing work if restart is executed in a computer. Computers will automatically start on SOS (Service Operating System) after shutdown.

Shutdown – Shutdown will force computers to shutdown regardless if there are users logged in or not. Keep in mind that users have little or no time to save ongoing work if shutdown is executed on a computer.

Wake on LAN – WOL (Wake On LAN) will send a magic package to wake a specific computer. Network package is sent like a broadcast to the entired network and/or to the subnet where the computer last connected to upKeeper. Default there are network restriction stopping broadcasts to be sent to other subnets, but this can be configured. When I comes to directed cast, it is normally accepted. Keep in mind that upKeeper sends directed cast to the last known subnet, if computer is moved to another subnet the WOL package will be sent to wrong subnet.

Inventory – Inventory will collect hardware, software, updates and missing updates information and report it to the central system. Inventory can be seen on specific computers or in different summery reports. Collected hardware information is based on WMI queries defined in the database. Queries and properties can be added or removed to satisfy specific needs. Software inventory is based on application information found under uninstallation information in the registry, the registry information is used to populate add/remove programs function in settings of the computer. Installed updates is also find in the registry, will the missing updates are collected from the Windows Update server configured for the computer. The missing update part normally tasks most of the time to perform and can be disabled.       

Do not restart – Do not restart function will enforce that computers with a task using this function added not restarted thru upKeeper. Keep in mind applications that require restart after installation or uninstallation will not go thru with the restart and may not work properly. Computers with a task using this function added can be restart locally or thru other systems.   

Do not install applications – Do not install applications will enforce that computers with a task using this function added not to install applications. Applications can be installed and uninstalled locally or thru other systems.