Updates & automationApplication updates & deployment
Use the application catalogue and supported package deployment, with rollout rings, pacing and stop controls. Confirm supported packages during setup.
Close explanation of Application updates & deployment
What it does
Keep supported applications current through the package catalogue and configured rollout workflow. Vycko helps distinguish a package it can manage from an application that is simply present in inventory.
How you can use it
- Catalogue and package matching. Review eligible application updates and supported deployment options, using the available package information rather than assuming every programme can be changed.
- Rollout controls. Apply pilot rings, pacing and stop choices so a supported application change can be reviewed on a smaller group before proceeding more widely.
- Exclusions that matter. Keep self-updating and business-critical applications out of an unsuitable automatic route, using the configured catalogue and customer exclusions.
In practice
A support team reviews a supported package update on a pilot group before planning a wider rollout, with the individual results available for follow-up.
Controls & availability
Windows package management primarily uses supported winget routes. Per-user installations, unknown packages and excluded applications may be ineligible; installation and removal support must be confirmed during setup.
Updates & automationAutomation calendar
Schedule reviewed runbooks across selected devices or groups, preview the plan, and see upcoming work and per-device outcomes.
Close explanation of Automation calendar
What it does
Make repeatable maintenance visible before it runs. The automation calendar schedules an enabled, reviewed runbook against a defined set of devices, with its plan and eventual results available to the team.
How you can use it
- Targets and timing. Choose devices, a customer, a site or a saved group, then schedule a one-off or recurring run in the relevant time zone.
- Practical scheduling choices. Configure supported blackout dates, maintenance windows, missed-run handling and what happens when a device is offline.
- A plan tied to approval. Review the runbook version, parameters and included or excluded computers. Material changes to that plan require a new approval decision.
In practice
A support provider schedules a reviewed check for a customer’s workstations, excludes an agreed blackout period and reviews the run’s device-by-device results afterwards.
Controls & availability
Schedules use reviewed procedures, not arbitrary free-text instructions. Newly joined devices are not silently added to an already approved plan, and servers require the applicable named approval.
Updates & automationMaintenance windows
Set maintenance periods for a device, site or customer. Suppress relevant alerts and hold automatic remediation during the window.
Close explanation of Maintenance windows
What it does
Tell the platform when planned work is taking place. A maintenance window gives support activity a defined scope and period, helping the team distinguish expected interruptions from a new fault and hold relevant automation.
How you can use it
- The right scope. Set a maintenance period for a supported device, site or customer so the window follows the environment actually being worked on.
- Relevant alert handling. Suppress eligible planned-work notifications while retaining the alert context and the reason for suppression.
- Coordinated automation. Hold automatic remediation during the applicable window and use supported schedule settings to run work only within its agreed period.
In practice
Before an office network change, the team creates a site window so expected connectivity interruptions do not produce the usual notification pattern.
Controls & availability
Maintenance is not a blanket mute for every serious condition. Defined protection remains for findings such as failing disks, antivirus problems and firewall issues.
