1. Install the proper operating system and name the new server with the same name as the lost server. Recovery won’t succeed if the server on which recovery is being performed doesn’t have the same name as the lost server.

2. Join the server to the same domain as the lost server.

3. Install the following 2008 R2 HotFixes

The following hotfixes are required for the Client Access server for Windows Server 2008 R2:

• Install the update described in Knowledge Base article 979099, An update is available to remove the application manifest expiry feature from AD RMS clients. Without this update, the AD RMS features may stop working.
• Install the hotfix described in Knowledge Base article 982867, WCF services that are hosted by computers together with a NLB fail in .NET Framework 3.5 SP1. For more information, see these MSDN Code Gallery pages:
  • For additional background information, see KB982867 – WCF: Enable WebHeader settings on the RST/SCT.
  • For the available downloads, see KB982867 – WCF: Enable WebHeader settings on the RST/SCT.
• Install the update described in Knowledge Base article 979744, A .NET Framework 2.0-based Multi-AppDomain application stops responding when you run the application.
• Install the update described in Knowledge Base article 983440, An ASP.NET 2.0 hotfix rollup package is available for Windows 7 and for Windows Server 2008 R2. For more information, see these MSDN Code Gallery pages:
  • For additional background information, see KB983440 – Win7 rollup package (PR for QFE 810219).
  • For the available downloads, see KB983440 – Win7 rollup package (PR for QFE 810219).
• Install the update described in Knowledge Base article 977020, FIX: An application that is based on the Microsoft .NET Framework 2.0 Service Pack 2 and that invokes a Web service call asynchronously throws an exception on a computer that is running Windows 7.

4. Set-Service NetTcpPortSharing -StartupType Automatic

5. RUN –> E:\Setup.com /m:recoverserver /InstallWindowsComponents

Outlook 2003 Service Pack 3 Clients
Issue:
During normal working hours users randomly was unable to access their mailboxes when they launched their Outlook client.

The users were receiving the following Outlook message:

“Unable to open your default e-mail folders. The Microsoft Exchange Server computer is not available. Either there are network problems or the Microsoft Exchange Server computer is down for maintenance.”
It was also reported that some users had issues expanding additional mailboxes. (Delegate Mailboxes )
The following Outlook message appeared.

Or users have issues opening Shared Calendars.

Solution:
http://support.microsoft.com/kb/2299468

With Get-ThrottlingPolicy you can see the value of RCAMaxConcurrency

(Exchange 2010 RTM default value 20) (Exchange 2010 SP1 default value 214748364)

I changed RCAMaxConcurrency to 214748364 and the problem is fixt:

Get-ThrottlingPolicy | set-ThrottlingPolicy -RCAMaxConcurrency 214748364

1. Get a SAN Certificate.

I my case I have the following URL’s registered with the certificate.
webmail.wardvissers.nl
autodiscover.wardvissers.nl
legacy.wardvissers.nl
casarray.wardvissers.local

2. Import the Certificate in to Exchange 2010. 
How to check HERE

3. Create on the Exchange 2010 Server a Client Access Array.
How you must do it I spoke it Configuring Client Access Array. I this case a used casarray.wardvissers.local for the client acces array.

4. Setting the internal & external url’s

Set-ClientAccessServer -Identity ward-ex01 -AutoDiscoverServiceInternalUri https://casarray.wardvissers.local/Autodiscover/Autodiscover.xml

Set-WebServicesVirtualDirectory -Identity “ward-ex01\EWS (Default Web Site)” -InternalUrl https://casarray.wardvissers.local/ews/exchange.asmx -ExternalUrl https:// webmail.wardvissers.nl/ews/exchange.asmx

Set-OABVirtualDirectory -Identity “ward-ex01\oab (Default Web Site)” -InternalUrl http:// casarray.wardvissers.local/oab -ExternalUrl https://webmail.wardvissers.nl/oab

Enable-OutlookAnywhere -Server ward-ex01 -ExternalHostname “webmail.wardvissers.nl” -ClientAuthenticationMethod “Basic”-SSLOffloading:$False

Set-ActiveSyncVirtualDirectory -Identity “ward-ex01\Microsoft-Server-ActiveSync (Default Web Site)” -InternalURL https://casarry.wardvissers.local/Microsoft-Server-Activesync
-ExternalURL https://webmail.wardvissers.nl/Microsoft-Server-Activesync

Set-ECPVirtualDirectory –Identity ward-ex01\ECP (default web site) -InternalURL https://casarry.wardvissers.local/ECP -ExternalURL https://webmail.wardvissers.nl/ECP

5. Configure Exchange 2010 for basic authentication

Set-OwaVirtualDirectory -id ward-ex01\* -BasicAuthentication $true -WindowsAuthentication $true -FormsAuthentication $false

set-WebServicesVirtualDirectory -Identity “ward-ex01\EWS (Default Web Site)” -WindowsAuthentication $true -BasicAuthentication $true

