Aargee Associates Network Architecture

Company Description

Aargee Associates are trendsetters in roofing concepts. The innovative concepts in the field of
light roofing make Aargee Associates a step ahead in light roofing techniques.

The company consists of more than 50 employee’s throughout India. The branch office
employees always need the server to create billings, knowing of new arrivals, transfer the official
mails etc. They will communicate with the server through internet. So the infrastructure look like
multiple LAN’s is going to interconnect with the help of ISP.

We are looking out the Aargee’s office complete network setup where all local networks are
interconnected with head office with the means of internet….

Scenario – 1

The above network layout illustrates the multiple branch offices interconnected with head office.
Description

The architecture represents couple of branch offices interconnected with head offices. The
network consists of Domain Controller, Database Server, Mail Server and Backup Server in head
office to provide the information’s for the staffs and store the site information’s to the branch
offices. A separate LAN called branch office which is available in Mumbai and Chennai. These
branches will communicate to the head office servers with the help of VPN connectivity.

As a system administrator you are responsible to implement and configure the servers in Delhi
and enable the connectivity between the sites which is located in different parts of India:

The first part of this scenario is configuring your servers. There are five servers in head office.

• Domain Controller – used for user administration.

• Database Server – used for software updation.
• Mail Server – used for secure messaging between multiple branches.
• Backup Server – used to store important information as a copy.

Configurations to be take place in head quarters

Head office Configurations

Steps to Configure the Domain Controller

Introduction to Active Directory Domain Services

Active Directory (AD) is a directory service created by Microsoft. Active Directory uses a number
of standardized protocols to provide a variety of network services, including:

• Lightweight Directory Access Protocol LDAP, the industry standard directory access
protocol, compatible with many management and query applications. Active Directory
supports LDAPv3 and LDAPv2.
• Optional Kerberos-based authentication
• DNS-based naming and other network information
Features include in AD DS

• Central location for network administration and security

• Information security and single sign-on for user access to networked resources
• The ability to scale up or down easily
• Standardizing access to application data
• Synchronization of directory updates across servers

Active Directory stores all information and settings for a deployment in a central database. Active
Directory allows administrators to assign policies, deploy and update software. Active Directory
networks can vary from a small installation with a few computers, users and printers to tens of
thousands of users, many different network domains and large server farms spanning many
geographical locations.

Pre-requisites to install Active Directory Domain Services

List of pre-requisites to install AD DS to configure Domain Controller:

* 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 2003 or Windows Server 2008 CD media (or at least the i386 folder)

After you have fulfill the pre-requisites continue the ADDS installation

An NTFS Partition

To successfully install AD you must have at least one NTFS formatted partition, preferably the
partition Windows is installed To convert a partition (C:) to NTFS type the following command in
the command prompt window:

convert c:/fs:ntfs

The NTFS partition is required for the SYSVOL folder.

You need at least 250mb of free space on the partition you plan to install AD on. You will need
more than that if you plan to create more users, groups and various AD objects. Local
Administrator's username and password. Only a local Administrator (or equivalent) can install the
first domain and thus create the new forest.

If you plan to create another Domain Controller for an existing domain - then you must have
Domain Admin right in the domain you're planning to join.
IP Configuration

You need a dedicated IP address to install Active Directory. If you do not use a dedicated IP
address, DNS registrations may not work and Active Directory functionality may be lost. If the
computer is a multi-homed computer, the network adapter that is not connected to the Internet
can host the dedicated IP address.

The Active Directory domain controller should point to its own IP address in the DNS server list to
prevent possible DNS connectivity issues.

To configure your IP configuration, use the following steps:

1. Right-click My Network Places, and then click Properties.

2. Right-click Local Area Connection, and then click Properties.

Click Internet Protocol (TCP/IP), and then click Properties.

Make sure you have a static and dedicated IP address. If you don't need Internet connectivity
through this specific NIC you can use a Private IP range such as 192.168.0.0 with a Subnet Mask
of 255.255.255.0.

Click Advanced, and then click the DNS tab. The DNS information should be configured as
follows:

• Configure the DNS server addresses to point to the DNS server. This should be the
computer's own IP address if it is the first server or if you are not going to configure a
dedicated DNS server.
• If the Append these DNS suffixes (in order) option is selected for the resolution of
unqualified names, the Active Directory DNS domain name should be listed first, at the
top of the list.
• Verify that the information in the DNS Suffix for this connection box is the same as the
Active Directory domain name.
• Make sure that the Register this connection's addresses in DNS check box is selected.

