Exchange Tools

Here I’ll share some free tools that can help simplify Microsoft Exchange deployment, troubleshooting, and administration. Some of the tools are simple—but still convenient—whereas others provide some powerful functionality.

There are some tools you can use during deployment to ease the process and reduce issues in the future, tools you can use for troubleshooting to reduce down-times, and tools you can use during day-to-day administration to monitor server health and perform tasks.

Microsoft Exchange Server Deployment Assistant

Microsoft’s Exchange Server Deployment Assistant is an online tool that produces a custom step-by-step checklist you can utilize during a server installation or upgrade. It first asks you questions about your current and desired deployment environment, such as the deployment type (on-premise, cloud, or hybrid), migration questions, desired features/functionality, and other miscellaneous caveats that impact the installation or upgrade.

Microsoft Remote Connectivity Analyzer

Microsoft’s Remote Connectivity Analyzer is a website with many tools to help test and troubleshoot connectively of Exchange servers, Outlook, Lync, OCS, Office 365, and POP, IMAP, and STMP email. Plus it offers downloadable Connectivity Analyzer Tools for local testing and a message header analyzer.

PFDAVAdmin and ExFolders
These are tools that enable you to perform tasks on Exchange public folders and mailboxes, such as checking or changing permissions. It can also connect to mailboxes, check the contents, and generate reports. PFDAVAdmin is for Exchange 2000, 2003, and 2007 and ExFolders is the updated version for Exchange 2007 and 2010 SP1 and later.

Jetstress

The Jetstress tool simulates disk I/O load on your server, allowing you to specify the amount of simulated Exchange users and profiles. This can help you verify the performance and stability of your server before installing Exchange and putting it into production-use.

Exchange Server Role Requirements Calculators

These are calculator tools that give sizing recommendations for your particular Exchange server roles for both client access and mailbox. The 2010 version is focused on mailbox calculations while the 2013 version includes recommendations on sizing Client Access servers too.

Exchange Environment Report

This Exchange Environment Report tool is from Steve Goodman and is a PowerShell script that generates an automatic overview of your Exchange environment. It supports Exchange 2003, 2007, 2010 and 2013 servers and database availability groups. It reports the number of and details about the servers, mailboxes, roles, and versions. It also gives you useful status on the Database Availability Groups (DAG) and non-DAG databases.

Exchange Reports

Exchange Reports offers reports on overall information about your Exchange Environment, supporting Exchange 2010 & Exchange 2013. You can keep an eye on configuration changes and status with Group Reports, Single Group Information, Mailbox Report, Single Mailbox Information, Message Tracking, and Environment Report.

The program doesn’t require any installation, but requires .Net 4.0, Powershell 2.0, and Remote Powershell access to the Exchange Server. Reports can be saved in history and also exported to Excel.

Microsoft Exchange Server MAPI Editor (MFCMAPI)

Microsoft’s Microsoft Exchange Server MAPI Editor (MFCMAPI) tool provides access to MAPI stores, useful when troubleshooting Exchange and Outlook issues, which can serve as a replacement to the old Microsoft Exchange Server Information Store Viewer. You can open and navigate through the message stores that are exposed through MAPI.

Free Exchange Monitor

The Free Exchange Monitor from SolarWinds supports Microsoft Exchange Server 2000 and 2003. It keeps tabs on the Exchange server stats, services, mail queue sizes, and host server health. In addition to notifying you of outages it can be useful in troubleshooting Exchange server problems and even help with pro-active monitoring, for instance detecting growing mail queues that can indicate bigger issues like transport failures, Internet connection failures, and virus activity.

Free Exchange Monitoring

This is another monitoring application, but from ManageEngine and supports Exchange Server 2003, 2007, 2010, and 2013. It gives stats on server health and Exchange services. It also provides details on the client access server, transport, Active Sync counters, and delivery aspects. You can generate real-time performance reports to be downloaded or emailed in PDF format.

Exclaimer Outlook Photos

