I would add to this - not sure if this should be in the business forums though? Since moving to the MSP RA model and no longer having access to do remote push installations through the Remote Administrator, we had to fall back on creating a script that deploys ESET using the msi etc. When I began using the script (after some testing and readjustment) to deploy ESET Endpoint Antivirus at our clients' sites (to replace NOD32 Business Edition; usually 4.2, but sometimes 4.1), I would always find (and still do) that some of the endpoints would fail to upgrade due to the error that "Guest_avisindo" mentions above. I should add that particular error has been the exception, not the norm (I would say perhaps once out of every 50 clients - approximate), but I do encounter a slightly more common error (say every 6 out of 50 wherein I get a series of error messages indicating there is an permissions issue making changes to various eset .dll's.
These occurances, albeit rare almost always force me to have to track down the endpoints where the failure occured, boot them into Safe Mode (remotely! Not fun!), run the ESET Uninstaller, reboot into normal mode, and install ESET Endpoint AV again.
This also occurs on servers that I previously had NOD32 Business Edition running on, and have been upgrading to ESET File Security - in those situations however, I'm not running the upgrade script, but instead a simple uninstall script following up by an installation script for File Security. Rebooting a workstation into Safe Mode - not a big deal; doing so with a server of course forces me to have to wait until after hours to do the repair. =) No worries, just venting a bit.
I have images available that show the .dll access errors if anyone would care to see - just not sure how to bring them over to these forums short of creating a photo-hosting account, -
Any insights that would reduce or even eliminate these occurances would be much aprpeciated!