I've been getting reports that the performance of 2013.2 is slower than the previous version of ADAxes.
Searching, editing, etc.
Is this a known issue?
What version (including the build number) are you using? Are Adaxes service and Adaxes Web Interface installed on the same computer or different computers? Are they in the same AD site? Please describe your environment in more detail.
Also, can you draw up at least an approximate list of pages that load slow?
Version 3.6.10022.0 (64 bit)
Running on a single server. 8.00 GB RAM.
It is a virtual server running in VMWare ESX 4.1
Results from searches seems to be the biggest complaint.
Just a qucik tip that we have experienced (if this is regarding the web interface). Google Chrome works MUCH quicker with the Adaxes Web Interface then IE. We were struggeling with slow performance, tried rebuilding everything, same problems.. Then someone tried it through Google Chrome, super quick response!
Can you do the following:
To enable tracing in the Web Interface:
Open the folder that contains the Web Interface site that you are experiencing issues with. By default, Adaxes Web Interface sites are installed to the following folders:
C:\Program Files\Softerra\Adaxes 3\Web Interface\Admin\
C:\Program Files\Softerra\Adaxes 3\Web Interface\HelpDesk\
C:\Program Files\Softerra\Adaxes 3\Web Interface\SelfService\
Find the Web.config file and open it with any text editor.
Find the following lines in the file:
<!--- Trace settings -->
<trace enabled="false" pageOutput="true" requestLimit="40" localOnly="false" mostRecent="true" />
Change trace enabled="false" to trace enabled="true".
Find the following lines:
<!-- Web settings -->
Paste the following block before the lines:
type="System.Web.WebPageTraceListener, System.Web, Version=2.0.3600.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"/>
Save the file.
Thank you for the information.
I've not changed anything at this point. We do use Chrome and I find the performance the same as it has always been (fast).
Sometimes, information gets lost in translation.
Last night I attempted to upgrade from 2012.01 to 2013.2. Other than losing my logs (fixed by a snapshot revert and backing up the logs) this process ... Is there any way to indicate the preferred method of communicating with particular Exchange environment?
Whenever i use exchange cmdlets through remote powershell from a script launched by Adaxes, i get this warning message in the execution log: "Some imported command names include ... now. I won't delete the post, should anyone else experience these problems.
After installing the 2013.2 update the updated template web portals have access to the new reports (recently created and modified groups). These are however not available for our ... two, as I don't really want to have to start again from scratch! Thanks
Hello, In previous versions I used the instructions in this post Handling child objects to view Bitlocker Recovery Key's for computers. After upgrading to 2013.2 these instructions no longer ... way to view it. Help... this is a critical issue for us. Thanks.
2013.2! That's right, it's here. Adaxes 2013.2 is packed with new features and improvements to make the best even better. The Adaxes team is incredibly excited to release this new version and we hope you enjoy it as much as we do. What's New Download