Fix Windows agent upgrade via WPK #9764

JcabreraC · 2021-08-19T10:08:34Z

Related issue
#9735

This PR implements a backup and restore system in case of update failure via WPK in windows.
An update is considered failed when the agent cannot connect to the manager or the ossec-agent.state file does not exist.

Backup process:

Stop Wazuh-Service
Save the Wazuh Home folder
Save the MSI of the currret installation

Rollback:

Uninstall the new version os Wazuh-Agent
Install the previous version of Wazuh-Agent (via msi backed)
Restore Wazuh-Home
Install the Wazuh Service
Start Wazuh-Service

Tests

Windows NT 6.0 ⚠️

Vista x86 -> Powershell is not installed by default and there are no official links to download it.
Vista x64 -> Powershell is not installed by default and there are no official links to download it.
Server 2008 32 bits -> In this specifict version, only the installer is saved in the registry and not the complete .msi file for later installation. When I rollback, the agent works perfectly, but it does not appear in the list of installed programs.

Windows 7 x86

Agent 3.5

Wazuh-Agent folder tree: No files are lost after the rollback. The logs of the failed upgrade (ossec.log) are kept.
After the rollback the agent connects to the manager
After reboot, the Wazuh-Agent starts and connects to the manager.
The correct Wazuh-Agent version is shown in the list of Windows' programs and features.
A new version of Wazuh-Agent can be manually installed via MSI after the rollback process.

Agent 3.7

Wazuh-Agent folder tree: No files are lost after the rollback. The logs of the failed upgrade (ossec.log) are kept.
After the rollback the agent connects to the manager
After reboot, the Wazuh-Agent starts and connects to the manager.
The correct Wazuh-Agent version is shown in the list of Windows' programs and features.
A new version of Wazuh-Agent can be manually installed via MSI after the rollback process.

Agent 3.13

Wazuh-Agent folder tree: No files are lost after the rollback. The logs of the failed upgrade (ossec.log) are kept.
After the rollback the agent connects to the manager
After reboot, the Wazuh-Agent starts and connects to the manager.
The correct Wazuh-Agent version is shown in the list of Windows' programs and features.
A new version of Wazuh-Agent can be manually installed via MSI after the rollback process.

Agent 4.0

Wazuh-Agent folder tree: No files are lost after the rollback. The logs of the failed upgrade (ossec.log) are kept.
After the rollback the agent connects to the manager
After reboot, the Wazuh-Agent starts and connects to the manager.
The correct Wazuh-Agent version is shown in the list of Windows' programs and features.
A new version of Wazuh-Agent can be manually installed via MSI after the rollback process.

Agent 4.1.5

Wazuh-Agent folder tree: No files are lost after the rollback. The logs of the failed upgrade (ossec.log) are kept.
After the rollback the agent connects to the manager
After reboot, the Wazuh-Agent starts and connects to the manager.
The correct Wazuh-Agent version is shown in the list of Windows' programs and features.
A new version of Wazuh-Agent can be manually installed via MSI after the rollback process.

Agent 4.2.1

Wazuh-Agent folder tree: No files are lost after the rollback. The logs of the failed upgrade (ossec.log) are kept.
After the rollback the agent connects to the manager
After reboot, the Wazuh-Agent starts and connects to the manager.
The correct Wazuh-Agent version is shown in the list of Windows' programs and features.
A new version of Wazuh-Agent can be manually installed via MSI after the rollback process.

Windows 7 x64

Agent 3.5

Wazuh-Agent folder tree: No files are lost after the rollback. The logs of the failed upgrade (ossec.log) are kept.
After the rollback the agent connects to the manager
After reboot, the Wazuh-Agent starts and connects to the manager.
The correct Wazuh-Agent version is shown in the list of Windows' programs and features.
A new version of Wazuh-Agent can be manually installed via MSI after the rollback process.

Agent 4.1.5

Wazuh-Agent folder tree: No files are lost after the rollback. The logs of the failed upgrade (ossec.log) are kept.
After the rollback the agent connects to the manager
After reboot, the Wazuh-Agent starts and connects to the manager.
The correct Wazuh-Agent version is shown in the list of Windows' programs and features.
A new version of Wazuh-Agent can be manually installed via MSI after the rollback process.

Agent 4.2.1

