<div>
Thanks. &nbsp;Shortly after I spoke with a colleague we came to the conclusion of the alternate names for the certificate as well. &nbsp;Thanks for the quick response. &nbsp;
</div>


<div>
<div class="content wysiwyg-content">
I have configured OCS 2007 with an EDGE server for remote user access. &nbsp;With a single domain this was easy, I created a DNS A record and a SIP SRV Record for my domain. <br />
<br />
I then attempted to add the additional domains and configured the new users with their new SIP URI. &nbsp;If you manually configure the connection everything works as intended. &nbsp;However if I try automatic connection the connection fails stating that it is invalid since the domain name is not an exact match. &nbsp;I take this as the new SIP URI doesn't match the DNS A record for my Edge server. &nbsp;<br />
<br />
For this new domain I then created a new DNS A record and updated the SIP SRV Record, however now I am obviously getting certificate errors since my certificate is valid for only my original DNS A record on the server. &nbsp;<br />
<br />
My question is, what is the best setup for my situation. &nbsp;All I am trying to do is successfully handle automatic logon for multiple SIP URI's. &nbsp;<br />
<br />
Thanks. &nbsp;
</div>
</div>


I have configured OCS 2007 with an EDGE server for remote user access.  With a single domain this was easy, I created a DNS A record and a SIP SRV Record for my domain. 

I then attempted to add the additional domains and configured the new users with their new SIP URI.  If you manually configure the connection everything works as intended.  However if I try automatic connection the connection fails stating that it is invalid since the domain name is not an exact match.  I take this as the new SIP URI doesn't match the DNS A record for my Edge server.  

For this new domain I then created a new DNS A record and updated the SIP SRV Record, however now I am obviously getting certificate errors since my certificate is valid for only my original DNS A record on the server.  

My question is, what is the best setup for my situation.  All I am trying to do is successfully handle automatic logon for multiple SIP URI's.  

Thanks.  

Thanks.  Shortly after I spoke with a colleague we came to the conclusion of the alternate names for the certificate as well.  Thanks for the quick response.  

Configure Automatic Login for multiple SIP URI&#39;s on one EDGE Server (DNS/certificate issues/Best Practice)

I have configured OCS 2007 with an EDGE server for remote user access.  With a single domain this was easy, I created a DNS A record and a SIP SRV Record for my domain. 

I then attempted to add the additional domains and configured the new users with their new SIP URI.  If you manually configure the connection everything works as intended.  However if I try automatic connection the connection fails stating that it is invalid since the domain name is not an exact match.  I take this as the new SIP URI doesn&#39;t match the DNS A record for my Edge server.  

For this new domain I then created a new DNS A record and updated the SIP SRV Record, however now I am obviously getting certificate errors since my certificate is valid for only my original DNS A record on the server.  

My question is, what is the best setup for my situation.  All I am trying to do is successfully handle automatic logon for multiple SIP URI&#39;s.  

Thanks.  

Configure Automatic Login for multiple SIP URI's on one EDGE Server (DNS/certificate issues/Best Practice)

The Microsoft Server topic includes all of the legacy versions of the operating system, including the Windows NT 3.1, NT 3.5, NT 4.0 and Windows 2000 and Windows Home Server versions.