This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Check for Updates - ZAA

Hi, i would like to have some clarification regarding the "Check for Updates" function in ZAA.

Let's say our severs are at version 2017 Update 3a and the clients are at 2017 Update 1.

How does this function works ?

When we click on this option, nothing happens...

I would like to have this update method enabled to give the mobile users some flexibility for the updates to ZAA to be done.

For the moment our mobile users have to contact the helpdesk to receive the update and this is adding more job to what our IT Helpdesk already do...

Thank you !
Parents
  • 0  
    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.

    --

    If you found this post useful, give it a “Like” or click on "Verify Answer" under the "More" button

    Be sure to "Like" My (and a few others) Cool Solutions below! 

    https://community.microfocus.com/members/craigdwilson/bookmarks

  • 0 in reply to   
    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.
  • 0 in reply to 
    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 ?
  • 0   in reply to 
    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.....

    --

    If you found this post useful, give it a “Like” or click on "Verify Answer" under the "More" button

    Be sure to "Like" My (and a few others) Cool Solutions below! 

    https://community.microfocus.com/members/craigdwilson/bookmarks

Reply
  • 0   in reply to 
    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.....

    --

    If you found this post useful, give it a “Like” or click on "Verify Answer" under the "More" button

    Be sure to "Like" My (and a few others) Cool Solutions below! 

    https://community.microfocus.com/members/craigdwilson/bookmarks

Children
  • 0 in reply to   
    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.....