0 votes

Hello

I'm a little (no, actually very) concerned about upgrading 2017.2 to 2018.1, because I am unsure how an upgrade will impact on our current solution (web UI).

In our 2017.1 solution, we strongly controls which features and data that is available for our users - which makes it easy for our
non-technical end-users to use the solution.

With all the new web features, I fear that our easy-to-use design will be replaced by a myriad of useless features, that will turn our solution into a not-so-easy-to-use solution :?

Anyone that have some experience about upgrading to version 2018.1 in this respect ?

- Thanks

by (2.6k points)

1 Answer

0 votes
by (220k points)
selected by
Best answer

Hello,

Once you migrate your Web Interface configuration on Adaxes 2018.1, the same features will be available as before. There should be no issues about that.

If you want to check your current settings in the latest version of Adaxes, you need to install it on a test computer and then 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 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 your 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.

For details, have a look at our Upgrade Instructions.

Related questions

0 votes
1 answer

I think this started happening back in August when we updated to the current version (3.13.18.106.0). We are not sure though because this only affects the web page ... We would prefer not to allow access through a firewall for this. Screenshot of the error:

asked Nov 23, 2020 by mark.it.admin (1.8k points)
0 votes
1 answer

Hello, I think I am not the only one disliking the new design, even though functionality is superior to the older one, but this is only due to practical reasons - I do ... , that is how frustrated I am with current design. Are there any options to get that?

asked Jun 14, 2019 by DLe (760 points)
0 votes
1 answer

When setting a default OU for new user creation, our domain does not expand. Editing users is fine, installed console is fine. Config was working before upgrade to 2018.1. Any suggestions?

asked Jul 17, 2018 by polley (1.2k points)
0 votes
1 answer

Hi Just upgraded to 2018.1 Seems that backing up the web interface works differently than in 2017.2? How do I back up my web configuration now ? Thanks in advance!

asked Jul 4, 2018 by pafa (500 points)
0 votes
1 answer

There seems to be a bug in the email being sent to approvers - the link for the selfservice portal is not reflecting the change in the IIS configuration - it still points ... the link to the selfservice portal they will get a 404 - File or Directory not found

asked Jul 4, 2018 by pafa (500 points)
2,740 questions
2,474 answers
6,475 comments
1,372,154 users