IT:Network:ApplicationsFall 2009

Running one “machine” inside another “machine”

OS in Virtual machines sees◦ CPU(s)◦ Memory◦ Disk◦ USB◦ etc

Disk is really a file on “host” Memory is usually part of “host’s” physical

memory◦ Only have so much so need to allocate sparingly

Para-virtualization◦ Guest OS “Knows” it is virtualized◦ Changes some of the function calls for hardware◦ FAST!◦ Guest OS must be modified◦ xen uses para-virtualization

Full virtualization◦ All details of virtual environment hidden◦ Guest OS unchanged◦ Time overhead!◦ VMWare and VirtualPC use full virtualization

Host-Only◦ Network internal to host◦ Guest OS can’t get out!!!◦ Nice for testing

NAT◦ Network internal to host◦ Host NIC acts as NAT router (like RRAS)

Substitutes own IP as source address as sends out◦ Nice for testing◦ More work for host◦ Double- (Triple-) NAT can cause some issues

Bridged Networking◦ Guest NICs all plugged into virtual bridge/switch◦ Each has own MAC address◦ Bridge keeps track of which MAC is which◦ Packet comes in

Hits Host NIC (only real connection out) Bridge software looks in bridging table for that MAC “Sends” to that virtual NIC

From outside, it looks like Host has multiple NICs, MACs, and IP addresses◦ E.g., each Vhost “looks” like a real machine

Cost◦ Cheaper to have one BIG machine than several smaller

ones Green

◦ Less electricity used Recovery

◦ Hardware fails, move Vhost files to other server and start!

Snapshot recovery◦ Roll it back

Need 32-bit OS but all have is 64-bit servers implemented

Microsoft’s email system Supports

◦ Outlook◦ SMTP◦ Webmail◦ Filtering (Spam)◦ etc

Windows 2003 32-bit◦ 64-bit OS not supported

Active Directory◦ Ideally Exchange not on DC but can work for testing

Patch OS Install

◦ Application Server ASP.NET IIS

NNTP & SMTP◦ Server 2003 Support Tools

D:\English\WindowsServer2003R2withSP2VLP\Enterprise\32bit\SUPPORT\TOOLS\SupTools.msi

Run DCDiag Run NetDiag Run ForestPrep Run DomainPrep Install Exchange

dcdiag /f:c:\dcdiaglog.txt /s:domaincontrollername.domain.com◦ /f:file # put output in this file◦ /s:DC # talk to this domain controller

Checks to make sure Active Directory is healthy and you can communicate with it.

Netdiag >c:\netdiaglog.txt Checks out network config

◦ IP address◦ domain membership◦ etc

Fix any errors that come up

Run off Exchange deployment wizard◦ or `setup /forestprep`

Must be logged on as◦ Forest-wide Administrator◦ Schema Administrator◦ Local Administrator

Changes AD Schema (rules)◦ New classes; New Attributes◦ Creates “MS Exchange System Object” container

in domain◦ Allows specified account full Exchange permissions

Run off Exchange deployment wizard◦ or `setup /domainprep`

Must be logged on as◦ Domain Administrator◦ Local Administrator

Creates two domain groups◦ Exchange Domain Servers (GG)

All exchange servers in the domain◦ Exchange Enterprise Servers (DLG)

ExchangeDomainServers groups from all domains

In wizard, click “Run Setup Now” Component Selection

◦ CONSIDER moving install path to different disk◦ MUCH more efficient if Exchange not on OS disk

Give you organization a name Accept summary Finish install

Disable Unwanted Services (via services.msc)◦ IMAP, POP3, NNTP, SMTP?

Setup Routing Connectors (opt)◦ Sort of like Sites and Site-Links in AD◦ Govern which exchange server can talk to which◦ Connectors link the routing groups◦ Bridge head server in each Group

Non-bridge head servers send to local bridge-head Bridge-head communicate between the groups

Setup Policies

AdminGroup > Servers > server > Storage group > ◦ props of Mailbox store◦ Set Mailbox limits and deletion settings

AdminGroup > Servers > publicStore◦ props of Public store◦ Set store limits and deletion settings

Can create a policy to do this globally

AdminGrps > FirstAdminGrp > RoutingGroups > FirstRoutingGrp > Connectors >

Create New Connector > SMTP◦ Give it a name

Specify Bridgehead Server◦ Send/Receive Internet mail

Address Space ◦ Add SMTP and leave defaults (can send/receive

to/from any address)

AdminGrps > FirstAdminGrp > Servers> Server> Protocols > SMTP

Create New SMTP Virtual Server◦ Give it a name◦ Pick IP (or all)

Limit Message Sizes, # recipients, etc Relays (BAAaaad – turn them off!)

Need a client◦ Outlook – comes with MS Office

We’ll do this later!◦ Web client

Check props of user(s)◦ Enable Web access

Rclick user > Exchange Tasks > Configure Features Outlook Web Access should be enabled

On client◦ http://server/exchange

Stay Tuned! More next week