We use CMS to image new machines. We have gotten in a few Dell laptops (like 5290) that don't have built in Ethernet and I use a USBC dongle to image them. I use the same procedure I use for any other desktop or laptop, get it to iPxe, pick image job, then it reboots to production where it should finish installing some software. Works great for regular desktops and laptops.
For clients without built in Ethernet with these dongles, I get duplicate records in CMS where there is a record in PXE and a record for when machine comes out of PXE. The problem is the job I chose in PXE deploys the image and reboots to production, but then the client never gets the rest of the job because it's a whole new record that has no history of the job running. The original job eventually fails because it thinks it never did reboot to production.
After talking to support, it seems like this is a known issue since NICs are used as primary identifier and in PXE it has 1 NIC (from USBC) and as soon as machine boots, it has a different "fingerprint" because it has USBC NIC + wireless NICs.
I know I could have 1 image job and then a post image task job, but that's a pain for techs, not to mention to then ask techs to delete the "bad" record.
Anyone have created workaround for the issue? I can't imagine managing a few hundred of these machines as is. As machines get smaller and dongles more popular, I'd hope Symantec has an answer for this coming soon.