# Natural Patch Update Issue

**URL:** <https://techcommunity.softwareag.com/t/natural-patch-update-issue/99311>\
**Category:** Forum\
**Tags:** Adabas-Natural, Natural, Natural-News-and-General-Topics\
**Created:** [December 20, 2011, 3:51am UTC](https://techcommunity.softwareag.com/t/natural-patch-update-issue/99311 "2011-12-20T03:51:41Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Tony\_Y](https://sea1.discourse-cdn.com/techcommunity/user_avatar/techcommunity.softwareag.com/tony_y/32/121_2.png) [@Tony\_Y](https://techcommunity.softwareag.com/u/Tony_Y)\
**Post date:** [December 20, 2011, 3:51am UTC](https://techcommunity.softwareag.com/t/natural-patch-update-issue/99311/1 "2011-12-20T03:51:41Z")

</div>

Hi all,

I recently performed an upgrade for Natural from v6.3.9 to v6.3.11. For ease of distribution, customer used Novell ZenWorks (patch management software) to capture the change and distribute to all workstations.

Our software upgrade (select “upgrade” option) in fact performed an uninstall and install actions rather than minor update. Hence, ZenWorks captured a lot of changes which posed a high risk when it reproduced these changes to users.

My questions are:

1. Could R&D make our upgrade process more neat for just minor patch update ? (we’re not upgrade from v6.2 to v6.3)
2. Can someone share how you do the upgrade for big number of Natural users (Windows) ?

Regards.

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/techcommunity/original/3X/c/d/cd19967bb605d28a72d77eb83a1cae22f3df2eb8.svg) [@system](https://techcommunity.softwareag.com/u/system)\
**Post date:** [April 2, 2021, 3:01pm UTC](https://techcommunity.softwareag.com/t/natural-patch-update-issue/99311/2 "2021-04-02T15:01:21Z")

</div>