Installing Active Directory Domain Services (AD-DS)

ADDS can be installed in one of 3 methods. They are:

Method 1 – Server Manager/Initial Configuration Tasks

Method 2 – Servermanagercmd.exe
Method 3 – Using “DCPROMO” command

Here we are starting the AD DS Installation using Method 3.

1. To run DCPROMO, enter the command in the Run command, or click on the DCPROMO
link from Server Manager > Roles > Active Directory Domain Services.
2. Depending upon the question if AD-DS was previously installed or not, the Active
Directory Domain Services Installation Wizard will appear immediately or after a short
while. Click Next.
 3. In the Operating System Compatibility window, read the provided information and click
Next.
4. In the Choosing Deployment Configuration window, click on "Create a new domain in a
new forest" and click Next.
5. Enter an appropriate name for the new domain. Make sure you pick the right domain
name, as renaming domains is a task you will not wish to perform on a daily basis. Click
Next.
6. Pick the right forest function level. Windows 2000 mode is the default, and it allows the
addition of Windows 2000, Windows Server 2003 and Windows Server 2008 Domain
Controllers to the forest you're creating. Read my "Understanding Windows Server 2008
Active Directory Domain and Forest Functional Levels" article for more information on
that.
7. Pick the right domain function level. Windows 2000 Native mode is the default, and it
allows the addition of Windows 2000, Windows Server 2003 and Windows Server 2008
Domain Controllers to the domain you're creating.
8. The wizard will perform checks to see if DNS is properly configured on the local network.
In this case, no DNS server has been configured, therefore, the wizard will offer to
automatically install DNS on this server.
9. It's most likely that you'll get a warning telling you that the server has one or more
dynamic IP Addresses. Running IPCONFIG /all will show that this is not the case,
because as you can clearly see, I have given the server a static IP Address. So, where
did this come from? The answer is IPv6. I did not manually configure the IPv6 Address,
hence the warning. In a network where IPv6 is not used, you can safely ignore this
warning.
10. You'll probably get a warning about DNS delegation. Since no DNS has been configured
yet, you can ignore the message and click Yes.
11. Next, change the paths for the AD database, log files and SYSVOL folder. For large
deployments, carefully plan your DC configuration to get the maximum performance.
When satisfied, click Next.
12. Enter the password for the Active Directory Recovery Mode. This password must be kept
confidential, and because it stays constant while regular domain user passwords expire
(based upon the password policy configured for the domain, the default is 42 days), it
does not. This password should be complex and at least 7 characters long. I strongly
suggest that you do NOT use the regular administrator's password, and that you write it
down and securely store it. Click Next.
13. In the Summary window review your selections, and if required, save them to an unattend
answer file. When satisfied, click Next.

14. The wizard will begin creating the Active Directory domain, and when finished, you will
need to press Finish and reboot your computer.

Troubleshooting Active Directory

The installation of Active Directory requires an active network connection. When you attempt to
use Dcpromo.exe to promote a Windows 2008 Server-based computer to a domain controller,
you may receive the following error message:

• Active Directory Installation Failed

• The operation failed with the following error
• The network location cannot be reached.
 • This problem can occur if the network cable is not plugged into a hub or other network
device.

To resolve this problem, plug the network cable into a hub or other network device. If network
connectivity is not available and this is the first domain controller in a new forest, you can finish
Dcpromo.exe by installing Microsoft Loopback Adapter.

The Microsoft Loopback adapter is a tool for testing in a virtual network environment where
access to a network is not feasible. Also, the Loopback adapter is essential if there are conflicts
with a network adapter or a network adapter driver. Network clients, protocols, and so on, can be
bound to the Loopback adapter, and the network adapter driver or network adapter can be
installed at a later time while retaining the network configuration information. The Loopback
adapter can also be installed during the unattended installation process. To manually install:

• Click Start, point to Settings, click Control Panel, and then double-click Add/Remove
hardware.
• Click Add/Troubleshoot a device, and then click Next.
• Click Add a new device, and then click Next.
• Click No, I want to select the hardware from a list, and then click Next.
• Click Network adapters, and then click Next.
• In the Manufacturers box, click Microsoft.
• In the Network Adapter box, click Microsoft Loopback Adapter, and then click Next.
• Click Finish.

