Re: 5.5 Organization GAL Seen by 2003 Environment...

Tech-Archive recommends: Fix windows errors by optimizing your registry

I see the GAL for our site, but not for the other sites within the
organization. Would it be a permissions issue on the AD Side?

"Al Mulnick" wrote:

The GAL isn't working?
Did you install the ADC then?


"icestormz" <icestormz@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:082CE4AC-1B51-4DAB-842B-8E40FAD0F50B@xxxxxxxxxxxxxxxx
I have already installed into the organization, but it is only seeing my
site
and not any of the other 12 sites in the organization. It doesn't have
any
problems routing mail, but the GAL isn't working.



"Al Mulnick" wrote:

Yes, but it's a little late for that.

The way to do that is the with the ADC and by installing the 2003
Exchange
server as a member of the organization vs. as a new organization as
you've
done already.

To get there from where you are, you can either a) uninstall Exchange
2003
and reinstall with the ADC option (that's uninstall all of it from the
AD,
the server, etc.) or b) consider a directory sync option such as MIIS
IIFP
or some other third party tools. What you have created is two
organizations.
Organizations are the replication boundary.

Al
"icestormz" <icestormz@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:921A5811-2974-41B5-A617-5458705D9D9A@xxxxxxxxxxxxxxxx
We have one Organization, multiply locations, multiply domains, NT and
one
AD.

We have all 5.5 Servers and One new 2003 Server.

I need to know if anyone knows how to set it up so that the 2003 Server
can
see the 5.5 Organization GAL.

Thanks






.

Relevant Pages

  • Re: MSADC 8355 LDAP Result failed
    ... The LDAP errors seemed to be caused by my enabling logging in the ADC ... I receive 2 when the server restarts. ... Opening LDAP session to directory xxx on port 389. ...
    (microsoft.public.exchange.setup)
  • Re: MSADC 8355 LDAP Result failed
    ... The ADC tools now all run!! ... The LDAP errors seemed to be caused by my enabling logging in the ADC tools ... I receive 2 when the server restarts. ... Opening LDAP session to directory xxx on port 389. ...
    (microsoft.public.exchange.setup)
  • Exchange 2003 Upgrade Problems
    ... I have taken over administration of a w2k AD domain running Exchange 5.5. ... DC/Ex5.5 server passes all netdiag/dcdiag tests. ... My current project is to upgrade the Ex5.5 server (which is also the domain's ... I also upgraded the ADC to the Ex2k SP3 ...
    (microsoft.public.exchange.setup)
  • Re: MSADC 8355 LDAP Result failed
    ... I made sure that the user for the adc service ... I receive 2 when the server restarts. ... Event Category: LDAP Operations ... Opening LDAP session to directory xxx on port 389. ...
    (microsoft.public.exchange.setup)
  • Re: MSADC 8355 LDAP Result failed
    ... If you put Exchange on one, then you won't need the other:) ... have another DC that is my global catalog server. ... think of no reason that it would "listen" to anything on that port. ... ADC is trying to start on port 389, but it is already in use since ...
    (microsoft.public.exchange.setup)