OCS 2007 R2/Exchange 2010 DNS calculator errata, notes and updated version

Published on
10,339 Points
2 Endorsements
Last Modified:

##the calculator has been updated to version 1.6 please download the use the updated version##

Hi there,
After the previous post of the original version of the calculator here :


I have received lot of feedback regarding the calculator, I was so amazed that a lot of people liked it, but lot of confusion came along with it, the errata has some clarification and also I made some corrections to the calculator to be more clear.

So here are my notes:
You can use the calculator with OCS 2007 R2 only, you cannot use it with OCS 2007, maybe it will work but we didn’t test it against 2007, there are no plans in the future to test it but it might be a step that we make but not soon.
You can use the calculator for Exchange 2007 and 2010 deployments; there are no differences between both products in the certificate requirements.
For HLB (hardware load balancers) the calculator will work if you assigned the edge FQDN to the VIPs, it will work very smoothly and we have tested it.
To generate certificate request, use the OCS installer to create the certificate using the certificate wizard, copy and paste the names generated by the certificate calculator in the certificate wizard.
Make sure to import the certificate on the same server you generated the certificate request from and export it along with the private key, this is mandatory to be able to assign the certificate to other servers.

We have uploaded a newer version of the calculator that has the following fixes:

If you are using a certificate for Exchange and OCS, the certificate common name must be sip.domain.com or whatever the FQDN that will be assigned to the edge access and web conference, this is a limitation that comes from the OCS and we fixed that in the current release.
If you cannot make the certificate common name the Edge Access FQDN, then you can use a separate certificate for the Access Edge and Web Conference Edge.
We removed the web conference FQDN selection, since it has to match the FQDN assigned to the access FQDN.
We added port feature, so now you can assign a port and this will help in configuring the web conference edge.

You can obtain the new version from the below link:

Expert Comment

According to the calculator av.domain.tld needs an external certificate. Is that really correct? As far as i know the certificate for av.domain.tld doesnt need a trusted certificate.
LVL 33

Author Comment

Yes AV certificate doesn't need to be external

Featured Post

Cloud Class® Course: Microsoft Windows 7 Basic

This introductory course to Windows 7 environment will teach you about working with the Windows operating system. You will learn about basic functions including start menu; the desktop; managing files, folders, and libraries.

Join & Write a Comment

Basic Overview of office 365 user portal
Learn the basics of Skype For Business in office 365

Keep in touch with Experts Exchange

Tech news and trends delivered to your inbox every month