set-EcpVirtualdirectory –Identity ward-ex01\ECP (default web site) -BasicAuthentication $true -WindowsAuthentication $true -FormsAuthentication $false

set-OabVirtualDirectory -Identity “ward-ex01\oab (Default Web Site)” -WindowsAuthentication $true -BasicAuthentication $true

set-ActiveSyncVirtualDirectory -Identity “ward-ex01\Microsoft-Server-ActiveSync (Default Web Site)” -BasicAuthentication $true

6. Import the SAN certificate in to the TMG server.

1. Click Start –> Run –> Type MMC
2. Click File –> add remove Snap-in –> Certificates –> ADD –> Computer account-> Next –> finish-> ok
3. Click Personal –> certificates
4. Right Click certificates –> all task –> import –> next –> select the *.pfx file –> next –> Password –> next –> next –> Finish

7. Publish OWA

1. Publish Exchange Web Client Access

2. Exchange Publishing rule name: OWA 2010

3. Choose Exchange Server 2010 & Outlook Web Access

4. Next ( I have only Single TMG Server)

5. Next

6.Internal Site Name: Client Access Array name. My Case casarray.wardvissers.local

7. Public Name: webmail.wardvissers.nl

8. At this moment I have no Web Listener so we gone create them

9. Weblister Name: HTTPS

10. Next

11. I choise for All Networks (and local host) because the Server has one NIC.

12. Select the Certificate that you just imported.
 

13. Choise for LDAP (Active Directory)

14. SSO Domain name: my case wardvissers.nl (External Domain name)

15. Finish

16. Next

17. Next

18. Next

19. Finish

8. Publish Active Sync

1. Publish Exchange Web Client Access

2. Exchange Publishing rule name: Active Sync 2010

3. Exchange Server 2010 & Exchange ActiveSync

4. Next

5. Next

6. Internal Site name: CasArray name

7. Public Name: I my case webmail.wardvissers.nl

8.Choise the HTTPS web listerner

9. Next

10. Next

11. Finish

Next Time I will publish how to deploy a Legacy Exchange Server 2003 & 2007 with TMG

Microsoft provides some documentation examples of well-designed, cost-effective Exchange 2010 solutions deployed on hardware offered by some partners from Microsoft.

9000 Mailboxes in Two Sites Running Hyper-V on Dell M610 Servers, Dell EqualLogic Storage, and F5 Load Balancing Solutions

16000 Mailboxes in a Single Site Deployed on IBM and Brocade Hardware 

500 Mailboxes in a Single Site Running Hyper-V on Dell Servers

It’s really nice info to read if you designing a Exchange 2010 Solution for your company or customer.

Today the Exchange Team released Rollup 2 for Exchange Server 2010 Service Pack 1 (KB2425179). This update raises Exchange 2010 version number to 14.1.270.1.

If your upgrading from Exchange 2007 you need to implement this rollup because the bug Exchange 2007 OWA redirect bug with Exchange 2010 sp1 is fixed check: kb2458419

The List with Fixes:

983186 The mailbox alias of a user contains the "?" character unexpectedly after you run the "Enable-Mailbox" cmdlet to create a mailbox for the user in an Exchange Server 2010 environment

2295902 An excepted occurrence is not excluded from a recurring iCalendar message for an Exchange Server 2010 mailbox user

2385017 You cannot edit public folder items even though you are the owner of the items in an Exchange Server 2010 environment

2385194 You cannot connect to an Exchange Server 2010 mailbox by using a MAPI application when a Mailbox server and a Client Access server are installed on different computers

2397171 You cannot reply or forward a large email message on an Exchange Server 2010 mailbox

2403783 An incorrect label is displayed in the date field in a public folder item when you open the item by using OWA in an Exchange Server 2010 environment

2408924 The subject of an item is deleted when you use the "UploadItems" operation together with the "Update" action or the "UpdateOrCreate" action in an Exchange Server 2010 environment

2409597 You cannot open a public folder item when the default public folder database for the mailbox database is unavailable in an Exchange Server 2010 environment

2423776 The Exchange Information Store service crashes frequently during a public folder replication process on an Exchange Server 2010 public folder

2431500 You cannot connect to an Exchange Server 2010 mailbox simultaneously by using Outlook Anywhere from several Windows XP-based computers

2433642 The "FETCH (BODYSTRUCTURE)" command returns a corrupted file name of an email message attachment on an Exchange Server 2010 computer

2452075 You cannot connect to mailboxes in a recovery database on a server after you install Exchange Server 2010 SP1

2458005  The Exchange Mailbox Replication service crashes when you use the "New-MailboxImportRequest" command to import a PST file to an Exchange Server 2010 mailbox

2458419 "A temporary change has occurred that requires you to connect to a different server" error message when Exchange Server 2007 mailbox users try to access their mailboxes by using an Exchange Server 2010 Client Access server

2322161 The replay queue length on passive copies of mailbox databases in Database Availability Group continues to increase in an Exchange Server 2010 environment

