Outlook Security msg connecting to Exchange

I have several small and non-profit clients that are getting those dreaded security alert msgs when they open their outlook (2010 and 2013) connected to Exchange 2010.  I have researched this several times and just am not comfortable with the powershell changes everyone recommends. I have tried the various manual adding of certificates and registry entries to supposedly disable - nothing works. These are small clients and do not want them to have to pay $500 for Microsoft to come in and do the work. Is there a surefire way to just disable the alerts via the registry or GPO OR add the certificate in Outlook 2010/2013??
Who is Participating?

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

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.

What exactly are these security messages saying?
bcp_cnsllcAuthor Commented:
it is your standard outlook security msgs listed in articles such as these



etc. There are a hundred of these and short of doing the ECS I am getting nowhere and to chicken to do the ECS. I would rather hack Outlook itself or try to do something based on a GPO which I have read mentioned but never seen any tangible suggestions/settings to try.

I can paste mult versions of these bec have them on 5 different small companies and 1 larger lawyer firm. These are pretty much based on either the .local is no longer allowed in an ssl OR companies doing a pop and dump into Exchange so they dont need an ssl.
First link has nothing to do with your problem.
For sure you have some problems with certificate.
Or certificate is not trusted by clients (have you bought the certificate), or it is created wrongly for configured exchange server settings. In some cases it is the easiest to change outlook providers for autodiscovery. All settings outlook clients gets from autodiscovery and even if you change registry manually the change will be reverted next time you open outlook.
I'm sorry, but if you plan to support exchange servers (and most of other Ms servers) you will need get comfortable with powershell, because there will be more and more stuff you will not be able to configure thru GUI. And using unsupported solutions can bring you more and more problems...

Is the certificate trusted when you try to connect to owa? Do certificate subject name is the same as msstd record used in outlook exchange proxy settings?

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
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

From novice to tech pro — start learning today.