Monday, March 22, 2010

Exchange 2007 Installation Step by Step Guide

Typical Installation Using Exchange Server 2007 Setup

Microsoft has taken Messaging to the next level & it is truly worthy of praise. In this article I will only cover a "Typical" install of Exchange 2007 32 BIT on a single server. How easy it is to simply deploy an Exchange 2007 server and the out of box experience. Your messaging solutions will be up and running especially if it is a brand new domain in no time. You will surely impress your boss and get a pay rise. :)

Lets see how this can be achieved.

Lab environment:

Hostname = DC1 (AD + DNS + DHCP) ( Windows 2003 R2 SP2 )
Hostname = CS1 (Exchange server) ( Windows 2003 R2 SP2 )

Note: Once both the servers are setup ensure DNS is setup and working correctly and the Exchange server is a member of the domain and can resolve all forward & reverse lookup queries.

For getting started with a new (Domain Controller) domain click here.

For this Demo I will be using Exchange 2007 "32 BIT version" the key reasons is none of my server's at home are x64 BIT.
Note: If you are deploying this in a production environment you will have to use x64 BIT.

Compare 32 BIT & x64 BIT click here.

To download the 32 BIT version of Exchange 2007 Click here.

For Exchange 2007 System Requirements click here:

Key pre install checks in a new Windows 2003 Domain:

1: The domain functional level to be at Windows 2000 native mode or higher.

Key pre install checks for the Exchange server:
1: Install .NET 2.0 (This is part of the Windows OS Win2k3 R2 under additional components so no need to download.)
2: You must also install the following hot fix:
.NET 2.0 Framework + 32 BIT hot fix
.NET 2.0 Framework + 64 BIT hot fix
3. MMC 3.0 (This is already part of my Windows 2003 R2 SP2 OS)
4: IIS (default install)
5: Windows PowerShell 1.0 (I will use the 32 Bit version due to my hardware)

Additional Windows 2003 components:
Mailbox Server: Network COM+, IIS, World Wide Web.
Client Access Server: World Wide Web, RPC over HTTP Proxy.
Hub Transport: None

Note: Do NOT install (SMTP & NNTP) like you did back in Exchange 2000 / 2003.

Step 1: Browse to the installation source files click setup.exe.

Step 2: The Windows simply indicates that the initial requirements have been installed already or else the links would be activated and you will need to complete the pre-requisites first.

Step 3: Click "Install Microsoft Exchange" and you will see the setup screen indicated below.

Step 4: You can read the "Intro" :) or if you are too excited Click next.

Step 5: "Accept the License Agreement" once you have read it of course. Select "I accept" and click next. :)

Step 6: This is an option for you to either (enable or disable) this would not affect the product features in anyways BUT I would highly recommend to enable this as it will help Microsoft to help us to enhance the product and eliminate any errors in the product. Select the option of your choice and click next.

Step 7: In this demo we will only select "Typical Installation" but if you notice in the same dialogue box below it gives you options for a few more roles which are not pat of the "Typical Exchnage 2007 Installation". Some of which can be installed on the same server and some you cannot i.e. "Edge Transport Role". For now select "Typical Installation" and click next.

In a production environment it will depend on many key factors where each role should be placed. i.e. Consolidated on one single server like this demo OR Distributed i.e. "Client Access Server" also known as CAS, Hub Transport server also known as HT, Mailbox Server also known as (MB). Each role can be deployed individually on a separate server.

There are some exceptions to the rule when it comes down to deploying Clusters. I will cover this in the upcoming articles.

Step 8: Plan your names right from the beginning not on the fly at the time of the installation.
Note: The organization name cannot be changed once the server is installed.

Step 9: Type you org name > click next.

Step 10: I will select yes and click next simply for my testing purpose. This can be enabled once the server is installed as well. This will enable "Public Folders" and ensure Outlook 2003 clients can connect successfully for OAB.

Note: I have come across some engineers saying that "Public Folders" feature has been completely removed from Exchange 2007 which is NOT true. Microsoft simply says some features are "De-Emphasized".

Some features were not part of the initial release which will be part of Exchange 2007 SP1. Some of which also includes "Public Folder MGMT". :)

Step 11: The wizard starts doing all its required checks.

Step 12: Don't be surprised after looking at the next screen shot!!!

I left this on purpose to demo how errors are displayed while the installation is carried out. The link I referred to earlier in this article "How to install Active Directory on Windows 2003" does not cover how to upgrade the "Domain functionality".

So i decided to leave the defaults and show you how this screen appears when setup detects some of the problems. I am sure you did notice at the start of this article I did mention the "Domain requirements".

Step 13: How to raise domain and forest functional levels in Windows Server 2003

Step 14: Ensure once this change has been carried out wait for replication to complete go back and verify this change has been applied and than restart your Exchange 2007 Setup.

