@Tom-Elliott The client is what I suspect is different as I haven’t actually been pushing the client for the last 3 months as I was instructed to remove the client from all but a couple labs. So this is the first attempt for a couple months to have the clients pushed to computers before we image them in order to take full advantage of multicasting from the local nodes. Now it seems that the process used before isn’t working completely together. If I push a client to a computer, it registers with fog, and I see the machine, I suppose (as I haven’t tested) that the snapins and power management will work on these hosts just as they always have. The problem is when I pxe boot the laptops, they show as not registered.
Now I have been running this system here for a couple years since trunk became available so it’s possible I have junk clients registered already, but I didn’t see these machines as I deleted them after removing the clients (at least not in the gui). I can verify this issue does not arise on desktop machines. I just don’t understand why the client would think it wasn’t registered.
I have no idea how any macs could be shared, as we haven’t done anything to initiate that. All clients are currently running Windows 7 so the “randomizing” of any wireless nics isn’t the issue here, but rather in the manner the client registers the hosts.
Quickreg works flawlessly, but it uses different mechanisms to register the nics I’m assuming since it’s still in a pre-boot environment.
