Testing latest Adaxes next to older Production, possible?

Question

Hello,
With recent grand update we are in urge to try out all the new goodies you have introduced, but because of a lot of changes we want to try it out without bringing down our older Production version of Adaxes. Is it possible to install fresh Adaxes instances on same domain without affecting the existing Adaxes instance? I mean doing a fresh install, without copying any existing configuration and just building some rules to try out the functionality. We have built some powershell based integrations with external system that we would like to try out with this new version.

Are there any other recommendations or concerns for soft migration to the new version?

Answer 1

Hello,

Is it possible to install fresh Adaxes instances on same domain without affecting the existing Adaxes instance?

Yes, sure. Just download Adaxes 2018.1 from our site and install it without sharing configuration with existing instances of Adaxes service.

Are there any other recommendations or concerns for soft migration to the new version?

Have a look at our Upgrade Instructions: https://www.adaxes.com/resources/InstNotes.htm#upgrade.

Comments

Hello,
As we used tons of powershell script we are also afraid about this upgrade. Not the process itself which is simple but the compatbility of all our scripts.
Regards,

---

Hello,

You need to have no worries, all the scripts should work fine after the upgrade.

---

Regarding the scripts, there are some limitations I assume.
Our prod 3.8 is running on 2008 R2 with PS v3 and our testing 3.9 is running on 2012 R2 with PS v5.1, none of these can run our PS script that runs fine on same 2008 R2 server natively...
3.9 Adaxes show less errors, but still fails with the error "The pipeline has been stopped."
Could you please list out the differences or limitations of both versions, what we should not expect to work when running powershell inside Adaxes and maybe possible alternatives?
Thank you.

---

Hello,

3.9 Adaxes show less errors, but still fails with the error "The pipeline has been stopped."

This error means that the script does not manage to complete within the specified limit of time which is 10 minutes by default. If you provide us with the full script you are using, we will be able to provide more details and a possible solution.

Also, you can increase the script timeout. For details, have a look at the following help article: https://www.adaxes.com/help/?ManageBusi ... meout.html.

Could you please list out the differences or limitations of both versions, what we should not expect to work when running powershell inside Adaxes and maybe possible alternatives?

The difference is that Adaxes 2017.2 and earlier support PowerShell 2.0 and Adaxes 2018.1 supports PowerShell 3.0 and later. There are no limitations in Adaxes itself, there are only limitations related to the PowerShell version supported.

---

Thank you. Powershell versions explain the issues I have.
And the timeout increase solved the issue on Adaxes 2018, but the script to change the timeout does not work on Adaxes 2017. Is that expected and there is a different way to increase the timeout on the older version?

On Server 2008 R2 with Adaxes 2017 I get this error when trying to query existing timeout:

GAC    Version        Location                                                                                                                                                                                                                                                                                        
---    -------        --------                                                                                                                                                                                                                                                                                        
True   v2.0.50727     C:\Windows\assembly\GAC_MSIL\Softerra.Adaxes.Adsi\3.8.14823.0__43a637781bd9a3c2\Softerra.Adaxes.Adsi.dll                                                                                                                                                                                        
cmdlet Get-Credential at command pipeline position 1
Supply values for the following parameters:
Exception calling "GetParameter" with "1" argument(s): "Specified method is not supported."
At line:15 char:1
+ Write-Host "Timeout for running PowerShell scripts and external programs: "`
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [], MethodInvocationException
    + FullyQualifiedErrorId : NotSupportedException

---

Hello,

The feature was introduced only in Adaxes 2018.1 and is not available in Adaxes 2017.2 and earlier.