After the adapter is installed successfully, you can configure its options manually, as with any
other adapter. Note that if the TCP/IP properties are configured to use DHCP (the default), the
adapter will eventually use an autonet APIPA address (169.254.x.x/16) because it is not actually
connected to any physical media.

Steps to Configure DNS Server

Introduction to DNS

DNS or Domain Name System is a general purpose, replicated and name resolution system that
resolves the host names into the IP addresses and it stores the information about your host
name, domain names on your local network and on internet. The DNS translates the IP address
into the domain name and domain name into the IP address.

Active directory clients locate need DNS for locating the domain controllers. While promoting the
stand alone server to the domain controller, the DNS is installed automatically. In this article we
will learn that how to install and configure the DNS separately. For managing the name
resolutions in your network, you need to understand the host names, primary, secondary and
stub zones, root name server, resource records, delegation and dynamic updates.

Secondly, you will need to know how to configure zones, how to monitor the DNS server,
understanding cache only server and implementing a delegating zone. DNS uses two different
types of processes to resolve the queries recursive and iterative.

Installation
 • Click Start > Settings > Control Panel > and Double click Add/Remove Programs
• Click Add/Remove Windows components. Windows component wizard will start now
click Next.
• Now click Networking Services and click Details button.
• Select the Domain Name System in the list and click ok.
• Start the server setup. The DNS server files will be copied to the computer.

After the installation has been completed, you need to test, whether it is successful or and you
are able to resolve the names or not. There is a built-in utility “NsLookup” that is used to check
whether the installation and configurations are okay or not.

Steps to Configure DNS server in existing DC

The following steps will tell you that how to configure the DNS in your Windows 2003 server.

• Click Start > Programs > Admin Tools and click DNS manager. DNS server configuration
wizard will start automatically and if the wizard does not start automatically then right click
your server name and click configure your server.
• Choose, add a forward look up zone and click next. The new forward lookup zone to
accept the dynamic updates, Click next.
• Use the zone name exactly same as your active directory domain name. Type the
domain name and click next. The zone name should match your local subnet id and click
next.
• Add a reverse lookup zone and click next.
• Now accept the default name of the new file and click next.
• Now click finish to complete the DNS configurations.

The next step is to accept the dynamic updates for the forward and reverse lookup zones.

How to Enable Dynamic Updates

• Click DNS Manager and expand the DNS server objects.

• Expand the forward lookup zone folder.
• Right click your forward lookup zone name and click properties.
• In the general tab, select “Allow dynamic updates” check box and click ok.
• Perform the same steps for the Reverse Lookup zone.

How to Enable DNS Forwarding on the Internet

• In the DNS console, right click the DNS server object and click Properties.
• Now, click the forwarders tab.
• Enter the IP address of the DNS servers in the IP address box. The IP addresses for the
DNS forwarding are usually of your local ISP.
• You can add multiple forwarding IP addresses, and the address which is on top will be
given priority.
• Click ok to finish the DNS forwarding.

Troubleshooting DNS servers

What problem are you having?

 • The DNS server is not responding to clients.
• The DNS server does not resolve names correctly.
• The DNS server appears to be affected by a problem for reasons not described above.

1. The DNS server is not responding to clients.

Cause - 1: The DNS server is affected by a network failure.

Solution - 1: Verify that the server computer has a valid functioning network connection. First,
check that related client hardware (cables and network adapters) are working properly at the
client using basic network and hardware troubleshooting steps.

If the server hardware appears to be prepared and functioning properly, check that it has network
connectivity by pinging other computers or routers (such as its default gateway) that are used and
available on the same network as the affected DNS servers.

Cause - 2: The DNS server is reachable through basic network testing but is not responding to
DNS queries from clients.

Solution - 2: If the DNS client can ping the DNS server computer, verify that the DNS server is
started and able to listen to and respond to client requests. Try using the nslookup command to
test whether the server can respond to DNS clients.

Cause - 3: The DNS server has been configured to limit service to a specific list of its configured
IP addresses. The IP address originally used in testing its responsiveness is not included in this
list.

Solution - 3: If the server was previously configured to restrict the IP addresses for which it
responds to queries, it is possible that the IP address being used by clients to contact it is not in
the list of restricted IP addresses permitted to provide service to clients.

Try testing the server for a response again, but specify a different IP address known to be in the
restricted interfaces list for the server. If the DNS server responds for that address, add the
missing server IP address to the list.

