This document is intended as a starting point when planning and executing an upgrade to BoKS Manager v7.x from a 6.x.
It is essential to go through the required reading and understand what it will require to upgrade the domain successfully.
A written plan is necessary so that no details are missed during the upgrade.
Make a Test Run
The plan should to be tested before the upgrade, as realistically as possible, in order to spot omitted details or unexpected consequences.
Work With FoxT Support
In order to provide optimal service, FoxT needs to, at the very least, be aware of the coming upgrade.
Inform FoxT of the upgrade date as early as possible, please, so that we can ensure resources are assigned and available to support you.
Request and Install Licence
We recommend involving FoxT already in the planning phase, but it is most important to notify FoxT well in advance before the actual upgrade in case assistance is needed.
Especially: Known Issues
Pay special attention to the section: “Key Features and Issues of Upgrading”
Based on our experience, the people best-suited to write the full upgrade instruction are the persons who will be performing it.
Due to major changes in this version there are a few areas that will require special attention in the planning phase:
Also note the new default log file storage location: $BOKS_var/auditlog
The written Upgrade Instruction should contain the following:
To initiate the plan, it could be a good idea to set up an online meeting with Systems Engineers from FoxT to discuss the best strategy for the domain in question.
The Unix Groups Migration Tool can be found in
Customer portal > My Products > BoKS Manager 7.x
Unix Groups Migration Tool for BoKS v7.x
FoxT can perform a review of the Upgrade Plan, written by the customer, in order to spot potential caveats and give advice on improvements.
During the upgrade FoxT can provide the following services:
Whichever upgrade services you choose, it is imperative you make sure FoxT Customer Service has been notified at least 2 weeks in advance of the upgrade as per Maintenance Agreement.
In large domains with many affected users and unix groups this process may take a lot of time and system resources, possibly affecting user updates meanwhile.
Still have questions? We can help. Submit a case to Technical Support.