Exchange 2007 / Entourage 2008

[Frank Trommer]

Hello group!

I have an new Windows 2008 Std Server with Exchange 2007 Std both in 64bit.

I have an Windows SBS 2003 Std SP2 Server in the same network which hosts
AD.
On this server in the past runs Exchange 2003 Std SP2 i ve done an intraorg
Migration to ex2007.

There ar some problems with the entourage 2004 and 2008 clients.
1.
At startup of entourage 2008 there comes up a windows which says i havent
installed an root ca to my client.
If i click ok everthing is working fine.
On the iis server i have activated http and https, but https is unenforced.
From the internet i only route the https port throug the server, and the
certificate is gernerated for the internet hostname.
That problem is only on entourage 2008.
Any ideas?

2.
I tried to open an calendar from a other user which gave me access rights,
but i cannot search the global catalog (global addressbook).
I get an error "no connection possible", i have cecked the ldap port on the
win2k3sbs server but everthing seems to be ok.

greets FT

 

[Corentin Cras-Méneur]

Hi Frank,

There ar some problems with the entourage 2004 and 2008 clients.
1.
At startup of entourage 2008 there comes up a windows which says i havent
installed an root ca to my client.
If i click ok everthing is working fine.
On the iis server i have activated http and https, but https is unenforced.
From the internet i only route the https port throug the server, and the
certificate is gernerated for the internet hostname.
That problem is only on entourage 2008.
Any ideas?

From the intranet, if https is unenforced, did you try setting up the
accounts in Entourage without checking the SSL option??
Did you try importing the root CA in the login (X509Anchors in Tiger)
keychain?

2.
I tried to open an calendar from a other user which gave me access rights,
but i cannot search the global catalog (global addressbook).
I get an error "no connection possible", i have cecked the ldap port on the
win2k3sbs server but everthing seems to be ok.

GAL lookups are conducted through LDAP. That could be a problem in your
LDAP settings. You need just than just the address of the server and the
port, check the many additional options,

Corentin