RE: Exchange 2003/5.5 Setup Issue

From: Jeff (Jeff_at_discussions.microsoft.com)
Date: 01/07/05 

Date: Fri, 7 Jan 2005 09:23:03 -0800

When I first setup the ADC, the wizard forced me to setup a connection
agreement for each site. Once I found out Exchange setup was trying to
attach to the first site in the list, I deleted the connection agreements for
all the sites except the host site, which is also the one that I want to
install the new 2003 server in to. I did change the two values that right
(not set) to my service account and domain..It then let me continue on with
the install, but what I don't know is what site it's actually going to
install this new server into. Sounds like it's going to install it into the
first site in the list, not the host site.

"Steve" wrote:

> Jeff,
>
> I'm thinking if you don't have rights set on the ADC (two way CA's) to all
> your domains then how is the AD domain going to talk to the Exchange sites
> and pull in the service accounts (maybe why it lists it as blank) and other
> information to populate AD - I would think that it would show all the
> Exchange Sites (under the Administrative Groups container in the ADSI tool)
> because your current one site connection would replicate that info from NT to
> AD but getting service account (or any other info from those sites) is
> blocked since you haven't allowed permission to those NT domains. Just a
> guess.
>
>
> "Jeff" wrote:
>
> > Well I found out why the info is blank, it's because the value in the first
> > site in the list is set to (Not Set) in the ADSI. Any ideas why it would
> > just default to the first site in the list? Does you think it really
> > matters? Maybe I should just call PSS... Thanks again for your help.
> >
> > "Steve" wrote:
> >
> > > Jeff,
> > >
> > > Okay, not sure I understand why your account user id / domain is blank since
> > > it should have one of your NT domains listed in it. This may be beyond me
> > > but I'll try to give you what insight I know.
> > >
> > > When you setup the ADC (and the CA agreements) you specify the service
> > > accounts to use. This information is, I believe, supposed to be the same
> > > user that has rights on your 5.5 server and 2003. I know if you use the
> > > wrong info your 5.5 MTA won't send messages to 2003 because of "rights issue"
> > > (i.e. wrong user or not sufficient permission). Since you have 10 different
> > > NT domains I'm assuming they are all using their own specific domain exchange
> > > service account. When you setup the intial site it ties into the site you
> > > specify but this is not the case for future exchange servers you introduce
> > > which is probably why your multiple domains with no permissions is causing a
> > > problem
> > >
> > > "Steve" wrote:
> > >
> > > > Have you been using the ADSI tool to help?
> > > > 1. From the Start menu, select Run…. In the Run window, type in adsiedit.msc
> > > > and hit enter.
> > > > 2. Navigate the Configuration Container: CN=Configuration (your domain) then
> > > > to CN=Services then to CN=Microsoft Exchange then to CN=<domain name> then to
> > > > CN=Administrative Groups then to CN=<admin/site group> and right click on
> > > > that container and select Properties,
> > > > 3. The Properties window appears. Under the Attribute Editor tab, scroll
> > > > down and highlight the MSExchangeLegacyDomain attribute
> > > >
> > > > This is where the information is being pulled from for this step (where the
> > > > user id and domain are greyed out).
> > > >
> > > > Our issue was we had 1 NT domain (18 Exchange sites) and were moving to a
> > > > new AD domain. The service account domain was wrong for us (showed the old
> > > > domain) and the reason was because during our testing in the lab the prod
> > > > folks converted the Exchange service account from the NT domain to the AD
> > > > domain when they moved the Exchange servers into the AD domain (The KB
> > > > Q152808 is how they changed the service account).
> > > >
> > > >
> > > > "Jeff" wrote:
> > > >
> > > > > Well I think i figured out my problem, but don't know how to resolve it....
> > > > >
> > > > > I have 10 Exchange 5.5 Sites in my Org, the site where the conversion is
> > > > > taking place is about 6 places down in the list of sites. When I go to
> > > > > install my second 2003 server it knows that this is a mixed mode setup and it
> > > > > tries to find any existing 5.5 sites, the first site it finds is the first
> > > > > one on the list so it tries to attach to that service. Well the problem is I
> > > > > don't have two-way trusts from my AD directory to the rest of my remote
> > > > > domains. Maybe this will solve my problem, but you still should be able to
> > > > > dictate what 5.5 server you want to setup the service from. Any ideas on
> > > > > what I can do to resolve this, I'm about ready to call the trouble into PSS.
> > > > >
> > > > > "Jeff" wrote:
> > > > >
> > > > > > I have an Exchange 5.5 site and I am currently in the process of migrating to
> > > > > > 2003. I have my first Exchange 2003 server setup coexisting with Exchange
> > > > > > 5.5 in the Exchange 5.5 Site. I am trying to setup an additional Exchange
> > > > > > 2003 Server (Cluster) in the 5.5 Site. When I start the setup and after it
> > > > > > asks me if I agree with the licensing agreement, it asks me to supply Service
> > > > > > account information for my 5.5 Exchange site, but the userame and domain are
> > > > > > grey'd out and only the password box is available. If I select next then an
> > > > > > error dialog pops up telling me that I have to select a valid account.
> > > > > > Anyone ever had this problem before?

Relevant Pages

  • Re: Damaged PC
    ... if you want to call it that is the NIC cable connection. ... That was initially disconnected until setup started looking for a network, ... I was also unable to do a repair install. ... >> software to look for viruses, trojans, etc results in reboots. ...
    (microsoft.public.windowsxp.hardware)
  • Re: ActiveSync 3.8 cannot connect to iPAQ.
    ... setup a connection with this computer. ... ActiveSync and follow the on-screen instructions." ... Did you perform any new updates or install new software prior to this issue? ...
    (microsoft.public.pocketpc.activesync)
  • Re: Possible compromise ?
    ... Subject: Possible compromise? ... I was not able to install and setup FreeBSD by ... >> me to retrieve connection dates from that file. ...
    (FreeBSD-Security)
  • Re: rww group & Outlook rpc over http
    ... first instance in order to setup that appears to be the issue. ... I have attempted setting up the Exchange profile, ... Connection and Modem sections are present). ... the Exchange Server, or cant this be achieved without running ConnectComputer? ...
    (microsoft.public.windows.server.sbs)
  • Remote Outlook 2003 connect Exchange 2003 via VPN
    ... Setup VPN by using PPTP ... When use mail.exchange.com to add new exchange account and check name, ... The connection to the Microsoft Exchange ... "Task 'Microsoft Exchange server' reported error:'The server is ...
    (microsoft.public.exchange.connectivity)