This article provides clear instructions and best practices for upgrading Commander systems in a production environment. It covers planning, staging, performing the upgrade, rolling back if necessary, and post-upgrade activities to ensure a smooth and successful upgrade process.
Pre-upgrade preparation
- Notify users about expected downtime at least 36 hours to a week before performing the upgrade.
- Update the Service Portal Message of the Day using these steps:
- Under the Configuration menu, choose System.
- Switch to the Portal tab.
- Enter your message in the Service Portal Message of the Day field and click Save Settings.
- Send email notifications to users who may not log in to the Service Portal during the outage window. A sample message could include timing details and contact information for issues after the upgrade.
Staging upgrade process
- Maintain a staging environment to test upgrades before applying them to production. If unavailable, clone the application server to perform a test run.
- For installations using SQL databases:
- Backup the SQL database.
- Create a dummy database on your SQL Server.
- Install the current version of Commander against the dummy database.
- Stop the Commander Windows service.
- Restore the backup, overwriting the dummy database.
- Restart the Commander Windows service.
- Perform the upgrade as a test.
Optionally, Flexera Technical Support can assist with running through the upgrade scenario if you upload a sanitized backup to the FTP server. Contact support at least 72 business hours in advance.
Production upgrade process
- Notify Flexera Technical Support if you need assistance or standby support.
- Notify users of upcoming downtime using Service Portal Message of the Day and email.
- Back up the Commander SQL database.
- Take a snapshot of the Commander application server.
- Download the latest release from the Support Downloads. For legacy versions, contact support.
- Copy Commander Installer.zip to the server, unblock the file, and extract it. Run executable files as Run as Administrator.
- Follow instructions on Documentation - Upgrade Commander for the remainder of the process.
Note: If the service account password changed, update it during the install and in Commander credentials afterward.
Roll back process
- Restore the Commander database from the pre-upgrade backup.
- Restore the Commander application server snapshot.
- Restart the Commander Windows services or reboot the application server.
Post-upgrade activities
- Turn off or update the Service Portal Message of the Day.
- Test common actions your users perform; report any unusual issues to Flexera Technical Support, including diagnostics or backups if requested.
- Take database backups and/or snapshots after completing the upgrade.
Outcome
Following these steps minimizes upgrade issues, provides rollback options, and ensures system readiness after upgrade.
Was this helpful?
Related Articles
Best practices for large environments (Snow License Manager and Snow Inventory) 1.17KNumber of Views Best Practices for Handling False Positives During Audits 8Number of Views Best Practices for the CLS instances which are not in use 9Number of Views What Are the Config File Best Practices in the Usage Intelligence Release Process? 9Number of Views Scanning Guidelines and Best Practices (v6) 4Number of Views
Revenera Assistant
Online
Hi, I am Reva - Ask me anything.
Updates
No new updates
Chat
Home
Updates
/**/
Thanks for the feedback!
Your feedback has been saved.Rate this response:
1
2
3
4
5
Add Additional feedback ( Optional )
0/240
English
English
Language changed successfully
Something went wrong
Email sent successfully
Something went wrong
Case create successfully
Are you sure you want to cancel
the case creation?
Please select a product to submit the case.
Please select a product version to submit the case.
0/255
Upload Attachment
File Upload
Maximum file
size allowed is 3 MB.
File type
not supported.
Supported file types:
Documents (.txt, .doc, .docx, .pdf), Images (.jpg, .png), Comma Separated Files
(.csv) Speadsheets (.xlsx, .xls)
Are you sure you want to cancel the case creation?
Case closed successfully
File Upload
Maximum file size allowed is 3 MB.
File type not supported.
Supported file types:
Documents (.txt, .doc, .docx, .pdf), Images (.jpg, .png), Comma Separated Files
(.csv) Speadsheets (.xlsx, .xls)
Are you sure you want to close this case
| Products | Region | Phone Numbers |
|---|---|---|
| FlexNet Operations FlexNet Embedded FlexNet Publisher FlexNet Connect FlexNet Code Insight InstallAnywhere InstallShield |
North America * |
+1 630-332-2513 (toll) +1 877-279-2853 (toll-free in North America) |
| Europe * |
+44 1925 944367 (toll) +44 800 047 8642 (toll-free in Europe) |
|
| Japan * | +81 3-4540-5335 (select option 2) | |
| Australia * |
+61 3 9895 2177 +61 1800 560 603 (toll-free in Australia) |
|
|
Usage Intelligence (formerly
Revulytics) Compliance Intelligence |
Please use the Case Portal to submit your support ticket or reach out to your Revenera contact. | |
File Upload
Maximum file
size allowed is 3 MB.
File type
not supported.
Supported file types:
Documents (.txt, .doc, .docx, .pdf), Images (.jpg, .png), Comma Separated Files
(.csv) Speadsheets (.xlsx, .xls)
Revenera Assistant
© 2026 Flexera Software. All Rights Reserved.
Case id: 00001065
Activity: Status change: 2 hours ago