@Wayne-Workman that tool helps with TCP/IP printers, not network shared ones.
@BrendoJohnso Can we see a screenshot of the printer config in the GUI (feel free to replace any sensitive information), as well as the C:\fog.log from a machine that is failing to add the printer?
@chaonatic the simplest way to find the duplicate mac is to open a sql prompt on your FOG server;
Run: mysql -u root -p, and enter your sql root password.
Then run the following commands (replacing the list of macs with the ones the client is using):
use fog;
SELECT * FROM hostMAC WHERE hmMAC IN ('00:01:00:00:00:66', '00:01:00:00:00:67');
exit;
Ideally each mac address should only appear once in the hmMAC result column. If there is one that appears multiple times, that is the culprit.
In general though, these kinds of errors are usually caused by virtual network adapters in your image.
@chaonatic okay, so that points to the virtual network adapter theory. Does your VM have any software-defined adapters that would be copied during imaging? Such as for a VPN, VirtualBox, or some other tunnel?
I remoted in and helped identify the problematic adapter.
I’m currently working on a way for the client to automatically filter out virtual interfaces to help prevent these kinds of issues in the future.
@LaurentB unfortunately, once a client installation occurs, it “locks itself” into the server you first point it at. If you had the old server available, I’d recommend doing: https://wiki.fogproject.org/wiki/index.php?title=FOG_Client#Maintain_Control_Of_Hosts_When_Building_New_Server.
Now, since you don’t have the old server(s), you will have to uninstall, and then install each client. However, if the machines are bound to an Active Directory domain, you should be able to automate this with a simple batch script, and deploy it via GPO.
@Zer0Cool snapins act like children processes attached to the client. This means if the client is stopped (via an uninstall), it’ll likely also stop and delete any running snapins. I’d recommend using a SnapinPack. There could be 2 files in it: a start.bat and a removeclient.[bat/cmd/ps1]. Essentially the start.bat would copy removeclient to another folder, as otherwise it’ll get removed on client uninstall, and then run that script as a new backgrounded process.