Anonymous_User Absent Member.
Absent Member.
947 views

ACU Update Agent is NOT SILENT

It has been a week plus since semi-successfully pushing out 4.91.sp2 to
1/3 of our 2,200 users. As luck would have it, someone tweaked the
MinorInternalVersion variable from 2 to 3. Well, this meant that all 150
users at my site were needing to update the client AGAIN, although the
version numbers and build numbers were identical.

Granted, this is a function just for this purpose.

However, instead of rerunning the installation as configured, the ACU
Update Agent decided to query the customer to see if they wanted an
UPDATE....

Considering the acu.ini and unattend.txt both say NO to InitialDisplay,
this fact really irked me.

I now have 150 people asking me, "Why do we need to rerun the client
installation?"

Please tell me that the "Update Agent" can run silently, and which
flags/variables are needed to make it work properly.


Labels (1)
0 Likes
1 Reply
Anonymous_User Absent Member.
Absent Member.

Re: ACU Update Agent is NOT SILENT

In the cuagent.ini (located in the i386\admin directory, needs to be moved
to the i386 directory if you want the Update Agent to use it):

[UpdatePrompt]
;
; Specifies whether users are prompted to begin the update
; and notified about the location the update will run from.
;
; Display specifies whether users are prompted to update Novell Client.
;
Display=
;
; Display Location specifies whether users are notified about
; the location that the update is to run from.
;
DisplayLocation=No
;
; Administrator Message specifies additional text that appears
; when the user is prompted to start an update.
;
AdministratorMessage=


>>> On 3/28/2006 at 3:54 pm, in message

<49jWf.368$Cc6.8@prv-forum2.provo.novell.com>, <brian.kinney@state.nm.us>
wrote:
> It has been a week plus since semi-successfully pushing out 4.91.sp2 to
> 1/3 of our 2,200 users. As luck would have it, someone tweaked the
> MinorInternalVersion variable from 2 to 3. Well, this meant that all
> 150
> users at my site were needing to update the client AGAIN, although the
> version numbers and build numbers were identical.
>
> Granted, this is a function just for this purpose.
>
> However, instead of rerunning the installation as configured, the ACU
> Update Agent decided to query the customer to see if they wanted an
> UPDATE....
>
> Considering the acu.ini and unattend.txt both say NO to InitialDisplay,
> this fact really irked me.
>
> I now have 150 people asking me, "Why do we need to rerun the client
> installation?"
>
> Please tell me that the "Update Agent" can run silently, and which
> flags/variables are needed to make it work properly.

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.