Hello,
There are generally no caveats in terms of the upgrade itself. The upgrade process remains the same. However, starting from Adaxes 2025.1, only PowerShell 7 is used to run scripts. If cmdlets from modules that are incompatible with PowerShell 7 are used in scripts, the modules are loaded implicitly in background Windows PowerShell 5.1 processes by the Windows PowerShell Compatibility feature. For details about the feature, have a look at the following Microsoft article: https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_windows_powershell_compatibility?view=powershell-7.5. From the Adaxes standpoint, it means that when such a module is imported, the corresponding powershell.exe process is started and will not be closed until Adaxes service is restarted. To remedy the issue, you need to ensure that only module versions compatible with PowerShell 7 are installed on the computer(s) where Adaxes service runs. For the modules that do not have versions compatible with PowerShell 7, we suggest importing/removing modules explicitly in scripts executed in Adaxes using try/finally blocks. This approach will close the external powershell.exe process when the module is removed in the script. For example:
try
{
Import-Module ServerManager
# Your code here
}
finally
{
Remove-Module ServerManager
}