That only works if the assignment is already made.

Look up the "Stand-Alone Updater" in the Docs.
This will create a stand-alone EXE that will upgrade the Agent.

You can then create a bundle user's can click-on to update their PCs on their schedule vs a push.

Got it !

It is located in the Zenworks System Update documentation :
https://www.novell.com/documentation/zenworks-2017-update-3/pdfdoc/zen_sys_updates/zen_sys_updates.pdf

You have to run the zman zcup command to get this bundle prepared.

For 64Bits clients
zman sucp 5017030a00fc50000000002018092713 -p=Windows -a=64

For 32Bits clients
zman sucp 5017030a00fc50000000002018092713 -p=Windows -a=32

Executables installer are created here :

/opt/novell/zenworks/install/downloads/system-update/5017030a00fc50000000002018092713

Then you can make a bundle with them

Will try this !

Thank you again Craig.

Hi Craig,

Do you know if there is a way for the update to have a similar behavior when launched this way ?

When we launch it with local administrator credentials we have console windows flashing every seconds for 2-3 minutes ( Unpleasant and not reassuring for the users )

If we launch it as a system task then we don't see the % percent of progress and never actually know when the setup is finished.


I have tried a couple known command line switches but they don't work...

Any idea ?

You can pre-extract the installer, which I believe prevents all those DOS boxes.
Run "installername.exe /?" for the command line parameters.

You will need parms to tell it where to extract, to not install(extract only, and the destination.

something like installer -a -x -d c:\temp

Just pulling from very long term memory.

----

If you want to run as system.......
You can set it to "not wait" to finish.
then run the next action as "user".
I can't recall the process name, but it is the small progress notifier in system tray.
Just check task manager.
You may also need to kill the existing process before you start the process as user.

Sorry for being a bit vague....It's been a while since I've done all of this, but the process has not changed.....

This is what i get :

Usage: 17.3.0.1270 windows 32.exe <options>

BUILDTIME <options> are:
-f <file> = add <file> to extractor
-o <outf> = create extractor named <outf>
(default is wrapped.exe)

RUNTIME <options> are:
-l = list contents only (do not extract)
-n = no command execution (extract only)
-x = suppress reboot command passed to ZENPreAgent(Manual Reboot)
-q = show no reboot prompt(quiet install)
-m = have a rebootless agent with limited agent if opting for silent install(-q)
-Z = log ZESM setup.exe installation
-U = force uninstall previous ZENworks Desktop Management agent
-k <registration key> = register with the specified registration key after install
-c <file> = custom standalone install file
-d <dest> = extract files to <dest>
(default is C:\Windows\novell\zenworks\stage\)
-A <file> = read arguments from file
-b <component> = block installation of component

OTHER <options> are:
-v = be verbose
-h = help (show this message)

Unable to continue with the installation. This may be because an instance of agent installation is already running.
Exiting with error code 1.
hit any key to continue

Now i did this :

"17.3.0.1270 windows 32.exe" /n /d ./tempX86
"17.3.0.1270 windows 64.exe" /n /d ./tempX64

I have the msi files and a setup.exe file.

The setup.exe itself does not have much command-line switches possibility
All the MSI are there...

There is also a ZENUpdater.exe file that you cant run directly
and ZENUpdateWatcher.exe

Also lot of jars, and config files.

From what you can recall what were you able to do with these files ?

CRAIGDWILSON;2492604 wrote:
You can pre-extract the installer, which I believe prevents all those DOS boxes.
Run "installername.exe /?" for the command line parameters.

You will need parms to tell it where to extract, to not install(extract only, and the destination.

something like installer -a -x -d c:\temp

Just pulling from very long term memory.

----

If you want to run as system.......
You can set it to "not wait" to finish.
then run the next action as "user".
I can't recall the process name, but it is the small progress notifier in system tray.
Just check task manager.
You may also need to kill the existing process before you start the process as user.

Sorry for being a bit vague....It's been a while since I've done all of this, but the process has not changed.....

ZENUpdater.exe is what you call to run the SU....(Setup.exe is the ZESM Component installer....the SU will call this no need to.)
It does not take parameters...When it kicks off, the SU will run as defined in the ZCC using the SU settings.

The simplest way is to run this as Dynamic Administrator....there should not be a ton of popups this way.

If you choose to run as system, you will want to make sure that action is set to "Not Wait" and have the 2nd action run
ZENUpdateWatcher.exe as user.
This is the process that gives the update progress.

ZENUpdater.exe is what you call to run the SU....(Setup.exe is the ZESM Component installer....the SU will call this no need to.)
It does not take parameters...When it kicks off, the SU will run as defined in the ZCC using the SU settings.

The simplest way is to run this as Dynamic Administrator....there should not be a ton of popups this way.

If you choose to run as system, you will want to make sure that action is set to "Not Wait" and have the 2nd action run
ZENUpdateWatcher.exe as user.
This is the process that gives the update progress.

Unfortunately i am unable to launch the ZenUpdater.exe file.

Takes 2-3 seconds then an error message is displayed saying that the process stopped due to an unknown error.

I tried it on a 32 Bits and a 64 Bits with each respective architecture setups and the results are the same...

:(

I finally found something, it seems that it is not the ZenUpdater.exe file that you need to use.

You can launch the following exe file : StandaloneUpdater.exe as system without waiting for it to end
and then you can launch the ZENUpdateWatcher.exe file as user for the users to see the progress of the update.

Unfortunately the StandaloneUpdater.exe does not seem to take any switches like /s /q -s -q so there is a console window appearing on the user desktop.

I will see if i can fine tune this even more, i would also like the users to have more control over the reboot process.

I will return back with what i find.

anto28;2492706 wrote:
Unfortunately i am unable to launch the ZenUpdater.exe file.

Takes 2-3 seconds then an error message is displayed saying that the process stopped due to an unknown error.

I tried it on a 32 Bits and a 64 Bits with each respective architecture setups and the results are the same...

:(

No, there are no command line parameters....
It will read and use the ZCC System Update Settings to control reboot/prompting behavior.....

For customers who primarily use bundles in this process......
They disable reboot and prompting in the SU settings in the ZCC.

Then use bundle options or a 3rd party tool to control reboot behavior...
(I wrote a cool little tool that some folks use to control reboot on installs....)

If you don't want to see the command line...you can call the EXE from a script action....

Yep, everything is fine now, i have been able to make a bundle out of this and our users were given an icon on their desktops with the condition (not 2017 U3a) and they were free to do the update when it made sense for them.

But in the end we forced the update because some of our users didn't cared or read their emails so...

Still a good thing to know that it is possible to a bundle with this.

We also ended up putting the files on a network share instead of ZCM since the download time via Zenworks was longer.

Thank you Craig for your answers as usual ;)