How to Install Exchange Server 2010 Beta

8/14/2019 How to Install Exchange Server 2010 Beta

1/36

How to Install Exchange Server 2010 Beta

Now that Exchange Server 2010 is available to download and try in Beta format, I wanted toprovide a quick blog on how to install the Exchange Server 2010 Beta.

Installing Exchange Server 2010 begins with installing and preparing the operating system.Exchange Server 2010 can be installed only on Windows Server 2008 Standard Edition orEnterprise Edition. If you plan on trying out database availability groups and mailboxdatabase copies, you will need to use the Enterprise Edition of Windows Server 2008. Formore information about the requirements for Exchange Server 2010, see Exchange 2010System Requirements.

Once the operating system has been installed, several pre-requisites must beinstalled. These include:

Operating system components, including RSAT-ADDS (needed onserver that will perform schema updates), Web-Server, Web-Metabase,Web-Lgcy-Mgmt-Console, Web-ISAPI-Ext, NET-HTTP-Activation, Web-Basic-Auth, Web-Digest-Auth, Web-Windows-Auth, Web-Dyn-Compression, RPC-over-HTTP-proxy, Web-Net-Ext and Net-Framework.You can install all of these components at one time (e.g., for theMailbox, Client Access and/or Hub Transport Server roles) by runningthe following command:

ServerManagerCmd -i RSAT-ADDS Web-Server Web-MetabaseWeb-Lgcy-Mgmt-Console Web-ISAPI-Ext NET-HTTP-ActivationWeb-Basic-Auth Web-Digest-Auth Web-Windows-Auth Web-Dyn-Compression RPC-over-HTTP-proxy Web-Net-Ext -Restart

For more information about the prerequisites for Exchange 2010,including those for the Edge Transport server role, see Exchange 2010Prerequisites.

You might have noticed that Failover-Clustering is not listed as a pre-requisite. There is a feature in Exchange Server 2010 called a databaseavailability group that does use Windows failoverclustering technologies. However, thanks to another Exchange Server2010 feature called incremental deployment, you no longerinstall failover clustering before installing Exchange. If you decide touse a database availability group, you simply create one, and then addMailbox servers to it. When you add a Mailbox server to a DAG, we
http://www.microsoft.com/exchange/2010http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=1898ed2c-2f88-48ac-824e-d3d20fad77d7http://technet.microsoft.com/en-us/library/aa996719(EXCHG.140).aspxhttp://technet.microsoft.com/en-us/library/aa996719(EXCHG.140).aspxhttp://technet.microsoft.com/en-us/library/bb691354(EXCHG.140).aspxhttp://technet.microsoft.com/en-us/library/bb691354(EXCHG.140).aspxhttp://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=1898ed2c-2f88-48ac-824e-d3d20fad77d7http://technet.microsoft.com/en-us/library/aa996719(EXCHG.140).aspxhttp://technet.microsoft.com/en-us/library/aa996719(EXCHG.140).aspxhttp://technet.microsoft.com/en-us/library/bb691354(EXCHG.140).aspxhttp://technet.microsoft.com/en-us/library/bb691354(EXCHG.140).aspxhttp://www.microsoft.com/exchange/2010


2/36

install the Windows failover clustering feature and automaticallycreate a cluster for you. So while you do need to have Exchangeinstalled on an operating system that supports Windows failoverclustering, you do not install the failover clustering feature manually,or ahead of time, and you don't manually create a cluster. It makes

deploying highly available mailbox databases quick and easy.

Exchange Server 2010 also supports installing the above pre-requisitesby using an Answer File with ServerManagerCmd, and answer files areincluded in the \AMD64\Scripts folder. To use them, you runServerManagerCmd -ip . For example:

ServerManagerCmd -ip Exchange-CAS.XML

I recommend that you don't use the XML Answer Files for Exchange-Typical or Exchange-MBX as is, because in the Beta build it mistakenly

includs the Failover-Clustering feature, which does not need to beinstalled before Exchange is installed. This is a remnant from theAnswer Files we had in Exchange 2007 that we've since removed.

Next, are the software pre-requisites, which include:o Microsoft .NET Framework 3.5o Windows Remote Management (WinRM) 2.0 CTP 3o Windows PowerShell 2.0 CTP 3o Update from KB 951725o Update from KB 950888o Update from KB 951116