Cause - 4: The DNS server has been configured to disable the use of its automatically created
default reverse lookup zones.

Solution - 4: Verify that automatically created reverse lookup zones have been created for the
server or that advanced configuration changes have not been previously made to the server.

To verify that these zones have been created, do the following:

1. Open the DNS console.

2. From the View menu, click Advanced.

3. In the console tree, click Reverse Lookup Zones.

o DNS/applicable DNS server/Reverse Lookup Zones

 4. In the details pane, verify that the following reverse lookup zones are present:

o 0.in-addr.arpa

o 127.in-addr.arpa

o 255.in-addr.arpa

Cause: The DNS server is configured to use a non-default service port, such as in an advanced
security or firewall configuration.

Solution: Verify that the DNS server is not using a non-standard configuration.

This is a rare but possible cause. By default, the nslookup command sends queries to targeted
DNS servers using User Datagram Protocol (UDP) port 53. If the DNS server is located on
another network only reachable through an intermediate host (such as a packet-filtering router or
proxy server), the DNS server might use a non-standard port to listen for and receive client
requests.

If this situation applies, determine whether any intermediate firewall or proxy server configuration
is intentionally used to block traffic on well-known service ports used for DNS. If not, you might be
able to add such a packet filter onto these configurations to permit traffic to standard DNS ports.

Also, check the DNS server event log to see if Event ID 414 or other critical service-related
events have occurred which might indicate why the DNS server is not responding.

2. The DNS server does not resolve names correctly.

Cause: The DNS server provides incorrect data for queries it successfully answers.

Solution: Determine the cause of the incorrect data for the DNS server.

Some of the most likely causes include the following:

• Resource records (RRs) were not dynamically updated in a zone.

• An error was made when manually adding or modifying static resource records in the
zone.

• Stale resource records in the DNS server database, left from cached lookups or zone
records not updated with current information or removed when they are no longer
needed.

To help prevent the most common types of problems, be sure to first review best practices for tips
and suggestions on deploying and managing your DNS servers. Also, follow and use the
checklists appropriate for installing and configuring DNS servers and clients based on your
deployment needs.

If you are deploying DNS for Active Directory, note new directory integration features. These
features can cause some differences for DNS server defaults when the DNS database is
directory-integrated, that differ from those used with traditional file-based storage.
Many DNS server problems start with failed queries at a client, so it is often good to start there
and troubleshoot the DNS client first.

Cause: The DNS server does not resolve names for computers or services outside of your
immediate network, such as those located on external networks or the Internet.

Solution: The server has a problem based on its ability to correctly perform recursion. Recursion
is used in most DNS configurations to resolve names that are not located within the configured
DNS domain name used by the DNS servers and clients.

If a DNS server fails to resolve a name for which it is not authoritative, the cause is usually a
failed recursive query. Recursive queries are used frequently by DNS servers to resolve remote
names delegated to other DNS zones and servers.

For recursion to work successfully, all DNS servers used in the path of a recursive query must be
able to respond to and forward correct data. If not, a recursive query can fail for any of the
following reasons:

• The recursive query times out before it can be completed.

• A remote DNS server fails to respond.

• A remote DNS server provides incorrect data.

If a server fails a recursive query for a remote name, review the following possible causes to
troubleshoot the problem. If you do not understand recursion or the DNS query process, review
conceptual topics in Help to better understand the issues involved.

Cause: The DNS server is not configured to use other DNS servers to assist it in resolving
queries.

Solution: Check whether the DNS server can use both forwarders and recursion.

Cause: Current root hints for the DNS server are not valid.

Solution: Check whether server root hints are valid.

If configured and used correctly, root hints always should point to DNS servers authoritative for
the zone containing the domain root and top-level domains.

By default, DNS servers are configured to use root hints appropriate to your deployment, based
on the following available choices when using the DNS console to configure a server:

1. If the DNS server is installed as the first DNS server for your network, it is configured as a
root server.

For this configuration, root hints are disabled at the server because the server is
authoritative for the root zone.

2. If the installed server is an additional DNS server for your network, you can direct the
Configure DNS Server Wizard to update its root hints from an existing DNS server on the
network.
 3. If you do not have other DNS servers on your network but still need to resolve Internet
DNS names, you can use the default root hints file which includes a list of Internet root
servers authoritative for the Internet DNS namespace.

