Re: Exchange 2000 question - Which DC used for security?

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

From: James Reichner (jreichner_at_hotmail.com)
Date: 05/06/04


Date: Thu, 6 May 2004 13:25:50 -0400

I am really confused as to why this is not working. From the root domain of
the forest I ran forestprep as stated in the knowledge base but when I check
to make sure the objectversion is correct, it lists 4409 instead of 6903. I
made sure I spelled everything correctly and I was logged in as the
administrator. I have also run the domainprep on all of my domain
controllers and I also have the same issue. I am not sure what is wrong but
the "preps" are not working the way they are stated. I really don't want to
build any users in my root domain but right now it looks like I have to if I
cannot find out why this is not working.

I also created the RUS successfully but I could not login to the mail
enabled user via outlook.

-- 
JAMES REICHNER
"Richard Roddy [MSFT]" <rroddy@online.microsoft.com> wrote in message
news:h6zs9j4MEHA.3364@cpmsftngxa10.phx.gbl...
> No, there is no need to remove Exchange 2000.
>
> As I noted, there are 2 things that have to be done:
> 1) DomainPrep run in all 3 domains
> 2) Create a Recipient Update Service (RUS) for any domain that doesn't
have
> one.
>
> So, if you've run the domainprep in all of the domains, now we need to
> create the additional RUS's. So look at the article referenced and create
a
> new RUS for any domain there is not currently a RUS for:
>
> 319065 HOW TO: Work with the Recipient Update Service in Exchange 2000
> http://support.microsoft.com/?id=319065
>
>
>
> Thanks,
> Richard Roddy
> Microsoft Exchange Support
>
> This posting is provided "AS IS" with no warranties, and confers no
rights.
>
> --------------------
> >From: "James Reichner" <jreichner@hotmail.com>
> >References: <et2vq5gMEHA.1392@TK2MSFTNGP09.phx.gbl>
> <i7eg90p34lnrfuene4vij99i10d7k6jga0@4ax.com>
> <qABm2F2MEHA.304@cpmsftngxa10.phx.gbl>
> >Subject: Re: Exchange 2000 question - Which DC used for security?
> >Date: Thu, 6 May 2004 11:08:55 -0400
> >Lines: 101
> >X-Priority: 3
> >X-MSMail-Priority: Normal
> >X-Newsreader: Microsoft Outlook Express 6.00.2800.1409
> >X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
> >Message-ID: <ueNmgx3MEHA.268@TK2MSFTNGP11.phx.gbl>
> >Newsgroups: microsoft.public.exchange.admin
> >NNTP-Posting-Host: host.rmshoemaker.com 146.145.39.2
> >Path:
>
cpmsftngxa10.phx.gbl!TK2MSFTFEED01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP11
> phx.gbl
> >Xref: cpmsftngxa10.phx.gbl microsoft.public.exchange.admin:426134
> >X-Tomcat-NG: microsoft.public.exchange.admin
> >
> >I previously had Exchange 2000 installed.  Should I remove Exchange
server
> >2000 before running the domainprep?  Because I ran domainprep before
doing
> a
> >reinstall and I still cannot gain access to the mailbox.
> >
> >-- 
> >JAMES REICHNER
> >"Richard Roddy [MSFT]" <rroddy@online.microsoft.com> wrote in message
> >news:qABm2F2MEHA.304@cpmsftngxa10.phx.gbl...
> >> It sounds like you're saying that if you have a user account in either
> >> SaturnV or Apollo that you're unable to get mailboxes for those users
to
> >> work properly.
> >>
> >> Did you run setup /domainprep in all 3 domains? Under Recipients in
ESM,
> >do
> >> you have a Recipient Update Service for each of the 3 domains? The
> >> domainprep has to be done for any domain that will have Exchange users
in
> >> it and a RUS has to be created for any domain that will have Exchange
> >users.
> >>
> >> The following article discusses working with the RUS:
> >> 319065 HOW TO: Work with the Recipient Update Service in Exchange 2000
> >> http://support.microsoft.com/?id=319065
> >>
> >>
> >> Thanks,
> >> Richard Roddy
> >> Microsoft Exchange Support
> >>
> >> This posting is provided "AS IS" with no warranties, and confers no
> >rights.
> >>
> >> --------------------
> >> >From: "Rich Matheisen [MVP]" <richnews@rmcons.com.NOSPAM.COM>
> >> >Subject: Re: Exchange 2000 question - Which DC used for security?
> >> >Date: Tue, 04 May 2004 20:49:25 -0400
> >> >Message-ID: <i7eg90p34lnrfuene4vij99i10d7k6jga0@4ax.com>
> >> >References: <et2vq5gMEHA.1392@TK2MSFTNGP09.phx.gbl>
> >> >X-Newsreader: Forte Agent 1.9/32.560
> >> >MIME-Version: 1.0
> >> >Content-Type: text/plain; charset=us-ascii
> >> >Content-Transfer-Encoding: 7bit
> >> >Newsgroups: microsoft.public.exchange.admin
> >> >NNTP-Posting-Host: dc4.rmcons.com 66.92.66.94
> >> >Lines: 1
> >> >Path:
> >>
>
>cpmsftngxa10.phx.gbl!TK2MSFTNGXA05.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP1
> 0
> >> phx.gbl
> >> >Xref: cpmsftngxa10.phx.gbl microsoft.public.exchange.admin:425776
> >> >X-Tomcat-NG: microsoft.public.exchange.admin
> >> >
> >> >"James Reichner" <jreichner@hotmail.com> wrote:
> >> >
> >> >>I have a problem with a new installation of Exchange 2000.  I have
also
> >a
> >> recently installed and configured AD forest.  Here is the config:
> >> >>
> >> >>Dedicated forest root.
> >> >>
> >> >>Voyager (root/Global Catalog)
> >> >>
> >> >>       /                             \
> >> >>SaturnV (DC)               Apollo (DC)
> >> >>                                        \
> >> >>                                  Gemini (Member of Apollo Domain and
> >> running Exchange 2000)
> >> >>
> >> >>During the Exchange 2000 install, I received a popup message stating
> >that
> >> I needed to run this with an id that is able to update the schema.  If
I
> >am
> >> correct that should be the administrator of the root domain.
> >> >
> >> >Possibly. But you really want to know who's a member of the Schema
> >> >Admins group in the root domain.
> >> >
> >> >>The install was successful to be best of my knowledge but I have one
> >> problem.  I have setup 2 separate DCs with in the same forest so that I
> >> could keep our 2 companies separate.  If Gemini is a member of the
Apollo
> >> domain, How can I get the email clients (Outlook) to access the mail
> boxes
> >> using the authority at their respective DC not the root domain.
> Currently
> >> I can only access the mailboxes on Exchange if I create User IDs at the
> >> root level.  This pretty much destroys the AD setup.  There must be
> >someway
> >> around this problem.
> >> >
> >> >The mailbox is a property of the user. If Gemini is a member of the
> >> >Apollo doman then the user id is Apollo\Gemini and the user is logged
> >> >on to (authenticated by) the Apollo domain.
> >> >
> >> >If the user's account in in some other domain then you'll have to give
> >> >that account permissions to use the other mailbox.
> >> >
> >> >-- 
> >> >Rich Matheisen
> >> >MCSE+I, Exchange MVP
> >> >MS Exchange FAQ at http://www.swinc.com/resource/exch_faq.htm
> >> >
> >>
> >
> >
> >
>


