Install and configure Exchange 2003 on Server 2003

Pre installation requirements:

• IIS (include options SMTP and NNTP)

• DNS must be set up
• Active Directory installed

Install IIS: (may require install cd)

1. Control panel add or remove windows components

2. Select application server, then click details
3. Select IIS, then click details
4. check NNTP and SMTP services then click OK
5. click OK again
6. Click Next, install will begin

Install Microsoft DNS Server

1. Click Start, point to Settings, and then click Control Panel.

2. Double-click Add/Remove Programs.
3. Click Add and Remove Windows Components.
4. The Windows Components Wizard starts. Click Next.
5. Click Networking Services, and then click Details.
6. Click to select the Domain Name System (DNS) check box, and then click OK.
7. Click OK to start server Setup. The DNS server and tool files are copied to your computer.
8. Continue to the next step to configure the DNS server.

Configure the DNS Server Using DNS Manager:

1. Click Start, point to Programs, point to Administrative Tools, and then click DNS Manager. You
see two zones under your computer name: Forward Lookup Zone and Reverse Lookup Zone.
2. The DNS Server Configuration Wizard starts. Click Next.
3. If the Wizard does not auto-start, right-click your server name object in the DNS Manager
console and choose Configure your Server.
4. Choose to add a forward lookup zone. Click Next. The new forward lookup zone must be a
primary zone so that it can accept dynamic updates. Click Primary, and then click Next.

5. The zone name must be exactly the same as your Active Directory Domain name, or, if on a
stand-alone or workgroup environment - the same as the suffix for all of the network computers
that are to register with this DNS server. Type the name of the zone, and then click Next.

6. Accept the default name for the new zone file. Click Next.
7. Choose to add a reverse lookup zone now. Click Next.

8. Click Primary, and then click Next.

9. Type the name of the zone, and then click Next. The zone name should match the Network ID
of your local subnet. For example, if your subnet range is from 192.168.0.1 to 192.168.0.254,
type 192.168.0 in the name value.

10. Accept the default name for the new zone file. Click Next.

11. Click Finish to complete the Server Configuration Wizard.

Enable Dynamic Update on the Forward and Reverse Lookup Zones
(Optional – Recommended):

1. In DNS Manager, expand the DNS Server object.

2. Expand the Forward Lookup Zones folder.
3. Right-click the zone you created, and then click Properties.
4. On the General tab, click to select the Allow Dynamic Update check box, and then click OK to
accept the change.

5. Do the same for the Reverse Lookup Zone.

Enable DNS Forwarding for Internet connections:

1. Click Start, point to Programs, point to Administrative Tools, and then click DNS to start the
DNS Management Console.
2. Right click the DNS Server object for your server in the left pane of the console, and click
Properties.
 3. Click the Forwarders tab.
4. Check the Enable forwarders check-box.
5. In the IP address box enter the IP address of the DNS servers you want to forward queries to -
typically the DNS server of your ISP. You can also move them up or down. The one that is
highest in the list gets the first try, and if it does not respond within a given time limit - the
query will be forwarded to the next server in the list.

6. Click OK.

External Link:

http://www.petri.co.il/install_and_configure_windows_2003_dns_server.htm

Install Active Directory on Windows Server 2003 server

Here is a quick list of what you must have:

• An NTFS partition with enough free space

• An Administrator's username and password
• The correct operating system version
• A NIC
 • Properly configured TCP/IP (IP address, subnet mask and - optional - default gateway)
• A network connection (to a hub or to another computer via a crossover cable)
• An operational DNS server (which can be installed on the DC itself)
• A Domain name that you want to use
• The Windows Server 2003 CD media (or at least the i386 folder)

Step 1: Configure the computer's suffix:

1. Right click My Computer and choose Properties.

2. Click the Computer Name tab, then Change.

3. Set the computer's NetBIOS name. In Windows Server 2003, this CAN be changed after the
computer has been promoted to Domain Controller.
4. Click More.

5. In the Primary DNS suffix of this computer box enter the would-be domain name. Make sure
you got it right. No spelling mistakes, no "oh, I thought I did it right...". Although the domain
name CAN be changed after the computer has been promoted to Domain Controller, this is not
a procedure that one should consider lightly, especially because on the possible consequences.
 6. Click Ok.
