Entourage auto setup and Exchange 2007

B

Bill Bryson

Is there some documentation somewhere that documents what needs to be done
on the Exchange 2007 server side to have the correct parameters passed to
the Entourage client during its auto setup process?

As it stands now, the Mac client must be configured manually to have a
search list in the "Search DNS" box of the Network pane for this to even
have a chance at success. This is because the Exchange server returns only
partially qualified names (e.g. "matrix" and not "matrix.place.com").
Unfortunately, in our environment, the Exchange server returns the backend
server (where the mailbox resides) and not the front-end server name that we
must manually change it to later.

This is quite frustrating to have an auto setup process that does not work
for our Exchange environment and evidently many others from the resources
I've found on the Internet.

I'm trying to determine if this is a mis-configuration on our server's part
or whether it is just not happening because that is Microsoft's way.
 
D

Diane Ross

Is there some documentation somewhere that documents what needs to be done
on the Exchange 2007 server side to have the correct parameters passed to
the Entourage client during its auto setup process?
Click to expand...

See if this will help until one of the Exchange experts come along with some
advice:

Connecting Entourage to an Exchange Server from Home

< http://www.entourage.mvps.org/exchange/exchangeathome.html>

Connecting Entourage to an Exchange Server at work

<http://www.entourage.mvps.org/exchange/exchangeatwork.html>
 
W

William Smith

Bill said:
Is there some documentation somewhere that documents what needs to be done
on the Exchange 2007 server side to have the correct parameters passed to
the Entourage client during its auto setup process?

As it stands now, the Mac client must be configured manually to have a
search list in the "Search DNS" box of the Network pane for this to even
have a chance at success. This is because the Exchange server returns only
partially qualified names (e.g. "matrix" and not "matrix.place.com").
Unfortunately, in our environment, the Exchange server returns the backend
server (where the mailbox resides) and not the front-end server name that we
must manually change it to later.

This is quite frustrating to have an auto setup process that does not work
for our Exchange environment and evidently many others from the resources
I've found on the Internet.

I'm trying to determine if this is a mis-configuration on our server's part
or whether it is just not happening because that is Microsoft's way.
Click to expand...

This mis-configuration is probably not to do with your Exchange Server
but more likely with your DNS.

Have a look at "Deployments in an Active Directory infrastructure" on
page 35 of the "Microsoft Office 2004 for Mac Resource Kit" found here
at the bottom of the page
<http://www.microsoft.com/mac/itpros/default.mspx?target=fae54042-e30c-466f-b4de-a1f0993e558c1033>.

Hope this helps!

--

bill

William M. Smith, Microsoft Interop MVP - Mac/Windows
Entourage Help Page <http://entourage.mvps.org/>
Entourage Help Blog <http://blog.entourage.mvps.org/>
 
B

Bill Bryson

William,

Thanks for pointing out the resource site. You mentioned DNS problems.
I've discovered that a number of our Exchange server machines do not have
reverse name lookups defined in our DNS. Therefore I can look up
name.machine.domain but can't look up the IP address (147.26.x.x) that is
associated with that machine. I know in some security schemes that a lookup
is done in both directions.

Bill
 
W

William Smith

Bill said:
William,

Thanks for pointing out the resource site. You mentioned DNS problems.
I've discovered that a number of our Exchange server machines do not have
reverse name lookups defined in our DNS. Therefore I can look up
name.machine.domain but can't look up the IP address (147.26.x.x) that is
associated with that machine. I know in some security schemes that a lookup
is done in both directions.
Click to expand...

Hi Bill!

That's correct. A reverse lookup is typically done to verify that a
server is not a rogue server. I can't tell you for sure that's why
Entourage does it but it would make sense.

--

bill

William M. Smith, Microsoft Interop MVP - Mac/Windows
Entourage Help Page <http://entourage.mvps.org/>
Entourage Help Blog <http://blog.entourage.mvps.org/>
 
Top