982004 Exchange Server 2010 users cannot access the public folder

983492 You cannot view updated content of an Exchange Server 2010 public folder

983549 Exchange Server 2010 removes the sender’s email address from the recipient list in a redirected email message

Download the Hotfix HERE

This 300 level hands-on labs online course (including seven hands-on labs) will prepare learners with the knowledge to engage with customers to help them implement best practices for smooth Exchange 2010 upgrades and deployments. These hands-on labs online (HOLOs) are provided at no charge to Microsoft partners, and provide IT Professionals with the essential information they need to setup, deploy, and configure Microsoft Exchange Server 2010.  The course will address gaps in knowledge around topics such as new features, upgrade paths, tools and processes to support upgrade and deployment planning.

Training includes the following curriculum:

Course (Online): Using Exchange 2010 Tools to Plan a Deployment (Part 1)

Course (Online): Using Exchange Tools to Plan a Deployment (Part 2)

Course (Online): Exchange 2010 Setup, Deployment, and Server Role Configuration

Course (Online): Configuring Mail Flow and Outlook Web Access

Course (Online): Moving Mailboxes to Exchange 2010

Course (Online): Moving Other Services to Exchange 2010 (Part 1)

Course (Online): Moving Other Services to Exchange 2010 (Part 2)

Thanks to

Bryan Von Axelson

I created a little procure to test it.

1. PDA sync at first with ISA 2006 against Exchange 2007.

2. Shutdown the ISA 2006 Server

3. Starting the TMG Server

4. Checking if the PDA would sync. (The PDA should be sync with legacy.wardvissers.nl automatically )

5. Move the Mailbox to Exchange 2010 and check again if the PDA sync works.

Windows Mobile PDA (6.1).

1. Works fine

2.

3.

4. The PDA will be redirected to legacy.wardvissers.nl and pda sync works great. The User had nothing to do.

5. Moving the Mailbox to Exchange 2010 there is no problem. The user will automatically redirected from legacy.wardvissers.nl to webmail.wardvissers.nl with out any problems.

Nokia E71/E72 (Mail for Exchange Client 3.0.73)

1. Works fine

2.

3.

4. PDA don’t sync anymore. The user must change the sync url manual to legacy.wardvissers.nl than it works again.

5. Moving the Mailbox to Exchange 2010 there is no problem. If you change the url to legacy.wardvissers.nl you must change it manually back.

Nokia E71/E72 With (Road Sync 4.0/5.0)

1. Works fine

2.

3.

4. PDA don’t sync anymore. The user must change the sync url manual to legacy.wardvissers.nl than it works again.

5. Moving the Mailbox to Exchange 2010 there is no problem. If you change the url to legacy.wardvissers.nl you must change it manually back.

Conclusion

Moving PDA users to Exchange 2010 can be a pain in the ass. Best practice is create a list of all PDA users and move them first to Exchange 2010 and than all other users.

When you want to import some pst’s you need some rights from doing this. This is a one time setting.

New-ManagementRoleAssignment ?Role ?Mailbox Import Export? ?User Administrator

Name                           Role              RoleAssigneeName  RoleAssigneeType  AssignmentMethod  EffectiveUserName

—-                           —-              —————-  —————-  —————-  —————-

Mailbox Import Export-Admin… Mailbox Import… Administrator     User              Direc

Set Mailbox Language

Set-MailboxRegionalConfiguration -Identity ward -Language nl-nl -DateFormat "dd-mm-yyyy

If you want this for multiple mailboxes you case the following script

$a=get-Mailbox *
$a | Set-MailboxRegionalConfiguration -language nl-nl -DateFormat "dd-mm-yyyy

Import a mailbox

New-MailboxImportRequest -Mailbox ward -FilePath \\win701\c$\ward.pst

Remove  newmailimportRequest

Get-MailboxImportRequest -Status Completed | Remove-MailboxImportRequest

Status

Get-MailboxImportRequest | Get-MailboxImportRequestStatistics | ft TargetAlias,Percent*,BytesTransferred*

Multiple Mailboxes at the same time

