Lab_Setup_Reference_Document.pdf

TRAINSIGNAL | THE GLOBAL LEADER IN PROFESSIONAL COMPUTER TRAINING

1 Exchange Server 2010 Training

LAB SETUP OVERVIEW

BY J. PETER BRUZZESE

The purpose of this document is to provide you with everything you need to know to follow along with

our Exchange 2010 Training course to the greatest degree possible. Though at times we may offer

alternative methods, the primary context of this document is to tell you exactly how we have setup our

own environment step-by-step so you can duplicate our every move.

Note: Although the Scenario we utilize throughout the series focuses on two different domains,

Globomantics.com and ParaisoBrokerage.com, we are focused solely on Globomantics at this

time. The ParaisoBrokerage domain is a demonstration domain that illustrates various aspects of

Exchange that do not come into play within the scope of our Globomantics organization. Its

purpose is to ensure that you, the learner, can see more than one type of solution and

sometimes that means stepping outside of the Globomantics environment to provide a realistic

second party approach. Feel free to duplicate ParaisoBrokerage in your environment if you like,

but it is not within the scope of this document to assist you in doing so.

THE SERVER

Assuming youve watched the Lab Setup video you already know that the server chosen to handle this

course (and it was in fact purchased specifically to meet the needs of the challenging multi-server

scenario necessary to show Exchange from every angle) is a Dell T310 with a 2.4 GHz Xeon

Processor and 16 GB of RAM. The goal here was virtualization and I knew we would need between 8

and 10 servers overall (plus the Hyper-V Server itself). RAM is the key element to virtualization and we

will discuss the allotments in a moment when we discuss setting up each child VM.

TO FOLLOW ALONG:

1. Install Server 2008 R2.

Once the server is up and running,

2. Provide a static IP address, subnet mask and default gateway.

I used 192.168.1.101 (with a 255.255.255.0 subnet mask).



My office router is a D-Link connected up to an external ISP for Internet. The IP coming in from the ISP

is dynamic which isnt ideal at times when setting up Exchange because sometimes anti-spam solutions

will check back to your IP and note the dynamic nature of it and refuse mail coming from your

environment.

To correct this,

3. Request a static IP from your ISP for a fee.

My internal IP (and hence, the default gateway) is simply 192.168.1.100.

Being that this server will not be a DNS server, nor will it be a part of the domain itself for Globomantics,

I set the DNS to also point off to 192.168.1.100 (because my D-Link router is also DNS oriented and will

provide the forwarding necessary). I also named the server something other than the names that the

server provides automatically and then checked for any Windows Updates.

Note: I named the server itself Kamino (after the name of the planet in Star Wars where all of

the clones who became stormtroopers were created).

WORKING WITH HYPER-V

Once the server was up and running with all updates installed, I added the Hyper-V role through the

Roles options in Server Manager.

To do this,

1. Open Server Manager (although it should open automatically upon login) and select the Role

option in the hierarchy (as shown in Figure 1).

2. Click the Add Roles link within the working pane to choose Hyper-V.

Upon reboot your system will now be a parent virtual machine (or VM) and you will have the

ability to add additional child VMs through the Hyper-V Manager.



Figure 1: The Server Manager options for adding in Roles.

For additional information in working with Hyper-V you can visit the Microsoft web site:

http://www.microsoft.com/hyper-v-server/en/us/default.aspx

THE HYPER-V MANAGER

1. Open the Hyper-V Manager by selecting the Start button and choosing Administrative Tools and

then Hyper-V Manager.

In the Lab Setup video we walked you through some of the options here but you can see from

Figure 2 that you have your server (in our case Kamino), your virtual machines (filled with all

sorts of systems that are named as VMs which do not reflect the names you provide to the

systems themselvesthe two are not connected), and you have your Actions pane.

http://www.microsoft.com/hyper-v-server/en/us/default.aspx



Figure 2: The Hyper-V Manager

You need to create empty VMs with memory requirements and hard disk requirements that you will

ultimately install your servers into.

2. Use the New action from the Actions pane and choose Virtual Machine.

3. Follow the wizard.

Depending on the VM you are creating, you will want to provide different memory settings. Using 2048 is

safe for all systems to perform the work we need to handle in a lab environment and follow along with

the course. However, if you want to save some memory room you can use 1024 on the Edge Transport

server roles. I also used 1024 on all Mailbox server roles that were not my main roles, just used for the

