WAPT 1.3 to 1.5 Migration Error

[sfonteneau]

The latest repository releases have enabled the migration.
remains. bug

This bug concerns certificate verification with a server where WAPT is not the only hosted server. It's a very specific case, which goes against the recommendations in the documentation. This doesn't seem to be your issue.

Initially, certificate verification was not active on my end, but a Wireshark query revealed that the agent attempted to contact the following during a `wapt-get register` command:

Code: Select all

_wapt-host._tcp.wapt.domaine.lan: type SRV, class IN
wapt-host.wapt.domaine.lan
wapt.wapt.domaine.lan
16:27:29.020990	DNS	192.168.1.1	53	192.168.1.101	59931	59931	59931	Standard query response 0xd256 No such name A wapt.wapt.domaine.lan SOA passerelle.domaine.lan	173

My agent configuration file:

Code: Select all

repo_url=https://wapt.domaine.lan/wapt
wapt_server=https://wapt.domain.lan

Since the URLs don't match, the agent is sending me back

Code: Select all

C:\WINDOWS\system32>wapt-get register
FATAL ERROR : Exception: Wapt server url not defined or not found in DNS

Thank you again for your attention to this issue!

Strange, could you specify the OS version, the exact Wapt version?.

Wapt seems to be having trouble reading your wapt-get.ini configuration correctly

Where is your Wapt installed? C:\Wapt? Program Files?

[tech62]

Can you specify the OS version and the exact Wapt version?.

Server: Debian 9.3.0
Client: Win10 Pro / 1.5.11 rev 1495 installed via the default path (C:\Program Files (x86)\wapt)

WAPT Server version: 1.5.1.11
WAPT Agent version: 1.5.1.11
WAPT Setup version: 1.5.1.11
WAPT Deploy version: 1.5.1.11
Database status: OK (1.5.1.11)

I tried modifying the file in the %appdata% directory as well as the one in the default installation folder after stopping the service and restarting the machine

[sfonteneau]

Does the Windows path point to

C:\Program Files (x86)\wapt

and not c:\wapt?


Have you made any specific DNS changes, such as modifying SRV records?

[tech62]

In the environment variables, there is no wapt option present.
The DNS is configured as follows:

srvwapt A 192.168.1.15
wapt CNAME srvwapt
wapt-host CNAME srvwapt (added following the Wireshark results).

Edit: I cleaned up the environment variables, where there was still a remnant from a client installation on the machine where the console is installed, but it still doesn't work.

Edit 2: After a reboot, the machine appears correctly, however, from the outside it is "disconnected", and it is impossible to launch the software installation.

[sfonteneau]

wapt-host CNAME srvwapt (added following the wireshark result)

That's not necessary!

Edit2: After a reboot, the computer appears correctly, however from the outside it is "disconnected", and it is impossible to launch the software installation.

What does `wapt-get register` return now?

Code: Select all

wapt-get register -ldebug

If it works, simply restart the service!

Code: Select all

net stop waptservice
net start waptservice

[tech62]

Result

Code: Select all

