One central component in an upKeeper Manager environment is upKeeper Application Server which actually is a service running on a Windows server. This component can be configured to run on multiple servers and all instances will be communicating with the upKeeper database server. It can be configured to act as a master or a slave where the master in general handles all central stuff and the slave perform server tasks and client communication (older clients). Application server works in intervals and you read about the details below.
Application server service configured as master
On startup
- Update running application server service version to database.
- Get scheduled tasks.
On demand
- Send information on what client should do.
- Send information about tasks.
Every minute
- Get and execute urgent server tasks.
- Execute scheduled tasks.
- Check if there are notifications for installed computers.
- Send notifications.
- Send application request emails and execute processed requests.
Every five minutes
- Synchronize devices form upKeeper MDM.
- Synchronize Windows Store for Business Applications.
- Download selected Windows Updates and package them to distribution area.
- Package new or updated applications.
- Package new or updated drivers.
- Collect information from new or updated platforms.
- Update tasks.
- Execute batch jobs.
- Update license (only once).
- Update computer membership in dynamic groups.
Every fifteen minutes
- Synchronize groups and computers from AD.
- scheduled tasks.
- Check Microsoft Intune computer import.
- Check Microsoft Azure AD user import.
- Check Microsoft Intune MDM device import.
- Remove expired remote sessions.
Every hour
- Remove unused application package files.
Every night (between 01 and 03)
- Synchronize WSUS updates catalogue.
- Update client statistics and license information (local).
- Check warranty dates for all computers that does not have one.
- Clear login information on computers that haven't connected recently.
- Update license.
- Clear expired refresh tokens.
- Perform database maintenance.
Application server service configured as slave
On startup
- Update scheduled tasks.
On demand
- Send information on what client should do.
Every minute
- Execute scheduled tasks.
Every five minute
- Update tasks.
Every fifteen minutes
- Update scheduled tasks.
Every hour
- N/A
Every night
- N/A
Summery
Application server service is a central component and responsible for a number of important tasks in a upKeeper Manager environment. Environments with more than 1000 clients should have a master server configured without any responsibility for client communication. In upKeeper Manager environments running version 4.7 or newer Application Server Service configured as slaves should be replaced with upKeeper Client API for client communication.
Comments
0 comments
Please sign in to leave a comment.