TECH

Exchange 2007 availability strategies

File share witness (fsw) needs to go in the preferred location (the one with the active node) as if you loose coms to datacentere and fsw is in other site then that will have majority so it will fail to that site. The site that has the majority (2) quorums will win.

Use a cname for file share witness when setting it up if file share witness server fails easier if you recreate it with same name

2003 cluster nodes on same subnet. If you get a node failover communications to the Hub and Client Access Servers would be to the original AD site. Mailbox server to Hub / CAS doesn’t talk across sites.

In failover state if all of original site is gone the failover node won't talk to hub and cas as they are in different ad site. Need to change ip config of either hub and cas or the failover node in failover state. With Longhorn cluster you can have nodes in different subnets…. So this may remote this issue??

Single AD site is ok if fast lan speeds between data centers.

If you move the mailbox server then in failover state you have to recatergorize the queues so that routing can continue. This is done with right click on queue

Recommend a File Share Witeness is provisioned in other datacenter in case of site failure

If fsw in site has failed the u need to use /forceqorum switch to force it to recreate the fsw
Think this is done on cluster service

When moving the fsw back make sure both nodes are up, delete contents of the fsw and then flip cname ip

Don't want failover to happen unless its necessary.

Autodatabasemountdial is a setting that controls how many log files you are happy to through away in a failover. If you are lossless the database won't mount until all logs are available. Two other levels have varying levels of loss acceptable

Transport dumpster on hub transport. In a ccr environment. Messages added to transport dumpster. These messages are used in case of a loss failover. Based on the time windows of the failure it will ask for those messages again.

-----------------------------------------------------------------------------------------------------------------------

Unified messaging

Client support built into outlook 2007 and OWA 2007

Spoken commands via telephone is english only even though it can read content in multiple languages. Other languages have to use touch tone for now.

10% headroom over quota limit for voicemail and fax messages

UM server only talks voip to pbx. Can use a voip gateway to work with legacy pbx systems

Dial plan object - users in a dial plan can call other users using just extension. Typical a single pbx config. Extensions are unique

UM ip gateway object has the ip address of the voip gateway

Um test phone is available for download to allow you to test functionality if you don’t have a pbx

Um server object - ex 2007 UM server. Can be associated with multiple dial plans

Basic Steps
Installed UM onto server.
Create new UM dial plan
Enter number digits
Create UM IP gateway
Add an IP address and associate it with a dial plan
Go to properties of server and associate with dial plan

Can add UM mailbox policies - international calls, pin number restrictions etc

Auto attendant - associated with dial plan, can create custom menus , transfer calls etc. Can be scheduled with different messages for out of hours

For a user to use UM they must be UM enabled. Need to have extension number and be associated with a mailbox policy. Select user and select configure Unified Messaging.

Configure the pbx to forward unanswered calls to UM.

When users first connect they can record a personal greeting. The greeting is stored in users mailbox

Auto attendant -has to be associated with a dialplan and given an extension number. Have to enable it to ensure it will answer calls

Recorded messages will be delivered into inbox and user can pick up using owa, outlook or phone. If using outlook and pc has no speaker or u want privacy can play back over phone

Voice functionality very good, has the ability to make calendar appoints move them, cancel meetings and send notifications. Call users in contacts or gal. Etc etc

Ip gateways can range from 4 lines upwards so quite scaleable.
Basic UM server 70 concurrent calls

30 seconds voicemail call 40k in size

Can be load balanced with multiple gateways and UM servers

-------------------------------------------------------------------------------------------

Installing and administrating exchange 2007

Ex 2007 needs windows 2003 domain function level.
2003 sp1 on GCs

Mailbox server won't use a hub server or CAS server in a different site

/preparead - this command preps the schema and sets permissions for exchange 2007
This can be broken down into 3 separate commands.

Setup.com /preparelegacyexchangepermissions for ex2k domains and 2k3

Setup.com /preparead

Can pre provision servers so that delegated amdins can install using the /newprovisionedserver switch on the setup command

Preparead can be run from the 32 bit media. That is supported. As 64 bit media is going to need a 64bit server.

Nntp and smtp are not needed
Www service is needed

.net3 *
Mmc 3 *
Poweshell 1
*=Included with R2

Product ID has to be entered after setup otherwise get 120 days useage

Once installed go through the next steps wizard

Exchange must be in native mode. Install 2007 client access servers first as 2003 front end servers can't talk to 2007

2007 checks recipients to make sure they are compliant like smtp addresses. Should be a tool to help check this

If install ex2007 into 2003 and there is no dedicated bridgehead then can have routing probs as mail will go to 2007 and sit there. Best practice is to have a bridgehead with 2003 with smtp connector

Setup /help gives all the commands for setup