2017-12-22 15:49:09,578 DEBUG Default encoding : ascii
2017-12-22 15:49:09,579 DEBUG Setting encoding for stdout and stderr to cp850
2017-12-22 15:49:09,579 DEBUG Python path ['C:\\Program Files (x86)\\wapt', 'C:\\Program Files (x86)\\wapt\\python27.zip', 'C:\\Program Files (x86)\\wapt\\DLLs', 'C:\\Program Files (x86)\\wapt\\lib', 'C:\\Program Files (x86)\\wapt\\lib\\plat-win', 'C:\\Program Files (x86)\\wapt\\lib\\lib-tk', 'C:\\Program Files (x86)\\wapt', 'C:\\Program Files (x86)\\wapt\\lib\\site-packages', 'C:\\Program Files (x86)\\wapt\\lib\\site-packages\\pywin32-221-py2.7-win32.egg']
2017-12-22 15:49:09,579 INFO Using local waptservice configuration C:\Program Files (x86)\wapt\wapt-get.ini
2017-12-22 15:49:09,581 DEBUG Config file: C:\Program Files (x86)\wapt\wapt-get.ini
2017-12-22 15:49:11,424 DEBUG Thread 6668 is connecting to wapt db
2017-12-22 15:49:12,349 INFO User Groups:[]
2017-12-22 15:49:12,351 DEBUG WAPT base directory : C:\Program Files (x86)\wapt
2017-12-22 15:49:12,351 DEBUG Package cache dir : C:\Program Files (x86)\wapt\cache
2017-12-22 15:49:12,351 DEBUG WAPT DB Structure version;: 20170610
2017-12-22 15:49:12,361 DEBUG Thread 6668 is connecting to wapt db
2017-12-22 15:49:12,361 DEBUG DB Start transaction
2017-12-22 15:49:12,362 DEBUG DB commit
2017-12-22 15:49:13,407 DEBUG Unable to GET username from SID [secret] 0 : (1332, 'LookupAccountSid', 'Le mappage entre les noms de compte et les ID de s\xe9curit\xe9 n\x92a pas \xe9t\xe9 effectu\xe9.'), using profile directory instead
2017-12-22 15:49:13,522 INFO Run "dmidecode -q"
2017-12-22 15:49:13,536 INFO dmidecode -q command returns code 0
2017-12-22 15:49:18,724 INFO Unknown UUID or hostname has changed: reading host UUID
2017-12-22 15:49:18,726 INFO reading custom host UUID from WMI System Information.
2017-12-22 15:49:18,746 DEBUG DB Start transaction
2017-12-22 15:49:18,747 DEBUG DB commit
2017-12-22 15:49:18,766 DEBUG DB Start transaction
2017-12-22 15:49:18,766 DEBUG DB commit
2017-12-22 15:49:23,430 DEBUG Starting new HTTPS connection (1): wapt.domaine.lan
2017-12-22 15:49:24,019 DEBUG https://wapt.domaine.lan:443 "POST /add_host HTTP/1.1" 200 174
2017-12-22 15:49:24,022 DEBUG Registering host info against server: {u'msg': u'register_host', u'result': {u'computer_fqdn': u'nompc', u'uuid': u'[UUIDSECRET'}, u'success': True, u'request_time': 0.26006007194519043}
Host correctly registered against server https://wapt.domaine.lan.

I am asked to generate a "code signing" certificate, but the option is not present in my version waptconsole 1.5.11, so I re-signed my packages via a classic certificate generated by WAPTConsole, but these do not appear in the list on the client side.

Any ideas?.

[sfonteneau]

The online documentation isn't complete yet, which is why we've advised against migrating from version 1.3 to 1.5 for the time being.

Only new installations of version 1.5 are recommended!

I'll try to push the new, complete migration documentation this afternoon.

Simon

[tech62]

Happy to serve as your "crash test"
Thank you!

[sfonteneau]

You must now follow this documentation:

https://www.wapt.fr/wapt-1.5/waptserver ... grade.html

It is subject to regular updates!

"Tag as code signing" is not available in your version! Don't worry, this option is included by default in the Community Edition.

[tech62]

I reread the documentation and created the missing group to update the database, but on the client side, I still don't see the list of available packages (it's empty).

From my console (version 1.5.11), generating the agent works fine. I then go to the portal to download the agent, and that's where the problem lies: it shows version 1.3.11. A

minor detail, but one that might help some:

I realized that wapt doesn't install/download on demand. Let me explain.

Basically, you have to create a group with the software inside via the console, assign this group to the machine(s) which, after the package update, will download all the components of this group.

Then, the user, by going to localhost:8088 via the web browser, can trigger the installation only if they have been added to the SYSTEM group "waptselfservice", which must first be created on the client.

When the user requests the installation, they will simply need to enter their usual login credentials to authorize the installation.