Re: DomainPrep in root domain

>From KB article:

The domain in which a server that is running Exchange Server is being
installed requires that you run the Setup program by using the /DomainPrep
command line option. You must also run /DomainPrep on any domains that
contain Windows global catalog servers or user accounts that are mail
enabled or mailbox enabled. Also, run /DomainPrep on any domain that
contains users or groups that will manage the Exchange organization.

Hope this helps!

Regards,

--
Sasa Milovanovic
MCSE:Messaging
sasa.milovanovic at exchangemaster.net

"Deano" <Deano@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:551D015E-3E35-40C3-970B-102401EEE046@xxxxxxxxxxxxxxxx
> Guys,
>
> Do I always need to run domainprep in my forest root domain after
> forestprep? What if there are no users in this domain? I have read
> conflicting statements saying domainprep must be run in every domain?
>
> Thanks


.

Relevant Pages

  • Re: Choosing a Namespace (Internal and External Domains?)
    ... internet FQDN. ... mail server for the company. ... E-Mail Server such as network solutions. ... possibility of running Exchange server included with SBS as the public ...
    (microsoft.public.windows.server.sbs)
  • "ghost" expired messages in queues
    ... We are running Exchange Server 2003 Enterprise on Windows Server 2003, ... we migrated to a new SAN for the cluster ... When I do a Find Messages on one of these queues, ...
    (microsoft.public.exchange.admin)
  • IS size limit
    ... I'm running Exchange server 2000 on Windows Server 2000. ... Once I create a second store, ... Will having two ISs cause any problems there? ...
    (microsoft.public.exchange2000.information.store)
  • Exchange Server takes more and more HDD space
    ... I am running Exchange Server 2k on Windows 2k. ... it was 1.5MB free space again. ... I checked the size of Exchange folder in Program Files. ...
    (microsoft.public.exchange.admin)
  • Re: Distributed or Centralized Executable?
    ... You may want to look at my post "Uninstalling Applications across ... > every workstation using the following scenario: ... > b) Delete the program executable which the setup program creates on the ... > executable on a remote server. ...
    (microsoft.public.win2000.setup_deployment)
Loading