Wazuh-Agent folder tree: No files are lost after the rollback. The logs of the failed upgrade (ossec.log) are kept.
After the rollback the agent connects to the manager
After reboot, the Wazuh-Agent starts and connects to the manager.
The correct Wazuh-Agent version is shown in the list of Windows' programs and features.
A new version of Wazuh-Agent can be manually installed via MSI after the rollback process.

Windows Server 2008 R2 x64

Agent 3.5

Wazuh-Agent folder tree: No files are lost after the rollback. The logs of the failed upgrade (ossec.log) are kept.
After the rollback the agent connects to the manager
After reboot, the Wazuh-Agent starts and connects to the manager.
The correct Wazuh-Agent version is shown in the list of Windows' programs and features.
A new version of Wazuh-Agent can be manually installed via MSI after the rollback process.

Agent 3.13

Wazuh-Agent folder tree: No files are lost after the rollback. The logs of the failed upgrade (ossec.log) are kept.
After the rollback the agent connects to the manager
After reboot, the Wazuh-Agent starts and connects to the manager.
The correct Wazuh-Agent version is shown in the list of Windows' programs and features.
A new version of Wazuh-Agent can be manually installed via MSI after the rollback process.

Agent 4.0

Wazuh-Agent folder tree: No files are lost after the rollback. The logs of the failed upgrade (ossec.log) are kept.
After the rollback the agent connects to the manager
After reboot, the Wazuh-Agent starts and connects to the manager.
The correct Wazuh-Agent version is shown in the list of Windows' programs and features.
A new version of Wazuh-Agent can be manually installed via MSI after the rollback process.

Agent 4.1

Wazuh-Agent folder tree: No files are lost after the rollback. The logs of the failed upgrade (ossec.log) are kept.
After the rollback the agent connects to the manager
After reboot, the Wazuh-Agent starts and connects to the manager.
The correct Wazuh-Agent version is shown in the list of Windows' programs and features.
A new version of Wazuh-Agent can be manually installed via MSI after the rollback process.

Agent 4.2

Wazuh-Agent folder tree: No files are lost after the rollback. The logs of the failed upgrade (ossec.log) are kept.
After the rollback the agent connects to the manager
After reboot, the Wazuh-Agent starts and connects to the manager.
The correct Wazuh-Agent version is shown in the list of Windows' programs and features.
A new version of Wazuh-Agent can be manually installed via MSI after the rollback process.

Windows 10 x64

Agent 3.5

Wazuh-Agent folder tree: No files are lost after the rollback. The logs of the failed upgrade (ossec.log) are kept.
After the rollback the agent connects to the manager
After reboot, the Wazuh-Agent starts and connects to the manager.
The correct Wazuh-Agent version is shown in the list of Windows' programs and features.
A new version of Wazuh-Agent can be manually installed via MSI after the rollback process.

Agent 3.13

Wazuh-Agent folder tree: No files are lost after the rollback. The logs of the failed upgrade (ossec.log) are kept.
After the rollback the agent connects to the manager
After reboot, the Wazuh-Agent starts and connects to the manager.
The correct Wazuh-Agent version is shown in the list of Windows' programs and features.
A new version of Wazuh-Agent can be manually installed via MSI after the rollback process.

Agent 4.0

Wazuh-Agent folder tree: No files are lost after the rollback. The logs of the failed upgrade (ossec.log) are kept.
After the rollback the agent connects to the manager
After reboot, the Wazuh-Agent starts and connects to the manager.
The correct Wazuh-Agent version is shown in the list of Windows' programs and features.
A new version of Wazuh-Agent can be manually installed via MSI after the rollback process.

Agent 4.1

Wazuh-Agent folder tree: No files are lost after the rollback. The logs of the failed upgrade (ossec.log) are kept.
After the rollback the agent connects to the manager
After reboot, the Wazuh-Agent starts and connects to the manager.
The correct Wazuh-Agent version is shown in the list of Windows' programs and features.
A new version of Wazuh-Agent can be manually installed via MSI after the rollback process.

Agent 4.2

Wazuh-Agent folder tree: No files are lost after the rollback. The logs of the failed upgrade (ossec.log) are kept.
After the rollback the agent connects to the manager
After reboot, the Wazuh-Agent starts and connects to the manager.
The correct Wazuh-Agent version is shown in the list of Windows' programs and features.
A new version of Wazuh-Agent can be manually installed via MSI after the rollback process.

Windows 10 x86

Agent 3.5