Relevant Pages

  • Re: migration planning, need suggestions/advice
    ... there will be no users or computers in the root domain. ... the new forest will have a new exchange org ... Is a separate tool, comes with exchange. ... ADMT is good and easy to implement. ...
    (microsoft.public.windows.server.active_directory)
  • Domain Rename / Migration with Exchange 2007
    ... So I have a Windows 2003 Native Forest with the root domain of ... not possible unless I completely uninstall Exchange first. ... in the same forest as burton.k12.ca.us and move ... Further complicating this is the Exchange Server. ...
    (microsoft.public.exchange.admin)
  • Domain Rename / Migration with Exchange 2007
    ... So I have a Windows 2003 Native Forest with the root domain of ... not possible unless I completely uninstall Exchange first. ... in the same forest as burton.k12.ca.us and move ... Further complicating this is the Exchange Server. ...
    (microsoft.public.windows.server.migration)
  • Windows 2000 Domain Consolidation
    ... Exchange 5.5 at each site connected to main site or Exchange Server via ... all Child Domains into the Forest Root domain as OU of ONE domain! ... then doing the migration to AD 2003. ...
    (microsoft.public.exchange.admin)
  • Windows 2000 Domain Consolidation
    ... Exchange 5.5 at each site connected to main site or Exchange Server via ... all Child Domains into the Forest Root domain as OU of ONE domain! ... then doing the migration to AD 2003. ...
    (microsoft.public.windows.server.active_directory)