Installing the ILM Service with all features (portal, etc.) on one server.You are prompted for a certificate. Rather than use the default I selected an SSL certificate already issued to this server (I was surprised to see it offered the IPsec certificate too).As the install progressed it stopped and reported that the service could not be started.I checked the Event Log to find many errors of "Service cannot be started. System.InvalidOperationException: Found multiple X.509 certificates...".Absolutely true; the SSL certificate has the FQDN and so has the IPsec certificate. What is wrong with that!I temporarily moved the IPsec certificate elsewhere and this dumb service started and the installation completed. I then moved back the IPsec certificate because it would be nice if the server can talk to the rest of the network!Obviously I'm going to have the same problem when this service restarts.What is the solution?ThanksPaul

your ssl cert probably have something more than CN=xxxx ? this is a known issue with RC0, should be fixed in the next release

Hi Anthony,There are the CN and the SAN DNS Name, bothare equal to the FQDN for both SSL and IPsec certificate.Guess it has the feel of an "issue" so I'll stop whining if it is known about.ThanksPaul

To follow-up with Anthony's point, in RC0 the service uses the common name to select the certificate. If your environment has multiple certs with the same CN, you will the see the behavior you described. The service no longer use CN in RC1.