J
Joachim
Hello all.
I built up a new Windows 2003 R2 domain from scratch named company.local and
installed Exchange 2007 choosing the typical installation routine. Forest and
Domainmode are native Windows 2003. The installation of a Edge-Exchange 2007
server is not desired, so this ist the only Exchange 2007 Server.
The company will use Office 2007 as client and Outlook Webaccess (OWA) as a
solution for accessing mail when travelling without a notebook.
The URL for OWA must be: https://webmail.company.com.
An internal Enterprise Root CA has been installed.
After adjusting the the external OWA URL everything worked fine with OWA.
But now Outlook 2007 shows a certificate error telling the name of the
certificate does not match the name of the site = Exchange Server.
I've tried the new-virtualdirectory cmdlet on a new website with a 2nd. IP
in order to get a seperate virtual directory for OWA to solve the issue. The
cmdlet exectuted fine without errors but OWA did not work. DNS entries have
been set to the 2nd. IP and poining to webmail.
I believe many companies will face this problems so does someone have a
solution to solve this issue?
Thanks & greetings.
Joachim
I built up a new Windows 2003 R2 domain from scratch named company.local and
installed Exchange 2007 choosing the typical installation routine. Forest and
Domainmode are native Windows 2003. The installation of a Edge-Exchange 2007
server is not desired, so this ist the only Exchange 2007 Server.
The company will use Office 2007 as client and Outlook Webaccess (OWA) as a
solution for accessing mail when travelling without a notebook.
The URL for OWA must be: https://webmail.company.com.
An internal Enterprise Root CA has been installed.
After adjusting the the external OWA URL everything worked fine with OWA.
But now Outlook 2007 shows a certificate error telling the name of the
certificate does not match the name of the site = Exchange Server.
I've tried the new-virtualdirectory cmdlet on a new website with a 2nd. IP
in order to get a seperate virtual directory for OWA to solve the issue. The
cmdlet exectuted fine without errors but OWA did not work. DNS entries have
been set to the 2nd. IP and poining to webmail.
I believe many companies will face this problems so does someone have a
solution to solve this issue?
Thanks & greetings.
Joachim