Wazuh-Agent folder tree: No files are lost after the rollback. The logs of the failed upgrade (ossec.log) are kept.
After the rollback the agent connects to the manager
After reboot, the Wazuh-Agent starts and connects to the manager.
The correct Wazuh-Agent version is shown in the list of Windows' programs and features.
A new version of Wazuh-Agent can be manually installed via MSI after the rollback process.

Agent 3.13

Wazuh-Agent folder tree: No files are lost after the rollback. The logs of the failed upgrade (ossec.log) are kept.
After the rollback the agent connects to the manager
After reboot, the Wazuh-Agent starts and connects to the manager.
The correct Wazuh-Agent version is shown in the list of Windows' programs and features.
A new version of Wazuh-Agent can be manually installed via MSI after the rollback process.

Agent 4.0

Wazuh-Agent folder tree: No files are lost after the rollback. The logs of the failed upgrade (ossec.log) are kept.
After the rollback the agent connects to the manager
After reboot, the Wazuh-Agent starts and connects to the manager.
The correct Wazuh-Agent version is shown in the list of Windows' programs and features.
A new version of Wazuh-Agent can be manually installed via MSI after the rollback process.

Agent 4.1

Wazuh-Agent folder tree: No files are lost after the rollback. The logs of the failed upgrade (ossec.log) are kept.
After the rollback the agent connects to the manager
After reboot, the Wazuh-Agent starts and connects to the manager.
The correct Wazuh-Agent version is shown in the list of Windows' programs and features.
A new version of Wazuh-Agent can be manually installed via MSI after the rollback process.

Agent 4.2

Wazuh-Agent folder tree: No files are lost after the rollback. The logs of the failed upgrade (ossec.log) are kept.
After the rollback the agent connects to the manager
After reboot, the Wazuh-Agent starts and connects to the manager.
The correct Wazuh-Agent version is shown in the list of Windows' programs and features.
A new version of Wazuh-Agent can be manually installed via MSI after the rollback process.

Windows Server 2016 x64

Agent 3.5

Wazuh-Agent folder tree: No files are lost after the rollback. The logs of the failed upgrade (ossec.log) are kept.
tree_3.5.zip
After the rollback the agent connects to the manager
After reboot, the Wazuh-Agent starts and connects to the manager.
The correct Wazuh-Agent version is shown in the list of Windows' programs and features.
A new version of Wazuh-Agent can be manually installed via MSI after the rollback process.

Agent 3.7

Wazuh-Agent folder tree: No files are lost after the rollback. The logs of the failed upgrade (ossec.log) are kept.
After the rollback the agent connects to the manager
After reboot, the Wazuh-Agent starts and connects to the manager.
The correct Wazuh-Agent version is shown in the list of Windows' programs and features.
A new version of Wazuh-Agent can be manually installed via MSI after the rollback process.

Agent 3.13

Wazuh-Agent folder tree: No files are lost after the rollback. The logs of the failed upgrade (ossec.log) are kept.
After the rollback the agent connects to the manager
After reboot, the Wazuh-Agent starts and connects to the manager.
The correct Wazuh-Agent version is shown in the list of Windows' programs and features.
A new version of Wazuh-Agent can be manually installed via MSI after the rollback process.

Agent 4.0

Wazuh-Agent folder tree: No files are lost after the rollback. The logs of the failed upgrade (ossec.log) are kept.
After the rollback the agent connects to the manager
After reboot, the Wazuh-Agent starts and connects to the manager.
The correct Wazuh-Agent version is shown in the list of Windows' programs and features.
A new version of Wazuh-Agent can be manually installed via MSI after the rollback process.

Agent 4.1

Wazuh-Agent folder tree: No files are lost after the rollback. The logs of the failed upgrade (ossec.log) are kept.
After the rollback the agent connects to the manager
After reboot, the Wazuh-Agent starts and connects to the manager.
The correct Wazuh-Agent version is shown in the list of Windows' programs and features.
A new version of Wazuh-Agent can be manually installed via MSI after the rollback process.

Agent 4.2

Wazuh-Agent folder tree: No files are lost after the rollback. The logs of the failed upgrade (ossec.log) are kept.
After the rollback the agent connects to the manager
After reboot, the Wazuh-Agent starts and connects to the manager.
The correct Wazuh-Agent version is shown in the list of Windows' programs and features.
A new version of Wazuh-Agent can be manually installed via MSI after the rollback process.

