Very unsuccessful getting Entourage to work with Exchange 2007

[ssciarrino]

Ok having major issues for over three weeks of not having Entourage to
connect to our newly install Exchange 2007 with Rollup 3 applied.

Entourage is 11.3.6
Exchange is 2007 with Rollup 3 applied on Windows 2003R2 SP2 Xeon processors
with 4GB of RAM

The users are part of Windows Active Directory. Currently the organizations
users are split. One office is still on Exchange 2003 and the other is one
Exchange 2007. ***The AD users on Exchange 2003 have no problems getting
onto Entourage for their mail.

IMAP4 service on Exchange 2007 server is started and using the local system
account. There are NO errors in the event viewer when trying to do the next
steps:

Login to a Macintosh workstation with the AD user that connects to Exchange
2007 (kf304)
Open Entourage go to new accounts, select Exchange account
Now user ID is kf304 yet mail is (e-mail address removed)

Upon the new account 'wizard' the email information defaults in and I check
exchange account and enter in the user ID, password and domain. This
information is correct because this user can use Outlook Web Access 2007 or
Outlook 2003/2007 on a Windows XP machine

The automatic configuration fails because it cannot detect Directory server
and free/busy server (I would like to tweak the server to avoid this)

Reading MANY sites I then choose Configure account manually instead of
continuing the wizard

On Account settings the Exchange 2007 server DOES default in Exchange server
field, I change this to

https://bo-mail.companyname.com/exchange/[email protected] as per a blog
I read to make this work.

We do use SSL I do not check the override default DAV port and leave this 443

Since there is no public folders setup in our Exchange 2007, I still enter
bo-mail.companyname.com/public

LDAP server defaults in correctly so I leave this alone.

I hit ok to establish the account.

The first thing I get is

'Unable to establish a secure connection to bo-mail.company.com because the
correct root certificate is not installed'

I have read up on this but I can hit Ok to continue, it prompts me for the
user kf304 password (we do not use keychain) and it logs in.

The send/receive doesn't occur automatically, therefore I right-click on the
account and do 'Syncronize Now'

I get 'The action could not be completed. HTTP error. The resource is not
found'

So if I go back and edit the account and check 'override WEBDAV port' and
enter in our port number, then right-click and hit 'syncronize now' again I
get the root certificate warning again and then

'The action could not be completed. An unknown error (170) occurred.'

So trying another option, I remove the 'https:...' line in exchange server
field and just enter BO-MAIL

I get HTTP error. Access to resource is forbidden so thus at least I know
the SSL needs to be on.

If I do https://bo-mail.companyname.com/owa/[email protected] I get

I get Mail could not be retrieved at this time the server account kf304
returned 'Logon failure: unknown user name/password....'

Thus the /owa is not the way to go...

Around and around I go....


Very desperate any insight is greatly appreciated

 

[Corentin Cras-Méneur]

If I do https://bo-mail.companyname.com/owa/[email protected] I get

I get Mail could not be retrieved at this time the server account kf304
returned 'Logon failure: unknown user name/password....'

If you try that in your browser, do you manage to get into the account
through OWA?? That's the only thing I can think of :-\

Corentin

 

[ssciarrino]

Hi Corentin,

Yes I am successful if I use the following:

https://bo-mail.companyname.com/owa/[email protected]

This gets me to the web site so the problem is Entourage and Exchange...

 

[Corentin Cras-Méneur]

Hi Corentin,

Yes I am successful if I use the following:

https://bo-mail.companyname.com/owa/[email protected]

This gets me to the web site so the problem is Entourage and Exchange...

The link structure doesn't seem familiar to me.
You might want to try to use https://bo-mail.companyname.com/owa as the
server address and "(e-mail address removed)" as the use name.

It's usually more like https://bo-mail.companyname.com/excahnge/kf304

with kf304 as the user name.

Corentin

 

[ssciarrino]

Corentin thanks for the help we found the problem...it is with the Exchange
Server 2007 installation. Since WebDav is a de-emphasized option with
Exchange 2007, there is an option during installation to include legacy
systems. This translates to mac clients.

without this install the Virtual folders called ExchWeb, Exchange are not
installed in IIS for the exchange server and thus entourage cannot connect.

We had to manually through the Exchange shell readd these folders and thus
Entourage works...

 

[Corentin Cras-Méneur]

Corentin thanks for the help we found the problem...it is with the Exchange
Server 2007 installation. Since WebDav is a de-emphasized option with
Exchange 2007, there is an option during installation to include legacy
systems. This translates to mac clients.

without this install the Virtual folders called ExchWeb, Exchange are not
installed in IIS for the exchange server and thus entourage cannot connect.

I see.... Thanks for posting the solution back,

We had to manually through the Exchange shell readd these folders and thus
Entourage works...

What a pain :-(

Corentin