OWAS Configuration and -CertificateName

I downloaded my certificate and was working on configuring an Office Web App Server 2013 Farm. As I was running the New-OfficeWebAppsFarm cmdlet, I received an error as I was using Subject Name of the certificate for the –CertificateName option as shown here, along with the results of the command saying that it doesn’t work.

New-OfficeWebAppsFarm -internalurl “https://owas.infrastructurehelp.com” -externalurl “https://owas.infrastructurehelp.com” –certificatename “owas.infrastructurehelp.com”

New-OfficeWebAppsFarm : Office Web Apps was unable to find the specified certificate.

At line:1 char:1

+ New-OfficeWebAppsFarm -internalurl “https://owas.infrastructurehelp.com” -externalurl “ht …

+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

    + CategoryInfo          : ObjectNotFound: (:) [New-OfficeWebAppsFarm], ArgumentException

    + FullyQualifiedErrorId : CertificateNotFound,Microsoft.Office.Web.Apps.Administration.NewFarmCommand

The option wants the Friendly Name for the certificate, but the certificate didn’t have one. In the Friendly Name field, if you looked at the Certificate by using the Certificates MMC, it showed “<None>” in the field.

The installation docs are pretty clear that it is supposed to be the Friendly Name. Hey, clip_image002what can I say other than, I just wanted to try and see if it would accept another method of identifying the certificate in the store if there isn’t a Friendly Name. So, I tried using several different variations for the Friendly Name. I tried leaving it blank, I tried using a space between quotes, and I tried a few other methods, but none of them worked. It was kind of a bit of fun on my part to see if I could make it work.

Finally, I broke down, and selected the properties of the certificate in the MMC and entered OWAS.  Of course, it worked perfectly when I used that Friendly Name.

Yeah, I could have saved a couple of minutes if I had taken this step earlier, but I really enjoy experimenting.

This entry was posted in Lync. Bookmark the permalink.

2 Responses to OWAS Configuration and -CertificateName

  1. Pingback: Weekly IT Newsletter – October 20-24, 2014 | Just a Lync Guy

  2. Anon says:

    Saved me the frustration – thanks man

Leave a Reply to Anon Cancel reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s