Exclaimer Outlook Photos can help you import staff photos into the Active Directory so they’ll show up in the Outlook People Pane, SharePoint profile, and on Microsoft Lync. It can auto-match pictures from a batch to names or other data in Active Directory, and even automatically crop and center the photos as well.

Certificate Manager for Exchange 2007

Exchange 2007 enables SSL within IIS by default, but creating and managing SSL certificates via PowerShell commands can be confusing. However, the Certificate Manager for Exchange 2007 from U-BTech eases the process with a GUI.

You can generate an Exchange 2007 Certificate Signing Request and process the Certificate Authority and enable certificates for Exchange 2007 Services (POP, IMAP, SMTP, IIS, UM). Plus you can include additional subject names in a single certificate. It supports import and exporting as well.

Exchange PST Capture

Exchange PST Capture from Microsoft will search your network for PST files and then import those files to mailboxes in your organization. It supports both on-premises Exchange Server 2010 and 2013 and Exchange Online. This tool can help, for instance, during the initial deployment of an Exchange Server, to move local Outlook data files into the Exchange Server.

LINK

What is the best way to migrate PDA’s or Tablets from a legacy version of Exchange to Exchange 2010.

Microsoft released November 2010 a great document: Publishing Exchange Server 2010 with Forefront Unified Access Gateway 2010 and Forefront Threat Management Gateway 2010.

One thing that I misted in that document: What is the best way to migrate PDA’s or Tablets from a legacy version of Exchange to Exchange 2010.

In most cases you wil use TMG als a firewall. Between the Internet and your internal Network.

Some weeks ago I did a Exchange 2010 migration en I don’t wanted a big bang scenario.

But I had the all the sort of phone’s that are on the marked today (Iphone, Android, Windows Phone 7.5 and some Windows Mobile phones and all so Ipad’s)

The First thing what is asked my self when design the new infrastructure.

Domain Joining Forefront TMG or Leaving in a Workgroup

In most organizations, the decision whether to domain join the server hosting Forefront TMG your production domain may be one of the most important parts of the deployment.

Forefront TMG deployments are more complex to discuss because Forefront TMG is considered a firewall and can protect the network edge. Domain joining Forefront TMG offers many advantages: it allows certificate based authentication to be used at Forefront TMG, using Kerberos Constrained Delegation to communicate to Exchange; it allows easy use of Active Directory groups and user objects in publishing rules to restrict access; and it provides other benefits. If your are not sure to domain join Forefront TMG, see Debunking the Myth that the ISA Firewall Should Not be a Domain Member.

I thinks that the best practice is to domain join TMG. Because is makes your live a lot easier.

First I created a Exchange 2010 group in the Active Directory.

Second you make the Exchange 2010 group available in TMG

Third you make four rules 2 for Exchange 2010 (OWA & ActiveSync) and 2 for your legacy server of servers (OWA & ActiveSync)

Fourth makes sure that the Exchange 2010 rules are above the legacy rules.

Fith: You change on the Exchange 2010 rules the all authenticated users to Exchange 2010. (After the migration you delete the legacy rules and change on the 2010 rules the Exchange 2010 back to all authenticated users).

pdasync2010pic2

Sixth: When you do a mailbox move you puth the user in de Exchange 2010 group.
Why you thing. When the user is in the Exchange 2010 group the PDA wil use the Exchange 2010 rule. When there user is not in the Exchange 2010 group the legacy rule will do the trick.

I migrated at this way about 300 users with random pda’s and tablets with no downtime at all Knipogende emoticon

Screenshot from the TMG rules.
 pdasync2010pic1

mail-enabled public folders stopped working after installing Exchange 2010 in existing Exchange 2003 or 2007 environment

I recently came across the following issue while performing an Exchange 2007 to Exchange 2010 migration for a company that still heavily utilised mail-enabled public folders. The client’s Exchange environment was quite old and had been previously migrated from Exchange 5.5 to 2003 and hadn’t been properly decommissioned with the original move to 2007, but that’s another story!

Issue

