Jooel, thanks for your efforts
After looking into the matter even further it seems your first option was the most suitable altho not in the fashion you've state it. Let me try to explain the whole thing.

Once a machine gets hookedup to our network the loginscript I've wrote sets the registry paths for Device Drivers to a network location. But since the machine is already installed and found no drivers for certain hardware items it isn't gonna look again after the paths are changed. Thats where this scanned comes in. the "Scan for Hardware Changes" in the device manager doesnt change anything because the devices aren't changed. However I did find that if you remove the unknown device and then scan for hardware changes. (also like Allen stated devcon does the trick for scanning for hardware changes) it does work. But when you rightclick the unknown device and then invoke the "update driver" function it also works, I think this could be done in Win32_PnPEntity wich can enumerate all hardware devices just have to try to get it to return devices that have no drivers.