Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1761
  • Last Modified:

Installation of Client Access role fails on Windows 2012

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:

[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 5A442CC0A9ED647E03DE0C1BCFD7321AEDF296EF 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 5A442CC0A9ED647E03DE0C1BCFD7321AEDF296EF because a cryptographic exception was thrown.
[12/22/2012 15:21:22.0196] [1] 0.  ErrorRecord: Microsoft.Exchange.Management.SystemConfigurationTasks.AddAccessRuleCryptographicException: Could not grant Network Service access to the certificate with thumbprint 5A442CC0A9ED647E03DE0C1BCFD7321AEDF296EF because a cryptographic exception was thrown. ---> System.Security.Cryptography.CryptographicException: Access is denied.

   at Microsoft.Exchange.Security.Cryptography.X509Certificates.TlsCertificateInfo.CAPIAddAccessRule(X509Certificate2 certificate, AccessRule rule)
   at Microsoft.Exchange.Security.Cryptography.X509Certificates.TlsCertificateInfo.AddAccessRule(X509Certificate2 certificate, AccessRule rule)
   at Microsoft.Exchange.Management.SystemConfigurationTasks.ManageExchangeCertificate.EnableForServices(X509Certificate2 cert, AllowedServices services, Boolean requireSsl, ADSystemConfigurationSession dataSession, Server server, List`1 warningList, Boolean allowConfirmation, Boolean forceNetworkService)
   --- End of inner exception stack trace ---
   at Microsoft.Exchange.Management.SystemConfigurationTasks.ManageExchangeCertificate.EnableForServices(X509Certificate2 cert, AllowedServices services, Boolean requireSsl, ADSystemConfigurationSession dataSession, Server server, List`1 warningList, Boolean allowConfirmation, Boolean forceNetworkService)
   at Microsoft.Exchange.Management.SystemConfigurationTasks.InstallExchangeCertificate.EnableForServices(X509Certificate2 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 5A442CC0A9ED647E03DE0C1BCFD7321AEDF296EF 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 5A442CC0A9ED647E03DE0C1BCFD7321AEDF296EF 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?
0
redworks
Asked:
redworks
  • 2
  • 2
1 Solution
 
Simon Butler (Sembee)ConsultantCommented:
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.
0
 
Lee W, MVPTechnology and Business Process AdvisorCommented:
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.
0
 
redworksAuthor Commented:
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...
0
 
Simon Butler (Sembee)ConsultantCommented:
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.
0
 
redworksAuthor Commented:
Seems this really does not work
0

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now