The issue I had was that once I moved all receive connectors to the new Exchange 2010 server, emails sent to any of the mail-enabled public folders (which were still being replicated between the 2 servers) was being rejected with the following NDR:

#< #5.2.0 smtp;554 5.2.0 STOREDRV.Deliver.Exception:ObjectNotFoundException; Failed to process message due to a permanent exception with message The Active Directory user wasn’t found. ObjectNotFoundException: The Active Directory user wasn’t found.> #SMTP#

The following error was found in Event Viewer:

Log Name: Application
Source: MSExchange Store Driver
Date: 7/09/2010 2:00:02 AM
Event ID: 1020
Task Category: MSExchangeStoreDriver
Level: Error
Keywords: Classic
User: N/A
Computer: server@domain
Description:
The store driver couldn’t deliver the public folder replication message “Folder Content (PublicFolderDatabase@domain)” because the following error occurred: The Active Directory user wasn’t found.

Solution

Given this Exchange environment was originally running versions prior to Exchange 2007, the legacy Administrative Group and all its empty subcontainers still existed. An explanation from the Microsoft Exchange Team of why this issue occurs can be found here: http://msexchangeteam.com/archive/2010/05/05/454821.aspx

The solution to this issue was to delete the empty Servers container from the legacy Administrative Group.

Using ADSIEdit.msc, connect to a domain controller and navigate to:

CN=Configuration , CN=Services, CN=Microsoft Exchange, CN=[ExchangeOrganisationName], CN=Administrative Groups, CN=[LegacyAdministrativeGroupName], CN=Servers.

Right click the Servers container and select Delete

Click Yes

Restart the Microsoft Exchange Active Directory Topology Service and the Microsoft Exchange Information Store on both the Exchange 2007 & Exchange 2010 Servers

Windows Phone app for the Exchange Team Blog

The Exchange Team Blog” app for your Windows Phone. You can download it from here or directly from the Marketplace on your Windows Phone.

The app allows you to read our blog posts on the go. Some notable features are:

  • Favorite posts you love and refer them quickly
  • Follow our tweets from the same app
  • Quickly filter and read posts by tags/categories
  • Send us your suggestions
  • Share posts with your social networks

Here are some screenshots:

Source: The Exchange Team Blog

Migrating to Exchange 2010 & PDA Sync Issues

Some day’s ago I was testing some PDA’s Windows Mobile and Nokia’s for a Exchange Migration to Exchange 2010.

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.

The security certificate on the server is invalid. Contact your Exchange Server administrator or ISP to install a valid certificate on the server. Support Code: 80072F0D or 0x80072f0d

I had some Windows Mobile device that did not sync anymore. I changed the Certificates on Exchange 2007 and ISA 2006 Servers.

After some investing. The problem was I was missing the GlobalSign Domain Validation CA certificate

image 

After creating the cer file and installed on my PDA active sync works again.

Source:
http://support.microsoft.com/kb/927465

http://support.microsoft.com/kb/915438

Exchange Tools

Microsoft Exchange Best Practices Analyzer v2.8

De Microsoft Exchange Best Practices Analyzer is bedoeld voor beheerders die willen weten hoe de algehele gezondheid van hun Exchange-servers is. De tool scant Exchange servers en identificeert items die niet in overeenstemming zijn met Microsoft best practices

Microsoft Exchange Server User Monitor

Gebruik de Microsoft Exchange Server User Monitor voor het verzamelen van real-time gegevens voor een beter inzicht in huidige omgeving waar de exchange server draait. Hier mee wordt inzichtelijk gemaakt plannen voor nu en in de toekomst. Beheerders kunnen verschillende objecten, waaronder IP-adressen, versies en modi van Microsoft Office Outlook en hulpbronnen zoals CPU-gebruik, server-side-processor latency, en de totale latentietijd voor netwerk-en verwerking. Ondersteund Microsoft Exchange Server 2000, 2003 en 2007.

Microsoft Exchange Troubleshooting Assistant v1.1