o Update from KB 952664o Update from KB 953290o Update from KB 958178

See Exchange 2010 Prerequisites for information about and links to otherpre-requisites that might apply to your environment (e.g., for Edge Transportand Unified Messaging server roles, and for environments that use SystemCenter Operations Manager).

Once the above pre-requisites have been installed, check Microsoft Updatefor any additional updates that might be needed. Make sure the system has

been rebooted after installing any updates which require a reboot.

Now you're ready to install Exchange 2010. You can perform the installationusing the GUI or command-line version of Setup. In this example, I'll use theGUI.

I'll start by launching Setup.exe from the AMD64 folder. This launches theExchange 2010 splash screen:
http://go.microsoft.com/fwlink/?LinkID=96339http://go.microsoft.com/fwlink/?LinkId=135126http://go.microsoft.com/fwlink/?LinkId=135123http://go.microsoft.com/fwlink/?LinkId=3052&kbid=951725http://go.microsoft.com/fwlink/?linkid=3052&kbid=950888http://go.microsoft.com/fwlink/?linkid=3052&kbid=951116http://go.microsoft.com/fwlink/?linkid=3052&kbid=952664http://go.microsoft.com/fwlink/?linkid=3052&kbid=953290http://go.microsoft.com/fwlink/?linkid=3052&kbid=958178http://go.microsoft.com/fwlink/?LinkID=96339http://go.microsoft.com/fwlink/?LinkId=135126http://go.microsoft.com/fwlink/?LinkId=135123http://go.microsoft.com/fwlink/?LinkId=3052&kbid=951725http://go.microsoft.com/fwlink/?linkid=3052&kbid=950888http://go.microsoft.com/fwlink/?linkid=3052&kbid=951116http://go.microsoft.com/fwlink/?linkid=3052&kbid=952664http://go.microsoft.com/fwlink/?linkid=3052&kbid=953290http://go.microsoft.com/fwlink/?linkid=3052&kbid=958178


3/36

As you can see, the Exchange 2010 splash screen is very similar to the one we had inExchange 2007. Any needed pre-requisites which are detected, are greyed out, indicatingthey have been installed, and that you can proceed to the next step. In this case, I canproceed directly to Step 4: Install Microsoft Exchange.

I click that link and it launches the GUI version of Exchange Setup, beginning with a file copyprocess, and the initialization of Setup.

Once Setup is initialized and the file copy process has completed, the Introduction pageappears:
http://blogs.technet.com/photos/scott_schnoll/images/3219966/original.aspx


4/36

I click Next, and the Language Files Location page appears:

I don't have any additional language files, so I'll leave the default setting ofContinue setupwithout language files and click Next. The Language Pack Confirmation page appears:
http://blogs.technet.com/photos/scott_schnoll/images/3219968/original.aspxhttp://blogs.technet.com/photos/scott_schnoll/images/3219967/original.aspx


5/36

I click Next, and the License Agreement page appears:

After reading the license agreement, I select I accept the terms in the licenseagreement and click Next. The Error Reporting page appears:


6/36

Error reporting is very helpful to us, which in turn is helpful to our customers, as it enablesus to gather a minimal amount of diagnostic data to troubleshoot and resolve errors andcrashes more quickly. So I am going to chooseYes (Recommended) and click Next. TheInstallation Type page appears:
http://oca.microsoft.com/en/dcp20.asphttp://blogs.technet.com/photos/scott_schnoll/images/3219973/original.aspxhttp://blogs.technet.com/photos/scott_schnoll/images/3219971/original.aspxhttp://oca.microsoft.com/en/dcp20.asp


7/36

Immediately, you might notice some differences from Exchange Server 2007. First, theCustom Exchange Server Installation option no longer lists any clustered mailbox serverroles. That's because clustered mailbox servers don't exist in Exchange Server 2010.Exchange 2010 includes a new feature called Incremental Deployment. This feature enablesto you configure high availability and site resilience for your mailbox database afterExchange has been installed.

Second, the default path for the Exchange Server installation is new and different. If I chooseCustom Exchange Server Installation, the Server Role Selection page appears:

If I choose Typical Exchange Server Installation instead of Custom Exchange ServerInstallation and click Next, or once I've completed the Custom Exchange Server Installationchoices and clicked Next, the Exchange Organization page appears:


8/36

I specify a name for my Exchange Organization, and then I click Next. The Client Settingspage appears:


9/36


10/36

As you can see, the readiness checks don't take much time at all. Once all readiness checkshave successfully passed, the Readiness Check page will look similar to this:


11/36

At this point, the system and server are ready for the installation to begin. I click Install tostart the installation of Exchange 2010 Mailbox, Client Access and Hub Transport serverroles, as well as the Exchange Management tools (Exchange Management Console andExchange Management Shell).

While Setup is progressing, a Progress page will be appeared:

Once Setup has completed successfully, the Completion page will appear:


12/36

As you can see, installing Exchange 2010 is quick and easy. On my system, Setup took justunder 10 minutes to complete.

I prefer to reboot the system before finalizing the installation. Uncheck the Finalizeinstallation using the Exchange Management Console checkbox, and click Finish tocomplete the Setup process. This returns Setup to the splash screen. Click Close to closethe splash screen, and when the Confirm Exit dialog appears:

ClickYes.

Then, reboot the server. OK, technically, you don't need to reboot the server, but I doanyway.

The installation of Exchange Server 2010 is now complete. Check out the Exchange 2010TechCenter for documentation and other resources for Exchange 2010.

Published Wednesday, April 15, 2009 12:01 AM by Scott Schnoll
http://technet.microsoft.com/en-us/exchange/default.aspxhttp://technet.microsoft.com/en-us/exchange/default.aspxhttp://blogs.technet.com/user/Profile.aspx?UserID=5776http://blogs.technet.com/photos/scott_schnoll/images/3221366/original.aspxhttp://technet.microsoft.com/en-us/exchange/default.aspxhttp://technet.microsoft.com/en-us/exchange/default.aspxhttp://blogs.technet.com/user/Profile.aspx?UserID=5776


13/36

Filed under:Setup, Exchange Server 2010

SECOND type

Step by Step guide on how to install Exchange Server 2010

Beta - Part 1

Introduction

Just got my hands on this latest new messaging product fromMicrosoft, and this has been one ofthe most anticipated products - Microsoft Exchange Server2010 Beta (code named Exchange 14).

You may can find the download linkhere, if you wish to test this out in your environment.

Design Diagram @MyLab

Below is the Exchange Server 2010 design in my Lab setup, all the servers are virtualized.
http://blogs.technet.com/scottschnoll/archive/tags/Setup/default.aspxhttp://blogs.technet.com/scottschnoll/archive/tags/Setup/default.aspxhttp://blogs.technet.com/scottschnoll/archive/tags/Exchange+Server+2010/default.aspxhttp://www.messagingtalk.org/http://www.messagingtalk.org/http://www.messagingtalk.org/http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=1898ed2c-2f88-48ac-824e-d3d20fad77d7http://blogs.technet.com/scottschnoll/archive/tags/Setup/default.aspxhttp://blogs.technet.com/scottschnoll/archive/tags/Exchange+Server+2010/default.aspxhttp://www.messagingtalk.org/http://www.messagingtalk.org/http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=1898ed2c-2f88-48ac-824e-d3d20fad77d7


14/36

Prerequisites

Before installing Exchange Server 2010, here are the prerequisites to be installed in all the

servers


15/36


16/36


17/36

Now we have done the initial preparation. The forest and domain are ready to have the first

Exchange 2010 server installed.

2. Install first Exchange 2010 server

We will do that on server"Bugis" which will have Client Access Role, Transport Role and

Mailbox Role. But we will eventually remove the Mailbox role and deploy DAG on server

"Outram", "Redhill" and "Dover". There is a reason behind why I choose to have 3 mailboxservers to form a DAG. That will be discussed in my future articles soon.

There are additional components needed before Exchange installation.,

As my first Exchange server is a combination all the 3 roles mentione above, I used the

following command (refer the below screen capture)

ServerManagerCmd -i Web-Server Web-Metabase Web-Lgcy-Mgmt-Console Web-Basic-Auth

Web-Windows-Auth Web-Net-Ext Web-Digest-Auth Web-Dyn-Compression NET-HTTP-

Activation Web-ISAPI-Ext RPC-over-HTTP-proxy RSAT-ADDS


18/36

Here is the break down of what you will need to install in role level.

Client Access Role