Step 15: It has passed all the "Readiness Checks" but it is clearly alerting "Exchange 2007 32 BIT" is not supported in a production environment.

Step 16: Exchange 2007 Installation has completed successfully click finish.

Step 17: This is the most annoying bit with this version and I guess you will have to learn to live with it. :)

You cannot get all the goodies with it being a freebie. :)

Step 18: Now it will mail enable the Administrator account by default and I have just verified that by clicking > recipient configuration > Mailbox.

Step 19: If you click on "Organisation Configuration" > Hub Transport > Accepted Domains. The default Active Directory domain is already listed as "Authoritative".

Step 20: So all I do now is to check if mail is flowing "internally" logon to Exchange using OWA.

Now this has changed a little but I will cover this later for now I will open my browser and openhttps://CS1/OWA. Logon with my Admin credentials and be prepared to get impressed with the new OWA. I cannot say enough about it, absolutely fantastic.

Keeping in mind I have not made any changes to OWA yet, even the SSL certificate option is a self generated certificate by the installer. This is the out of the box secure messaging environment approach from Microsoft..

I have sent an email to myself & received the email successfully with a confirmation as I requested it!!!

You can go ahead and create a new mailbox using Exchange 2007 MMC and send emails between different users.

Now there are few other things you will need to do but what I have covered uptil now will get you excited enough to start playing with the features.

In the upcoming articles I will cover how to configure the server further in various different ways so if you are patient enough you can wait for the other articles or else do some research by yourself and get the ball rolling.

I will also cover how to verify a successful Exchange 2007 Install very soon.

Hope this was informative enough!!! :)

Note :

Source Address : http://www.ahmedgroup.co.uk/articles

Compare Exchange 2007 32 BIT & Exchange 2007 64 BIT versions

Microsoft has released two different versions of Exchange 2007.

Exchange 2007 32 BIT
Exchange 2007 64 BIT

The Exchange 2007 64 BIT does have a subset i.e.

Standard Edition
Enterprise Edition

For this article I will only cover differences between 32 BIT & 64 BIT.

Some of you might be wondering this is absolute rubbish & I am not too surprised either. Simple reason being I have recently come across a few engineers who were so sure and simply would not agree a 32 BIT version exists.

So lets look at some differences.

Before we go any further click here to download the 32 / 64 BIT version from Microsoft website.

Note:The first and most important thing to keep in mind is Excahnge 2007 32 BIT version is NOTsupported by Microsoft in a production enviroment.

Exchange 2007 32 bit	Exchange 2007 64 bit
Not Supported in a production environment.	This is the only version which is supported by Microsoft.
32 BIT Management tools can be deployed to manage a production environment running on 64 BIT versions.	Fully supported in a production environment.
The schema can be upgraded using the 32 BIT version.	Fully supported in a production environment.
SCC + CCR can be used for testing purpose only in a non production (LAB) environment. These are enterprise edition features but do work in this version.	Fully supported in a production environment.
Unified Messaging can be tested in a non production environment.	Fully supported in a production environment.
This version can NOT be purchased from Microsoft OR Microsoft partners.	This can be purchased through the normal Microsoft channels.
No Trial License keys are required	License keys will be provided when the product is purchased.
Automatic spam updates don’t work in this version.	Can be updated using Microsoft Windows Updates.
Available editions: Exchange 2007 32 BIT Standard edition.	Available editions: Exchange 2007 64 BIT Standard edition. Exchange 2007 64 BIT Enterprise edition.
Storage groups and databases: You can have a maximum of 5 databases per server in as many as 5 storage groups on the 32-bit version. Note:This limit is also applicable on X64 BIT Standard Editions)	Storage groups and databases: You can create a maximum of 50 storage groups on each Exchange 2007 server, with up to a maximum of 50 databases.
This SHOULD NOT be used as a edge Transport server either as it is considered as a production environment	Fully supported in a production environment.

I personally think this is an absolute excellent option for customers to test this product and get a feel of it before going ahead in a production environment.

To give it a thought you can always use an old server which is not currently utilized to have a play with the 32 BIT version which will bring you up to speed & without impacting your production environment.

You can also test power shell scripts & gear yourself before hand for your move over to Exchange 2007. The same scripts can be edited as necessary and re utilized if your LAB domain does not reflect the production environment. For example:

LAB Domain: Lab.local
Production domain: abc.com

Note :

Source Address : http://www.ahmedgroup.co.uk/articles

ISA Server 2006 Configuration Step by Step Guide

Step by Step Guide Installing ISA 2006 Enterprise Edition Part 2

Step by Step Guide Installing ISA 2006 Enterprise Edition Part 2

Configure ISA 2006 Enterprise edition in an Enterprise Array. Now we are ready with the information we have gathered in Part 1 in this article series I will walk you through the process of how to install Configuration Storage servers (CS) installation & perform some initial configuration before we start deploying Internet Security & Acceleration Server services.

