Problem solved.

It was simply a matter of placing the "dns" folder from the PyDSN module in the package.

Remember to also create a copytree to add it to the clients' WAPT libraries; otherwise, package auditing will return an error.

Hello,

here's a tip for anyone who might find themselves in a similar situation:

I have an executable I compiled myself using AutoIt, which I use to map a network drive. To deploy it, I created a simple WAPT package that pastes the file into the desired location.

Problem: Windows...

If I had to nitpick, there would just be one point:

The audit on the machines gives the same error message, even though the installation is OK.

Hello Denis, and thank you for your reply.

It works perfectly.

The solution was so simple...

I restarted the install on a freshly installed workstation:

Traceback (most recent call last):
File "C:\Program Files (x86)\wapt\common.py", line 3841, in install_wapt
setup = import_setup(setup_filename)
File "C:\Program Files (x86)\wapt\waptutils.py", line 1498, in import_setup
py_mod = imp ...

At the beginning of the code I have a
How do I package it with the package?

Hello,

I've developed a package for post-installation Windows configuration across my network, initially on WAPT 1.8.
The idea is to configure a newly installed machine by retrieving its name from its IP address using reverse DNS.
For this, I'm using the dnspython module.

Since...

Hi,

It seems this functionality is implemented now (button in the right-click menu) but not operational.

At least, for a configuration with machines not in a domain.

Is this normal?