7. You'll get a warning window.
8. Click Ok.
9. Check your settings. See if they're correct.

10. Click Ok.

11. You'll get a warning window.
12. Click Ok to restart.
Step 2: Configuring the computer's TCP/IP settings:

*You must configure the would-be Domain Controller to use it's own IP address as the address of the
DNS server, so it will point to itself when registering SRV records and when querying the DNS
database.

1. Click Start, point to Settings and then click Control Panel.

2. Double-click Network and Dial-up Connections.
3. Right-click Local Area Connection, and then click Properties.
 4. Click Internet Protocol (TCP/IP), and then click Properties.

5. Assign this server a static IP address, subnet mask, and gateway address. Enter the server's IP
address in the Preferred DNS server box.Note: This is true if the server itself will also be it's
own DNS server.

6. Click Advanced.
7. Click the DNS Tab.
8. Select "Append primary and connection specific DNS suffixes"
9. Check "Append parent suffixes of the primary DNS suffix"
10. Check "Register this connection's addresses in DNS". If this Windows 2000/2003-based DNS
server is on an intranet, it should only point to its own IP address for DNS; do not enter IP
addresses for other DNS servers here. If this server needs to resolve names on the Internet, it
should have a forwarder configured.

11. Click OK to close the Advanced TCP/IP Settings properties.

12. Click OK to accept the changes to your TCP/IP configuration.
13. Click OK to close the Local Area Connections properties.

Step 3: Configure the DNS Zone:

Creating a Standard Primary Forward Lookup Zone

1. Click Start, point to All Programs, point to Administrative Tools, and then click DNS Manager.
You see two zones under your computer name: Forward Lookup Zone and Reverse Lookup
Zone.
2. Right click Forward Lookup Zones and choose to add a new zone.
3. Click Next. The new forward lookup zone must be a primary zone so that it can accept dynamic
updates. Click Primary, and then click Next.

4. The name of the zone must be the same as the name of the Active Directory domain, or be a
logical DNS container for that name. For example, if the Active Directory domain is named
"lab.dpetri.net", legal zone names are "lab.dpetri.net", "dpetri.net", or "net".
Type the name of the zone, and then click Next.

5. Accept the default name for the new zone file. Click Next.
 6. To be able to accept dynamic updates to this new zone, click "Allow both nonsecure and secure
dynamic updates". Click Next.

7. Click Finish.

*You should now make sure your computer can register itself in the new zone. Go to the Command
Prompt (CMD) and run "ipconfig /registerdns" (no quotes, duh...). Go back to the DNS console, open
the new zone and refresh it (F5). Notice that the computer should by now be listed as an A Record in
the right pane.

If it's not there try to reboot (although if it's not there a reboot won't do much good). Check the spelling
on your zone and compare it to the suffix you created in step 1. Check your IP settings.

Step 4: Running DCPROMO:

1. Click Start, point to Run and type "dcpromo".

2. The wizard windows will appear. Click Next.
3. In the Operating System Compatibility windows read the requirements for the domain's clients
and if you like what you see - press Next.
4. Choose Domain Controller for a new domain and click Next.

5. Choose Create a new Domain in a new forest and click Next.

6. Enter the full DNS name of the new domain, for example - kuku.co.il - this must be the same as
the DNS zone you've created in step 3, and the same as the computer name suffix you've
created in step 1. Click Next.
This step might take some time because the computer is searching for the DNS server and
checking to see if any naming conflicts exist.

7. Accept the the down-level NetBIOS domain name, in this case it's KUKU. Click Next

8. Accept the Database and Log file location dialog box (unless you want to change them of
course). The location of the files is by default %systemroot%\NTDS, and you should not
change it unless you have performance issues in mind. Click Next.
9. Accept the Sysvol folder location dialog box (unless you want to change it of course). The
location of the files is by default %systemroot%SYSVOL, and you should not change it unless
you have performance issues in mind. This folder must be on an NTFS v5.0 partition. This
folder will hold all the GPO and scripts you'll create, and will be replicated to all other Domain
Controllers. Click Next.

