Page 1 of 1
Prepare for the deployment of software updates
Published: January 25, 2019 - 12:35 PM
by stfr49
Hello,
I'd like to explain my situation. Our network is locked down with a time freeze.
Software updates are performed 3 to 4 times a year.
I wanted to create a group to prepare for the deployment of new software versions from the online repository.
When I select, for example, the latest version of Flash Player, it updates the old version on all workstations.
I would like the workstations to remain on the old version, and for the update to the new version to only occur when I assign them to the newly created group, and then delete the old one.
Is this possible?
Sincerely,
Olivier.
Re: Preparing for software update deployment
Published: January 29, 2019 - 10:02 AM
by gaelds
Good morning,
We also use DeepFreeze on some of our workstations. The only solution I've found so far is to disable the WAPT service on the frozen PCs. When I want to update these rooms, I unfreeze the PC, then restart the WAPT service before running the package upgrade.
I use AutoIt executables to stop or reactivate the service:
Code: Select all
#Region ;**** Directives created by AutoIt3Wrapper_GUI ****
#AutoIt3Wrapper_Icon=Icons\Web Server.ico
#EndRegion ;**** Directives created by AutoIt3Wrapper_GUI ****
#include <Constants.au3>
#include <Timers.au3>
;
; Fonction: Stoppe le service WAPTService et le passe en démarrage en "manuel" dans le registre
;
Const $options_msg = "1+48+256+262144" ; options d'affichage pour la message box principale
WAPTServiceStop()
Func WAPTServiceStop()
Local $user = "administrateur"
Local $pass = "xxx"
RunAsWait($user,@ComputerName,$pass,1,@ComSpec & " /c " & 'net stop WAPTService', @WorkingDir, @SW_HIDE)
RunAs($user,@ComputerName,$pass,1,RegWrite("HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\WAPTService", "Start", "REG_DWORD", 3),@WorkingDir, @SW_HIDE)
Sleep(5000)
MsgBox($options_msg,"Service WAPT","Le service WAPT est arrêté",60)
EndFunc
Re: Preparing for software update deployment
Published: January 29, 2019 - 12:03 PM
by stfr49
I found a solution using the "maturity" parameter.
On the update test machine, I set
`maturities = PROD, DEV, PREPROD`
. On the other client machines, I set it to `PROD`.
This means it will accept all packages with a maturity of either PROD, DEV, or PREPROD.
When I import a new package, I select "Download and edit" and enter "PREPROD" in the "maturity:" field. Then I rebuild the package.
This way, only the PC with PREPROD updates.
I'm now going to leave it in test mode with the software up to date.
I'll then update the PREPROD packages to PROD.
To do this, I right-click on the package in question, select "Edit," change PREPROD to PROD, save, and rebuild the package. The new package with the PROD maturity then updates on all machines.
Re: Preparing for software update deployment
Published: January 29, 2019 - 10:14 PM
by vcardon
Perfect, that's the right use for this feature.
Question?
stfr49, which high school or middle school in Maine-et-Loire is that?
Regards,
Vincent
Re: Preparing for software update deployment
Published: January 31, 2019 - 10:25 AM
by stfr49
This is the Saint Francis college in Châteauneuf-sur-Sarthe
Re: Preparing for software update deployment
Published: January 31, 2019 - 11:47 PM
by vcardon
Saint Francis in Châteauneuf-sur-Sarthe, OK,
give us a call
02 40 97 57 55.
We'd like to know how to better interact with Catholic schools. Can you help us find the right solution?
Vincent
Re: Preparing for software update deployment
Published: February 1, 2019 - 4:19 PM
by stfr49
I just thought of something else: currently, the wapt-get.ini file has to be modified manually on each machine.
Is there a way to modify it remotely in the console without having to physically go to the machine?