1.) Open the Active Directory Users and Computers snapin
2.) Navigate to the Users organizational unit
3.) Delete the DiscoverySearchMailbox account
4.) Rerun the Exchange 2010 setup. The setup will install Exchange 2010 fine now…
5.) Open the Exchange Management Shell (EMC)
6.) Run the command: setup.com /prepareAD The DiscoverySearchMailbox account will be created again.
7.) Mail-enable the new DiscoverySearchMailbox with the following command:
Enable-Mailbox -Discovery -Identity “DiscoverySearchMailbox {D919BA05-46A6-415f-80AD-7E09334BB852}”
8.) Force the Active Directory Replication
9.) Your Exchange 2010 environment is ready for production now

1.) Navigate to the file EdgeTransport.exe.config, located in the Bin directory of the Exchange installation folder.
2.) Search for the rules QueueDatabasePath and QueueDatabasesLoggingPath. This is the orrigional location
3.) Open the Exchange Management Shell
4.) Browse to the scripts directory in the Exchange installation folder
5.) Select the script Move-TransportDatabase.PS1
6.) Run the following command
Move-TransportDatabase.PS1 -QueueDatabasePath NEWLOCATION -QueueDatabaseLoggingPath NEWLOCATION
In my example it’s moving to D:\Queue
7.) Now the Hub Transport database and logfiles will be moved to the new location. It’s containing the following files;

Trn.chk – The checkpoint file
Trn.log – The current transaction log file
Trntmp.log – The next provisioned transaction log file that is created in advance
Trnnnn.log – Other transaction log files that are created when Trn.log reaches its maximum size
Trnres00001.jrs – The Reserve log file
Trnres00002.jrs – The Second Reserve log file
Temp.edb – Temp DB used to verify database schema on start-up

The most common issue is that ExMon crashed while collecting data and the Exchange trace is in progress.  Follow the below given steps to stop the Exmon trace.

1.) Make sure the ExMon.exe process isn’t running.
2.) From CMD, Query running traces
Logman query -ets
3.) Stop Exmon trace
Logman stop “Exchange Event Trace” -ets
5.) Verify trace has stopped or is no longer running
Logman query -ets

If that did not resolve the issue, check the following:
- The Disk did not run out of space. If it did, clear out the old ETL files, make space on the drive or move the install directory to a larger drive.
- Another user is running Exmon already. Ask the other user to stop tracing and exit Exmon. Then restart your Tracing and start saving the Trace files.

You can download it from the Microsoft Download Center now.

Microsoft Exchange Server 2010 SP2 helps IT Professionals achieve new levels
of reliability with greater flexibility, enhanced user experiences, and
increased protection for business communications.

• Flexible and reliable – Exchange Server 2010 SP2 gives you the
  flexibility to tailor your deployment based on your company’s unique needs and a
  simplified way to keep e-mail continuously available for your users.
• Anywhere access – Exchange Server 2010 SP2 helps your users get more
  done by giving them the freedom to securely access all their communications -
  e-mail, voice mail, instant messaging, and more – from virtually any platform,
  Web browser, or device.
• Protection and compliance – Exchange Server 2010 SP2 delivers
  integrated information loss prevention, and compliance tools aimed at helping
  you simplify the process of protecting your company’s communications and meeting
  regulatory requirements.

The team has updated the tool now and provides three scenarios – on-premises only, co-existence (onsite + cloud) and cloud only.

You can find the Deployment Assistant here

1.) New-RoleGroup “Mailbox Import Export Group” -Roles “Mailbox Import Export”
2.) Add-RoleGroupMember “Mailbox Import Export Group” -Member “Administrator”
3.) New-MailboxExportRequest -Mailbox mswi -FilePath \\SRV-EXC01\Z$\Export_PST\mswi.PST

When you want to export all the mailboxes in your Exchange environment, you can use the following powershell command.
foreach ($mbx in (Get-Mailbox)) { New-MailboxExportRequest -Mailbox $mbx -FilePath “\\win2008srv01\c$\PST\$($mbx.Alias).pst” }

You can edit the maximum of two threads within the following file; MSExchangeMailboxReplication.exe.config. This file is located in the installation directory of Microsoft Exchange. In my environment it is D:\Program Files\Microsoft\Exchange Server\V14\Bin

Change the following settings:

• MaxActiveMovesPerTargetMDB = “2″

The default value (as of SP1, version 218.15, at least) seems to be 2. Change the 2 to a 5, or an 8, or whatever you’d like it to be.

• MaxActiveMovesPerSourceMDB – 5, 0, 100
• MaxActiveMovesPerTargetMDB – 5, 0, 100

