Page 1 of 1

Miscellaneous questions

Published: April 28, 2015 - 10:57 AM
by Wapt_use
Hello,

I'm contacting you because I have several questions and I can't find the answers in your documentation.

First, I installed WAPT Server on a 2012R2 machine and it seems that the "WAPTDeploy (to set up GPO deployment)" option is only available on Linux. Can you confirm this?

Second, I edited the wapt-get.ini file on a client machine, adding the following lines to automatically install packages when the machine shuts down: `

waptupgrade_task_period=360`

, `waptupgrade_task_maxruntime=360`

, `waptupdate_task_period=30`,

`waptupdate_task_maxruntime=10`.

However, no scheduled tasks have been created.

Also, do I need to add the above lines to all machines, or can I edit the .ini file when creating my agent?

Finally, I'm currently trying to automate the installation of MS Office 2010, however, I'm encountering a 504 Bad Gateway Network error message when I upload the build I created, even though it works with other packages. Is there a limit to the package size that can be uploaded to the server (the one for MS Office 2010 is 600 MB)?

Thank you in advance for your answers.

Re: Miscellaneous questions

Published: April 29, 2015 - 12:06 PM
by htouvet
Good morning,
1 - The small waptdeploy executable is supposed to be used as part of a GPO to perform the initial client installation.
It's not included in the default Windows version of WaptServer setup (it could be)... but it is available for download
You can take, for example http://wapt.tranquil.it/wapt/releases/l ... deploy.exe

2 - There are 2 operating modes for the customer.
Most commonly, we use the "waptservice" modeA service runs on each client's system account and periodically checks for available updates and updates to be installed using two parameters:
waptupdate_task_period=30
waptupgrade_task_period=360
The waptupdate_task_period parameter has a default value of 120 minutes, which means that each client checks for package updates every 120 minutes, possibly pre-downloading updates useful to it, but without installing them.

The waptupgrade_task_period parameter has a default value of undefined. This means that by default, updates must be initiated by the user, upon shutdown of the machine, or forced by the administrator via the console.
In this mode, a local GPO can be set up to perform updates when the workstation is shut down (via the waptexit.exe program)

The xx_maxruntime parameters are not taken into account in this case

In "agent less" modeWe do not install the waptservice, but we create one or two scheduled tasks that launch the update.
This mode must be set up "manually" (not included by default in the basic wapt installer).
To create scheduled tasks, after installing the wapt client without installing the service, and configuring the 2 or 4 parameters in wapt-get.ini
waptupgrade_task_period=360
waptupgrade_task_maxruntime=60
waptupdate_task_period=30
waptupdate_task_maxruntime=10
and run the command as administrator
wapt-get setup-tasks
If waptupgrade_task_xxx is not defined in the wapt-get.ini file, the upgrade task is not created, only the update task.
The xxx_maxruntime values ​​are used in the Windows task settings to limit the maximum execution time of wapt-get and prevent ghost processes that would remain in case of an error.

Hubert

Re: Miscellaneous questions

Published: April 30, 2015 - 11:21
by Wapt_use
Hello

, thank you for taking the time to reply.

My goal is to install package updates when the computer shuts down.

I'm using WAPT Service mode; you mentioned the waptexit.exe program launched via a scheduled task in GPO. Is that all I need to do?

Valentin

Re: Miscellaneous questions

Published: April 30, 2015 - 12:24 PM
by htouvet
Yes, it's that simple.

The default installation settings are waptservice mode
—checking for available updates every 120 minutes and pre-downloading packages
—and offering to install updates when the computer shuts down using waptexit.exe.

Regarding
the MS Office upload problem, yes, there is a known issue with large packages.
To work around the bug in version 1.1.1:
http://forum.tranquil.it/viewtopic.php? ... ges.py#p23

With version 1.2.3, 64-bit, it should work.

Re: Miscellaneous questions

Published: June 12, 2015 - 11:33
by Wapt_use
I've resolved all my issues; however, the user is given the option to cancel package installations when the computer shuts down.

Is there a way to prevent this window from appearing or to gray out the cancel button?

Re: Miscellaneous questions

Published: June 12, 2015 - 5:05 PM
by Yvan Karmouta
Hello,
I think this thread should answer your question: http://forum.tranquil.it/viewtopic.php?f=13&t=299

Regards,
Yvan

Re: Miscellaneous questions

Published: June 12, 2015 - 5:34 PM
by htouvet
A radical solution is to modify the local GPO to do

Code: Select all

c:\wapt\wapt-get upgrade
instead of launching the graphical interface
waptexit.exe
To implement this, create a WAPT package with an installation procedure similar to

Code: Select all

# -*- coding: utf-8 -*-
from setuphelpers import *

uninstallkey = []

def install():
    try:
        print('Remove waptexit.exe local GPO')
        remove_shutdown_script('c:\wapt\waptexit.exe','')
    except:
        print('GPUpdate failed...')

    try:
        print('Add "waptget.exe upgrade" local GPO')
        add_shutdown_script(r'c:\wapt\wapt-get.exe','upgrade')
        print('Hide UI of shutdown scripts')
        shutdown_scripts_ui_visible(False)
    except:
        print('GPUpdate failed...')


def uninstall():
    try:
        print('Add waptexit.exe local GPO')
        add_shutdown_script('c:\wapt\waptexit.exe','')
    except:
        print('GPUpdate failed...')

    try:
        print('Add "waptget.exe upgrade" local GPO')
        remove_shutdown_script(r'c:\wapt\wapt-get.exe','upgrade')
    except:
        print('GPUpdate failed...')

    print('Show UI of shutdown scripts')
    shutdown_scripts_ui_visible(True)