Re: RE:SETUP 2003 and exchange 2003 DC

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Hello Anugu,

answers inline

"winwoo3_68" <anugu.pramod@xxxxxxxxx> wrote in message news:1159707227.116924.87630@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
I did the following
Control Panel- System- ComputerName--Change-Click on Member of .
--Enter the domain name. Enter the username and password of the DC.
1. What is advantage of adding a server to a domain?

Loads of them: Central Management, single account store (domain users can log onto each domain member usually), ... - and to run Exchange you need to have the server in an AD-Domain.
Implementing and administering Windows Server 2003 Domains is a big toppic, you can sit couple weeks in classes or read some good books. Also there are a lot of ressources online available. To explain the whole concept with all the details of domains is a big huge for a newsgroup - however we are always happy to answer specific questions.

2. Can the Exchange server act as DC if the DC goes down for some
reason.

You can install multiple DCs for a Domain, and it is recommended to have at least two DCs for each domain. Exchange is not recommended but runs on a DC as well. Exchange will not provide domain logon services (act as a DC) if it does not run on a DC. In your scenario you might consider running Exchange on a DC to have two DCs, or stick with one DC + one Exchange-only.

3. Exchange server requires Acive Directory. If the i run DCPROMO on
the Exchange server. I will 2 Active Directories.Is there a way to use
DC users on the Exchange Server.

The domain concept allows you to logon to each client/server which is member of the domain. If you make one server a DC and the other one a Exchange Server Exchange will use the User-Accounts of the DC (domain) and will put additional informations (E-Mail Adresses - where the mailbox of the user is stored a.s.o.) in Active Directory. You can only use domain users on Exchange, it does not support Useraccounts which are not in Active Directory.

--
Gruesse - Sincerely,

Ulf B. Simon-Weidner

Profile & Publications: http://mvp.support.microsoft.com/profile=35E388DE-4885-4308-B489-F2F1214C811D
Weblog: http://msmvps.org/UlfBSimonWeidner
Website: http://www.windowsserverfaq.org

.

Relevant Pages

  • Re: Connection to a SAMBA Active Directory
    ... Keep in mind that you're trying to setup a NT4 style trust ... if you setup the Exchange as a resource forest model, ... domain and the Exchange server in another domain will work. ... I am able to define a 2 way Realm trust using the Active Directory ...
    (microsoft.public.exchange.connectivity)
  • Re: Connection to a SAMBA Active Directory
    ... domain and the Exchange server in another domain will work. ... I am able to define a 2 way Realm trust using the Active Directory ... There is a bit of confusing on the SAMBA side. ...
    (microsoft.public.exchange.connectivity)
  • Re: Sites & Services - DSAccess w/E2K3 SP2
    ... I don't believe the firewalls are the issue as they are set to any-any among ... the all the DCs and exchange server. ... All the DCs replicate information in a mesh ... Immediately after upgrading to Exchange 2003 SP2, ...
    (microsoft.public.exchange.admin)
  • Re: Exchange Disaster Recovery Server
    ... The backup server is setup also in the lab so I ... >>> The Microsoft Exchange Server computer is not available. ... >>> Microsoft Exchange Server Information Store ...
    (microsoft.public.exchange2000.admin)
  • Re: Home Network Dilemma
    ... You must understand Active Directory first, in order to implement Exchange. ... Matter of fact, Exchange must alter Active Directory prior to installation, to accomodate the changes. ... On top of that, an understanding of DNS is required, because AD will not work if DNS is not implemented properly for its internal use only, and on top of that, an understanding of DNS on the internet is required in order to manipulate public records so others in the world can 'find' your mail server on your network. ...
    (microsoft.public.windows.server.networking)