Save the file, and restart the Microsoft Exchange Mailbox Replication service. Now you can perform 5 move requests at one time!! Cool…

In this example, I want the users to see the message “Please send only e-mails with ICT related problems” while they compose an email to the ICT Helpdesk. This can be done in two ways, either from Exchange Control Panel (ECP) or Shell.

Run the following shell command to set this feature.
Set-MailBox -Identity HelpdeskICT -MailTip “Please send only e-mails with ICT related problems”

An IIS directory entry couldn’t be created. The error message is Access is denied.

Solution: Make sure that the group Exchange Trusted subsystem is member of local administrator group on all the Exchange 2007 servers.

Remove-MailboxDatabase -Identity “Mailbox Database 0075281871″
This mailbox database contains one or more mailboxes or arbitration mailboxes. To get a list of all mailboxes in this databa
se, run the command Get-Mailbox -Database <Database ID>. To get a list of all arbitration mailboxes in this database, run th
e command Get-Mailbox -Database <Database ID> -Arbitration. Before you can remove this mailbox database, you must disable, m
ove, or remove user mailboxes and move arbitration mailboxes.
    + CategoryInfo          : InvalidOperation: (Mailbox Database 0075281871:DatabaseIdParameter) [Remove-MailboxDatabase],
    AssociatedUserMailboxExistException
    + FullyQualifiedErrorId : 68BDB73C,Microsoft.Exchange.Management.SystemConfigurationTasks.RemoveMailboxDatabase

When I create an overview of all the arbitration mailboxes, they are already succesfully moved to a new created mailboxdatabase. Why I’m getting this error…?? There’s another default created mailbox, called: Discovery Search Mailbox. After moving this mailbox to another mailboxdatabase, I wass able to delete succesfully the default created mailboxdata from my Exchange 2010 environment.

Download details Update Rollup 2 for Exchange Server 2010 (KB979611)

1.) Open the Exchange Management Console
2.) Navigate to Recipient Configuration, Distribution Group
3.) Click New Dynamic Distribution Group
4.) Give up  a Name and Alias
5.) Change the Filter settings. In this example I’m using the Active Directory attribute Department
6.) Give up the Filter Condition. To see a preview of all the effected users, click Preview
7.) Click New to finish the last step

This version of Exchange is just really cool stuff!!

For more information, you can read this article on msexchangeteam.com

Server 1
Name: SRV-E2K10DC-01
OS: Microsoft Windows 2008 R2 x64
IP: 172.16.1.10
Roles: DC/DNS

Server 2
Name: SRV-E2K7-01
OS: Microsoft Windows 2008 SP2 x64
IP: 172.16.1.11
Roles: Exchange 2007 SP2 HT/CAS/MBX

Server 3
Name: SRV-E2K10-01
OS: Microsoft Windows 2008 R2 x64
IP: 172.16.1.12
Roles: Exchange 2010 HT/CAS/MBX

Domain FQDN: EXCHANGE.LOCAL
Forest Functional Level: Windows Server 2008 R2
Domain Functional Level: Windows Server 2008 R2

1.) First I’ve installed all the prerequisites for Exchange 2007 SP2 on server SRV-E2K7-01
Command: servermanagercmd -ip exchange-typical.xml
2.) Install all the prerequistes for Exchange 2010 on server SRV-E2K10-01
Command: servermanagercmd -ip exchange-typical.xml
3.) After rebooting server SRV-E2K7-01, you can install Exchange 2007 SP2
4.) After succesfully installing Exchange 2007 SP2, you can install Exchange 2010 on server SRV-E2K10-01
5.) Open the Exchange Management Console on server SRV-E2K7-01
6.) I’ve created some user account (100) and all mailbox enabled
7.) Open the Exchange Management Console on server SRV-E2K10-01
8.) As you can see, all the mailboxes are vissible!
9.) The next step is to move the mailboxes from Exchange 2007 to Exchange 2010
10.) Return to the Exchange 2010 server and open the Exchange Management Console
11.) Navigate to Recipient Configuration, Mailbox
12.) Select the mailboxes you want to migrate and right-click
13.) Choose “New Local Move Request”
14.) Select the new Mailbox Database
15.) Wait until the users are migrated to the new Mailbox Server
16.) Select all the completed move requests and select Clear Move Request

The users are now migrated to the new Exchange 2010 environment. In the next post we are going to de-install the Exchange 2007 environment.