10. If your DNS server, zone and/or computer name suffix were not configured correctly you will
get the following warning:This means the Dcpromo wizard could not contact the DNS server, or
it did contact it but could not find a zone with the name of the future domain. You should check
your settings. Go back to steps 1, 2 and 3. Click Ok.

You have an option to let Dcpromo do the configuration for you. If you want, Dcpromo can
install the DNS service, create the appropriate zone, configure it to accept dynamic updates, and
configure the TCP/IP settings for the DNS server IP address.

11. If your DNS settings were right, you'll get a confirmation window.

12. Accept the Permissions compatible only with Windows 2000 or Windows Server 2003
settings, unless you have legacy apps running on Pre-W2K servers.
 13. Enter the Restore Mode administrator's password. In Windows Server 2003 this
password can be later changed via NTDSUTIL. Click Next.

14. Review your settings and if you like what you see - Click Next.

15. See the wizard going through the various stages of installing AD. Whatever
you do - NEVER click Cancel!!! You'll wreck your computer if you do. If you see
you made a mistake and want to undo it, you'd better let the wizard finish and
then run it again to undo the AD.

16. If all went well you'll see the final confirmation window. Click Finish.
17. You must reboot in order for the AD to function properly.

You should now check to see if the AD installation went well.

1. First, see that the Administrative Tools folder has all the AD management tools installed.
2. Run Active Directory Users and Computers (or type "dsa.msc" from the Run command).
See that all OUs and Containers are there.

3. Run Active Directory Sites and Services. See that you have a site named Default-First-
Site-Name, and that in it your server is listed.

4. If they don't (like in the following screenshot), your AD functions will be broken (a good
sign of that is the long time it took you to log on. The "Preparing Network Connections" windows
will sit on the screen for many moments, and even when you do log on many AD operations will
give you errors when trying to perform them).

= Bad

This might happen if you did not manually configure your DNS server and let the
DCPROMO process do it for you.
Another reason for the lack of SRV records (and of all other records for that matter) is the fact
that you DID configure the DNS server manually, but you made a mistake, either with the
computer suffix name or with the IP address of the DNS server (see steps 1 through 3).

Open the DNS console. See that you have a zone with the same name as your AD domain (the
one you've just created, remember? Duh...). See that within it you have the 4 SRV record folders.
They must exist.
 = Good

To try and fix the problems first see if the zone is configured to accept dynamic updates.

5. Right-click the zone you created, and then click Properties.

6. On the General tab, under Dynamic Update, click to select "Nonsecure and secure" from
the drop-down list, and then click OK to accept the change.You should now restart the
NETLOGON service to force the SRV registration.
 You can do it from the Services console in Administrative tools:

Or from the command prompt type "net stop netlogon", and after it finishes, type "net start
netlogon".

Let it finish, go back to the DNS console, click your zone and refresh it (F5). If all is ok you'll
now see the 4 SRV record folders.

If the 4 SRV records are still not present double check the spelling of the zone in the DNS
server. It should be exactly the same as the AD Domain name. Also check the computer's suffix
(see step 1). You won't be able to change the computer's suffix after the AD is installed, but if you
have a spelling mistake you'd be better off by removing the AD now, before you have any users,
groups and other objects in place, and then after repairing the mistake - re-running DCPROMO.

7. Check the NTDS folder for the presence of the required files.

8. Check the SYSVOL folder for the presence of the required subfolders.

9. Check to see if you have the SYSVOL and NETLOGON shares, and their location.

If all of the above is ok, I think it's safe to say that your AD is properly installed.

External Link:

http://www.petri.co.il/how_to_install_active_directory_on_windows_2003.htm

Install exchange 2003

Run first forest prep

# On the Start menu, click Run, and then type E:\setup\i386\setup /ForestPrep, where E is your CD-
ROM drive.

Then run Domain Prep:

# On the Start menu, click Run, type E:\setup\i386\setup /DomainPrep, where E is your CD-ROM
drive.

Then install exchange server (choose typical)

On the Start menu, click Run, and then type E:\setup\i386\setup, where E is your CD-ROM drive
firewall must allow port 110, 25 and imap ports

configure exchange system manager

right click organization unselect display admin groups to show servers

enable pop3 and imap ( you might need to start the service under servicesset to automatic