clients accessing their mailboxes. It is used to automatically set up accounts in

Outlook profiles. It is also used to determine which Client Access Server a remote

client should use based on where their mailbox server is located for optimal

performance.

• Availability Automatic load balancing of inbound and outbound connections

between Hub Transport Servers within an Active Directory site.

• Built on Active Directory The routing topology for Exchange Server 2007 servers

is based on the Active Directory site topology. It no longer requires the creation of

routing groups to control mail flow.

• Development A new set of web services to access mailbox content on Exchange

Mailbox Servers via HTML extends developers’ capabilities.

• Exchange Management Console Replacement tool for the Exchange System

Manager (ESM). The Exchange Management Console (EMC) is based on Microsoft

Management Console (MMC) 3.0 and combines all of the Exchange management

tasks into a single graphical interface. That means no more jumping between the

ESM and Active Directory Users and Computers (ADUC) to get Exchange

administrative tasks done.

• Exchange Management Shell A new command-line interface (CLI) from Microsoft

built on the PowerShell technology for advanced administrative tasks that cannot be

performed or automated in the Exchange Management Console.

• High availability for Mailbox servers Transaction Log Shipping is now available

for Mailbox Server roles in two flavors: Local Continuous Replication (LCR) and

Cluster Continuous Replication (CCR). Each creates a second copy of the production

database for rapid recovery scenarios. LCR stores the copy on the local server. CCR

stores the copy on another server. The Single Copy Cluster (SCC) is the latest

implementation for the traditional Exchange Microsoft Cluster Service.

• Message conversion The Hub Transport Server role has the ability to analyze the

formatting and encoding of messages and, based on the originator and recipient of

the message, make the necessary conversion to prevent formatting errors.

• Minimization of mail traffic Within an organization, least-hop routing is used to

determine the best path to a recipient’s mailbox. This has a greater potential of

reducing traffic than least-cost routing, which is subject to arbitrary administrative

constraints. Hub Transport Servers are responsible for determining the least-hop

route between Active Directory sites.

Performance improvements Exchange Server 2007 is a native 64-bit application.

Sixty-four-bit computing benefits are visible in the increased memory cache size,

increased number of storage groups, and increased number of information stores

per server.

• Recipient resolution It has always been possible to designate an expansion server

for a Distribution List. This is not as critical to do now that the Hub Transport

Servers are site-aware and will use the directory servers that are within the same

site for expanding distribution lists.

• Unified messaging For many years unified messaging has been available for

Exchange Server from third-party vendors. This technology, which integrates voice

messaging, faxing, and e-mail, has also been price-prohibitive for many small- and

medium-size businesses. By including unified messaging with Exchange Server

2007, all Exchange organizations can begin to take advantage of this powerful

productivity tool.

   1. Open the Exchange Management Console.
   2. Choose Server Configuration > Client Access.
   3. Click the “Owa (Default Web Site)” entry.
   4. From the Action pane, choose the Properties option.
   5. From the Owa (Default Web Site) Properties page, click the Authentication tab.
     
Under the “Use Forms-Based Authentication” option there are three options for enforcing a particular logon format. The Domain\User Name option is self-explanatory and is useful if you have multiple domains. The User Principal Name (UPN) option, or e-mail address format, is probably the easiest for users to remember since they use it all the time. The User Name Only option is the last option, which is also self explanatory. If you choose the User Name Only format, you also need to choose a Logon Domain.
   6. Click OK

Because this change affects IIS, you must restart IIS. From a command line on the Outlook Web Access server, issue the command iisreset /noforce.

Open up the cmd prompt and type:
ServerManagerCmd -i RSAT-ADDS

You should then see if it completed successfully or if it was ran already.

The command requires a reboot after it installs. After you reboot, try the prep again.

in the ldif.err shows

Entry DN: CN=ms-Exch-Resource-Schema,CN=Schema,CN=Configuration,DC=buckleyschoolnyc,DC=org
Add error on line 180: No Such Attribute
The server side error is “The parameter is incorrect.”
An error has occurred in the program

You have to use adsiedit and modify some attributes in AD
go to the ms-Exch-Resource-Schema under schema configuration
then where it says display name if you see anything that says DUP with some numbers, remove the DUP and numbers and should just show the schema atrribute for example ms-Exch-Resource-Schema should show as ms-Exch-Resource-Schema not as DUP12312311ms-Exch-Resource-Schema

 Second go to
ms-exch-resource-property-schema
change ldapdisplayname that had a dup prefix and guid suffix to: msExchResourcePropertySchema