New Adaxes Version Released

Question

Adaxes 2018.1 has finally arrived and is available for download!

New Web Interface. New reporting platform. New user experience.

Check out what’s new in the latest version: https://www.adaxes.com/info_whats-new.htm

Download Adaxes 2018.1: https://www.adaxes.com/download.htm

Follow the Upgrade Instructions: https://www.adaxes.com/resources/releas ... tNotes.htm

Comments

Are users notified when updates are released? For an example I noticed on the forum support told a user to re-download and install 2018.1 to fix an issue reported, but I can't find anything about other issues fixed in the newly release build. Would nice to be notified when you release patches and have access to release notes.

---

Hello Jake,

Are users notified when updates are released? For an example I noticed on the forum support told a user to re-download and install 2018.1 to fix an issue reported, but I can't find anything about other issues fixed in the newly release build.

You can check for updates using Adaxes Administration Console manually:

1. Launch Adaxes Administration Console.
2. In the Console Tree, right-click the service node and click Properties in the context menu.
   
3. On the General tab, click Check for Updates.
   
4. If a new Adaxes version is available, the corresponding notification will be displayed in the dialog box that opens.

To automatically display a notification in the Output pane when the Administration Console starts if a new version of Adaxes is available:

1. Launch Adaxes Administration Console.
2. In the main menu, click Tools.
3. In the drop-down menu, click Options.
4. Activate the Automatic Updates tab.
5. Select Automatically check for the product updates and then select the required period.
   
6. Click OK.

Would nice to be notified when you release patches and have access to release notes.

Release notes are available for each Adaxes version on our site. However, they do not include information about updates, it is available in the What’s New section.

---

We're currently running version 2017.2. I'd like to install this new version on a test VM because we're not in the position to upgrade our Production environment at this time. Can you provide some procedures on the best way to accomplish this without impacting the Production environment. Ideally, I'd like to be able to connect to AD, test the functionality in the Administration Console and the Web Interface, both of which are used heavily.

Thanks...

---

Hello Sandra,

For the new installation not to influence your production Adaxes configuration, install the latest version without sharing configuration with the production one. To do so, select New configuration on the Service Configuration page of the installation wizard.

As long as your instances of Adaxes service will not share configuration, you won’t be able to apply the same license key for the new version. However, you can install a 30-days free trial of the latest Adaxdes version on your VM and play with it.

If you want to check your production settings in the latest version of Adaxes, you need to backup/restore the service and Web Interface configuration. To do so:

1. Backup your production Adaxes service configuration using the Softerra.Adaxes.BackupRestore.exe tool. The tool is located in the folder where Adaxes service is installed, which is C:\Program Files\Softerra\Adaxes 3\Service by default.
2. Backup your production Adaxes Web Interface configuration using Adaxes Web Interface Customization tool.
3. Restore the service configuration on your VM using the Softerra.Adaxes.BackupRestore.exe tool. The tool is located in the folder where Adaxes service is installed, which is C:\Program Files\Softerra\Adaxes 3\Service by default.
4. Migrate your Web Interface configuration on your VM using the Softerra.Adaxes.Web.Migration.UI.exe tool. The tool is located in the folder where Adaxes Web Interface is installed, which is C:\Program Files\Softerra\Adaxes 3\Web Interface by default.

For details, have a look at our Upgrade Instructions.

---

Thank you!

---

Hello,

Do I understand correctly, that by restoring Adaxes backup on a test instance will not make it a shared config and I will be able to play with new Adaxes having my prod settings for 30 days? I thought restoring the configuration would apply same license and will make the servers share the config...

---

Hello,

Do I understand correctly, that by restoring Adaxes backup on a test instance will not make it a shared config and I will be able to play with new Adaxes having my prod settings for 30 days?

Yes, you understand right.

I thought restoring the configuration would apply same license and will make the servers share the config...

For a new instance of Adaxes service to share common configuration with an existing instance, you need to select the Shared configuration option during the new instance installation. You can check details in our Installation Instructions: https://www.adaxes.com/resources/releas ... lti_server.

License key is not included into the backup. You need to activate it manually on each computer where Adaxes service is installed.

---

Great news. I was afraid i would mess up our prod server, now I can go and do an actual test on new Adaxes.
Thanks!