Windows 8.1 x64

Agent 3.5

Wazuh-Agent folder tree: No files are lost after the rollback. The logs of the failed upgrade (ossec.log) are kept.
After the rollback the agent connects to the manager
After reboot, the Wazuh-Agent starts and connects to the manager.
The correct Wazuh-Agent version is shown in the list of Windows' programs and features.
A new version of Wazuh-Agent can be manually installed via MSI after the rollback process.

Agent 3.13

Wazuh-Agent folder tree: No files are lost after the rollback. The logs of the failed upgrade (ossec.log) are kept.
After the rollback the agent connects to the manager
After reboot, the Wazuh-Agent starts and connects to the manager.
The correct Wazuh-Agent version is shown in the list of Windows' programs and features.
A new version of Wazuh-Agent can be manually installed via MSI after the rollback process.

Agent 4.0.4

Wazuh-Agent folder tree: No files are lost after the rollback. The logs of the failed upgrade (ossec.log) are kept.
After the rollback the agent connects to the manager
After reboot, the Wazuh-Agent starts and connects to the manager.
The correct Wazuh-Agent version is shown in the list of Windows' programs and features.
A new version of Wazuh-Agent can be manually installed via MSI after the rollback process.

Agent 4.2.0

Wazuh-Agent folder tree: No files are lost after the rollback. The logs of the failed upgrade (ossec.log) are kept.
After the rollback the agent connects to the manager
After reboot, the Wazuh-Agent starts and connects to the manager.
The correct Wazuh-Agent version is shown in the list of Windows' programs and features.
A new version of Wazuh-Agent can be manually installed via MSI after the rollback process.

Windows 8.1 x86

Agent 3.5

Wazuh-Agent folder tree: No files are lost after the rollback. The logs of the failed upgrade (ossec.log) are kept.
After the rollback the agent connects to the manager
After reboot, the Wazuh-Agent starts and connects to the manager.
The correct Wazuh-Agent version is shown in the list of Windows' programs and features.
A new version of Wazuh-Agent can be manually installed via MSI after the rollback process.

Agent 3.13

Wazuh-Agent folder tree: No files are lost after the rollback. The logs of the failed upgrade (ossec.log) are kept.
After the rollback the agent connects to the manager
After reboot, the Wazuh-Agent starts and connects to the manager.
The correct Wazuh-Agent version is shown in the list of Windows' programs and features.
A new version of Wazuh-Agent can be manually installed via MSI after the rollback process.

Agent 4.1.5

Wazuh-Agent folder tree: No files are lost after the rollback. The logs of the failed upgrade (ossec.log) are kept.
After the rollback the agent connects to the manager
After reboot, the Wazuh-Agent starts and connects to the manager.
The correct Wazuh-Agent version is shown in the list of Windows' programs and features.
A new version of Wazuh-Agent can be manually installed via MSI after the rollback process.

Agent 4.2.1

Wazuh-Agent folder tree: No files are lost after the rollback. The logs of the failed upgrade (ossec.log) are kept.
After the rollback the agent connects to the manager
After reboot, the Wazuh-Agent starts and connects to the manager.
The correct Wazuh-Agent version is shown in the list of Windows' programs and features.
A new version of Wazuh-Agent can be manually installed via MSI after the rollback process.

Windows server 2012 R2 x64

Agent 3.5

Wazuh-Agent folder tree: No files are lost after the rollback. The logs of the failed upgrade (ossec.log) are kept.
After the rollback the agent connects to the manager
After reboot, the Wazuh-Agent starts and connects to the manager.
The correct Wazuh-Agent version is shown in the list of Windows' programs and features.
A new version of Wazuh-Agent can be manually installed via MSI after the rollback process.

Agent 3.13

Wazuh-Agent folder tree: No files are lost after the rollback. The logs of the failed upgrade (ossec.log) are kept.
After the rollback the agent connects to the manager
After reboot, the Wazuh-Agent starts and connects to the manager.
The correct Wazuh-Agent version is shown in the list of Windows' programs and features.
A new version of Wazuh-Agent can be manually installed via MSI after the rollback process.

Agent 4.0.4

Wazuh-Agent folder tree: No files are lost after the rollback. The logs of the failed upgrade (ossec.log) are kept.
After the rollback the agent connects to the manager
After reboot, the Wazuh-Agent starts and connects to the manager.
The correct Wazuh-Agent version is shown in the list of Windows' programs and features.
A new version of Wazuh-Agent can be manually installed via MSI after the rollback process.

