• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 3782
  • Last Modified:

Installing Exchange Server 2013 on Windows Server 2012

I'm trying to install exchange server 2013. Everytime I get an error whilst it tries to install the Mailbox Role.

Error:
The following error was generated when "$error.Clear();
          Install-ExchangeCertificate -WebSiteName "Exchange Back End" -services "IIS, POP, IMAP" -DomainController $RoleDomainController -InstallInTrustedRootCAIfSelfSigned $true
          if ($RoleIsDatacenter -ne $true -And $RoleIsPartnerHosted -ne $true)
          {
            Install-AuthCertificate -DomainController $RoleDomainController
          }
        " was run: "Could not grant Network Service access to the certificate with thumbprint F14E751BD8D7252CD084F144753E4E9BE8CD571B because a cryptographic exception was thrown.".

That's the error the setup has provided me. A google search hasn't been fruitfull so I turned to you guys for some help. From the error I can understand that the Network Service account ouldn't be granted the access it needed to complete it's task.

In the meantime I'll try and grant the Network Service account the access it needs but so far I wasn't all that successfull. Due to the fact that I couldn't find any certificate with the described thumbprint.

Some information about the server:

- Windows Server 2012 Standard
- No DC, only SQL Server runs on it.
- Quad-core, 8 gb of ram
0
feanaro100
Asked:
feanaro100
  • 4
1 Solution
 
Will SzymkowskiSenior Solution ArchitectCommented:
Do you have an Internal CA? Are you installing CAS/Mailbox role on the same server? Do you already have a older verison of Exchange running in your environment 2007/2010? Take a look at the below link which is a PAQ to an identical issue. Also, do you have your firewalls enabled on this server? When you say
No DC
i am assuming that you are just meaning on this particular server.

PAQ

Will.
0
 
feanaro100Author Commented:
Yes, this server is part of a domain network but the server itself is nog domain controller. We don't have an internal CA and this is the first time we are trying to install exchange server. And because this is a datacenter server the firewalls are indeed enabled.
0
 
feanaro100Author Commented:
Oh and we are trying to install all of the exchange server components on the same server.
0
 
feanaro100Author Commented:
By changing the ownership of the Certificates private keys to myself and granting Network Service Full Control the installation continued.

I did this through the Certificates MMC snap-in and click Manage Private Keys... in the All Tasks sub-menu of the certificate. Thanks for the help @spec01!
0
 
feanaro100Author Commented:
Because the problem disappeared after the above proposed solution.
0

Featured Post

Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

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