Yet another problem:
not all package groups are associated with the machines.
The search returned 5 results
- March 27, 2018 - 7:47 PM
- Forum: WAPT Server
- Subject: Migration from 1.3.13 to 1.5 - grayed-out button
- Answers: 7
- Views : 5286
- March 27, 2018 - 7:42 PM
- Forum: WAPT Server
- Subject: Migration from 1.3.13 to 1.5 - grayed-out button
- Answers: 7
- Views : 5286
Re: Migration 1.3.13 to 1.5 - greyed-out button - SOLVED
Good catch, the problem was indeed with the Wapt server clock.
Thank you very much for your help,
the buttons are accessible again
. Thanks again.
Thank you very much for your help,
the buttons are accessible again
. Thanks again.
- March 27, 2018 - 7:39 PM
- Forum: WAPT Server
- Subject: Migration from 1.3.13 to 1.5 - grayed-out button
- Answers: 7
- Views : 5286
Re: Migration 1.3.13 to 1.5 - greyed-out button
6 minutes behind the domain
, the Wapt server is now on time
, the Wapt server is now on time
- March 27, 2018 - 7:20 PM
- Forum: WAPT Server
- Subject: Migration from 1.3.13 to 1.5 - grayed-out button
- Answers: 7
- Views : 5286
Re: Migration 1.3.13 to 1.5 - greyed-out button
However, all the positions in the console are online:
`services wapt`, start `wapt.ini`, fill in the correct information.
`services wapt`, start `wapt.ini`, fill in the correct information.
- March 27, 2018 - 6:28 PM
- Forum: WAPT Server
- Subject: Migration from 1.3.13 to 1.5 - grayed-out button
- Answers: 7
- Views : 5286
Migration button from 1.3.13 to 1.5 (greyed out)
Hello,
I have a Debian 8 x64 environment
and a console installed on Windows 10 x64 FC.
The migration procedure was followed to the letter.
All agents were on version 1.3.13 with wapt-upgrade. I
'm having a small problem after the migration, which went very well; my machines appear correctly in the console, but I can't...
I have a Debian 8 x64 environment
and a console installed on Windows 10 x64 FC.
The migration procedure was followed to the letter.
All agents were on version 1.3.13 with wapt-upgrade. I
'm having a small problem after the migration, which went very well; my machines appear correctly in the console, but I can't...
