Hi there...
I recently started my own Consulting Company and I landed a big corporate account writing several manufacturing automation desktop solutions for their fabrication floor. I developed these solutions in Visual Studio 2010. The problem I am having is that every time the Operators start the software (Win 7 Pro x86) SEP displays a window stating that the exe came from an unknown source and that I should run it at my own risk.
If I choose to not run, then SEP quarantines the file (REMOVES IT!) and I get a phone call simply because the file is gone. This has happened every time there is a new operator on the floor. The IT Corporate guys are NOT playing fair at all: they REFUSE to add an exception and demand that I purchase a certificate. This is insanity as it was the Company itself that requested the solutions! Anywho, there is nothing I can do now, the projects are deployed and production is underfoot. I can't go back.
I have Signed the solution in Visual Studio with a "self-certificate", as I do with 100% of the solutions I write, but still, I get a detection. I went as far as to create PFXs and CERs and manually force them on the local PC, but still SEP flags my exe.
This is starting to cost me money.
I would like to know what the real and permanent solution for this problem is. If I have to submit my exe to Symantec and pay for a Certificate, so be it, but I am no longer in a position where I can take a call at 3am just because the people on the floor did not read the prompt.
If I am asking something obvious or otherwise idiotic, please bear with me. I am an excellent Automation and Controls guy. I am just completely clueless when it comes to the onerous process of Certification for the Corporate Environment.
Finally, keep in mind I am NOT a 200+ employee development powerhouse. I am Lone Coder trying to earn a living, so solutions on the $10k range are out of the question.
Thanks for ANY guidance!
-Hector