De Microsoft Exchange Troubleshooting Assistant kan helpen om de oorzaak van de slechte prestaties, mail en database mounting problemen op computers met Microsoft Exchange Server. De tool automatiseert gespecialiseerde stappen voor geïdentificeerde symptomen.

Microsoft Exchange Server Information Store Viewer (MDBVU32)

Gebruik Information Store Viewer (ook wel MDBVu32) te bekijken of informatie over een gebruiker de boodschap van de opslag van bestanden, die bestaat uit de prive-gegevens opslaan, het bestand met persoonlijke mappen (. PST), het publiek te slaan en het bestand met off line mappen (. Ost) . De Information Store Viewer toont de eigenschappen die beschikbaar zijn voor elk bericht, hoe u ze kunt gebruiken, en in welk formaat ze verschijnen.

Microsoft Exchange Server SMTPDiag Tool

SmtpDiag is een hulpmiddel voor het oplossen van problemen. Het is ontworpen om direct op een Windows server met IIS / SMTP-service  draait of op een server waar Exchange is  geïnstalleerd.  Het maakt gebruik van dezelfde API’s als Windows en Exchange om de configuratie te diagnosticeren en connectie problemen met SMTP-en DNS op te lossen.

Microsoft Exchange Server Mailbox Merge Wizard (ExMerge)

Exporteren van  gegevens uit mailboxen vanaf een Exchange-server en vervolgens de gegevens weer importeren in mailboxen op dezelfde of andere Exchange-server.

Microsoft Exchange Server Outlook Web Access Web Administration

De Outlook Web Access (OWA) administratie tool biedt een web-based gebruikersinterface aan voor alle beheerders om OWA instellingen te fijne tunen.

Offline Defragmentatie Exchange Database in Exchange 2003 & Exchange 2007

Een Exchange omgeving dient jaarlijks 1 of 2 een offline defragmentatie van een Exchange database gedaan te worden.

Hier onder staan een aantal stappen om dit op een juiste manier te doen.

Waar moet je allemaal op controleren:

– Zorg dat je ongeveer 130-150% vrij ruimte uit om de database te defragmenteren.
– De store’s zijn ge-unmount
– MSexchangeIs service actief is alleen voor Integerity Check.

Integerity Check
Mailbox: eseutil.exe /G  D:\Exchsvr\Data\mb01.edb
Public Folder: eseutil.exe /G  D:\Exchsvr\Data\mb01.edb 

Checksum test
Mailbox: eseutil.exe /K D:\Exchsvr\Data\mb01.edb 
Public Folder: eseutil.exe /K D:\Exchsvr\Data\mb01.edb 

Defragmentatie
Mailbox: eseutil.exe /D  D:\Exchsvr\Data\mb01.edb  D:\temp\tmp_mb01.edb
Public Folder: eseutil.exe /D  D:\Exchsvr\Data\mb01.edb  D:\temp\tmp_mb01.edb

e2k7defrag
Paar Interessante linkjes met extra Info:

Link 1 Link 2 Link 3 Link 4 Link 5

Anonymous user toevoegen in Exchange 2003 & Outlook 2003

Download PFDAdadmin
http://www.microsoft.com/downloads/details.aspx?familyid=635be792-d8ad-49e3-ada4-e2422c0ab424&displaylang=en

Start PFDAVAdmin
clip_image002
Kies voor File  Connect
Vul hier de volgende gegevens is. Ben je geen Exchange Admin vul hier dan als login gegevens de gegevens in van de gebruiker dan werkt het ook.
clip_image004

clip_image006
Klik met rechter muis knop op http://…..
clip_image008

Kies voor Propagete Folder ACEs

clip_image010
Vink beide aan (NT AutorityAnonymous Logon & Everyone ) en klik vervolgens op OK.
clip_image012

Klik met rechter muis knop vervolgens nog maals op http://…. met
clip_image008[1]
Kies voor Check DACL State
clip_image014
Klik op Yes
clip_image016

Nu is alles prima en is anoniem success vol toegevoegd.