Enable Your Employees To Focus On The Core With Intuitive Onscreen Guidance That is With You At The Moment of Need.
Course Of The Month
5 days, 19 hours left to enrollBecome a Premium Member and unlock a new, free course in leading technologies each month.
Solved
Installation of Client Access role fails on Windows 2012
Posted on 2012-12-22
I know Exchange 2010 (prior to SP3) is not fully supported on Win2012, but I read that it might just work.
I am getting the following error contstantly:
I tried the following which I found many times over:
Still, it keeps giving that error. What to do?
I am getting the following error contstantly:
[12/22/2012 15:21:22.0145] [2] Unexpected Error
[12/22/2012 15:21:22.0191] [2] Could not grant Network Service access to the certificate with thumbprint 5A442CC0A9ED647E03DE0C1BCFD7321AEDF2 96EF because a cryptographic exception was thrown.
[12/22/2012 15:21:22.0192] [2] Access is denied.
[12/22/2012 15:21:22.0194] [2] Ending processing.
[12/22/2012 15:21:22.0195] [1] The following 1 error(s) occurred during task execution:
[12/22/2012 15:21:22.0195] [1] 0. ErrorRecord: Could not grant Network Service access to the certificate with thumbprint 5A442CC0A9ED647E03DE0C1BCFD7321AEDF2 96EF because a cryptographic exception was thrown.
[12/22/2012 15:21:22.0196] [1] 0. ErrorRecord: Microsoft.Exchange.Management.System Configurat ionTasks.A ddAccessRu leCryptogr aphicExcep tion: Could not grant Network Service access to the certificate with thumbprint 5A442CC0A9ED647E03DE0C1BCF D7321AEDF2 96EF because a cryptographic exception was thrown. ---> System.Security.Cryptograp hy.Cryptog raphicExce ption: Access is denied.
at Microsoft.Exchange.Security.Cryptogr aphy.X509C ertificate s.TlsCerti ficateInfo .CAPIAddAc cessRule(X 509Certifi cate2 certificate, AccessRule rule)
at Microsoft.Exchange.Security.Cryptogr aphy.X509C ertificate s.TlsCerti ficateInfo .AddAccess Rule(X509C ertificate 2 certificate, AccessRule rule)
at Microsoft.Exchange.Management.System Configurat ionTasks.M anageExcha ngeCertifi cate.Enabl eForServic es(X509Cer tificate2 cert, AllowedServices services, Boolean requireSsl, ADSystemConfigurationSessi on dataSession, Server server, List`1 warningList, Boolean allowConfirmation, Boolean forceNetworkService)
--- End of inner exception stack trace ---
at Microsoft.Exchange.Management.System Configurat ionTasks.M anageExcha ngeCertifi cate.Enabl eForServic es(X509Cer tificate2 cert, AllowedServices services, Boolean requireSsl, ADSystemConfigurationSessi on dataSession, Server server, List`1 warningList, Boolean allowConfirmation, Boolean forceNetworkService)
at Microsoft.Exchange.Management.System Configurat ionTasks.I nstallExch angeCertif icate.Enab leForServi ces(X509Ce rtificate2 cert, AllowedServices services)
[12/22/2012 15:21:22.0196] [1] The following error was generated when "$error.Clear(); Install-ExchangeCertificate -services "IIS, POP, IMAP" -DomainController $RoleDomainController" was run: "Could not grant Network Service access to the certificate with thumbprint 5A442CC0A9ED647E03DE0C1BCF D7321AEDF2 96EF because a cryptographic exception was thrown.".
[12/22/2012 15:21:22.0196] [1] Could not grant Network Service access to the certificate with thumbprint 5A442CC0A9ED647E03DE0C1BCFD7321AEDF2 96EF because a cryptographic exception was thrown.
[12/22/2012 15:21:22.0196] [1] Access is denied.
I tried the following which I found many times over:
Fire up MMC, add the Local Computer Certificate store into the console, located the certificate for the computers DNS name when you first went to install Exchange 2010 Beta/RC, (It will be in the personal store if you are getting this error), move it into the Trusted Root Certification Authorities. Now you can install, enjoy :).
Still, it keeps giving that error. What to do?
[X]
Welcome to Experts Exchange
Add your voice to the tech community where 5M+ people just like you are talking about what matters.
- Help others & share knowledge
- Earn cash & points
- Learn & ask questions
2-
2
5 Comments
Active today
Its unsupported. Stop trying to get something to work that hasn't been documented, tested or is a supported configuration. Hearing something "might" work isn't really a good reason to do it.
Deploy it on a supported OS and wait until the service pack is released.
Simon.
Deploy it on a supported OS and wait until the service pack is released.
Simon.
Active today
Wait.
For Service Pack 3.
Do you really think it's a GOOD idea to run a mail service in a known unsupported configuration? I don't know your organization, but all the organizations I've worked for/with find mail pretty critical these days - doing this doesn't just seem unwise... it seems HORRIBLY unwise.
If you need to install Exchange 2010, then use the downgrade rights from 2012 to install a 2008 R2 server and install Exchange 2010 on that.
For Service Pack 3.
Do you really think it's a GOOD idea to run a mail service in a known unsupported configuration? I don't know your organization, but all the organizations I've worked for/with find mail pretty critical these days - doing this doesn't just seem unwise... it seems HORRIBLY unwise.
If you need to install Exchange 2010, then use the downgrade rights from 2012 to install a 2008 R2 server and install Exchange 2010 on that.
I understand your point. I would prefer Exchange 2013 to be honest, but I want it all combined (for many reasons, which dont really matter at the time) on a remote-desktop-server. This setup (RDS+Exchange 2013) is not possible. It won't install.
So its either Exchange 2010 with Win2012, or Win2012 with RDS and Exchange 2013...
So its either Exchange 2010 with Win2012, or Win2012 with RDS and Exchange 2013...
Active today
What you want and what you can have are not always the same thing.
RDS should be deployed on its own server.
Exchange should be deployed on its own server.
You aren't going to get Exchange 2010 to run on Windows 2012, even if you can make it install. That is because Windows 2012 uses PowerShell 3.0 which will not run Exchange 2010 commandlets with the current release.
You are going to have to rethink what you want to do, because I don't think either of your options are possible.
Simon.
RDS should be deployed on its own server.
Exchange should be deployed on its own server.
You aren't going to get Exchange 2010 to run on Windows 2012, even if you can make it install. That is because Windows 2012 uses PowerShell 3.0 which will not run Exchange 2010 commandlets with the current release.
You are going to have to rethink what you want to do, because I don't think either of your options are possible.
Simon.
Featured Post
Question has a verified solution.
If you are experiencing a similar issue, please ask a related question
Suggested Solutions
| Title | # Comments | Views | Activity |
|---|---|---|---|
| Spam Attack - Exchange 2010 | 14 | 40 | |
| Exchange 2013 Message Tracking | 3 | 35 | |
| Ransomware case | 23 | 107 | |
| NSLOOKUP for a DC/GC/DNS results Non-existent Domain | 8 | 21 |
Background Information
Recently I have fixed file server permission issues for one of my client. The client has 1800 users and one Windows Server 2008 R2 domain joined file server with 12 TB of data, 250+ shared folders and the folder structure i…
Find out what you should include to make the best professional email signature for your organization.
In this Micro Tutorial viewers will learn how to use Boot Corrector from Paragon Rescue Kit Free to identify and fix the boot problems of Windows 7/8/2012R2 etc. As an example is used Windows 2012R2 which lost its active partition flag (often happen…
how to add IIS SMTP to handle application/Scanner relays into office 365.
Suggested Courses
Course of the Month5 days, 19 hours left to enroll
734 members asked questions and received personalized solutions in the past 7 days.
Join the community of 500,000 technology professionals and ask your questions.