New version - upgrade process

Question

Hello,

I was wondering if there is an upgrade process from version 2.6.6702 to the latest release? I've read the Release Notes for the latest version of Adaxes, but I don't see an upgrade section; I only see an installation section.
I tried running the new version executable, but it says that there is another version already installed and I didn't get an option to do an upgrade.
If I have to completely remove the previous version, will I lose my current configuration or do I have to manually back them up?

Answer 1

Hello,

To upgrade to a new version of Adaxes you need to perform the following steps:

• 1. Backup the configuration of your Adaxes service. For details, see Backup/Restore Service Configuration.
• 2. Uninstall the old version.
• 3. Install the new version.
• 4. Restore the configuration.

The next version will include a GUI tool for backing up and restoring the configuration of Adaxes service and Web Interface. Also, it will be possible to backup/restore configuration using the Adaxes installer.

Comments

Thanks for your quick reply.

I was able to perform the backup/restore; however, after updating our management consoles (10 users) the "binding" process to the service takes almost five minutes!
I'm using the same server where I had the previous version of Adaxes, so no change in hardware. Even from the server itself, launching the console takes almost a minute during the "binding" process.

Can you help?

---

After restoring the configuration, you need to provide credentials for managed AD domains (in 2011.1 passwords are not stored in the backup file). To do this, you just need to expand the node of your AD domain in the Adaxes Administration Console. Have you done this?

Also, please have a look at the Adaxes Event Log. Are there any errors in this log?

---

I've not tried any of those. Is this done at the server level or per management console? If it's done per management console, what credentials am I using? In the previous version I never had to do that.

Thanks!

---

You need to specify the credentials that will be used by Adaxes to access your AD domain.
The Adaxes service will use these credentials to perform all operations within this domain.

1. Right click your AD domain in the Adaxes Administration Console
2. Select Change/Provide Logon Information

3. Specify the user name and password of an AD account that has administrative privileges in your AD domain.

---

Thanks for your reply.

I checked that, and it's using the default credentials used by the Adaxes services, and that account has domain admin credentials.

As soon as I launch the application, I get the Connecting to MYSERVER....Binding...

That window stays on for almost 5 minutes (I clocked it); then clicking on on any domain OU or object takes a very long time - longer than it used to take in the previous version. This seems to happen mainly on our management consoles.

When I run the management console from the server - the application runs much faster.

---

This is very strange...

1. Please try connecting to your Adaxes service using the credentials of the default Adaxes service administrator (the one you specified during the installation of your service). Does it take less time to connect?
2. Are there any errors in the Adaxes Event Log?
3. Do you use new version of the Adaxes Administration Console?

---

Okay, I had to remove all leftover files/folders from the previous console installation on my desktop (located in my Documents and Settings\MyProfile folder). Re-installed the application and that fixed the "binding..." delay.

All good now, thanks!

---

That's great!
However it is strange. I cannot understand what can cause such delays and we cannot reproduce the issue in our environment...