Configuration Storage server database is stored using (ADAM).

Logon to host CS1 and follow the instructions mentioned below.

Step 1: Insert the ISA server Enterprise Edition cd and start the installation click next.

Step 2: Accept the license agreement and click next.

Step 3: Enter the correct details including your license keys and click next.

Step 4: Select "Install configuration storage server" and click next.

a) Install ISA services: We will be using this option on the other two servers (ISA01 + ISA02) in PART 3 of the series.

b) Install Configuration Storage server: This is the option we will use for this part 2 of the article series. This will install ADAM on the following servers (CS1 + CS2). The ISA server configuration database will be stored using ADAM on these two servers.

CS1: The Primary Server.
CS2: The Replica Server.

c) Install both ISA server services and Configuration Storage server: This option would be used only on those servers when all the services would be installed on a signle server.

Note: This is also a possible option but I would not recommend using this approach.

Step 5: If you would like to change the destination location of the installation now is the time. ISA management console will be installed by default on the Configuration Storage servers; this will allow you to manage the ISA configuration from these servers as well. Once the changes are made click next.

Step 6: Select "Create a new ISA server enterprise" click next.

a) Create a new ISA server enterprise: This is the option we will select right now as this is the Primary CS server i.e. ( CS1) we are about to install.

b) Create a replica of the enterprise configuration: We will select this option when we will be running the same installation on (CS2) i.e. the second redundant / replica server which is part of our design. This can be used for redunancy & load sharing as well.

Note: I will not be demonstrating how to install a replica copy on (CS2) as the steps are almost identical with a minor change in Step 6 you will need to select "Create a replica of the enterprise configuration" you will NOT create a "New Enterprise" but "Join an existing Enterprise" by clicking on the browse button and selecting the Enterprise name you have chosen for your ISA enterprise name.

Step 7: Please read the text in the dialog box below as it is self explanatory and click next.

Step 8: Type your "Enterprise name" & and relevant "Description" and click next.

Step 9: For this lab we select option 1 as we only have a single domain.

Note: If this needs to be implemented in a production environment you need to be well aware of your current AD infrastructure and design your ISA services according to those requirements for e.g. I have seen a few deployments in a workgroup environment which were ideal for some sites, so it is all about what fits your requirements keeping best practises in mind.

Step 10: Now is the last chance to make any changes if not click Install.

Step 11: Status only.

Step 12: It will now prompt you to insert "Widnows 2003 R2" "Disk 2" so it can copy ADAM source installation files. Once this has been done click ok.

Step 13: Click finish.

With this we have successfully installed Configuration Storage services on host CS1 + CS2.

Now we need to create a new "Enterprise Array" using the ISA Management console installed on one of the CS servers i.e. ( CS1 / CS2 ). This will prepare us for going ahead and installing ISA services on ( ISA01 & ISA02 ) in PART 4 of the article series.

Note: We don't need to create this array right now and we can do this while installing the the first ISA server OR create multiple arrays while installing multiple ISA servers. But this makes the entire process straight forward so it is recommended to create the "Array" right now.

Lets me demonstrate how this can be achieved in the part 3 of this series.

Note :

Post Source Address : -

http://www.ahmedgroup.co.uk/articles

CCNP BCMSN

Pass4sure p4s bcmsn 642 812 with 379 6.79

Pass4sure p4s ccnp bcmsn 642-812 version 6.79 with 379 questions and answers

This is Full version

Link Download

How to setup

0. rightclick My Computer -> Manage -> Services and Applications -> Services -> rightclick DCOM Server Process Launcher -> Startup type : Disabled

1. use volumeid.exe and change you C: drive to ID : 5555-7777 ( volumeid C: 5555-7777 )

2. Reboot your PC ( you'll get some errors because you disabled DCOM but that's ok )

3. Check that your C: drive volume ID is indeed 5555-7777 ( by typing dir at the cmd.exe prompt )

4. install 642-812_setup.exe

5. copy the license.key to C:\program files\pass4sure test environment\350-001

6. right click license.key and make sure that it is READ-ONLY ! ( very important )

7. launch program

Ccnp p4s 642 845 v3.12

Pass4sure Ccnp p4s 642 845 v3.12

Link Download

CCNP 642-892

Pass4sure CCNP composite 642-892 v3.27

All password unrar is http://networkmanagers.googlepages.com

Source

http://www.pass4sure.com/642-892.html

Product Description Link

Pass4sure CCNP composite 642-892 v3.27

Note :

Please don't click "Interactive Test Engine-642-8923.25.exe" because you had problem "install error,please reinstall pass4sure test engine or contact customer support"

Let's Double Click "examengine.jar" to Run pass4sure -> it OK