Agent 4.1.5

Wazuh-Agent folder tree: No files are lost after the rollback. The logs of the failed upgrade (ossec.log) are kept.
After the rollback the agent connects to the manager
After reboot, the Wazuh-Agent starts and connects to the manager.
The correct Wazuh-Agent version is shown in the list of Windows' programs and features.
A new version of Wazuh-Agent can be manually installed via MSI after the rollback process.

Agent 4.2.0

Wazuh-Agent folder tree: No files are lost after the rollback. The logs of the failed upgrade (ossec.log) are kept.
After the rollback the agent connects to the manager
After reboot, the Wazuh-Agent starts and connects to the manager.
The correct Wazuh-Agent version is shown in the list of Windows' programs and features.
A new version of Wazuh-Agent can be manually installed via MSI after the rollback process.

Windows server 2012 R2 x64

Agent 3.5

Wazuh-Agent folder tree: No files are lost after the rollback. The logs of the failed upgrade (ossec.log) are kept.
After the rollback the agent connects to the manager
After reboot, the Wazuh-Agent starts and connects to the manager.
The correct Wazuh-Agent version is shown in the list of Windows' programs and features.
A new version of Wazuh-Agent can be manually installed via MSI after the rollback process.

Agent 3.13

Wazuh-Agent folder tree: No files are lost after the rollback. The logs of the failed upgrade (ossec.log) are kept.
After the rollback the agent connects to the manager
After reboot, the Wazuh-Agent starts and connects to the manager.
The correct Wazuh-Agent version is shown in the list of Windows' programs and features.
A new version of Wazuh-Agent can be manually installed via MSI after the rollback process.

Agent 4.0.4

Wazuh-Agent folder tree: No files are lost after the rollback. The logs of the failed upgrade (ossec.log) are kept.
After the rollback the agent connects to the manager
After reboot, the Wazuh-Agent starts and connects to the manager.
The correct Wazuh-Agent version is shown in the list of Windows' programs and features.
A new version of Wazuh-Agent can be manually installed via MSI after the rollback process.

Agent 4.1.5

Wazuh-Agent folder tree: No files are lost after the rollback. The logs of the failed upgrade (ossec.log) are kept.
After the rollback the agent connects to the manager
After reboot, the Wazuh-Agent starts and connects to the manager.
The correct Wazuh-Agent version is shown in the list of Windows' programs and features.
A new version of Wazuh-Agent can be manually installed via MSI after the rollback process.

Agent 4.2.0

Wazuh-Agent folder tree: No files are lost after the rollback. The logs of the failed upgrade (ossec.log) are kept.
After the rollback the agent connects to the manager
After reboot, the Wazuh-Agent starts and connects to the manager.
The correct Wazuh-Agent version is shown in the list of Windows' programs and features.
A new version of Wazuh-Agent can be manually installed via MSI after the rollback process.

Windows server 2019

Agent 3.5

Wazuh-Agent folder tree: No files are lost after the rollback. The logs of the failed upgrade (ossec.log) are kept.
After the rollback the agent connects to the manager
After reboot, the Wazuh-Agent starts and connects to the manager.
The correct Wazuh-Agent version is shown in the list of Windows' programs and features.
A new version of Wazuh-Agent can be manually installed via MSI after the rollback process.

Agent 3.13

Wazuh-Agent folder tree: No files are lost after the rollback. The logs of the failed upgrade (ossec.log) are kept.
After the rollback the agent connects to the manager
After reboot, the Wazuh-Agent starts and connects to the manager.
The correct Wazuh-Agent version is shown in the list of Windows' programs and features.
A new version of Wazuh-Agent can be manually installed via MSI after the rollback process.

Agent 4.0.4

Wazuh-Agent folder tree: No files are lost after the rollback. The logs of the failed upgrade (ossec.log) are kept.
After the rollback the agent connects to the manager
After reboot, the Wazuh-Agent starts and connects to the manager.
The correct Wazuh-Agent version is shown in the list of Windows' programs and features.
A new version of Wazuh-Agent can be manually installed via MSI after the rollback process.

Agent 4.1.5

