Hello,
I'm writing to share a problem I haven't been able to solve yet.
I migrated from version 1.2.3 to 1.3.5 and added the waptupgrade package to all the machines being migrated. However, the update isn't working for everyone:
- there are no errors in the console, but...
The search returned 4 results
- June 24, 2016 - 3:09 PM
- Forum: WAPT Packages
- Subject: WaptUpgrade sometimes not working
- Answers: 1
- Views : 2617
- April 25, 2016 - 10:13
- Forum: WAPT Packages
- Subject: Waptagent and wapt-get.ini
- Answers: 5
- Views : 6966
Re: Waptagent and wapt-get.ini
Hello,
the modification to waptsetup.iss works perfectly!
Thank you.
ED
the modification to waptsetup.iss works perfectly!
Thank you.
ED
- April 21, 2016 - 9:31 AM
- Forum: WAPT Packages
- Subject: Waptagent and wapt-get.ini
- Answers: 5
- Views : 6966
Re: Waptagent and wapt-get.ini
Thanks for the replies, I'll test modifying the .iss file and regenerate the client.
ED
ED
- April 20, 2016 - 3:19 PM
- Forum: WAPT Packages
- Subject: Waptagent and wapt-get.ini
- Answers: 5
- Views : 6966
Waptagent and wapt-get.ini
Hello,
I'm trying to configure the console settings (co-located with the server) so that the "generated" waptagent installs a custom wapt-get.ini file (the multi-repository settings) on the target workstation.
Do you have any tips on how to achieve this without using a meta-executable?
Thanks...
I'm trying to configure the console settings (co-located with the server) so that the "generated" waptagent installs a custom wapt-get.ini file (the multi-repository settings) on the target workstation.
Do you have any tips on how to achieve this without using a meta-executable?
Thanks...