Cause: The DNS server does not have network connectivity to the root servers.

Solution: Test for connectivity to the root servers.

If root hints appear to be configured correctly, verify that the DNS server used in a failed query
can ping its root servers by IP address.

If a ping attempt to one root server fails, it might indicate that an IP address for that root server
has changed. Reconfiguration of root servers, however, is uncommon.

A more likely cause is a full loss of network connectivity or in some cases, poor network
performance on the intermediate network links between the DNS server and its configured root
servers. Follow basic TCP/IP network troubleshooting steps to diagnose connections and
determine whether this is the problem.

By default, the DNS service uses a recursive time-out of 15 seconds before failing a recursive
query. Under normal network conditions, this time-out does not need to be changed. If
performance warrants it, however, you can increase this value.

To review additional performance related information on DNS queries, you can enable and use
the DNS server debug log file, Dns.log, which can provide extensive information about some
types of service-related events.

Cause: Other problems exist with updating DNS server data, such as an issue related to zones
or dynamic updates.

Solution: Determine whether the problem is related to zones. As needed, Troubleshoot any
issues in this area, such as possible failure of zone transfer.

3. The DNS server appears to be affected by a problem for reasons not described above.

Cause: My problem is not described above.

Solution: Search TechNet at the Microsoft Web site for the latest technical information that
could relate to the problem. If necessary, you can obtain information and instructions that pertain
to your problem or issue.

Steps to Configure Database Server

Database server

A database server is a computer program that provides database services to other computer
programs or computers, as defined by the client–server model. The term may also refer to a
computer dedicated to running such a program. Database management systems frequently
provide database server functionality, and some DBMSs (e.g., Microsoft Structured Query
Language) rely exclusively on the client–server model for database access.
Such a server is accessed either through a "front end" running on the user’s computer which
displays requested data or the "back end" which runs on the server and handles tasks such as
data analysis and storage.

In a master-slave model, database master servers are central and primary locations of data while
database slave servers are synchronized backups of the master acting as proxies.

Some examples of Database servers are Oracle, DB2, Informix, Ingres, SQL Server. Every
server uses its own query logic and structure. The SQL query language is more or less the same
in all the database servers.

Installing SQL Server 2005

The SQL Server 2005 Installation Wizard is Microsoft Windows Installer-based, and provides a
single feature tree for installation of all Microsoft SQL Server 2005 components:

• SQL Server Database Engine

• Analysis Services
• Reporting Services
• Notification Services
• Integration Services
• Management Tools
• Documentation and Samples

Note - SQL Server 2005 is available in 32-bit and 64-bit editions. The 64-bit editions of SQL
Server 2005 are installed using the same methods as the 32-bit editions: through the Installation
Wizard, or via the command prompt. For more information on SQL Server 2005 components, see
Editions and Components of SQL Server 2005. Regardless of whether you use the SQL Server
2005 Installation Wizard or the command prompt to install SQL Server 2005, the Setup process
involves the following steps.

To prepare your computer for SQL Server 2005, review hardware and software requirements,
System Configuration Checker requirements and blocking issues, and security considerations.

Step to Install SQL Server 2005

• The first screen to be displayed is the End User License Agreement (EULA). The user is
expected to read through the license agreement and accept the license before he can
proceed any further. After accepting the license agreement, click on Next to proceed.

Note that .NET Framework 2.0, Microsoft SQL Native Client and Microsoft SQL Server 2005
Setup support files have to be installed. The finish button is to be clicked. Now the Welcome
screen appears.

• The next step is the system configuration check. The report of the check is displayed to
the user. The success or failure of the check is reported along with warnings if any.

• Once the user clicks continue the installation begins.

• The next step is to enter the registration information. The user enters his name, company
name and the serial number as it appears on the yellow sticker on the cover of the DVD.
The user then clicks on Next to continue.

• Next the components to be installed have to be specified. The user can chose to install
all the components or some of the components. Some of these components require
further configuration information and the user will be prompted to enter such information if
the components are selected. If the SQL Server is being installed on a cluster, the user
will be required to enter cluster information.

• On clicking Next, the Feature selection dialog box appears. All the selected features are
displayed.

• On clicking next the user is prompted to select the instance name. If he selects Default
instance no name need be specified. If he selects Named instance, he will have to
specify a name for the instance. Click Next to continue.

