Need to Enable SHA384 on WIndows Server 2008R2

We are trying to enable SHA384 for TLS1.2 on our Windows Server 2008R2. Our credit card merchant account provider is forcing us to it.
Any detailed steps about enabling the higher version would be appreciated!
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.

Russ SuterSenior Software DeveloperCommented:
Your merchant account provider is complying with PCI DSS 3.2 standards. However, the minimum requirement for compliance is TLS 1.1, not 1.2. You need to make sure the lower protocols (PCT 1.0, SSL 2.0, SSL 3.0, TLS 1.0) are disabled. Doing so requires a little registry work but it's not too bad. Here are a couple of articles on how to do it.
Euless_TechAuthor Commented:
Thanks for responding Russ.
Regardless of whether PCI DSS 3.2 standards dictate it, our merchant account provider is requiring us to go to it.
The information above is good about enabling TLS 1.1 and 1.2, but I'm looking specifically for something to help enable SHA384.
Russ SuterSenior Software DeveloperCommented:
OK, well first of all, your merchant provider is being unreasonable. I'd start shopping for a new one. TLS 1.1 is acceptable under PCI DSS 3.2. You might want to hold them to the fire and ask why they require TLS 1.2. Push back a bit (nicely). That being said, in what context are you requiring the SHA384 protocol? Is this for IIS, Certificate Authority, or something else?
Are You Protected from Q3's Internet Threats?

Every quarter, WatchGuard's Threat Lab releases a security report that analyzes the top threat trends impacting companies around the world. For Q3, we saw that 6.8% of the top 100K websites use insecure SSL protocols. Read the full report to start protecting your business today!

Euless_TechAuthor Commented:
Russ SuterSenior Software DeveloperCommented:
OK then, you're talking about the actual SSL certificate? If that's the case then you'll need to get it re-issued by the certificate authority. They should be able to do this either at no charge or for a minimal fee unless they have some sort of tiered pricing which is one price for SHA256 and another for SHA384 or SHA512.
Euless_TechAuthor Commented:
And unfortunately, we have a pretty intricate post/reply configuration set up with the vendor, so changing is not really an option at this time.
Euless_TechAuthor Commented:
I found that the TLS 1.2 settings on the actual server needed to be modified to allow/disallow various connection scenarios.
This is the location for the powershell script I ran, which corrected everything -

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
Euless_TechAuthor Commented:
No one was able to answer my question. I found the solution on the site mentioned on my last comment.
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.