Plan updates and recovery
Treat an update as an operational change. Keep a record of the installed versions and the working configuration.
Check the installed release and the agreed project scope before using a feature.
Before an update
- Agree a maintenance window and identify the affected apps and users.
- Record the current platform, service and app versions.
- Check service health, storage space, power and network stability.
- Confirm the backup and recovery method for this installation.
- Use the approved update source and channel. Review app permission changes.
After an update
- Confirm the expected version and healthy service status.
- Compare selected machine values with the source.
- Open the required apps using their normal user permissions.
- Test a remote connection and access removal.
- Record the results and any action still needed.
If the update fails
Stop repeated retries. Record the error, version, free space and service state. Contact support with that evidence.
Do not delete configuration databases, identity keys or authentication files. Do not bypass signed update checks. Restore only through the agreed recovery procedure.
A local restart, Internet outage and configuration-server outage are different tests. Record which functions remain available and which need a live connection.