Web-Windows-Auth Web-Net-Ext Web-Digest-Auth Web-Dyn-Compression NET-HTTP-

Activation Web-ISAPI-Ext RPC-over-HTTP-proxy RSAT-ADDS

Transport Role


Web-Windows-Auth Web-Net-Ext RSAT-ADDS

Mailbox Role

ServerManagerCmd -i Web-Server Web-Metabase Web-Lgcy-Mgmt-Console Web-Basic-AuthWeb-Windows-Auth Web-Net-Ext RSAT-ADDS

*For Mailbox Role, you have to install another component call "MSFilter Pack"

After the installation, you are required to perform restart server.
http://www.microsoft.com/downloads/details.aspx?FamilyId=60C92A37-719C-4077-B5C6-CAC34F4227CC&displaylang=enhttp://www.microsoft.com/downloads/details.aspx?FamilyId=60C92A37-719C-4077-B5C6-CAC34F4227CC&displaylang=en


19/36

There are some updates & fixes need to be applied in specific.

Client Access Role

KB951725, KB950888,KB952664, KB953290

Transport Role

KB951725, KB950888,KB952664

Mailbox Role

KB951725, KB950888,KB952664

Now we are truly ready for the installation. I will not talk about installation using UI, because Iprefer using command line.

Execute the command as shown in the screen capture below.
http://support.microsoft.com/kb/951725http://support.microsoft.com/kb/950888http://support.microsoft.com/kb/950888http://support.microsoft.com/kb/952664http://support.microsoft.com/kb/953290http://support.microsoft.com/kb/951725http://support.microsoft.com/kb/950888http://support.microsoft.com/kb/950888http://support.microsoft.com/kb/952664http://support.microsoft.com/kb/951725http://support.microsoft.com/kb/950888http://support.microsoft.com/kb/950888http://support.microsoft.com/kb/952664http://support.microsoft.com/kb/951725http://support.microsoft.com/kb/950888http://support.microsoft.com/kb/952664http://support.microsoft.com/kb/953290http://support.microsoft.com/kb/951725http://support.microsoft.com/kb/950888http://support.microsoft.com/kb/952664http://support.microsoft.com/kb/951725http://support.microsoft.com/kb/950888http://support.microsoft.com/kb/952664


20/36

Here are the definitions of the parameters

/m = /mode

/r = /role, /roles

H = Transport or you can use HT

C = Client Access or you can use CA

M = Mailbox or you can use MB

Just hit "Enter" and sit back enjoy your coffee or newspaper. :-)


21/36


22/36


23/36


24/36

Let me conclude this article with Quiz.

What was the significant difference you noticed in the above Exchange Management Consolescreen capture? Please send your answer to my Twitter @tristonwan

