Page 1 of 1

Installation order

Published: March 5, 2019 - 10:38
by btravers
Hello everyone,

I'd like to install one package first, before all the others. I understand dependencies in the control panel, but that's not enough. Let me explain. I deploy my agents and assign a dependency list to an OU; so far, so good. The problem is that one of my dependencies is the package that allows me to modify my wapt-get.ini file and therefore configure my local repository. If the package isn't applied and my WAPT service hasn't been restarted, they download the software from my main repository...
How can I fix this? I have many workstations behind it.

Thanks
, Bastien

Re: Installation order

Published: March 7, 2019 - 09:02
by seb b
Good morning,

It's worth what it's worth, but for a roughly similar problem, we chose to install the wapt-get.ini configuration package via a startup script.

Code: Select all

wapt-get install xxx-waptserverconfig
which is executed on the first startup of the machine.

That said, it doesn't solve the problem when moving a machine without reinstalling.

Hopefully this might help a little.

Good day.

Seb

Re: Installation order

Published: March 7, 2019 - 09:19
by btravers
Hello, thank you for the reply. That's indeed what I did in a batch file like the one below. It's a bit of a hack, but oh well. I thought there was a built-in method or logic for choosing the first package the client installs. I tried creating a package with a name like s-yyyyyyy or s-0a, but no, it doesn't install first.


`ipconfig /flushdns` `
ping 127.0.0.1`
`gpupdate /force` `
ping 127.0.0.1`
wapt-get remove monpaquetconfigwaptgetini`
`
-get install monpaquetconfigwaptgetini` `
127.0.0.1`
`service stop watservice` `
ping
service start watservice` `
127.0.0.1`
`wapt-get update`
`ping 127.0.0.1`
`wapt-get upgrade`