CONSOL and AGENT
Published: September 17, 2019 - 3:54 PM
Hello,
Information:
WAPT Server version: 1.7.4
WAPT Agent version: 1.7.5.6177
WAPT Setup version: 1.7.5.6177
WAPT Deploy version: 1.7.5.6177
Database status: OK (1.7.4.0)
Disk space: 92% free
Problem description:
I had opened another post for an installation problem, and that was resolved.
Now my problem is with the CONSOL. In version 1.3.13, the PCs retrieved the associated package groups and loaded their packages.
Since upgrading to version 1.7.0, the PCs no longer join the groups, and when I do it manually, they create a new "package" with their names instead of using the existing groups.
Is this a configuration issue with my server or the agent?
Furthermore, the groups were retrieved from the old server running version 1.3.13.13.
The hosts from the old PCs are not being restored. I would like to find a solution for this as well.
Thank you.
Sincerely,
William.
Information:
WAPT Server version: 1.7.4
WAPT Agent version: 1.7.5.6177
WAPT Setup version: 1.7.5.6177
WAPT Deploy version: 1.7.5.6177
Database status: OK (1.7.4.0)
Disk space: 92% free
Problem description:
I had opened another post for an installation problem, and that was resolved.
Now my problem is with the CONSOL. In version 1.3.13, the PCs retrieved the associated package groups and loaded their packages.
Since upgrading to version 1.7.0, the PCs no longer join the groups, and when I do it manually, they create a new "package" with their names instead of using the existing groups.
Is this a configuration issue with my server or the agent?
Furthermore, the groups were retrieved from the old server running version 1.3.13.13.
The hosts from the old PCs are not being restored. I would like to find a solution for this as well.
Thank you.
Sincerely,
William.