Chapter 1: Introduction to Exchange Server 2010
    1.1 Getting Started
    1.2 What’s been removed from Exchange Server 2010?
    1.3 What’s new in Exchange Server 2010?
    1.4 Exchange Server 2010 and Active Directory
    1.5 Exchange Server coexistence
    1.6 Exchange Server 2010 Server roles
    1.7 Summary
Chapter 2: Installing Exchange Server 2010
Chapter 3: Exchange Server 2010 Coexistence
    3.1 Coexistence with Exchange Server 2003
    3.2 Installing Exchange Server 2010 in an Exchange Server 2003 environment
    3.3 Coexistence with Exchange Server 2007
    3.4 Installing Exchange Server 2010 into an Existing Exchange Server 2007 Environment
    3.5 Summary
Chapter 4: Managing Exchange Server 2010
    4.1 The Exchange Management Shell
    4.2 The Exchange Management Console
    4.3 The Exchange Control Panel (ECP)
    4.4 Role Based Access Control (RBAC)
    4.5 Archiving and Compliancy
    4.6 Summary
Chapter 5: High Availability in Exchange Server 2010
    5.1 High Availability in Exchange Server 2010
    5.2 Exchange Server Database technologies
    5.3 High Availability in Exchange Server
    5.4 High Availability on other Server Roles
    5.5 Summary

This is my Exchange 2010 environment:

Server 1 – SRV-EXDC-01
OS: Microosft Windows 2008 R2 Enterprise x64
IP: 172.16.1.10
Roles: Active Directory, DNS

Server 2 – SRV-EX10HT-01
OS: Microsoft Windows 2008 R2 Enterprise x64
IP: 172.16.1.11
Roles: Exchange 2010 HT/CAS

Server 3 – SRV-EX10MB-01
OS: Microsoft Windows 2008 R2 Enterprise x64
IP: 172.16.1.12
Roles: Exchange 2010 MBX

Server 4 – SRV-EX10MB-02
OS: Microsoft Windows 2008 R2 Enterprise x64
IP: 172.16.1.13
Roles: Exchange 2010 MBX

1.) First I’ve created 2 new mailbox database on each mailbox server.
SRV-EX10MB-01 - MD01, MD02
SRV-EX10MB-02 - MD03, MD04
2.) The next step is to create a new Database Availability Group.
Groupname: DAG01
Witness Server: SRV-EX10HT-01 (Could also be a another server, but not a member of the DAG!!)
Witness Directory: C:\FSW_DAG01
3.) After succesfully creating the DAG, we can added some mailbox servers to it
SRV-EX10MB-01 and SRV-EX10MB-02
4.) The Windows Failover Clustering feature will automatically installed on each Mailbox server
5.) Give the Database Availability Group an IP address. This can be done with the following command:
Set-DatabaseAvailabilityGroup -Identity DAG01 -DatabaseAvailabilityGroupIpAddresses 172.16.1.50
6.) The next step is to add a Mailbox Database Copy
7.) The copy of the Mailbox Database will be copied to the other mailbox server. As you can see, Mailbox Server SRV-EX10MB-02 is now also containing Mailbox Database MD01 and MD02
8.) Login through the Outlook Web App with a user in Mailbox Database MD01
9.) Disable the LAN connection on Mailbox Server SRV-EX10MB-01 (fake a failover!)
10.) You’ll now receive an error in your Outlook Web App, this is normal, because the active mailbox is unavailable!! Wait a copple of seconds and click another e-mail message! As you can see, the passive Mailbox Database copy is now become active!! cool….
11.) After enabling the LAN connection on Mailbox Server SRV-EX10MB-01, the copy status become Healthy again!
12.) You can also test the “Fail Over” manually. Right click on your Mailbox Database, choose Move Active Mailbox Databse, and select the new active Mailbox Server.

So….after all, a copple of seconds downtime for the users!

As you increase the size of mailboxes, you don’t necessarily want all the data stored locally on user machines, because it can lead to very long initial download times when users get a new machine. The data users frequently access is stored in the primary mailbox, which is ideally less than 10GB and is cached locally. Everything else is stored in the archive mailbox and available online, so it can be much larger and contain historical data. Because the archive mailbox is part of the same mailbox database, its availability is the same as the primary mailbox (it will be replicated as part of a DAG, database availability group).

Users will see their mailbox and their archive mailbox. They can drag and drop a PST file into the archive and the PST will be imported into the archive automatically. The viewing and navigation of the primary and archive mailbox is the same. If a user searches all mail items, the archive content is included. Users or administrators can set retention policies so that mail is automatically moved to the archive after a number of days, and different policies can be set on different folders.

Here are some keynotes for the archiving feature in Exchange 2010:

- Archive mailbox gets rid of PST files by giving the user an additional mailbox
- PST files are local to the user’s machine, gets corrupted easily and is hard to include the files in backup.
- Archive mailbox sits in the same mailbox database as the user’s main mailbox and can be included in the backup easily
- Archive Mailbox is available in Outlook as well as Outlook Web App (OWA), which is a huge improvement.
- Users can access their email archive irrespective of where they are
- Archive Mailbox is included as part of the Exchange Enterprise CALs and hence no extra cost is required (for those who have ECALs)
- Retention policies can be set for emails/folders in the archive mailbox
- User has the option to search for emails in archive only or both primary & archive mailbox
- Archive Quota can be set separate to the primary mailbox
- Emails in existing PSTs can be dragged into the archive mailbox very easily
- The archive and primary mailbox share the same user account
- Only one archive mailbox can be configured for a user
- Archive mailbox gets created on the same mailbox database as the primary one, which is a drawback.
- Future service packs might bring the option to create the archive mailbox in a different database
- The default quota warning for the archive mailbox is 10GB, which can be changed

How to configure a archive mailbox for a specific user:

1.) Open the Exchange Management Console
2.) Navigate to Recipient Configuration and select the specific user
3.) On the action pane, select “Enable Archive”
Note: Online archiving requires an Exchange Enterprise Client Access License (CAL)!
4.) The icon of the specific user has changed to an archive  icon.
5.) Login to the Outlook Web App with the specific user and you’ll see the archive mailbox
6.) Drag and drop some e-mail into the online archive
7.) You can change the name of the online archive by navigating to the specific user, Properties, Mailbox Features, Archive
8.) Login again to the Outlook Web App and you’ll see the new name of the archive mailbox

You can fix this issueu to put some permissions on this Address Lists. Let’s have a look on that.

1.) Open the Exchange Management Console
2.) Create a new Address List
3.) Give up the filter settings (in this example it is based on the Active Directory field “Department“)
4.) Open ADSI Edit, adsiedit.msc
5.) Open Configuration,CN=Configuration,DC=E2K10.local,CN=Services,CN=E2K10,CN=Address Lists Container,CN=All Address Lists,<your Address Lists>
6.) Open the Properties, and click the Security tab, Advanced
7.) Disable “Include inheritable permissions from this object’s parent”
8.) Click Copy
9.) Remove the Authenticated Users
10.) Make a new Security Group in your Active Directory called for example “AL_ICT_Department”
11.) Place all the users of the ICT department in this Security Group
12.) Open the security settings again and at the group AL_ICT_Department
13.) Give this group the following permissions Read, Open Address List
14.) Login with a user that is member of the AL_ICT_Department. Make sure you see the Address List
15.) Login with a user that is not a member of the AL_ICT_Department. You didn’t see the Address List now.

When you pass Exam 70-662 TS: Microsoft Exchange Server 2010, Configuring, you complete the requirements for the following certification(s):

• Microsoft Certified Technology Specialist (MCTS): MIcrososft Exchange Server 2010, Configuration

Exam 70-662 TS: Microsoft Exchange Server 2010, Configuring: counts as credit toward the following certification(s):

• Microsoft Certified IT Professional (MCITP): Enterprise Messaging Administrator 2010

     – Exchange-all.xml
     – Exchange-base.xml
     – Exchange-cadb.xml
     – Exchange-cas.xml
     – Exchange-eca.xml
     – Exchange-edge.xml
     – Exchange-hub.xml
     – Exchange-mbx.xml
     – Exchange-typical.xml
     – Exchange-um.xml

In this example we are going to prepare a Microsoft Windows 2008 SP2 server for installing the Exchange 2010 Hub Transport Role, using the XML file Exchange-hub.xml.

1.) Open the command prompt (CMD)
2.) Browse to your installation source directory
3.) Type in ServerManagerCmd -ip Exchange-Hub.xml
4.) All prerequisites will be installed now
5.) After this is finished, you can start the installation of Exchange 2010

• Total Databases
• Total Database copies
• Total Exchange 2003 / 2007 / 2010 servers
• How many Exchange server with a specific role installed
• Total user mailboxes, distribution groups, contacts, legacy mailboxes

When you open the Exchange Management Consosle, go to Microsoft Exchange, Microsoft Exchange On-Premises. 

In Exchange 2010 Release Candidate (RC), there’s a new command available to move a mailbox to another mailbox database, New-Moverequest.

In this example I’m going to move all the mailboxes, including the default arbitration mailboxes to a new mailbox database, otherwise you can not delete the default mailbox database created by Exchange!

