Publisher could not be verified - Windows 2003 server

I have an application that I am running on W2003 server.   When I access it from a workstation, the Security Warning box that advises "The publisher could not be verified..."  also has a check box that I can advise "don't ask again".

However, when I need to access the app on the server itself, the Security Warning screen does not have the checkbox... so I have to click through all the time.  I am scheduling this app to run at specific times... and I will not be there to click through it.

Is there somewhere I can disable this security "feature" for this application?

Thanks.
Tomster2Asked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

gidds99Commented:
The publishers are listed in Internet Option/Content/Publishers - you can change the options by clicking the advanced button under trusted or untrusted publishers.
Jeff BeckhamEngineerCommented:
bbaoIT ConsultantCommented:
you may also do it with GPEDIT.MSC, the Group Policy Editor. under Local Computer Policy/Computer Configuration/Windows Setttings/Security Settings/Public Key Policies/Automatic Certificate Request Settings, add your new policy here with the build-in wizard.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
The 7 Worst Nightmares of a Sysadmin

Fear not! To defend your business’ IT systems we’re going to shine a light on the seven most sinister terrors that haunt sysadmins. That way you can be sure there’s nothing in your stack waiting to go bump in the night.

Tomster2Author Commented:
Still testing options on this... please leave thread open... thanks.
Tomster2Author Commented:
Found another solution before I got into these.

If you setup the application to be run from a batch file, windows security ignores it... and the question about publishes never comes up.
Tomster2Author Commented:
PS thanks for your comments.  Although I never got into the other solutions, I split the points as a thanks for your taking time to post possible solutions.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
OS Security

From novice to tech pro — start learning today.