Axigen patches update script - Windows

Support Tools
1

Our support team have generated a PowerShell script to ease installation of Axigen minor updates (Axigen binary, WebMail, and WebAdmin) on Windows.

axigen-update.ps1

SHA1: 3ea331984db280b8c1c2313b7484ce1c1fe1b557

Usage: ./axigen-update.ps1 <SERVICE_NAME>

:information_source: The script requires PowerShell version 5 or newer
:information_source: Because the script is not signed an error could occur. In this case to allow the script to run on your system you should run below command:

Unblock-file axigen-update.ps1

This script will restart the Axigen service, we strongly recommend to run it during a maintenance window.

:warning: Note that this script is not suitable for High-availability cluster installations.

Feel free to express your feedback about this script here or by contacting support team.

Updated: 2024-11-12T22:00:00Z

5

Hi,
I am unable to to use script on Server Core. Manual upgrade is OK.

PS C:\Program Files\Axigen Mail Server> ./axigen-update.ps1 “Axigen Mail Server”
Microsoft Windows Server 2019 Datacenter detected
Axigen service is installed

Axigen install folder: C:\Program Files\Axigen Mail Server
Axigen Working Directory: C:\Program Files\Axigen Mail Server\

Axigen binary version: 10.3.3.2
Webmail interface version: 10.3.3.2.0
Webadmin interface version: 10.3.3.2.0

Invoke-WebRequest : The response content cannot be parsed because the Internet Explorer engine is not available, or
Internet Explorer’s first-launch configuration is not complete. Specify the UseBasicParsing parameter and try again.
At C:\Program Files\Axigen Mail Server\axigen-update.ps1:87 char:21

  • $latest_version = (Invoke-WebRequest -Uri $version_url ).Content

  •                    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    • CategoryInfo : NotImplemented: (:slight_smile: [Invoke-WebRequest], NotSupportedException
    • FullyQualifiedErrorId : WebCmdletIEDomNotSupportedException,Microsoft.PowerShell.Commands.InvokeWebRequestComman
      d

You cannot call a method on a null-valued expression.
At C:\Program Files\Axigen Mail Server\axigen-update.ps1:92 char:1

  • $major_new = $latest_version.split(’.’)[0] + “.” + $latest_version.sp …
  •   + CategoryInfo          : InvalidOperation: (:) [], RuntimeException
  + FullyQualifiedErrorId : InvokeMethodOnNull

You cannot call a method on a null-valued expression.
At C:\Program Files\Axigen Mail Server\axigen-update.ps1:93 char:1

  • $minor_new = $latest_version.split(’.’)[3]
  •   + CategoryInfo          : InvalidOperation: (:) [], RuntimeException
  + FullyQualifiedErrorId : InvokeMethodOnNull

The requested version of Axigen does not exit

Regards
Nenad

6

Hello,

Thank you for your report I will investigate this and I will came back when an update is available.

Thank you.

7

Hi guys. Thanks for the script but seem to have some problems.

Firstly I have the install and the working directories on separate drives. In the script on line 61 & 62, you have the script asking for the $working_path instead of $install_path. I fixed that in my script but then it is throwing up the error of

The requested version of Axigen does not exit

My current version is
Axigen binary version: 10.4.2
Webmail interface version: 10.4.2
Webadmin interface version: 10.4.2

when I point manually to the update url, it is saying that the current version is 10.4.3 but it wont update

Thanks again

8

Hello Acas,

I’m sorry to inform but the update script is not supporting 10.4 (and upper) Axigen versions as we are not anymore distributing patches (for binary and web components) so you have to manual execute the update procedure.

Best regards,
Ioan

9

This is a shame as it was a VERY handy script to use :pensive:

11

A new script that will work with Axigen 10.4.x+ on Windows is available at:
Axigen 10.4.x or newer update script - Windows

12

Unfortunately there’s no such script for Axigen 10.5.x

13

Have you checked above script and did not work for your - or what?