Wazuh-Agent folder tree: No files are lost after the rollback. The logs of the failed upgrade (ossec.log) are kept.
After the rollback the agent connects to the manager
After reboot, the Wazuh-Agent starts and connects to the manager.
The correct Wazuh-Agent version is shown in the list of Windows' programs and features.
A new version of Wazuh-Agent can be manually installed via MSI after the rollback process.

Agent 4.2.0

Wazuh-Agent folder tree: No files are lost after the rollback. The logs of the failed upgrade (ossec.log) are kept.
After the rollback the agent connects to the manager
After reboot, the Wazuh-Agent starts and connects to the manager.
The correct Wazuh-Agent version is shown in the list of Windows' programs and features.
A new version of Wazuh-Agent can be manually installed via MSI after the rollback process.

Windows server 2022

Agent 3.5

Wazuh-Agent folder tree: No files are lost after the rollback. The logs of the failed upgrade (ossec.log) are kept.
After the rollback the agent connects to the manager
After reboot, the Wazuh-Agent starts and connects to the manager.
The correct Wazuh-Agent version is shown in the list of Windows' programs and features.
A new version of Wazuh-Agent can be manually installed via MSI after the rollback process.

Agent 3.13

Wazuh-Agent folder tree: No files are lost after the rollback. The logs of the failed upgrade (ossec.log) are kept.
After the rollback the agent connects to the manager
After reboot, the Wazuh-Agent starts and connects to the manager.
The correct Wazuh-Agent version is shown in the list of Windows' programs and features.
A new version of Wazuh-Agent can be manually installed via MSI after the rollback process.

Agent 4.0.4

Wazuh-Agent folder tree: No files are lost after the rollback. The logs of the failed upgrade (ossec.log) are kept.
After the rollback the agent connects to the manager
After reboot, the Wazuh-Agent starts and connects to the manager.
The correct Wazuh-Agent version is shown in the list of Windows' programs and features.
A new version of Wazuh-Agent can be manually installed via MSI after the rollback process.

Agent 4.1.5

Wazuh-Agent folder tree: No files are lost after the rollback. The logs of the failed upgrade (ossec.log) are kept.
After the rollback the agent connects to the manager
After reboot, the Wazuh-Agent starts and connects to the manager.
The correct Wazuh-Agent version is shown in the list of Windows' programs and features.
A new version of Wazuh-Agent can be manually installed via MSI after the rollback process.

Agent 4.2.0

Wazuh-Agent folder tree: No files are lost after the rollback. The logs of the failed upgrade (ossec.log) are kept.
After the rollback the agent connects to the manager
After reboot, the Wazuh-Agent starts and connects to the manager.
The correct Wazuh-Agent version is shown in the list of Windows' programs and features.
A new version of Wazuh-Agent can be manually installed via MSI after the rollback process.

nmkoremblum

LGTM 👍

JcabreraC · 2021-10-06T15:16:33Z

LGTM !

JcabreraC · 2021-10-06T15:16:39Z

LGTM !

JcabreraC added module/upgrade/wpk module/upgrade Issue related to the upgrade process labels Aug 19, 2021

JcabreraC assigned juliancnn, JcabreraC and nmkoremblum Aug 19, 2021

JcabreraC linked an issue Aug 19, 2021 that may be closed by this pull request

Fix upgrade via WPK on Windows #9735

Closed

nmkoremblum force-pushed the 9735-fix-WPK-upgrade-windows branch from 3c5c50b to 8742a69 Compare August 26, 2021 14:32

juliancnn force-pushed the 9735-fix-WPK-upgrade-windows branch from 8742a69 to d4f50db Compare August 31, 2021 20:18

juliancnn marked this pull request as ready for review August 31, 2021 20:19

juliancnn force-pushed the 9735-fix-WPK-upgrade-windows branch from f8ff2fc to d43129c Compare September 2, 2021 13:23

nmkoremblum marked this pull request as draft September 2, 2021 13:39

juliancnn force-pushed the 9735-fix-WPK-upgrade-windows branch 4 times, most recently from bf421ad to 22dafd2 Compare September 2, 2021 20:57

nmkoremblum marked this pull request as ready for review September 3, 2021 12:54

juliancnn force-pushed the 9735-fix-WPK-upgrade-windows branch 2 times, most recently from f051879 to d513844 Compare September 6, 2021 19:31

nmkoremblum force-pushed the 9735-fix-WPK-upgrade-windows branch 2 times, most recently from b205a55 to 31b0946 Compare September 7, 2021 13:30

