[SOLVED] OS deployment without an RJ45 controller on a PC

[Nicolas19]

Hello,

First, here's my configuration information:
- WAPT version installed: 2.6.1.17765
- Server OS: Debian
- Administration/package creation machine OS: Windows Server

A quick question regarding OS deployment:
I deploy my OSes using a bootable USB drive, which has always worked perfectly, but the new machines in my fleet no longer have RJ45 ports.
So, I used a small USB Type-C adapter with an RJ45 connector to deploy my first machine, but when I try to deploy a second machine, WAPT uses the MAC address of my adapter, and I end up with the same "not ready" or "awaiting deployment" message.
Do you have any tips to avoid this situation?
For example, can I clear my list of already deployed PCs in the deployment tab without it affecting the PCs in my inventory?
Can the deployment use the machine's serial number as an alternative reference value instead of the network controller's MAC address? (Terrible in my opinion)
Or will I need to buy a separate adapter for each new PC I deploy? (Just kidding, of course. )

Anyway, how do you manage with these new generations of PCs without an RJ45 controller?

Thank you in advance.

[dcardon]

Hi Nicolas,

the machine entries in the deployment tab can be deleted after deployment (and they can be recreated by importing from the inventory).

Depending on the models and dongles, machines may report a different MAC address on the dongle, but this is often after the driver is loaded, so it's not compatible with PXE booting.

However, if you boot with a WADS USB drive and the dongle driver is loaded, it might work. Worth testing.

Otherwise, you'll need to delete the entry in the deployment and reuse the line with the new machine immediately after it. We'll discuss this internally to see how to better handle this case, which we already see from time to time and which will become increasingly common.

Best regards,

Denis

[Nicolas19]

Hello Denis, and first of all, thank you for your quick reply

You tell me:

The machine entries in the deployment tab may be post-deployment (and they can be recreated by importing from the inventory).

I imagine the verb "delete" is missing, and I need to understand correctly: the machine entries in the deployment tab can be deleted after deployment (and they can be recreated by importing from the inventory).

So if it doesn't impact my machines in the inventory then I think I'll do it this way for the moment because in itself, it's not a big deal to have the history of everything that has been deployed.

Yes, in this case, I think RJ45 sockets will soon be nothing more than a distant memory for all of us

[dcardon]

Hello again Nicolas,

You tell me:

The machine entries in the deployment tab may be post-deployment (and they can be recreated by importing from the inventory).

I imagine the verb "delete" is missing, and I need to understand correctly: the machine entries in the deployment tab can be deleted after deployment (and they can be recreated by importing from the inventory).

Yes, indeed... I clicked submit too quickly, I've corrected the post ...

So, if it doesn't affect the machines in my inventory, then I think I'll do it this way for now, because it's not a big deal to have the history of everything that's been deployed.

But yes, I think RJ45 ports will soon be nothing more than a distant memory for all of us.

Maybe I'm a bit too old, but personally I like RJ45 sockets...

Denis

[Nicolas19]

Maybe I'm a bit too old, but personally I like RJ45 sockets...

I'm like you and I think it's a real shame that they're removing them just to make ultra-slim laptops (with increasingly fragile screen hinges, though) )

Thank you again