Anonymous_User Absent Member.
Absent Member.
1014 views

Novell client non SP update using update agent. How?

Hi all.

I was reading ACU and Automatic update agent documentation and didn't
found any clues how to force update of, lets say, NC491SP2 patch kit b.

Documentation says

"If it is run automatically, the Update Agent determines if the
preconfigured number of days have elapsed since the last upgrade check
and then checks the specified location for a newer version of the client.".

What do I need to change in order to make update agent update patches
that do not change client or SP version?

Timo Pietilä
Labels (1)
0 Likes
3 Replies
Anonymous_User Absent Member.
Absent Member.

Re: Novell client non SP update using update agent. How?

Timo Pietilä wrote:

>
>What do I need to change in order to make update agent update patches that
>do not change client or SP version?


It works the same as with ACU.EXE. E.g. you created an unattend.txt file
and you use the major- and minorinternalversion options to force a new
install. E.g. each time you apply some update the client installation
files, you increase the version number in unattend.txt and this will
trigger a new upadate.

--
Marcel Cox
http://support.novell.com/forums
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Novell client non SP update using update agent. How?

Marcel Cox wrote:
> Timo Pietilä wrote:
>
>> What do I need to change in order to make update agent update patches
>> that do not change client or SP version?


> install. E.g. each time you apply some update the client installation
> files, you increase the version number in unattend.txt and this will
> trigger a new upadate.


Thanks. hmmmm... It seems we have so old unattend.txt that isn't
compatible with new nciman.exe. I need to make new one. (weird that it
did work with that old one).

Timo Pietilä
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Novell client non SP update using update agent. How?

Timo Pietilä wrote:

>Thanks. hmmmm... It seems we have so old unattend.txt that isn't
>compatible with new nciman.exe. I need to make new one. (weird that it did
>work with that old one).


I think Novell build an extra securty into NCIMAN.EXE and it now "signs"
the configuration files it generates and refuses versions from a different
version of NCOMAN. This has the advantage that you don't end up with
"dead" options that are not visible in NCIMAN but that might still have an
effect on the client.

--
Marcel Cox (using XanaNews 1.18.1.3)
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.