High Availability lessons later on in the course.

As for hard disk settings you want to configure for 20 GB which will give you plenty of room to install

your OS, your Exchange files and more.

SERVERS TO CONFIGURE:

NYDC1: This is a server where you will install Server 2008 R2 and configure Active Directory and DNS to

run off of it as shown in the Lab Setup video (running DCPROMO).



1. Install the server into the VM and configure the IP settings to be 192.168.1.1 with a

255.255.255.0 subnet mask

2. Point the default gateway off to the router (which in my case is 192.168.1.100).

For DNS you are going to want to point it at itself (you can use the 127.0.0.1) with the

secondary DNS address pointing to the router at 192.168.1.100.

Remember to change the name. You dont have to use NYDC1 but you dont want to

leave the default and upgrade to Active Directory in this way.

When you install Active Directory following the method in the Lab Setup video, remember

to install the DNS side as well.

In determining your domain name you should consider if this is going to be a fully functional Exchange

organization when you are done or simply a lab organization.

Will I need to send and receive email to the Internet from this organization for real when I am

finished?

Then you will need to register a domain name with GoDaddy or some other provider, as

explained in Lab Setup video.

Even if you simply want to follow along with the course when it comes to certificates and federation, you

will need a registered DNS name. Watch the Lab Setup video to help you make your decision as to what

kind of naming structure you want to go with. You may decide on a bogus internal FQDN structure but

register a real DNS name that is different from what you use in-house. In our video series however, we

use Globomantics.com for both the internal and external domains. We use GoDaddy to handle our DNS

for external connections and we use our internal DNS infrastructure for the internal side.

Note: The DNS server will update itself automatically with all the IP addresses of additional

servers that join the domain. The one server that will be unique is the Edge Transport server

because you do not join the domain with this server so you will need to go into DNS and

configure a manual A host record for that Edge Transport server. Without this in place your Edge

Subscription (shown later on in the course) will fail because your Hub Transport server will not

see your Edge Transport server.

Once you have NYDC1 setup and running Active Directory and DNS, that server is pretty much left alone

for the majority of the course. You may update the Schema from here and you might return to add

users; however, most of these tasks can be one without actually working on the literal machine. So, you

leave NYDC1 running and supporting the AD side to our Lab Setup.

Cant I just install Exchange on a DC?

Yes, but it is not supported as Best Practice for a variety of different reasonsperformance,

security-oriented, and otherwise. In a lab situation, however, you are welcome to reduce the

number of needed servers by installing Exchange directly on the DC. In our case, we chose to go

with real-world best practices and set it up separately.



ADDITIONAL SERVERS:

You are going to install three additional servers to move forward in the course from the Globomantics

perspective. At this time they will all be setup exactly the same way.

Follow these steps:

1. Configure the Child VMs to have 2048 MB of RAM (unless you decide to go 1024 on the Edge)

with 20 GB of RAM.

2. Install Server 2008 R2

Note: you can use 2008 if you like, but we go all R2 in the course

3. Rename each server to a name that relates to the roles.

In the course we have EX2K10MB1, we have EX2K10PRIME (which seemed like a good idea for

naming when you have CAS and HT together) and we have EDGE.

4. Configure IP address settings to be 192.168.1.x (with x being .2, .3, .4 or whatever addressing

you think is best for your lab) and subnet masks being 255.255.255.0 with each of them pointing

off to your default gateway (in my case 192.168.1.100).

5. Join EX2K10MB1 and EX2K10PRIME to the domain (DO NOT JOIN the EDGE server to the

domain).

6. Move over your Exchange installation software.

If you are working with an ISO, you can mount that ISO in the VM settings for DVD so that you

can install through the ISO. If you have an EXE you can move it into the server and open it to

expand the files so that you can eventually click the Setup file and perform the installation.

Next? Nothing. We will continue the process within the course itself. In the videos following, we will

use some PowerShell commands to help us in configuring all the little side elements that need to be

installed and configured. This is much better than trying to manually go through and perform these

tasks.

Take a look at some of the prerequisites here and the commands for both Server 2008 and

Server 2008 R2 here: http://technet.microsoft.com/en-us/library/bb691354.aspx

http://technet.microsoft.com/en-us/library/bb691354.aspx



WHERE DO WE GO FROM HERE

At this point you have several servers installed and running on a Hyper-V box. They are all ready to have

the prerequisites be the focus. Those prerequisites will call for changes to the Active Directory Schema