1.) With the following command you can get a list of all the Move Requests. Get-Moverequest | fl
2.) Run the command Get-Mailbox -Database “database name” -Arbitration | ft -wrap -auto for a list of all the hidden arbitration mailboxes in the default mailbox database
3.) To move the arbitration mailbox to the new mailbox database, run the following command New-MoveRequest -Identity “SystemMailbox{e0dc1c29-89c3-4034-b678-e6c29d823ed9}” -TargetDatabase MD01
4.) After moving all the arbitraion mailboxes to the new mailbox database, run the following command Get-Moverequest | fl
5.) Before we can remove the default mailbox database, you’ve to remove all the move requests associated with the source mailbox database
6.) To get a list off all the associated move requests, run the following command Get-MoveRequest -SourceDatabase “Mailbox Database 1205181900″
7.) To remove the move requests, run the command Remove-Moverequest -<Recipient ID>
Note: For a list off all the Recipient ID’s you can run Get-Mailbox -Database “database name” -Arbitration | ft -wrap -auto
8.) After removing all the remove requests, you’re able to succesfully remove the default mailbox database

The fist step is to prepare the Schema.

1.) Open the root directory of the Exchange 2010 installation files
2.) Run the following command: .\Setup /PrepareSchema
Note: make sure you’ve SchemaAdmin rights

The next step is to prepare the Active Directory.

1.) Run the following command: .\Setup /PrepareAD /OrganizationName:<Your-Organization-Name>

The last step is to prepare the Domain.

1.) Run the following command: .\Setup /PrepareDomain
Note: make sure you’ve DomainAdmin rights

Your environment is now succesfully prepared to install Exchange 2010.

————————————————————————————
The mailbox database ‘DB01′ cannot be deleted.

DB01
Failed
Error:
This mailbox database contains one or more mailboxes or arbitration mailboxes. To get a list of all mailboxes in this database, run the command Get-Mailbox -Database <Database ID>. To get a list of all arbitration mailboxes in this database, run the command Get-Mailbox -Database <Database ID> -Arbitration. To disable a non-arbitration mailbox so that you can delete the mailbox database, run the command Disable-Mailbox <Mailbox ID>. Arbitration mailboxes should be moved to another server; run the command Move-Mailbox <Mailbox ID> -Arbitration -TargetDatabase <Database ID>.  To remove the arbitration mailbox if this is the last server in the organization, run the command Remove-Mailbox <Mailbox ID> -Arbitration -RemoveLastArbitrationMailboxAllowed.
————————————————————————————

You cannot remove the database, because there are some mailboxes in it. Oké….let’s have look what mailboxes are left in this mailbox database.

Get-Mailbox -Database DB01

As you can see, there are no mailboxes left in de mailbox database, but why we are still receiving this error!! This is the answer…….there are two hidden mailboxes left in de mailbox database, called arbitration mailboxes. With the following command you’re able to see this mailboxes

Get-Mailbox -Database DB01 -Arbitration | ft -wrap -auto

When you move these two mailboxes to another mailbox database, all the error messages are gone! So let’s do that!

Move-Mailbox “SystemMailbox{1f05a927-3be2-4fb9-aa03-b59fe3b56f4c}”  -Arbitration -TargetDatabase DB02
Move-Mailbox “SystemMailbox{e0dc1c29-89c3-4034-b678-e6c29d823ed9}”  -Arbitration -TargetDatabase DB02

 The continuous availability architecture built into Exchange 2010 provides new benefits for organizations and their messaging administrators:

• Multiple server roles can co-exist on servers that provide high availability. This enables small organizations to deploy a two-server configuration provides full redundancy of mailbox data, while also providing redundant Client Access and Hub Transport services.
• An administrator no longer needs to build a failover cluster in order to achieve high availability. Failover clusters are now created by Exchange 2010 in a way that is invisible to the administrator. Unlike previous versions of Exchange clusters which used an Exchange-provided cluster resource DLL named ExRes.dll, Exchange 2010 no longer needs or uses a cluster resource DLL. Exchange 2010 uses only a small portion of the failover cluster components, namely, its heartbeat capabilities and the cluster database, in order to provide database mobility.
• Administrators can add high availability to their Exchange 2010 environment after Exchange has been deployed, without having to uninstall Exchange and then re-deploy in a highly availability configuration.
• Exchange 2010 provides a view of the event stream that combines the events from the operating system with the events from Exchange.
• Because storage group objects no longer exist in Exchange 2010, and because mailbox databases are portable across all Exchange 2010 Mailbox servers, it is very easy to move databases when needed.