juliancnn force-pushed the 9735-fix-WPK-upgrade-windows branch 10 times, most recently from 3091abc to 2065669 Compare September 9, 2021 16:14

nmkoremblum requested a review from miguemedina11 September 23, 2021 20:11

nmkoremblum assigned JcabreraC Sep 23, 2021

nmkoremblum requested review from nmkoremblum and juliancnn September 23, 2021 20:12

juliancnn and others added 13 commits October 5, 2021 19:36

Excluding folders from being eliminated on unistall

3699883

Add Windows rollback when WPK upgrade fails

048761d

Forces reading Windows native registry

f009dd6

Code and logging improved

7884e02

Remove backup folder adter

e13afc9

Select powershell according to architecture

85abbaa

Wait until the agent uninstall is finished

06b3bcc

Powershell selection condition modified and do-while fixed

1123188

Forces wazuh-agent stop before downgrade

59851f0

Removes rollback check-install

4ce44da

Service installation improved when doing rollback

5ae1d00

PowerShell scope issue fixed

4038a38

Delete installer.log.save if already exists

186dc23

juliancnn marked this pull request as draft October 5, 2021 19:41

juliancnn force-pushed the 9735-fix-WPK-upgrade-windows branch from 3a7dfa7 to 186dc23 Compare October 5, 2021 19:41

juliancnn changed the base branch from 4.2 to master October 5, 2021 19:42

juliancnn marked this pull request as ready for review October 5, 2021 19:42

Removes the MSI file before restore files

3781141

juliancnn approved these changes Oct 6, 2021

View reviewed changes

nmkoremblum approved these changes Oct 6, 2021

View reviewed changes

vikman90 approved these changes Oct 6, 2021

View reviewed changes

vikman90 merged commit a9bb41a into master Oct 6, 2021

vikman90 deleted the 9735-fix-WPK-upgrade-windows branch October 6, 2021 15:47

vikman90 mentioned this pull request Nov 6, 2023

Wazuh's upgrade process reboot remote host without confirmation or warning #19994

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Fix Windows agent upgrade via WPK #9764

Fix Windows agent upgrade via WPK #9764

JcabreraC commented Aug 19, 2021 •

edited

Loading

nmkoremblum left a comment

JcabreraC commented Oct 6, 2021

JcabreraC commented Oct 6, 2021

Fix Windows agent upgrade via WPK #9764

Fix Windows agent upgrade via WPK #9764

Conversation

JcabreraC commented Aug 19, 2021 • edited Loading

Backup process:

Rollback:

Tests

Windows NT 6.0 ⚠️

Windows 7 x86

Agent 3.5

Agent 3.7

Agent 3.13

Agent 4.0

Agent 4.1.5

Agent 4.2.1

Windows 7 x64

Agent 3.5

Agent 4.1.5

Agent 4.2.1

Windows Server 2008 R2 x64

Agent 3.5

Agent 3.13

Agent 4.0

Agent 4.1

Agent 4.2

Windows 10 x64

Agent 3.5

Agent 3.13

Agent 4.0

Agent 4.1

Agent 4.2

Windows 10 x86

Agent 3.5

Agent 3.13

Agent 4.0

Agent 4.1

Agent 4.2

Windows Server 2016 x64

Agent 3.5

Agent 3.7

Agent 3.13

Agent 4.0

Agent 4.1

Agent 4.2

Windows 8.1 x64

Agent 3.5

Agent 3.13

Agent 4.0.4

Agent 4.2.0

Windows 8.1 x86

Agent 3.5

Agent 3.13

Agent 4.1.5

Agent 4.2.1

Windows server 2012 R2 x64

Agent 3.5

Agent 3.13

Agent 4.0.4

Agent 4.1.5

Agent 4.2.0

Windows server 2012 R2 x64

Agent 3.5

Agent 3.13

Agent 4.0.4

Agent 4.1.5

Agent 4.2.0

Windows server 2019

Agent 3.5

Agent 3.13

Agent 4.0.4

Agent 4.1.5

Agent 4.2.0

Windows server 2022

Agent 3.5

Agent 3.13

Agent 4.0.4

Agent 4.1.5

Agent 4.2.0

nmkoremblum left a comment

Choose a reason for hiding this comment

JcabreraC commented Aug 19, 2021 •

edited

Loading