Introduction
When is the time to update my AnywhereNow software?
AnywhereNow is a suite of software components that need regular maintenance and updates just like any other software in use in private or corporate environments.
All AnywhereNow software components are built on underlying Microsoft technology (Windows OS, Skype for Business, Teams, SQL, or SharePoint to name a few) and Microsoft programming standards (.NET and C++).
Besides version updates of the individual AnywhereNow software components also these underlying technologies need updates or even replacement due to life cycle or strategic changes.
AnywhereNow will adhere to its End-of-life guideline for support on AnywhereNow software, no more technical support on the last 3 minor versions and functional support up until a year after release, unless no new version has been released within that time. Read more about AnywhereNow Support End-of-Support Policy.
Every 3, 6 or 12 months
To stay up to date with the latest AnywhereNow our guideline is to schedule a planned AnywhereNow component refresh every 3, 6 or at most 12 months. We don’t have “a new version is available” push mechanism inside our software (as Windows OS or Office or (mobile) AppStore programs do), but we do require customers to keep their software updated none the less.
The best (and only) place to see the latest version of each individual software component is the Release Notes Website. On here you will find what new features, enhancements and sometimes relationship to other software components are added to this release. Below are instructions on how to handle each software component update.
For a list of possible AnywhereNow software components you have found are eligible for updating a good starting place is the list on the “Guides” page on this GoLive website.
Besides a listing all documented AnywhereNow software components, many have a direct link to an “Update” article, which describes how to update the specific components.
Approach
Before you start the update, you need to think about your approach and prepare the update. Are the versions of the underlying Microsoft technology still supported and up to date?
Which components are used, which version of the component is used? Are there any dependencies for updating a component? How do I validate if the component(s) is working correctly after the update? Do I have a rollback plan in case something goes wrong?
If you have a user acceptance environment, then start with the server(s) in that environment if the update is successful, then continue with the production environment. If you have a failover server, then start with this server.
You can have different architectures, which lead to different approaches for the update. Each approach exists of a couple of phases:
- Preparation
- Update
- Testing
- Clean up