Managing certificates in Exchange 2010
If you are familiar with Exchange 2010 and trying to install Exchange 2010 for the first time you should have already noticed that the powershell cmdlets used to request and install certificates in Exchange 2007 no longer work in Exchange 2010.
For instance running
New-ExchangeCertificate -GenerateRequest -domainname mail.contoso.msft,autodiscover.contoso.msft,myserver,myserver.internal.contoso.msft -FriendlyName mail.contoso.msft -privatekeyexportable:$true -path c:\cert_myserver.txt
will fail with the following error
A positional parameter cannot be found that accepts argument ‘-Path’.
+ CategoryInfo : InvalidArgument: (:) [New-ExchangeCertificate], ParameterBindingException
+ FullyQualifiedErrorId : PositionalParameterNotFound,New-ExchangeCertificate
and running
Import-ExchangeCertificate -path "c:\CertNew.cer"
will also fail with the same error
A positional parameter cannot be found that accepts argument '-path'.
+ CategoryInfo : InvalidArgument: (:) [Import-ExchangeCertificate], ParameterBindingException
+ FullyQualifiedErrorId : PositionalParameterNotFound,Import-ExchangeCertificate
So here are the commands you should use for Exchange 2010
Solved: Setup Exchange 2007 SP1 CCR passive node fails
When installing Exchange 2007 SP1 in Cluster Continuous Replication (CCR) configuration. The setup of the passive node fails with the following error:
"This is not a passive node. A clustered mailbox server represented by the cluster resource group [clustername] was found on this node."
I've found out that the reason for the problem is that upon finishing the Exchange Cluster installation on the active node the setup will ask you for a restart. Restarting the machine will cause the Windows cluster to failover to the passive node to be and thus causing the Exchange installation to fail on that node.
To solve this problem make sure to move back the cluster resources to the active node and re-run the Exchange 2007 SP1 installation on passive node.
This solution was tested on Microsoft Windows 2008 and Microsoft Exchange 2007 SP1
Give me 2 minutes and I'll save you hours of Exchange troubleshooting !
Disclaimer: Guys if you happen to be suffering from "Event ID: 494" syndrom on your Microsoft Exchange Server do not attempt anything before reading this article, I might save you a lot of time.
It is always frustrating to me to receive a calls from customers telling me that their exchange database is refusing to mount and that they have tried everything, even restored from their last backup but nothing seems to work! Oh if only they'd call earlier
Symptoms: Typically a storage group will fail to mount and an error will be logged in the Application Log with an event id of 494. The error is the following