(http://twitter.com/trsitonwan) and if you like this article please tweet this.

Related Links

1. Installing Exchange 2010 Beta: Quick Preparation

2. How to Install Exchange Server 2010 Unified Messaging Beta

How to Install Exchange Server 2010 Unified Messaging

BetaOn April 14, 2009, Microsoft released a beta version of Exchange Server 2010. To expand on

Scott Schnolls blog on How to Install Exchange Server 2010 Beta, this topic will discuss how to

install the Exchange 2010 Unified Messaging Server Role.

To install the Exchange 2010 Unified Messaging Server Role on a Windows Server 2008operating system, the following prerequisites must be installed first:

Microsoft .NET Framework 3.5

Windows Remote Management ( WinRM ) 2.0 Community Technology Preview 3

(CTP3) Windows PowerShell V2 CTP3

Update from KB 951725

Extensions for ASP.NET AJAX 1.0

IIS 7.x Prerequisites

ServerManagerCmd -i Web-Server

ServerManagerCmd -i Web-Metabase

ServerManagerCmd -i Web-Lgcy-Mgmt-Console

ServerManagerCmd -i Web-Basic-Auth

ServerManagerCmd -i Web-Windows-Auth

Microsoft Windows Media Player Audio/Video Codecs

ServerManagerCmd -i Desktop-Experience

Exchange Server 2010 also supports installing the above pre-requisites by using an Answer File

with ServerManagerCmd, and answer files are included in the \Scripts folder. To use them, yourun ServerManagerCmd -ip . For example:
http://twitter.com/trsitonwanhttp://blogs.dirteam.com/blogs/davestork/archive/2009/04/22/exchange-2010-beta-a-first-impression.aspxhttp://www.goldsys.com/blog/blog/how-to-install-exchange-server-2010-unified-messaging-betahttp://blogs.technet.com/scottschnoll/archive/2009/04/15/how-to-install-exchange-server-2010.aspxhttp://twitter.com/trsitonwanhttp://blogs.dirteam.com/blogs/davestork/archive/2009/04/22/exchange-2010-beta-a-first-impression.aspxhttp://www.goldsys.com/blog/blog/how-to-install-exchange-server-2010-unified-messaging-betahttp://blogs.technet.com/scottschnoll/archive/2009/04/15/how-to-install-exchange-server-2010.aspx


25/36

ServerManagerCmd -ip Exchange-UM.XML

For more information about the requirements for Exchange Server 2010, see Exchange 2010

System Requirements.

For purposes of this demonstration, all Exchange 2010 Server Roles will be installed on one

physical lab server. The Mailbox, Hub Transport, and Client Access Server roles have alreadybeen installed beforehand.

Launch Setup.exe from the installation folder and select Step 4: Install Microsoft Exchange.

In the Exchange Maintenance Mode window, clickNext.
http://technet.microsoft.com/en-us/library/bb691354(EXCHG.140).aspxhttp://technet.microsoft.com/en-us/library/bb691354(EXCHG.140).aspxhttp://www.goldsys.com/blog/wp-content/uploads/2009/04/exum13.pnghttp://technet.microsoft.com/en-us/library/bb691354(EXCHG.140).aspxhttp://technet.microsoft.com/en-us/library/bb691354(EXCHG.140).aspx


26/36

In the Exchange Server 2010 Setup window, select Unified Messaging Server Role. If

necessary, change the paths of the Specify the path for the Exchange Server installation files

and Specify the path for the Exchange Server installation fields. ClickNext.
http://www.goldsys.com/blog/wp-content/uploads/2009/04/exum21.png


27/36

The system and server will be checked for the prerequisites mentioned at the beginning of this

blog.


28/36

Once all readiness checks have successfully passed, the Readiness Checks window will be

displayed. ClickInstall.


29/36

While Setup is progressing, a Progress window will be displayed.


30/36


31/36

ClickFinish to complete the installation of the Exchange Server 2010 Unified Messaging Server

role.

If necessary, select Step 5: Get Critical Updates for Microsoft Exchange to download andinstall the latest patches, hotfixes, and upgrades for Exchange Server 2010 Beta.


32/36

At this point, you can launch the Exchange Management Console to begin configuring theExchange Server 2010 Unified Messaging Server role.

We will cover the configuration in another blog posting in the near future. In the meantime, you

can read about all the new features in Exchange 2010 Unified Messaging here:
http://www.goldsys.com/blog/wp-content/uploads/2009/04/exum9.pnghttp://www.goldsys.com/blog/wp-content/uploads/2009/04/exum8.png


33/36

Voice Mail with Unified Messaging

Also, check out this video:

Exchange 2010 Videos: Whats New in Unified Messaging

For more online resources, check out theExchange 2010 Home Page.

Tags: Exchange Server 2010,Microsoft, UM, Unified Messaging

This entry was posted on Tuesday, April 21st, 2009 at 3:48 pm and is filed underGold Systems Blog.

Exchange 2010 Beta: A First Impression

A few days ago the beta of Exchange Server 2010 has been released. As Exchange hasalways been of special interest of me, I jumped at the opportunity to install it and check it out. So

will 2010 be the year we will make better contact with our own mail?

(for those sci-fi geeks out there, this was a reference to a A.C. Clark novel)

First of I used my own home computer with virtualization, but 2GB is just not enough (note:

today I bought a 4GB memory kit, hehehe). But my employergracefully let me use several of

our educational computers. These were Dell XPS420, with an Intel Quad Core Q6600 processor

and 6GB of RAM. Excellent gaming machines, but also excellent Exchange test servers :-)

For the setup I installed a Windows Server 2008 Domain Controller and another Windows 2008

server for a member server Exchange Server 2010 installation. Both fully updated as of 21 April

2009. I decided to let the forest and domain functional level at 2003.