• The user is now prompted to enter the details of the service account which is to be used
for login to the server. The local or Domain user account can be selected. The security
context required to run the SQL server demands that a user account be specified during
installation. By default Windows authentication mode is supported.

• The Authentication mode dialog box appears. The user must specify the authentication
mode. It can be Windows authentication or Mixed mode. The user must assign a login
irrespective of the mode selected. He must enter the password and confirm it before
clicking next to continue.

• The next dialog box is the Collation Settings dialog box. Collation settings define the
sorting behaviour of the server. SQL server collations are used for setting up compatibility
with earlier versions of SQL Servers.

• The Report server database setup dialog box which appears requires the user to specify
the instance of the SQL Server which will host the report server database. Select Host in
current instance of SQL Server and specify the report server database name and click
next to continue.

• The Next dialog box is the Report Server Delivery Settings dialog box. The user has to
specify the parameters required for sending email reports. Click Next to continue if you
do not wish to enter any details here.

• The Error Reporting dialog box appears prompting the user that SQL server, its
components and Analysis services will be configured to send fatal service error reports to
Microsoft or a corporate error reporting server. The user can select the check box and
click next as this helps Microsoft in monitoring its services and improving upon its
software. Click Next to continue.

• The ready to install dialog box displays all the components that are going to be installed
on the system. To proceed with the installation the user has to click on Next.
 • The setup progress bar is displayed. On completion of set up the Next button will become
enabled and the user has to click on Next to proceed.

• The next dialog box displays all the files that are being configured. The user has to click
on Next to continue.

• The last dialog box displays the progress of the set up. All the selected components
being configured are displayed and their status indicated. Click on Next to continue.

• This takes the user to the final screen of the setup. The system is required to be rebooted
for the configuration to take effect. The user is asked to click on finish to reboot the
system. The user is informed that any errors in set up are recorded in the summary log
for future reference. Click on Finish to complete the process.

Steps to Configure Exchange Server

Introduction to Exchange Server

Microsoft Exchange Server is the server side of a client–server, collaborative application

product developed by Microsoft. It is part of the Microsoft Servers line of server products and is
used by enterprises using Microsoft infrastructure products. Exchange's major features consist of
electronic mail, calendaring, contacts and tasks; support for mobile and web-based access to
information; and support for data storage.

Pre-requisites to Install Exchange Server

Make sure you have all of the following steps in place before you setup Exchange Server 2003.

For simplicity we are assuming you are setting up a small office where one machine will be used
for both the Active Directory and the Exchange Server. This setup works just fine and reduces the
number of machines to maintain. If you have a larger office you may want to consider separating
the Active Directory machine and the Exchange 2003 Server.

1. You must have IIS (Internet Information Server) installed.

When you install IIS, you should select the typical install that includes an SMTP
component.
2. Make sure your networking has DNS setup.
If you use DHCP, the DNS setting should be set, if you do not use DHCP then make sure
that you have entered your DNS server names. Exchange Server will use your DNS
settings when it sends e-mail to the Internet.
3. You must have Active Directory setup.
To setup active directory, go to Start -> Programs -> Administrative tools -> Configure
your server.
Select Active Directory from the left hand panel, then select "Start" in the right hand panel
to start the setup wizard.

Steps to install Exchange Server

Run the Exchange Server Setup - it will walk you through the following wizard
 1. Agree to the licenses agreement
2. Enter your serial number
3. The next screen will prompt you to select what components you want to install.
The typical configuration is selected. This should be fine with most installation. If you
need you can enable any additional services you wish.
4. At the installation type screen - we are setting up a new organization, so we have
used the default selection “Create a new Exchange Organization”.
5. At the organization name screen - enter the name of your company
6. Agree to the license statement
7. Review the your selections and press next to begin

The installation wizard will now install the components you have selected - this will take
several minutes to 1/2 hour. When it is complete you are ready to add your users.

Adding E-Mail Users

Go to the start menu -> Programs -> Microsoft Exchange -> Active Directory Users and
Computers

On the left hand side of the screen, select users. Then right click in the right hand panel and
select "New" and at the sub menu select "User". You will be presented with a wizard where
you enter the users name and e-mail address. Then press next and enter that users password
and press next. On the last screen select that you want to create an Exchange Mailbox. When
you press finish the user is created and you are ready to enter another user name.

• At last interconnect the servers together

• Configuring the branch office clients to reach the head office servers

• Creating the VPN tunnel for secure transmission between head office and Branch office.