> This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.
--B_3342772216_480056
Content-type: text/plain;
charset="ISO-8859-1"
Content-transfer-encoding: 8bit
A;;,
We have discovered an issue with the GAL and 13.0.3.
It appears in both 10.5.8 and 10.6.2 Macs.
The GAL is very unreliable, most of the time it�s inaccessible.
If we uninstall and go back to 13.0.0, it�s fine.
Anyone else?
Scott
--B_3342772216_480056
Content-type: text/html;
charset="ISO-8859-1"
Content-transfer-encoding: quoted-printable
<HTML>
<HEAD>
<TITLE>GAL broken with Entourage 13.0.3 and EWS</TITLE>
</HEAD>
<BODY>
<FONT FACE=3D"Helvetica, Verdana, Arial"><SPAN STYLE=3D'font-size:11pt'>A;;,<BR=
>
<BR>
We have discovered an issue with the GAL and 13.0.3.<BR>
It appears in both 10.5.8 and 10.6.2 Macs.<BR>
The GAL is very unreliable, most of the time it’s inaccessible.<BR>
If we uninstall and go back to 13.0.0, it’s fine.<BR>
<BR>
Anyone else?<BR>
<BR>
Scott</SPAN></FONT>
</BODY>
</HTML>
--B_3342772216_480056--
|
|
0
|
|
|
|
Reply
|
Scott
|
12/4/2009 7:50:16 PM |
|
Scott Boettcher wrote:
> We have discovered an issue with the GAL and 13.0.3.
> It appears in both 10.5.8 and 10.6.2 Macs.
> The GAL is very unreliable, most of the time it�s inaccessible.
> If we uninstall and go back to 13.0.0, it�s fine.
I'm using 13.0.3 both at home, connecting to our OWA server, as well as
at work connecting to our internal Exchange server. No problems
accessing the GAL.
What specifically is not working for you? The 12.x version of Entourage
will use just LDAP for GAL connectivity whereas the 13.x version of
Entourage will use both LDAP and Exchange Web Services (EWS).
EWS facilitates searching/lookups and LDAP facilitates browsing the GAL.
LDAP will only work internally to your company where your Exchange
server is located. Be sure that you're using the address of a Global
Catalog server, which is a special type of domain controller.
Hope this helps!
--
bill
Entourage Help Page <http://entourage.mvps.org/>
Entourage Help Blog <http://blog.entourage.mvps.org/>
YouTalk <http://nine.pairlist.net/mailman/listinfo/youtalk>
Twitter: follow <http://twitter.com/meck>
|
|
0
|
|
|
|
Reply
|
William
|
12/5/2009 3:17:43 AM
|
|
> This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.
--B_3343126509_2805115
Content-type: text/plain;
charset="ISO-8859-1"
Content-transfer-encoding: 8bit
Hi Bill,
Thanks for the reply.
We have verified that on numerous Macs, going from 13.0 to 13.0.3 kills our
GAL access on the EXCH 2007 RU9 setup.
Entourage 12.x is also fine.
So...something changed, and I don�t know what.
We can�t use the 12.2.3 / 13.0.3 upgrade until we know what happened.
Scott
On 12/4/09 7:17 PM, in article u#N$DmVdKHA.3300@TK2MSFTNGP02.phx.gbl,
"William Smith [MVP]" <mecklists@REM0VETH1S.comcast.net.INVALID> wrote:
> Scott Boettcher wrote:
>
>> > We have discovered an issue with the GAL and 13.0.3.
>> > It appears in both 10.5.8 and 10.6.2 Macs.
>> > The GAL is very unreliable, most of the time it�s inaccessible.
>> > If we uninstall and go back to 13.0.0, it�s fine.
>
> I'm using 13.0.3 both at home, connecting to our OWA server, as well as
> at work connecting to our internal Exchange server. No problems
> accessing the GAL.
>
> What specifically is not working for you? The 12.x version of Entourage
> will use just LDAP for GAL connectivity whereas the 13.x version of
> Entourage will use both LDAP and Exchange Web Services (EWS).
>
> EWS facilitates searching/lookups and LDAP facilitates browsing the GAL.
> LDAP will only work internally to your company where your Exchange
> server is located. Be sure that you're using the address of a Global
> Catalog server, which is a special type of domain controller.
>
> Hope this helps!
--B_3343126509_2805115
Content-type: text/html;
charset="ISO-8859-1"
Content-transfer-encoding: quoted-printable
<HTML>
<HEAD>
<TITLE>Re: GAL broken with Entourage 13.0.3 and EWS</TITLE>
</HEAD>
<BODY>
<FONT FACE=3D"Helvetica, Verdana, Arial"><SPAN STYLE=3D'font-size:11pt'>Hi Bill=
,<BR>
<BR>
Thanks for the reply.<BR>
We have verified that on numerous Macs, going from 13.0 to 13.0.3 kills our=
GAL access on the EXCH 2007 RU9 setup.<BR>
Entourage 12.x is also fine.<BR>
So...something changed, and I don’t know what.<BR>
We can’t use the 12.2.3 / 13.0.3 upgrade until we know what happened.=
<BR>
<BR>
Scott<BR>
<BR>
<BR>
<BR>
On 12/4/09 7:17 PM, in article <a href=3D"u#N$DmVdKHA.3300@TK2MSFTNGP02.phx.g=
bl">u#N$DmVdKHA.3300@TK2MSFTNGP02.phx.gbl</a>, "William Smith [MVP]&quo=
t; <<a href=3D"mecklists@REM0VETH1S.comcast.net.INVALID">mecklists@REM0VETH=
1S.comcast.net.INVALID</a>> wrote:<BR>
<BR>
</SPAN></FONT><BLOCKQUOTE><SPAN STYLE=3D'font-size:11pt'><FONT FACE=3D"Arial">S=
cott Boettcher wrote:<BR>
<BR>
> We have discovered an issue with the GAL and 13.0.3.<BR>
> It appears in both 10.5.8 and 10.6.2 Macs.<BR>
> The GAL is very unreliable, most of the time it’s inaccessible.<=
BR>
> If we uninstall and go back to 13.0.0, it’s fine.<BR>
<BR>
I'm using 13.0.3 both at home, connecting to our OWA server, as well as <BR=
>
at work connecting to our internal Exchange server. No problems <BR>
accessing the GAL.<BR>
<BR>
What specifically is not working for you? The 12.x version of Entourage <BR=
>
will use just LDAP for GAL connectivity whereas the 13.x version of <BR>
Entourage will use both LDAP and Exchange Web Services (EWS).<BR>
<BR>
EWS facilitates searching/lookups and LDAP facilitates browsing the GAL. <B=
R>
LDAP will only work internally to your company where your Exchange <BR>
server is located. Be sure that you're using the address of a Global <BR>
Catalog server, which is a special type of domain controller.<BR>
<BR>
Hope this helps!<BR>
</FONT></SPAN></BLOCKQUOTE><SPAN STYLE=3D'font-size:11pt'><FONT FACE=3D"Arial">=
<BR>
</FONT></SPAN>
</BODY>
</HTML>
--B_3343126509_2805115--
|
|
0
|
|
|
|
Reply
|
Scott
|
12/8/2009 10:15:07 PM
|
|
Scott Boettcher wrote:
> Thanks for the reply.
> We have verified that on numerous Macs, going from 13.0 to 13.0.3 kills
> our GAL access on the EXCH 2007 RU9 setup.
> Entourage 12.x is also fine.
> So...something changed, and I don�t know what.
> We can�t use the 12.2.3 / 13.0.3 upgrade until we know what happened.
Ah, so if you're saying Entourage 12.x is working for you then you're
connecting to LDAP inside your company network.
Try this:
In Entourage 13.0, remove the LDAP server address and test addressing a
new message to someone who's not likely in your Most Recently Used list.
(I often test with our CEO.) For example, if I start typing "Johnst"
then via EWS you should still receive matches from the GAL for
"Johnston...", etc.
Entourage 12.x did not have this functionality and relied exclusively on
LDAP for lookups.
Do you receive anything at all with the LDAP server removed in either
13.0.0 or 13.0.3?
--
bill
Entourage Help Page <http://entourage.mvps.org/>
Entourage Help Blog <http://blog.entourage.mvps.org/>
YouTalk <http://nine.pairlist.net/mailman/listinfo/youtalk>
Twitter: follow <http://twitter.com/meck>
|
|
0
|
|
|
|
Reply
|
William
|
12/12/2009 3:10:45 PM
|
|
> This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.
--B_3343719787_5449620
Content-type: text/plain;
charset="ISO-8859-1"
Content-transfer-encoding: 8bit
Hi Bill,
Thanks for the continued replies.
I am testing now with NO entry in LDAP.
Here�s the rub � we indeed needed to populate the LDAP server field as we
have an outsourced (Microsoft) email service.
The GAL is across our and their Domains.
Our local domain accounts are in �expired� status for this config, and if we
used the MS Domain, we got �your password will expire in 0 days� messages
upon every launch of Entourage.
So, we populate with our internal LDAP to avoid this.
Will report back to you.
Best,
Scott
On 12/12/09 7:10 AM, in article #8zwI1zeKHA.2460@TK2MSFTNGP04.phx.gbl,
"William Smith [MVP]" <mecklists@REM0VETH1S.comcast.net.INVALID> wrote:
> Scott Boettcher wrote:
>
>> > Thanks for the reply.
>> > We have verified that on numerous Macs, going from 13.0 to 13.0.3 kills
>> > our GAL access on the EXCH 2007 RU9 setup.
>> > Entourage 12.x is also fine.
>> > So...something changed, and I don�t know what.
>> > We can�t use the 12.2.3 / 13.0.3 upgrade until we know what happened.
>
> Ah, so if you're saying Entourage 12.x is working for you then you're
> connecting to LDAP inside your company network.
>
> Try this:
>
> In Entourage 13.0, remove the LDAP server address and test addressing a
> new message to someone who's not likely in your Most Recently Used list.
> (I often test with our CEO.) For example, if I start typing "Johnst"
> then via EWS you should still receive matches from the GAL for
> "Johnston...", etc.
>
> Entourage 12.x did not have this functionality and relied exclusively on
> LDAP for lookups.
>
> Do you receive anything at all with the LDAP server removed in either
> 13.0.0 or 13.0.3
--B_3343719787_5449620
Content-type: text/html;
charset="ISO-8859-1"
Content-transfer-encoding: quoted-printable
<HTML>
<HEAD>
<TITLE>Re: GAL broken with Entourage 13.0.3 and EWS</TITLE>
</HEAD>
<BODY>
<FONT FACE=3D"Helvetica, Verdana, Arial"><SPAN STYLE=3D'font-size:11pt'>Hi Bill=
,<BR>
<BR>
Thanks for the continued replies.<BR>
I am testing now with NO entry in LDAP.<BR>
Here’s the rub – we indeed needed to populate the LDAP server f=
ield as we have an outsourced (Microsoft) email service.<BR>
The GAL is across our and their Domains.<BR>
Our local domain accounts are in “expired” status for this conf=
ig, and if we used the MS Domain, we got “your password will expire in=
0 days” messages upon every launch of Entourage.<BR>
So, we populate with our internal LDAP to avoid this.<BR>
Will report back to you.<BR>
<BR>
Best,<BR>
Scott<BR>
<BR>
<BR>
On 12/12/09 7:10 AM, in article <a href=3D"#8zwI1zeKHA.2460@TK2MSFTNGP04.phx.=
gbl">#8zwI1zeKHA.2460@TK2MSFTNGP04.phx.gbl</a>, "William Smith [MVP]&qu=
ot; <<a href=3D"mecklists@REM0VETH1S.comcast.net.INVALID">mecklists@REM0VET=
H1S.comcast.net.INVALID</a>> wrote:<BR>
<BR>
</SPAN></FONT><BLOCKQUOTE><SPAN STYLE=3D'font-size:11pt'><FONT FACE=3D"Arial">S=
cott Boettcher wrote:<BR>
<BR>
> Thanks for the reply.<BR>
> We have verified that on numerous Macs, going from 13.0 to 13.0.3 kill=
s <BR>
> our GAL access on the EXCH 2007 RU9 setup.<BR>
> Entourage 12.x is also fine.<BR>
> So...something changed, and I don’t know what.<BR>
> We can’t use the 12.2.3 / 13.0.3 upgrade until we know what happ=
ened.<BR>
<BR>
Ah, so if you're saying Entourage 12.x is working for you then you're <BR>
connecting to LDAP inside your company network.<BR>
<BR>
Try this:<BR>
<BR>
In Entourage 13.0, remove the LDAP server address and test addressing a <BR=
>
new message to someone who's not likely in your Most Recently Used list. <B=
R>
(I often test with our CEO.) For example, if I start typing &qu=
ot;Johnst" <BR>
then via EWS you should still receive matches from the GAL for <BR>
"Johnston...", etc.<BR>
<BR>
Entourage 12.x did not have this functionality and relied exclusively on <B=
R>
LDAP for lookups.<BR>
<BR>
Do you receive anything at all with the LDAP server removed in either <BR>
13.0.0 or 13.0.3<BR>
</FONT></SPAN></BLOCKQUOTE>
</BODY>
</HTML>
--B_3343719787_5449620--
|
|
0
|
|
|
|
Reply
|
Scott
|
12/15/2009 7:03:06 PM
|
|
|
4 Replies
126 Views
(page loaded in 0.081 seconds)
Similiar Articles:9/6/2012 2:24:49 AM
|