Posted on 2009-04-09
ive had issues in the past with sending email externally from the client pc. i have now got a "static ip" address from my ISP and the email appeared to be stuck in the smtp queue saying that smtp had an error.
i have though done various things since and now ive so reinstalled a fresh copy and run the following on my exchange server:
- added to AD which made it become a DC
- i will once i figured out how to run: orgprepcheck to confirm that the above commands successfully installed everything. as i have a thread already out there waiting a response, because exchange deploy tools is asking for the name of my global server and when i type it in it does not recognise!!
my current setup is:
- 1 x primary win 2003 server & domain, where i will add all user accounts
QNS1: - 1 x win server 2003 with exchange added. im assuming i cant install exchange by itself because i tried and the disc would not pick up?
QNS2: after repeat reading through my install procedures that ive found on the internet and not on my exchange disc. its states that I should also run:
- /domainprep on my primary server, is this correct although i can understand why?
i know there are many scenarios but just wish to complete this task of successfully sending email externally!!
INFO IVE READ FROM INTERNET:
One well-equipped Global Catalog server can support several Exchange 2003 servers on the same LAN segment. There should be at least one Global Catalog server in every Active Directory site that contains an Exchange 2003 server. For large sites, two Global Catalogs are much better and provide redundancy in the event the first Global Catalog server is unavailable.
For optimization, plan on having a Global Catalog server close to the clients to provide efficient address list access. Making all domain controller servers Global Catalog servers is recommended for an organization that has a single Active Directory domain model and a single site, and its also not a bad idea for Active Directory designs that use a placeholder domain as the forest root with one or two first-level domains. A good Active Directory site design helps make efficient use of bandwidth in this design. This design helps reduce some of the overhead with multiple Global Catalogs in every Active Directory site.
Before you perform the procedure in this topic, consider the following:
" Before you run DomainPrep, you must have run ForestPrep in the forest.
" Before you run DomainPrep, make sure the schema changes made during ForestPrep have replicated throughout the forest.
" The account you use to run DomainPrep must be a member of the following groups:
" Domain Administrators for the local domain
" Local Machine Administrator
" You must run DomainPrep in the following domains
" The root domain.
" All domains that will contain Exchange 2003 servers.
" All domains that will contain Exchange Server 2003 mailbox-enabled objects (such as users and groups), even if no Exchange servers will be installed in these domains.
" All domains that contain global catalog servers that Exchange directory access components may potentially use.
" All domains that will contain Exchange 2003 users and groups that you will use to manage your Exchange 2003 organization.
" You do not need any Exchange permissions to run DomainPrep