and the domain configuration through commands we will run (and you can see running in the video

series). We will use the PowerShell cmdlets to install all the prerequisite roles and features on each

server that requires those pieces. We will install Exchange and the various role types that are designed

for each of these servers in videos ahead as well.

At this point, you are on the cusp of exploding into a world of Exchange. Take a deep breath exhale

and Ill see you in the next lesson.

Possible Alternative Configurations

Its understandable that you may not have the hardware to perform a multi server install as we have

outlined above. Perhaps you have a server with 4 GB or 8 GB of RAM and you know that at some point

you will run out of memory or resources. Do not stress to too great a degree. You may want to setup

multiple desktop systems with 4 GB of RAM and run some form of client-side, type-2 virtualization

product (I personally like VMWare Workstation for this sort of thing) to allow you to run a single

Exchange VM or 2 Exchange VMs) and build out your Lab in this way.

However, you should know that you can follow along with 90% of this course with 2 servers. One server

running as a DC with DNS, which is also running the Mailbox, Hub Transport and Client Access roles

and another server running the Edge Transport role. Now, you wont be able to do any High Availability.

And you wont be able to do more than configure your UM (which is actually the case with the structure

you have outlined above because you would need a VoIP Gateway or some actually telephony

infrastructure to perform UM testing). BUT you would be able to perform most of the configuration

outlined in the course itself.

Exchange Server 2010 Training


Hardware:

16 GB of RAM

2.4 GHz Processor

Software/Roles Installed:

Server 2008 R2

Hyper-V Role

Networking:

IP Address: 192.168.1.101

Subnet Mask: 255.255.255.0

Default Gateway:192.168.1.100

THE SERVER (KAMINO) THE DOMAIN CONTROLLER (NYCD1)

EACH VM

Software/Roles Installed:

Server 2008 R2

Active Directory

DNS

Networking:

IP Address: 192.168.1.1

Subnet Mask: 255.255.255.0

Default Gateway: 192.168.1.100

Software:

Server 2008 R2

Hardware

RAM:1024 to 2048 MB

Disk Space: 20 GB

8



SCENARIO SETUP

9

NYDC1

NYDC2

Globomantics.com

EX2K10MB1EX2K10PRIME

EDGE1

EX2K10

ParaisoBrokerage.com

CHIDC1

Site 2: Chicago Site 1: New York

Site 3: Brazil

BRDC1

T3

Internet

Switch

Router

192.168.1.x

10.1.1.x

T3

T1

Internet

Texas Branch



LAB SETUP

10

NYDC1

Globomantics.com

EX2K10MB1

EX2K10PRIME

EDGE1

EX2K10 ParaisoBrokerage.com

CHIDC1

Site 2: Chicago

Site 1: New York

Site 3: Brazil

BRDC1

Internet

VirtualRouter

192.168.1.x

10.1.1.x

Router



DETAILED SETUP

11

SITE 1: NEW YORK

NYDC1

EX2K10MB1

EX2K10PRIME

EDGE1

192.168.1.x

Server OS: Server 2008 R2IP Address: 192.168.1.1Server Roles: Domain ControllerDomain: Globomantics.com

Server OS: Server 2008 R2IP Address: 192.168.1.2Server Roles: Member ServerExchange Server Roles: HT, CASDomain: Globomantics.com

Server OS: Server 2008 R2IP Address: 192.168.1.4Server Roles: Member ServerExchange Server Roles: EdgeDomain: Globomantics.com

Server OS: Server 2008 R2IP Address: 192.168.1.3Server Roles: Member ServerExchange Server Roles: MBDomain: Globomantics.com

SITE 2: CHICAGO

CHIDC1

10.1.1.x

Server OS: Server 2008 R2IP Address: 10.1.1.1Server Roles: Domain ControllerDomain: Globomantics.com



DETAILED SETUP

12

SITE 3: BRAZIL

EX2K10BRDC1

Server OS: Server 2008 R2IP Address: 192.168.1.6Server Roles: Member ServerExchange Server Roles: TypicalDomain: ParaisoBrokerage.com

Server OS: Server 2008 R2IP Address: 192.168.1.5Server Roles: Domain ControllerDomain: ParaisoBrokerage.com

Lab Setup Document_Heatherized2LabSetup Exchange

Lab_Setup_Reference_Document.pdf

Documents

Transcript of Lab_Setup_Reference_Document.pdf