The first attempt to install reminded me of the beta install of Exchange 2007. A lot of updates,pre-requirements and such before you could even think of starting setup.exe. I followed

instructions fromMicrosoft and Sander Berkouwer (dutch). As I have installed a lot of Exchange

2007 servers, I use a batch file to install the roles and features. You Mind you, this is for aMailbox, Client Access and Hub Transport role server all-in-one.

ServerManagerCmd -i Web-Server

ServerManagerCmd -i Web-ISAPI-Ext

ServerManagerCmd -i Web-Metabase

ServerManagerCmd -i Web-Lgcy-Mgmt-Console

ServerManagerCmd -i Web-Basic-Auth

ServerManagerCmd -i Web-Digest-Auth
http://www.microsoft.com/exchange/2010/en/us/Unified-Messaging.aspxhttp://edge.technet.com/Media/Whats-new-in-Unified-Messaging-in-Exchange-2010/http://technet.microsoft.com/en-us/exchange/2010/default.aspxhttp://technet.microsoft.com/en-us/exchange/2010/default.aspxhttp://www.goldsys.com/blog/tag/exchange-server-2010http://www.goldsys.com/blog/tag/microsofthttp://www.goldsys.com/blog/tag/microsofthttp://www.goldsys.com/blog/tag/umhttp://www.goldsys.com/blog/tag/unified-messaginghttp://www.goldsys.com/blog/category/bloghttp://www.ogd.nl/http://technet.microsoft.com/en-us/library/bb123694(EXCHG.140).aspxhttp://technet.microsoft.com/en-us/library/bb123694(EXCHG.140).aspxhttp://blogs.microsoft.nl/blogs/itprocommunity/archive/2009/04/16/aan-de-slag-met-exchange-server-2010-beta.aspxhttp://blogs.dirteam.com/blogs/davestork/Exchange2010logo_4AEE0764.pnghttp://www.microsoft.com/exchange/2010/en/us/Unified-Messaging.aspxhttp://edge.technet.com/Media/Whats-new-in-Unified-Messaging-in-Exchange-2010/http://technet.microsoft.com/en-us/exchange/2010/default.aspxhttp://www.goldsys.com/blog/tag/exchange-server-2010http://www.goldsys.com/blog/tag/microsofthttp://www.goldsys.com/blog/tag/umhttp://www.goldsys.com/blog/tag/unified-messaginghttp://www.goldsys.com/blog/category/bloghttp://www.ogd.nl/http://technet.microsoft.com/en-us/library/bb123694(EXCHG.140).aspxhttp://blogs.microsoft.nl/blogs/itprocommunity/archive/2009/04/16/aan-de-slag-met-exchange-server-2010-beta.aspx


34/36


35/36

Online Mailbox moves without disabling access for the user at the start ofmoving items (pleasant for users with very large mailboxes);

o Not yet tested, but I saw some options that would suggest this ability. Runs only on Windows Server 2008 (perhaps even R2?).

o Confirmed! I do not think that Exchange 2010 will be 2008R2 exclusive,I even think this would be unwise.

What was I hoping for?

Opening of specific folders of others users via OWA, without having fullcontrol;

o Not tested User customizable group calendars in OWA (preferably the same as in

Outlook);o Not tested

Centralized configuration of Document folders in OWA (i.e. homefolder as afavorite);

o The Document folderbutton isnt even active in OWA Edge transporter support for Windows Core server (yeah, not really

something the Exchange team can do something about);o Not tested/checked.

Better Public Folder Management;o Not tested, but define better. One could argue that the ultimate PF

management would be the delete button

Interesting items and Concluding

Well, no real surprises actually. This version is more evolution than revolution like Exchange

2000 and Exchange Server 2007 were compared to their predecessors. But there are enough

improvements warranting at least a closer examination.

The Database Availability Group is probably the biggest change (and with it the end of StorageGroups etc.). I havent read or otherwise know anything about it, but this will probably be

another great addition to achieving higher groupware availability.

An interesting addition is Microsoft Exchange On-Premises in the Exchange Management

Console. So are the terms Federation Trusts, Sharing Relationships and Sharing Policies.

Definitely going to check those out.

The upgrades on OWA are the next big thing, threaded conversations, more self administration

(user information, but also distribution groups). Its clear however that it is definitely not finished

as some buttons arent present yet (Documents, Public Folder to name a few).


36/36