Dir \\win701\c$\Exmerge-PSTS\*.pst | %{

    New-MailboxImportRequest ?Name ImportOfPst ?BatchName ImportPstFiles `

        ?Mailbox $_.BaseName ?FilePath $_.FullName

}

The property is MSExchDelegateListLink. You can check it with adsiedit.

When you open now Outlook 2010 you can now see that Wardtest is automatilly Added

And additional mailboxes is empty

When you migrating from Exchange 2007 to Exchange 2010 and upgraded the Clients to Outlook 2010
Use dis script to set the MSExchDelegateListLink object automatically. Test I first. It’s your own risk.

$a=get-MailboxPermission * | where {$_.IsInherited –eq $False –and $_.accessrights –eq “FullAccess”}
$a | remove-MailboxPermission –confirm:$false
$a | add-MailboxPermission

Save the scripts to MSExchDelegateListLink.ps1

It works great
Source

If you want a list with al the pda’s that are connected to your Exchange Organization.

You can use the following Powershell command let.
Get-Mailbox –resultsize unlimited | Get-ActiveSyncDevice | fl userdisplayname,DeviceModel,Devicetype, DeviceUserAgent > c:\pdas.txt

If your are an Exchange Admin I can recommend the following book Microsoft Exchange Server 2010 Best Practices. It covers SP1. It  contains the following Chapters.

Part I  Preparing for Exchange Server 2010

Chapter 1: Introducing Exchange Server 2010

Chapter 2: Exchange Deployment Projects

Chapter 3: Exchange Environmental Considerations

Part II  Designing Exchange Server 2010

Chapter 4: Client Access in Exchange 2010

Chapter 5: Routing and Transporting

Chapter 6: Mailbox Services

Chapter 7: Edge Transport and Messaging Security

Chapter 8: Automated Message Processing, Compliance, and Archiving

Chapter 9: Unified Messaging

Chapter 10: Federated Delegation

Chapter 11: Designing High Availability

Chapter 12: Backup, Restore, and Disaster Recovery

Chapter 13: Hardware Planning for Exchange Server 2010

Part III  Upgrading to Exchange Server 2010

Chapter 14: Upgrading from Exchange Server 2003 and Exchange Server 2007

Part IV  Deploying and Managing Exchange Server 2010

Chapter 15: Preparing for a Deploying Exchange Server 2010

Chapter 16: Managing Exchange

Chapter 17: Operating and Troubleshooting Exchange Server 2010

This book is also not a preparation guide for Exam 70-662: TS: Microsoft Exchange Server 2010, Configuring, or Exam 70-663: Pro: Designing and Deploying Messaging Solutions with Microsoft Exchange Server 2010, even though when you apply the knowledge and experience covered in this book, it will help you to pass these exams.

In SP1, this redirection is no longer silent.  When your Exchange 2007 user logs in via webmail.wardvissers.nl, they are presented with this screen:

The text reads:

A temporary change has occurred that requires you to connect to a different server.  To connect, click the button below.  For security reasons, you’ll be asked to enter your user name and password again.

Sure enough, when you click Connect, you are redirected to legacy.wardvissers.nl, where you have to re-enter your user information.
Thankfully, the same sort of thing doesn’t seem to happen with Outlook Anywhere or ActiveSync clients.
I checked the LegacyRedirectType value on my 2010 SP1 CAS boxes and they are all still set to Silent.  The issue occurs because the OWA virtual directory value for LegacyRedirectType is being ignored.  This is an extraordinarily unfortunate thing to have been introduced with SP1.   If you have a mixed Exchange 2007/2010 environment, I suggest you wait until the rollup 2 is out before deploying SP1. 

Update 15 December 2010

Update 2 for Exchange 2010 and the fix is there described 2458419 "A temporary change has occurred that requires you to connect to a different server" error message when Exchange Server 2007 mailbox users try to access their mailboxes by using an Exchange Server 2010 Client Access server

You can download the rollup HERE

For Exchange 2010 (RTM & SP1) you have the tool ExFolder to set rights on the public Folder store.

But the Exchange Team did a great job to add Public Folder Rights to the Public Folder Management Console.

When you right click on the a public folder you can set permission on two ways.

1. Right click on the public folder and choose Manage Settings

I give my self Owner rights for this little demo.

2. Select Properties from the public folder and then select the Permissions tab.

SafeSearch Enforcement. Forefront TMG can enforce blocking adult text, images and videos from search results by popular search engines. SafeSearch can be enforced on specific groups or to the entire organization.
Including non-primary URL filtering categorizations. Forefront TMG uses an algorithm to select a URL’s “primary” category from among up to four categorizations provided by Microsoft Reputation Services (MRS). In Update 1 you can control access to sites that match any of the non-primary categorizations provided by MRS. For example, a URL with a primary categorization of News can now match a rule by any of its non-primary categorizations (such as Web Mail).
Support for Exchange 2010 SP1
Bug fixes and various other improvements. For details, see http://go.microsoft.com/fwlink/?LinkId=201151.

Download

So I am very pleased with it. Last month’s I’m working a lot with Exchange 2010. I love the product. Last Friday evening I updated a customer DAG cluster to SP1. Next moth starting moving the 2000 mailboxes from Exchange 2007 tot Exchange 2010.

Some of the hotfixes would have been rolled up in a Windows update or service pack. Given that the Exchange team released SP1 earlier than what was planned and announced earlier, it did not align with some of the work with the Windows platform. As a result, some hotfixes are available from MSDN/Connect, and some require that you request them online using the links in the corresponding KBs. All these updates may become available on the Download Center, and also through Windows Update.

These hotfixes have been tested extensively as part of Exchange 2010 SP1 deployments within Microsoft and by our TAP customers. They are fully supported by Microsoft.

The TechNet article Exchange 2010 Prerequisites is updated with the hotfixes and install the prerequisites required for your server version (the hotfixes are linked to in the above table).

You can use the Install the Windows Server 2008 SP2 operating system prerequisites on a Windows 2008 R2 server. Only you have to run the following powershell command: Import-Module ServerManager

Installed Exchange 2010 SP1 on a Windows 2008 R2 Server with problems. I feels that the MMC is faster. Tomorrow upgrading a DAG/NLB cluster to Exchange 2010 SP1.

So What’s New in Exchange SP1:

New Deployment Functionality

During an Exchange 2010 SP1 installation, you can now select a new option to install the required Windows roles and features for each selected Exchange 2010 SP1 server role. For more information, see New Deployment Functionality in Exchange 2010 SP1.

Exchange ActiveSync

In Exchange 2010 SP1, you can manage Exchange ActiveSync devices using the Exchange Control Panel (ECP). Administrators can perform the following tasks:

• Manage the default access level for all mobile phones and devices.
• Set up e-mail alerts when a mobile phone or device is quarantined.
• Personalize the message that users receive when their mobile phone or device is either recognized or quarantined.
• Provide a list of quarantined mobile phones or devices.
• Create and manage Exchange ActiveSync device access rules.
• Allow or block a specific mobile phone or device for a specific user.

For every user, the administrator can perform the following tasks from the user’s property pages:

• List the mobile phones or devices for a specific user.
• Initiate remote wipes on mobile phones or devices.
• Remove old mobile phone or device partnerships.
• Create a rule for all users of a specific mobile phone or device or mobile phone type.
• Allow or block a specific mobile phone or device for the specific user.

SMS Sync

SMS Sync is a new feature in Exchange ActiveSync that works with Windows Mobile 6.1 with the Outlook Mobile Update and with Windows Mobile 6.5. SMS Sync is the ability to synchronize messages between a mobile phone or device and an Exchange 2010 Inbox. When synchronizing a Windows Mobile phone with an Exchange 2010 mailbox, users can choose to synchronize their text messages in addition to their Inbox, Calendar, Contacts, Tasks, and Notes. When synchronizing text messages, users will be able to send and receive text messages from their Inbox. This feature is dependent on the user’s mobile phones or devices supporting this feature

Reset Virtual Directory

In Exchange 2010 SP1, you can use the new Reset Client Access Virtual Directory wizard to reset one or more Client Access server virtual directories. The new wizard makes it easier to reset a Client Access server virtual directory. One reason that you might want to reset a Client Access server virtual directory is to resolve an issue related to a damaged file on a virtual directory. In addition to resetting virtual directories, the wizard creates a log file that includes the settings for each virtual directory that you choose to reset. For more information, see Reset Client Access Virtual Directories.

Exchange Store and Mailbox Database Functionality

The following is a list of new store and mailbox database functionality in Exchange 2010 SP1:

• With the New-MailboxRepairRequest cmdlet, you can detect and repair mailbox and database corruption issues.
• Store limits were increased for administrative access.
• The Database Log Growth Troubleshooter (Troubleshoot-DatabaseSpace.ps1) is a new script that allows you to control excessive log growth of mailbox databases.
• Public Folders client permissions support was added to the Exchange Management Console (EMC).

Mailbox and Recipients Functionality

The following is a list of new mailbox and recipient functionality included in Exchange 2010 SP1:

• Calendar Repair Assistant supports more scenarios than were available in Exchange 2010 RTM.
• Mailbox Assistants are now all throttle-based (changed from time-based in Exchange 2010 RTM).
• Internet calendar publishing allows users in your Exchange organization to share their Outlook calendars with a broad Internet audience.
• Importing and exporting .pst files now uses the Mailbox Replication service and doesn’t require Outlook.
• Hierarchical address book support allows you to create and configure your address lists and offline address books in a hierarchical view.
• Distribution group naming policies allow you to configure string text that will be appended or prepended to a distribution group’s name when it’s created.
• Soft-delete of mailboxes after move completion

High Availability and Site Resilience Functionality

The following is a list of new high availability and site resilience functionality included in Exchange 2010 SP1:

• Continuous replication – block mode
• Active mailbox database redistribution
• Enhanced datacenter activation coordination mode support
• New and enhanced management and monitoring scripts
• Exchange Management Console user interface enhancements
• Improvements in failover performance

Messaging Policy and Compliance Functionality

The following is a list of new messaging policy and compliance functionality included in Exchange 2010 SP1:

• Provision personal archive on a different mailbox database
• Import historical mailbox data to personal archive
• Delegate access to personal archive
• New retention policy user interface
• Support for creating retention policy tags for Calendar and Tasks default folders
• Opt-in personal tags
• Multi-Mailbox Search preview
• Annotations in Multi-Mailbox Search
• Multi-Mailbox Search data de-duplication
• WebReady Document Viewing of IRM-protected messages in Outlook Web App
• IRM in Exchange ActiveSync for protocol-level IRM
• IRM logging
• Mailbox audit logging

Technet Exchange 2010 SP1 info
Release Notes for Exchange Server 2010 SP1
What’s New in Exchange 2010 SP1
Downloads:
Microsoft Exchange Server 2010 Service Pack 1
Microsoft Exchange Server 2010 SP1 Language Pack Bundle
Exchange Server 2010 SP1 UM Language Packs
Exchange Server 2010 SP1 Help

MailTips are work with the Scenarios given below.

1. If one of the recipients is out of office.
2. When the recipient’s mailbox is full
3. Message size exceeds sender’s send limit.
4. If The Message quota exceeds of the recipient.
5. When Sending email to a large number of recipients.
6. When trying to send email to restricted recipients.
7. When a booking a room with exceeded invitees.
8. When sending to External and invalid domains.
9. When trying to send to moderated recipients.
10. Attaching more attachments than allowed.

Configuring MailTips

Gather Organization wide configuration MailTips settings.

Get-OrganizationConfig | fl *mailtips*

Enable or Disable MailTips.

You must use “Set-OrganizationConfig” CmdLet to enable or disable mailTips. Mailtips are enabled by default.

Set-OrganizationConfig -MailTipsAllTipsEnabled $true

Configure the large audience size for MailTips.

You must use “Set-OrganizationConfig” Cmdlet to configure large audience size. With a fresh Exchange Server 2010 installation it would be 25 by default. If we decrease it to 15, then Mailtip would be display to sender if sender add more than 15 recipients. See figure 3.

Set-OrganizationConfig -MailTipsLargeAudienceThreshold 15

Large Audience Threshold MailTip will display after adding more than 15 recipients . See figure 4.

Enable or disable the External Recipients MailTips

We have some embarrassing experiences of sending some internal information to external parties. However company doesn’t want to restrict sending emails to outside domains. With MailTips  at least we can give a alert to the sender before click send button. See figure 5.

Set-OrganizationConfig –MailTipsExternalRecipientsTipsEnabled $True

External Recipients MailTips displays when trying to send to an external domains. See figure 6.

Enable or disable MailTips that rely on mailbox data

Mailbox based MailTips are rely on the mailbox data. There are two Mailbox based Mailtips, The Recipient Out of Office and Mailbox Full MailTips, rely on the mailbox data.

Set-OrganizationConfig -MailTipsMailboxSourcedTipsEnabled $true

The Recipient Out of Office. You can get to know if whether the recipient is out of the office before you send the email. See figure 8.

Mailbox Full. If recipient’s Mailbox is full, you can know that before sending the email. See figure 9.

Configure Group Metrics

MailTIps relies on Group Metrics data to provide information on the the size of distribution groups and dynamic distribution groups. Exchange  server normally query a lot of LDAP requests to the Active Directory to get group membership information for each message.This could affect the the performance experienced by the users. To eliminate these issues Exchange server uses the Group Metric data. Group Metric data can be scheduled to run during office hours. You should use Set-MailboxServer CmdLet to configure Group metric Data. See figure 10.

Set-MailboxServer DAGEK10-01 GroupMetricsGenerationEnabled $true

Used this article as Source for my article.

- Use de VMXNET 3 Adapter
- Use per Disk a SCSI Controller
- Store the Log & Database files on physical Lun on a SAN
- Use the LSI LOGIC SAS controller for Windows 2008 & 2008 R2
- Use the VMware Paravirtual SCSI (PVSCSI) Controller for Every physical Raw Device Mapping (RDM).

Another TIP.  Exchange 2007 & Exchange 2010 needs a lots of Memory. When choosing the size for the OS partition, swap file need also al lot of space.

Error:
Failed to communicate with the mailbox database.

MapiExceptionLogonFailed: Unable to make connection to the server. (hr=0×80040111, ec=1010)
Diagnostic context:
    Lid: 37053   Win32Error: 0x6A6
    Lid: 23065   EcDoConnectEx called [length=48]
    Lid: 17913   EcDoConnectEx returned [ec=0x0][length=48][latency=31]
    Lid: 18969   EcDoRpcExt2 called [length=313]
    Lid: 27161   EcDoRpcExt2 returned [ec=0x3F2][length=342][latency=46]
    Lid: 41073   StoreEc: 0x3F2    
    Lid: 48243 
    Lid: 50033   StoreEc: 0x3F2    
    Lid: 1494    —- Remote Context Beg —-
    Lid: 1238    Remote Context Overflow
    Lid: 49213   StoreEc: 0x8004010F
    Lid: 48573 
    Lid: 64957   StoreEc: 0x8004010F
    Lid: 56253 
    Lid: 65085   StoreEc: 0x8004010F
    Lid: 40381 
    Lid: 56765   StoreEc: 0x8004010F
    Lid: 31229   Error: 0×0
    Lid: 19149   Error: 0×0
    Lid: 24509   Error: 0×0
    Lid: 1219    StoreEc: 0x8004010F
    Lid: 3225    StoreEc: 0x8004010F
    Lid: 60049   StoreEc: 0x8004010F
    Lid: 49469 
    Lid: 65341   StoreEc: 0x8004010F
    Lid: 56125 
    Lid: 47933   StoreEc: 0x8004010F
    Lid: 32829 
    Lid: 49213   StoreEc: 0x8004010F
    Lid: 48573 
    Lid: 64957   StoreEc: 0x8004010F
    Lid: 31229   Error: 0×0
    Lid: 19149   Error: 0×0
    Lid: 24509   Error: 0×0
    Lid: 1219    StoreEc: 0x8004010F
    Lid: 24041 
    Lid: 13488   StoreEc: 0x3F2    
    Lid: 28780 
    Lid: 20076   StoreEc: 0x3F2    
    Lid: 57713   StoreEc: 0x3F2    
    Lid: 49009   StoreEc: 0x3F2    
    Lid: 1750    —- Remote Context End —-
    Lid: 52465   StoreEc: 0x3F2    
    Lid: 60065 
    Lid: 33777   StoreEc: 0x3F2    
    Lid: 59805 
    Lid: 52209   StoreEc: 0x3F2    
    Lid: 19778 
    Lid: 27970   StoreEc: 0x3F2    
    Lid: 17730 
    Lid: 25922   StoreEc: 0x3F2    

Exchange Management Shell command attempted:
‘wardvissers.local/wardvissers/wardtest2′ | New-MoveRequest -TargetDatabase ‘MailStore II’

Elapsed Time: 00:00:01

Solution:

I backup the AD with Windows Backup for sure.

Then I suspend and dismounted every mailbox database.

I opened ADSIEDIT.MSC to check the value of HomeMDB and homeMTA:

Go to:
CN=Configuration->CN=Services->CN=Microsoft Exchange->CN=wardvissers->CN=Administrative Groups->CN=Exchange Administrative Group (FYDIBOHF23SPDLT)->CN=Servers->CN=DAGEK10-01->CN=Microsoft System Attendant

The value by my mailbox server looks a bid strange:
HomeMDB: CN=InformationStore,CN=DAGEK10-02,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=wardvissers,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=wardvissers,DC=local

HomeMTA: CN=Microsoft MTA,CN=DAGEK10-01,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=wardvissers,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=wardvissers,DC=local

Clear the Value bij HomeMDB & HomeMTA like the picture below.

Important:
Clear the value by every mailbox server if you have a dag cluster

Restarted the Microsoft Exchange System Attendant Service on every mailbox server.

Mounted & Resuming the mailbox database. Now the users could login again in OWA .

Well, let us first list the directories that are used in the Exchange web service:

EWS is used for OOF, Scheduling assistance and free+busy Lookup.
OAB provides offline address book download services for client.
Autodiscover is used to provide users with autodiscover service.
EAS provides ActiveSync services to Windows Mobile based devices.
OWA provides outlook web access for users.
ECP provides Exchange control panel feature for Exchange 2010 users only.

Issues that might be resolved using the troubleshooting steps here:

You cannot set the OOF using outlook client, you receive the server not available error.
You cannot view free/busy information for other users.
You cannot use scheduling assistance, also you might receive not free/busy information data retrieved.
You cannot download Offline Address book errors.
You cannot use autodiscover externally.
Certificate mismatch error in autodiscover, users prompted to trust certificate in outlook 2007/2010.

First let us start by settings the right virtual directory configuration required for Exchange 2010 to work correctly:
Configure External and Internal URLs for OWS, ref: http://technet.microsoft.com/en-us/library/bb310763.aspx

You have to configure the internal URL to be the server name. In case you have multiple cas/hub servers configured in a NLB then can use the nlb cluster name for the internal url. 
External URL will be the URL used by users to access webmail e.g. https://webmail.wardvissers.nl/owa 

Configure the autodiscover internal URL, ref: http://technet.microsoft.com/en-us/library/bb201695.aspx

You will use the powershell cmdlet : Set-ClientAccessServer –Identity <CAS Server Name> -AutoDiscoverServiceInternalUri: <Internal URL>, this FQDN must match the URL included in the certificate. If you have NLB cluster then you put the internal name here like nlbek10.wardvissers.local

If you cannot use autodiscover.wardvissers.nl internally (you have a domain name of domain.local and you must use it), you will get a certificate miss match error, you will have to include the internal name in the SAN certificate if you purchase an external SAN certificate. 

You cannot set autodiscover external URL since outlook will try to access https://autodiscover.wardvissers.nl/autodiscover/autodiscover.xml, this behavior is by design and cannot be changed.

Best Practice: Use SAN Certificates

Depending on how you configure the service names in your Exchange deployment, your Exchange server may require a certificate that can represent multiple domain names. Although a wildcard certificate, such as one for *.wardvissers.nl, can resolve this problem, many customers are uncomfortable with the security implications of maintaining a certificate that can be used for any sub-domain. A more secure alternative is to list each of the required domains as SANs in the certificate. By default, this approach is used when certificate requests are generated by Exchange.

Best Practice: Use the Exchange Certificate Wizard to Request Certificates

There are many services in Exchange that use certificates. A common error when requesting certificates is to make the request without including the correct set of service names. The certificate request wizard in the Exchange Management Console will help you include the correct list of names in the certificate request. The wizard lets you specify which services the certificate has to work with and, based on the services selected, includes the names that you must have in the certificate so that it can be used with those services. Run the certificate wizard when you’ve deployed your initial set of Exchange 2010 servers and determined which host names to use for the different services for your deployment.

Which Names you must include when you use a third party SAN certificate, ref http://technet.microsoft.com/en-us/library/dd351044.aspx:
External:
webmail.wardvissers.nl
autodiscover.wardvissers.nl
legacy.wardvissers.nl (If you migrating from 2003 to 2010)
Internal:
autodiscover.wardvissers.local
legacy.wardvissers.local
nlbek10.wardvissers.local(Internal NLB CAS/HUB Cluster)
casarray.wardvissers.local(I use this address for the casarray. It has the same ip as the nlbek10)

When you try to delete the default database you will get this message:

The Database is not empty, even though it does look empty if you do a get-mailbox for the specific database:

get-mailbox -Database “Mailbox Database 1905367170″

There is a switch that you should use if you want to see all mailboxes, even the “hidden” Arbitration mailboxes:

get-mailbox -Database “Mailbox Database 1905367170″ –Arbitration

This gives a different result.

As you can se the database is n’t as empty as we first thought. To move these mailboxes to the new database you can easily pipe the result of the get-mailbox command and create new move requests for all Arbitration mailboxes:

get-mailbox -Database “Mailbox Database 1905367170″ -Arbitration | New-MoveRequest –TargetDatabase “MailboxDatabase1″

Source: msundis.wordpress.com

Configuration:

Server 1 – HYPERVDC-01
OS: Microsoft Windows 2008 R2 Standard x64
IP: 192.168.150.90
Roles: Active Directory / Hyper-V

Server 2 – CHEK10-01
OS: Microsoft Windows 2008 R2 Standard x64
IP: 192.168.150.91
Roles: Exchange 2010 HT / CAS

Server 3 – CHEK10-02
OS: Microsoft Windows 2008 R2 Standard x64
IP: 192.168.150.92
Roles: Exchange 2010 HT / CAS

Server 4 – DAGEK10-01
OS: Microsoft Windows 2008 R2 Enterprise x64
IP: 192.168.150.93
Roles: Exchange 2010 MBX

Server 5 – DAGEK10-02
OS: Microsoft Windows 2008 R2 Enterprise x64
IP: 192.168.150.94
Roles: Exchange 2010 MBX

Creating the DAG

Groupname: DAG01
Witness Server: CHKEK10-01 (Microsoft says use one of the CAS or Hub Servers. You cannot use a DAG Server! If you want use a non Exchange 2010 server you must at the Exchange Trusted Subsystem group at the local administrators group.
Witness Directory: C:\DAG01

Add a MB server to a DAG

Setting a IP address on a Database Availability Group

With the following command you can set the DAG Database Availability Group an IP address. Set-DatabaseAvailabilityGroup -Identity DAG01 -DatabaseAvailabilityGroupIpAddresses 192.168.150.96

KB 982639 lists all the fixes included in this rollup. Here are some of the product improvements and critical bug fixes we’d like to call out starting with 5 improvements we made to prevent crashes in very unique scenarios.

• KB 980852 The RpcClientAccess process on an Exchange Server 2010 server crashes when you access a mailbox by using a MAPI application
• KB 979801 An error message is generated in Exchange Server 2010 when you use Exchange Troubleshooting Assistant
• KB 980364 The Exchange Transport service on an Exchange Server 2010 server crashes when a certain message is processed
• KB 980353 A MAPI application that is used to access Exchange Server 2010 mailboxes crashes when the application accesses an address book
• KB 979790 An IMAP4 client crashes when accessing an Exchange Server 2010 mailbox

We corrected a few replication issues some of you encountered.

• KB 980149 The Add-MailboxDatabaseCopy command fails when it is used to add a database copy to a Database Availability Group in an Exchange Server 2010 environment
• KB 981961 Event ID 4033 is logged and the Free/Busy replication from an Exchange Server 2003 server to an Exchange Server 2010 server fails
• KB 979921 You cannot replicate a public folder from one Microsoft Exchange Server 2010 server to another, and Event ID 3079 is logged on the target server

Important:
Microsoft Update does not detect Update rollups on Exchange Server 2010 Mailbox servers that are part of a database availability group (DAG).

Download Rollup 4 for Exchange 2010 HERE