We have some new HP Spectre machines that we have to image using a USB to Ethernet dongle. Since there is no Ethernet card in the machine there is no MAC address for FileWave to identify the computer with when it is connecting to the IVS. We have to enter the MAC of the dongle into FileWave for that machine when we need to image it.
Since we are not going to buy a dongle for every HP Spectre we purchase, and we only keep 3 in our tech center for when these machines come in, is there going to be problem if we leave the MAC address of the dongle in the MAC address field in FileWave?
If I try and remove it after the machine does it's inventory I get a formatting error. I could just delete the MAC address completely and then connect it to our wireless but then we will have to log in and then log back out again since we use WPA2 Enterprise for authentication. Not the biggest deal in the world but I was just wondering if leaving it in would cause an issue.
I too am interested in how this could work, as I will have to do the same thing with some Dell Venue tablets. I had an idea that might work, but it is not tested yet, but it is worth a shot. Again, just an idea that might work.
What if we create a dummy client in Filewave that is tied to the MAC address of the dongle, and just put imaging associations with that. Then have placeholders for the systems themselves using the Wireless mac addresses and proper names. From what I understand, the Filewave does not check in with clients based on their MAC address, but rather their hostnames. The IVS would use the MAC. So if you image the system with the dongle MAC address, then rename the system to what it should be name (which can be done during th imaging process automatically) then when it checks in, it will check in with the hostname and automatically be tied to the matching placeholder rather than with the dummy imaging client. The dummy client can then be reused with the next system, just re-enabling the imaging association.
Note: This idea came about when I had to perform a mass renaming of all my systems. If a system is checking in with Filewave regularly, and you rename the system, then it will no longer check in with the Filewave, because it is looking for the hostname. So what I did, was create a script fileset to rename the computers and reboot. Then before applying it, I duplicated all my clients, with the only difference being the listed hostname, as placeholders. Once I pushed out the script, I could see that the original client listed stopped checking in, and when they came back up with the new name, they were checking in with the new client placeholders. Then I was able to delete the original client listings once they all checked in under the new names.