---

We have many things to test to make sure they will still work correctly in the latest version. We are currently using Adaxes 2015.
First question:
Do we have to upgrade to 2017.2 before going to 2018?
- Probably the safest bet.
-We are on an older version because the last time we tried to upgrade it failed.
Reading this post it does not seem there is an option for a side by side upgrade?
-Would like to test all functionality before releasing to production.
-Would also like to update documentation and train on the new interface.
-Its my understanding if we add the 2018 server to the current config, the Adaxes service will send request to either server via its built in load balancing. If we have not produced updated documentation, trained our admins and tested our functionality before this I am worried we may have issues arise.

We are thinking the best solution for us is to do a side by side install, backup the current configs and restore them to a new instance of Adaxes. That way we can update our documentation, train our admins and test functionality. Then cut-over to the new version. Is this supported?

---

Hello,

Do we have to upgrade to 2017.2 before going to 2018?

No, you can go directly to Adaxes 2018.1 following the Upgrade Instructions.

Reading this post it does not seem there is an option for a side by side upgrade?

If you want to check your production settings in the latest version of Adaxes, you can backup the service and Web Interface configuration, install the latest version on a test computer and then restore the configurations. To do so:

1. Backup your production Adaxes service configuration using the Softerra.Adaxes.BackupRestore.exe tool. The tool is located in the folder where Adaxes service is installed, which is C:\Program Files\Softerra\Adaxes 3\Service by default.
2. Backup your production Adaxes Web Interface configuration using Adaxes Web Interface Customization tool.
3. Restore the service configuration on a test computer using the Softerra.Adaxes.BackupRestore.exe tool. The tool is located in the folder where Adaxes service is installed, which is C:\Program Files\Softerra\Adaxes 3\Service by default.
4. Migrate your Web Interface configuration on a test computer using the Softerra.Adaxes.Web.Migration.UI.exe tool. The tool is located in the folder where Adaxes Web Interface is installed, which is C:\Program Files\Softerra\Adaxes 3\Web Interface by default.

You will have a 30-days free trial to check new functions and your settings.

Once you are done with testing and ready to switch to the latest version, you will need to do the following:

1. Uninstall your Adaxes version 2015.
2. Install the latest version of Adaxes sharing common configuration with the Adaxes instance installed on your test computer.
3. Wait for the replication to complete.
4. Uninstall Adaxes from your test computer.

---

Hello,

If you want to check your production settings in the latest version of Adaxes, you can backup the service and Web Interface configuration, install the latest version on a test computer and then restore the configurations.

Is there an easy way to accomplish this in a "read-only" fashion so that all business rules, scheduled tasks, etc are disabled?

---

Hello,

Sure, you can disable Business Rules, Scheduled Tasks, etc. after restoring configuration. It is totally up to you, how you check the functionality of the latest version. Just take into account that disabled Business Rules do not trigger, disabled Scheduled Tasks do not run, etc.

---

Hey guys,
I am doing a parallel build for the new version and was trying to make it work. But due to year-end holidays, some other workloads and validation complexities for my custom scripts, 30-day evaluation has been expired. What do I do? I don't really want to go thru the re-install, restore thing again. Can I temporarily copy my original prod licenses file to this server and run it for a few weeks parallel to the old server - without impacting anything? So I can finish my validation and get rid of the old server and cut over the DNS to the new one.

Also when I am ready to move - how do I just move contents related to Password reset tool, if it is possible at all?

Thanks,

---

Hello,

But due to year-end holidays, some other workloads and validation complexities for my custom scripts, 30-day evaluation has been expired. What do I do?

It is possible to extend your trial license. Just specify the email address to which the license should be sent and our Sales Department will get back to you as soon as possible. Alternatively, you can contact our Sales Department directly at sales[at]softerra.com and request extension of your trial license.

Can I temporarily copy my original prod licenses file to this server and run it for a few weeks parallel to the old server - without impacting anything?

It is not recommended, because using the same license key will require sharing common configuration between the instances of Adaxes service. In this case, the changes you make in the testing instance will be replicated to the production one which is probably not desired.

Also when I am ready to move - how do I just move contents related to Password reset tool, if it is possible at all?

Unfortunately, there is no such possibility.