Here's the situation, if anyone can help: 1. Created an installer package and exported the einstaller.exe file and used that to install on a client PC. 2. Later, made a change to the installer and wanted to test it. Edited and saved the packaged (did not rename as it was not needed, installer was for the same use) and exported the einstaller.exe file. 3. Uninstalled ESET of the client PC and attempted to install with the new installer; it kept failing. The client installer log shows the server closing the connection and no real information aside from that. The server log shows it was rejecting the install because it thinks the same package was already installed on the client. Bear in mind, I didn't do a config push because it wasn't a change that would effect operation, but more over installation. 4. I cleared the registry of all references to ESET and NOD32, ensured the Program Files directory was clean, tried again with the same result. 5. Renamed the installer package and it worked fine (once exported again) My concern here is if we have a client who's installation becomes corrupted and we have to reinstall, we don't want to have to change a package name just to reinstall on a client.