Hi everyone,
I'm contacting you again because I'm having a problem. I can't seem to launch package installations when the computers are powered off.
I'd like to be able to schedule package installations for when the computers start up.
Is this possible with this wonderful tool?
Thank you very much.
Offline workstation deployment
Forum Rules
Community Forum Rules
* English support on www.reddit.com/r/wapt
* French community support is available on this forum
* Please prefix the topic title with [RESOLVED] if it is resolved.
* Please do not edit a topic that is tagged [RESOLVED]. Open a new topic referencing the old one.
* Specify the installed WAPT version, full version, and build number (2.2.1.11957 / 2.2.2.12337 / etc.) as well as the Enterprise/Discovery edition.
* Versions 1.8.2 and earlier are no longer supported. The only questions accepted regarding version 1.8.2 are related to upgrading to a supported version (2.1, 2.2, etc.).
* Specify the server OS (Linux/Windows) and version (Debian Buster/Bullseye - CentOS 7 - Windows Server 2012/2016/2019).
* Specify the OS of the administration/package creation machine and the machine with the problematic agent, if applicable (Windows 7/10/11/Debian 11/etc.).
* Avoid asking multiple questions when opening a topic, otherwise it may be ignored. If there are multiple topics, open separate topics, preferably one after the other and not all at the same time (i.e., do not spam the forum).
* Include code snippets, screenshots, and other images directly in the post. Links to Pastebin, Bitly, and other third-party sites will be systematically removed.
* As with any community forum, support is provided voluntarily by members. If you require commercial support, you can contact Tranquil IT's sales department at 02.40.97.57.55
Community Forum Rules
* English support on www.reddit.com/r/wapt
* French community support is available on this forum
* Please prefix the topic title with [RESOLVED] if it is resolved.
* Please do not edit a topic that is tagged [RESOLVED]. Open a new topic referencing the old one.
* Specify the installed WAPT version, full version, and build number (2.2.1.11957 / 2.2.2.12337 / etc.) as well as the Enterprise/Discovery edition.
* Versions 1.8.2 and earlier are no longer supported. The only questions accepted regarding version 1.8.2 are related to upgrading to a supported version (2.1, 2.2, etc.).
* Specify the server OS (Linux/Windows) and version (Debian Buster/Bullseye - CentOS 7 - Windows Server 2012/2016/2019).
* Specify the OS of the administration/package creation machine and the machine with the problematic agent, if applicable (Windows 7/10/11/Debian 11/etc.).
* Avoid asking multiple questions when opening a topic, otherwise it may be ignored. If there are multiple topics, open separate topics, preferably one after the other and not all at the same time (i.e., do not spam the forum).
* Include code snippets, screenshots, and other images directly in the post. Links to Pastebin, Bitly, and other third-party sites will be systematically removed.
* As with any community forum, support is provided voluntarily by members. If you require commercial support, you can contact Tranquil IT's sales department at 02.40.97.57.55
-
sfonteneau
- WAPT Expert
- Messages: 2318
- Registered: July 10, 2014 - 11:52 PM
- Contact :
It seems to me that if you add c:\wapt\waptexit.exe to the machine's startup script (GPO),
the installation/update should happen at startup.
Simon
the installation/update should happen at startup.
Simon
-
sfonteneau
- WAPT Expert
- Messages: 2318
- Registered: July 10, 2014 - 11:52 PM
- Contact :
Local group policies on the machine should work (gpedit.msc);
this should be automatable in a WAPT package.
this should be automatable in a WAPT package.
-
sfonteneau
- WAPT Expert
- Messages: 2318
- Registered: July 10, 2014 - 11:52 PM
- Contact :
When the workstation starts up, the client will check its host package and the packages it needs to install or update, download the packages, and then wait.
When the workstation shuts down, waptexit will run and install the updates. So, in a way, the installation can be scheduled.
We can go even further. For example, if you want to schedule an installation in the middle of the night, you can have your workstations start in wake-on-LAN mode with a script starting at 2:00 AM and then schedule them to shut down at 2:15 AM. The software will install, and then the workstation will shut down.
You can also have the installation performed at startup with waptexit.exe (and startup scripts).
However, this will make your workstation take longer to start up while installations are in progress.
Another solution, if your users have a strong tendency to never shut down your workstations and to put them in sleep mode (I know some), is to create a scheduled task that will wake the computer to launch waptexit.exe and thus perform the installations.
In short, you can do a lot. For me, standard mode remains the best, with wake-on-LAN mode as an option for machines that don't boot often.
A cool thing you could do is create a script that reads the machine's packages, and if a package isn't up to date, the machine boots in wake-on-LAN mode, while the up-to-date machine doesn't.
Basically, you can do a lot; you just have to be creative!
When the workstation shuts down, waptexit will run and install the updates. So, in a way, the installation can be scheduled.
We can go even further. For example, if you want to schedule an installation in the middle of the night, you can have your workstations start in wake-on-LAN mode with a script starting at 2:00 AM and then schedule them to shut down at 2:15 AM. The software will install, and then the workstation will shut down.
You can also have the installation performed at startup with waptexit.exe (and startup scripts).
However, this will make your workstation take longer to start up while installations are in progress.
Another solution, if your users have a strong tendency to never shut down your workstations and to put them in sleep mode (I know some), is to create a scheduled task that will wake the computer to launch waptexit.exe and thus perform the installations.
In short, you can do a lot. For me, standard mode remains the best, with wake-on-LAN mode as an option for machines that don't boot often.
A cool thing you could do is create a script that reads the machine's packages, and if a package isn't up to date, the machine boots in wake-on-LAN mode, while the up-to-date machine doesn't.
Basically, you can do a lot; you just have to be creative!
