[RESOLVED] Remote Site OS Deployment

[x-davidl]

Hello,

I would like to configure OS deployment from a remote site
. I have therefore set up a secondary repository. Replication works fine (also for WADS).
I have uploaded the ISO image, drivers, etc., to the primary server.

PXE boot and TFTP boot work correctly,

however, I cannot load scripts and files onto the secondary server.


This works fine on the primary server.

Question: Has anyone already tested and successfully implemented this architecture?

WAPT Server version: 2.2
WAPT Agent version: 2.2.0.11720

Thank you in advance

.

[sfonteneau]

Hello

, the baseipxe link must point directly to the WAPT server and not to the secondary repository.

The WAPT server will then read the secondary repository rules and redirect directly to the correct repository.

Therefore, in your DHCP server, the "baseipxe" link must continue to point to the WAPT server and not to the secondary repository.

[x-davidl]

Hello,

thank you for your reply.

I just tested it, the machine successfully contacts the WAPT server, the ipxe.efi file loads correctly, then contacts the secondary repository and nothing happens. Yet the server is indeed waiting for deployment for this machine with its MAC address.
I've attached all the screenshots.

If I delete the secondary server, it starts downloading boot.wim then the ISO, etc... but it takes too long, hence the secondary repository. But it seems the Nginx server part isn't configured correctly on the secondary server.

Thanks in advance.


Best regards

[sfonteneau]

The nginx installation in your secondary repository seems to be working fine since wads is present.

However, what does your wapt-get.ini file in your secondary repository contain?

Does it have the remote_repo_dirs key in the repo-sync section?

Also, does the folder C:\Program Files (x86)\wapt\repository\wads exist?

Have the secondary repository rules been configured for wads? Is the repository using HTTP or HTTPS? Does your repository support HTTP? (IPXE works with HTTPS but only with public certificate bundles; in that case, HTTP is better.)

Simon

[x-davidl]

Thank you for your reply.

I've attached screenshots; they explain things better:

-wapt-get.ini (remote_repo_dirs is indeed present with wads)
-Program Files folder (the wads directory is indeed inside)
-Secondary repository which is properly synchronized

. Yes, it works with HTTPS (see screenshot). To switch to HTTP, I commented out:

listen 443 ssl;

Thank you in advance

. Best regards.

[x-davidl]

Hello again,

thank you for your help.

It's OK, indeed via HTTP

. Regards.

[x-davidl]

It's much better now,

thank you again.