Overview

This script automates the SRM update process for windows environments.

It supports both All-in-One (AIO) and Distributed deployments.

Important Notes

vApp/Binary SRM environments are not updated by this script; they are skipped and must be handled manually.

Prerequisites

Before running the script, ensure the following on the SRM Environments:

* All VMs are powered on and reachable over the network.

* The script should be executed on all windows server of SRM environment.

* The script should be executed from ‘PowerShell’ with administrator user.

* Download `Windows_SRM_Update_1VM_4VM.zip` and copy it to all Windows Environment.

* Download SRM_6.1.1.0_Windows_64-bit_Update_File.zip file and copy it to the same folder where the windows update script is copied

Package Contents

The `Windows_SRM_Update_1VM_4VM.zip ` archive includes:

* ` Windows_SRM_Update.ps1` – Main update script

* ` README.md ` – Reference documentation

Execution Steps

1. Connect to all the windows servers via RDP.

2. Navigate to the directory where Windows update and upgrade zip files are copied.

3. Extract the ‘Windows_SRM_Update_1VM_4VM.zip’ file

4. Copy the SRM windows upgrade file`SRM_6.1.1.0_Windows_64-bit_Update_File` into extracted folder ‘Windows_Update_1_VM_4VM'.

5. Run  ‘PowerShell’ as Administrator user and Navigate to Script Directory

 cd "<Path_to_copied_script _directory>"

6. Run the update script :

.\Windows_SRM_Update.ps1

7. Enter SRM APG Installation Directory

             - When prompted, enter the SRM installation directory

             - Press Enter for default directory: `C:\Program Files\APG`

8. Monitor the Upgrade Progress

  - The script will display progress messages for all modules

9. Repeat all the above steps on all other Windows servers.

Manual steps on ‘Frontend’ Server :

1.Tomcat Configuration

Steps :

Navigate to below file and Comment out the deprecated endorsed JVM parameter and update the jvm-param sequence-number in win-service configuration.

C:\Program Files\APG\Web-Servers\Tomcat\Default\conf\win-service

2. Update the tomcat service and restart.

• manage-modules.cmd update tomcat
• manage-modules.cmd service restart tomcat

Logs

Upgrade logs are available in the SRM Environment at below location:

`<APG_INSTALLATION_PATH>\Tools\Update-Manager\9.1.1\<COMPUTERNAME>.log`

Post SRM Upgrade 

1.       Login to the SRM Admin-UI

2.       Navigate to CONFIG -> SolutionPacks -> Installed SolutionPacks

3.       Check for SolutionPacks Updated and update it

4.       Execute ‘manage-modules.cmd service status all ‘on all windows server to check the status of the services and all services should be up and running.