Effective tips to troubleshoot MS Exchange Server Performance – A Quick Guide

Is your Exchange server running too slow to execute potential tasks with accuracy? Are you facing problems with your Exchange server?
Troubleshooting the performance of Microsoft Exchange Server- an integral messaging and communication platform that allows people to collaborate via email, is extremely crucial especially when you know the underlying server is unable to achieve the desired goals for an organization as a whole.
This blog aims at educating readers about some of the things that significantly leave a considerable impact on the Exchange server performance and the effective troubleshooting tips to tune the server while allowing it to make use of minimum system resources including memory, storage capacity, CPU performance etc.

1) Perform Disk Partition Alignment to enhance storage performance 

Microsoft Exchange server takes over the disk resources while specific operations are going on. Also, the latest hard drives available in the market typically make use of 4 kilo byte sectors instead of the traditional 512 byte sectors that were used in old hard drives. Hence, in order to ensure that the physical space on the hard drive is not wasted and rather used in an efficient way, disk partition alignment can be done to tune the performance of the MS Exchange server.

Usually, a physical disk maintains sixty-four sector in one track and thus the Windows operating system always creates the partition beginning from the 64th sector. However, in such a scenario, misalignment is encountered with the underlying physical disk and hence to ensure that proper disk alignment is done, Microsoft provides user with an inbuilt utility in its Windows Server 2003 SP1 Support Tools. This utility possesses the ability to set the starting offset in the MBR – master boot record for better alignment and in order to track it at the same time. Ultimately, the storage performance of the disk is maximized in the whole process.

2) Get Rid of Useless Mailbox Items

When your exchange databases are overburdened with worthless chunks of information that you don’t need for future reference, it’s time to get rid of unused email items or mailboxes. This not only removes all the unessential clutter flooded in your mailbox but also improves the performance of your exchange server by freeing up the storage space for new messages.

3) Carry out Public Folder Indexing for fast data access 

Indexing public folders in an Exchange server is beneficial for allowing users to quickly search for the specific pieces of information across a public folder store without any hassle. The performance of an Exchange server largely depends on how fast the data can be accessed by the users.

But before the public folder indexing is done, it is important to ensure that there is enough capacity in terms of storage space (both RAM and ROM) for accommodating the public folder index which takes near about 20% of the size of the public folder store in the MS Exchange server.

4) Schedule the maintenance of your Exchange database

Often, when databases are not properly maintained, they get corrupted or damaged due to adverse situations or unavoidable circumstances. In such a scenario, reliable third party Exchange Server recovery tool may help to recover mailbox items stored in exchange database along with the content via standard scan and advanced scan modes.

Also, it is extremely essential to run regular maintenance tasks via scheduling the maintenance cycle of the database on a nightly basis in Exchange server 2003 after specifying the allotted time. While creating the database maintenance schedule, it is important to note that the online defragmentation process takes time even after the end of the maintenance cycle.

The Final Verdict

While the MS Exchange is largely perceived as a robust platform for both desktop and mobile users, it becomes a pre-requisite to pay attention to remote data accessibility at the same time. However, the enhanced productivity of an exchange server solely depends on how fast the communication is taking place along with zero downtime, no server shutdowns and the ability to support data storage.
The troubleshooting tips as explained could help you in boosting the performance of your Exchange server. However, if you don’t get desired results from the native tools and procedures, there are alternate solutions to improve the Exchange Server performance and one such solution is Kernel for Exchange Server. The utility not just facilitates extraction of information from both online and offline exchange database files but also helps in migrating the data from one server to another without incurring any significant losses. The trial version of the software is available for free download. https://www.kerneldatarecovery.com/exchange-server-recovery.html . To test the features and download the demo for a limited period of time, please contact our technical experts for assistance.

Exchange Shell Commands / cmdlets - Useful Exchange cmdlets (Part 6)

Exchange Shell cmdlets Part 6

RSG Dismount removal :

dismount-database " ServerName\StorageGroupName\DatabaseName \mdb a" -confirm:$false

dismount-database " ServerName\StorageGroupName\DatabaseName " -confirm:$false

remove-mailboxdatabase " ServerName\StorageGroupName\DatabaseName " -confirm:$false

remove-storagegroup " ServerName\StorageGroupName “  -confirm:$false

If we are getting errors while dismounting the RSG DB, we can try this.

Dismount-Database -Identity "ServerName\StorageGroupName\DatabaseName" -ErrorAction: SilentlyContinue

To Restore Mailbox :

Restore-Mailbox –RSGMailbox “Test User 1” -RSGDatabase “servername\RSG name\database name” –Identity “Test User 2” –TargetFolder “Test User 1 Recovered data”

To Set Mailbox Quota :

Set-Mailbox -Identity jsmith@company.com -IssueWarningQuota 209715200 -ProhibitSendQuota 262144000 -ProhibitSendReceiveQuota 293601280 -UseDatabaseQuotaDefaults $false

get-content size.txt | Set-Mailbox -ProhibitSendQuota 512000 -UseDatabaseQuotaDefaults $false

(Note : jsmith@company.com (user’s Email ID) and 209715200 , 293601280 , 293601280 (Size in KBs))

DL is not showing in GAL (Solved)

If DL is not showing in GAL :

In your office network GAL Contains all the user's email IDs, contacts, DLs in it. GAL means Global Address Book. but in some cases DL will not showing in GAL. It Makes IT Admins restless.

Here is the simple solution for DL not showing in GAL

Open ADSIedit -> Select

ShowInAddressBook

Change the Value :

CN=Default Global Address list,CN=All Global Address Lists,CN=Address Lists Container,CN=Company name,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=Swk,DC=pri

(Note: Highlighted thing will be changed appropriate to your Exchange environment)

Exchange Shell Commands / cmdlets - Useful Exchange cmdlets (Part 5)

Exchange Shell cmdlets

Script for Mailbox Movement :

$AdminSessionADSettings.ViewEntireForest=$true

Get-Mailbox -ResultSize Unlimited | where {$_.Database -eq "Database Path"}

Get-MailboxDatabase " Database Path " | Get-MailboxStatistics | ft DisplayName, LastLoggedOnUserAccount, ServerName, DatabaseName, ItemCount, TotalItemSize

Get-Content 1.TXT | Move-Mailbox -TargetDatabase ‘Database Path’  -BadItemLimit 100  -maxthreads 6 >>.\1_out.txt

Points to note:

Ensure the log drive is not running out of disc space

Dont delete the database without ensuring, no mailboxes reside in it



Public Folder Access :

Get-PublicFolderClientPermission -Identity "\NAME OF PF" | fl

Install Exchange Server 2010 on Windows Server 2008 R2

Installing Exchange 2010 on Windows Server 2008 R2. I would like to install the Exchange 2010 Sp2 in a Environment where Exchange 2003 Server is already there. Its as similar . where we need to prepare the legacy Exchange permission to get that installed and working properly.

Follow the instructions to install Exchange Server 2010: 

Step 1.

I have installed Service pack 1 on Windows Server 2008 R2 where I can overcome without installing hotfixes for Exchange 2010. Prerequisites Differs with the operating Systems.

For other Versions follow this link http://technet.microsoft.com/en-us/library/bb691354.aspx

Step 2.  

Download and Install “Microsoft Filter Pack” (64bit Version)

http://www.microsoft.com/en-in/download/details.aspx?id=17062 

Step 3. 

On the Start menu, navigate to All Programs > Accessories > Windows PowerShell. Open an elevated Windows PowerShell console (Right Click – Run as administrator), and run the following command.

     Import-Module ServerManager




And Running this command for typical installation where all the roles will be installed HUB , CAS and Mailbox Servers

Add-WindowsFeature NET-Framework,RSAT-ADDS,Web-Server,Web-Basic-Auth,Web-Windows-Auth,Web-Metabase,Web-Net-Ext,Web-Lgcy-Mgmt-Console,WAS-Process-Model,RSAT-Web-Server,Web-ISAPI-Ext,Web-Digest-Auth,Web-Dyn-Compression,NET-HTTP-Activation,Web-Asp-Net,Web-Client-Auth,Web-Dir-Browsing,Web-Http-Errors,Web-Http-Logging,Web-Http-Redirect,Web-Http-Tracing,Web-ISAPI-Filter,Web-Request-Monitor,Web-Static-Content,Web-WMI,RPC-Over-HTTP-Proxy -Restart




Step 4.

Reboot the Server.

Now Prerequisites Installed successfully.
  
Step 5.
  

Now open Command Prompt "Browse the Command prompt into the setup location"

 and Run

setup /PrepareLegacyExchangePermissions

or

setup /pl

We run this as we prepare the legacy (Exchange 2003) Server permissions,

Running this command won’t harm your environment .

Befor Running this command make sure your Domain Function Level and Forest Functional level in Windows Server 2003 is in native mode and your Exchange 2003 is in native mode,

Otherwise , It won’t allow you to install Exchange 2010.

 

Step 6.

 

Preparing the Schema

Setup.com /PrepareSchema 

 

Step 7.

Preparing Active Directory

Setup.com /preparead /OrganizationName:"First Organization"

This Switch can be removed if you have an Exchange Server already in your Organization

/OrganizationName:"First Organization"

Or if you want to change the organization name . you can use this switch

Step 8.

Now prepare the domain

Setup.com /Preparedomain

If you have multiple domains run

Setup.com /preparealldomains







Step 9.

Now Run the Setup.

Step 10.

Choose Typical to Install HUB,CAS and Mailbox

Give a Check mark for Automatically install Windows Server roles.

Step 11.

If this is my internet facing server , Give the external domain name

Step 12.

If Exchange 2003 Exists in your Environment , you will get this option to configure mail flow between these Servers.

Step 13.

Now Setup will Run for some time.

 Step 14.

 Reboot your Server.


                    Finally Microsoft Exchange Server 2010 installed successfully. 




 




 

 

Exchange Shell Commands / cmdlets - Useful Exchange cmdlets (Part 2)

Exchange Shell Commands - Part 2

To give full mailbox permission :

get-user -identity “Source mailbox” | Add-MailboxPermission -User ”User’s Mailbox who need to access” -AccessRights ‘FullAccess’

To Get All the Active nodes in Cluster :

Get-WMIObject Win32_ComputerSystem -ComputerName servername

To Get the Transport Server Configuration :

get-transportconfig

Exchange Shell Commands / cmdlets - Useful Exchange cmdlets (Part 1)

Exchange Commands (Part 1)

To Create QBDL : 

(Dynamic Distribution Group)

• New-DynamicDistributionGroup -Name "<<DL  NAME>>" -OrganizationalUnit "OU Path" -RecipientFilter { ((memberofgroup -eq "CN=G-CRP-STS-ProWatch-User,OU=Corporate,OU=Groups,DC=americas,DC=swk,DC=pri")) }

(Note : given Recipient filter is a sample please replace this according to your environment)

• Set-DynamicDistributionGroup -Identity "created DL Name" -RecipientContainer ‘OU Path'

To Get the List of member in DL  in Notepad :

Get-DistributionGroupMember –identity “group name” | ft name >> output.txt

To Add user into the group :

Add-ADPermission –identity DistributionGroup –User username –AccessRights WriteProperty –Properties “Member”

Share if you care :)

How to Remote wipe iphone / Android for Exchange mail issues ( Remove mobile partnership exchange )

To perform a remote device wipe:

In some cases user reports that emails are not updating in Iphone/Android devices. For that our first thinking is to Reconfigure the account in device.

Yes, we have to do but before that please remote wipe the device which removed the partnership between mobile phone and exchange.

To do that please follow the steps given below:

• Open the Exchange Management Console.

• Under Recipient Configuration, click Mailbox.

• In the Mailbox window, select the user.

• In the action pane, click Manage mobile device or right-click the user's mailbox, and then click Manage mobile device.

• Select the mobile device from which you want to clear all data.

• In the Actions section, click Clear.

• Click Clear again.

Outlook Calendar delegate issue (Exchange 2007 and 2010)

Hello IT Admins,

Let we assume a small example for this type of issues.

ISSUE: When 'Chris' sends meeting request, it shows as from 'Barbara'. But Barbara is a delegate for Chris.

In this scenario, we need to check both Chris and Barbara.

Barbara is using outlook 2010 and Chris using outlook 2007.(Both of them in Exchange 2007)

In such cases the organizer of the meeting will automatically change to the delegate. So we need change registry in Chris's machine. 

To resolve this problem, Install the Outlook 2007 hot fix package that is dated June 30, 2009 (or Latest) or set the value of the SkipSentRepresenting registry entry to enable the hot fix package. To do this, follow these steps:

• Click Start, Run, type regedit, and then click OK

• Locate and then click the following registry subkey:

• HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\Outlook\Options\Calendar

• On the Edit menu, point to New, and then click DWORD Value.

• Type SkipSentRepresenting, and then press ENTER.

• Right-click  SkipSentRepresenting , and then click Modify.

• In the Value data box, type 1, and then click OK.

• Exit Registry Editor.

Before, making any changes in Registry Please Backup Registry for our Safety.

How to grant Send On Behalf Of permission

"Send on Behalf Of" allows one user to be able to send emails on behalf of another. The message will show the recipient who the message was sent on behalf of and who actually sent the message.

There are two ways of granting "Send on Behalf Of":

• via Outlook

allowing a user to grant others to send on their behalf

• via Active Directory Users and Computers

which can be performed by system managers only

Grant Send on Behalf of via Outlook

This procedure will allow you to grant other users the ability to send on your behalf:

1. Start Outlook

2. Tools → Options, select the "Delegates" tab

3. Click on [Add ...]

4. Add the user or users that you want to grant the send-on-behalf-of permission to, then click [OK]

5. The next window will allow you to specify which permissions you are granting. To allow send-on-behalf-of, you need to grant permissions on the "Inbox" to either "Author" or "Editor", then click [OK]

6. Click [OK] to close the "Options" dialog.


Note:
• The above has been demonstrated to work when using Outlook 2003, but not with Outlook 2000 connected to a Exchange 2003 server (I have not had time to identify why).

Grant Send on Behalf of via Active Directory Users and Computers

This procedure will allow system managers to grant users the ability to send on the behalf of other users:

1. Log onto the server running Exchange.

2. Run Active Directory Users and Computers.

3. Find the user's account that you want to be able to send on behalf of, and open up the account properties.

4. Select the "Exchange General" tab.

5. Click [Delivery Options...]

6. Click [Add ...] and add the user (or users) that are to be granted permission to send on behalf of this account.

7. Click [OK] to close the "Delivery Options" dialog.

8. Click [OK] to close the account properties dialog..

How to Send a Message on Behalf of Another

To send an email on behalf of another (assuming you have been granted the necessary send-on-behalf-of privilege):

1. Start Outlook.

2. Go to your Inbox.

3. Click [New] to start a new mail message.

4. If the message does not show a "From" field then pull down the "View" menu and check "From Field".

Note: I have noticed that if you have Outlook set to use Microsoft Word then the "From Field" does not appear in the "View" menu. The work around is to clear the option to use Word (Outlook → Tools → Options → Mail Format → Use Microsoft Office Word 2003 to edit e-mail messages), you will then be able to show the From field, and this remains even if you re-select to use use Word to edit emails.

5. Click [From...] and select the account that you wish to send an email on behalf of.

6. Compose the email as normal.

Delivery has failed to these recipients or distribution lists

Delivery has failed to these recipients or distribution lists : 

Your message wasn’t delivered because of security policies in Exchange 2007. Microsoft Exchange will not try to redeliver this message for you. Please provide the following diagnostic text to your system administrator.

In most cases, this error appears because you’re trying to email from outside your company to an internal distribution. By default, only authenticated users are allowed to email to a distribution group.

To allow emailing to the distribution group from outside your organization, follow these steps:

1. Open the Exchange Management Console
2. Expand Recipient Configuration
3. Click Distribution Group
4. Double click the distribution group
5. Select the Mail Flow Settings Tab
6. Double click Message Delivery Restrictions
7. Uncheck “Require that all senders are authenticated“
8. Click OK

Settings are immediately effective ,so it should work right away.

To create a more secure environment, it’s better to define email addresses where from mail may be sent to the distribution group. This allows you to prevent spamming from unknown email senders. To only allow email from known email senders (outside your organization), you first need to create a mail contact. To create a mail contact, go to Exchange Management Console -> Recipient Configuration -> Mail Contact , right mouse click and choose New Mail Contact.
After you have created the mail contact, do the following:

1. Open the Exchange Management Console
2. Expand Recipient Configuration
3. Click Distribution Group
4. Double click the distribution group
5. Select the Mail Flow Settings Tab
6. Double click Message Delivery Restrictions
7. Select “Only senders in the following list:“
8. Click Add…
9. Select the mail contact and click OK
10. Click OK

How to Migrate Exchange Server

How To Migrate conference room mailbox from 2003 to 2007

1. We are not using Auto Accept agent with Exchange 2003, so we need to manually login to the mailbox and remove Auto acceptance on calendar in NAPTG. To do this:

a. Tools ->Options -> Calendar options Resource scheduling

b. “Uncheck”  Automatically accept meeting requests and process cancellation

2. Now migrate the mailbox to Americas using Quest

3. Open Exchange management shell with “Run as Administrator”

4. Run the cmdlet to convert the mailbox to ROOM mailbox

(Note : Here we used "Tow700_Heritage_Conf_rm" and "Tow700_Marketing_Conf_rm"  as a Exchange server name replace this with your Server name)

Set-Mailbox "##TOW700_MARKETING_CONF_ROOM" -Type Room

5. Run the cmdlet to have the mailbox accept meetings automatically:

Set-MailboxCalendarSettings "##TOW700_HERITAGE_CONF_RM" -AutomateProcessing AutoAccept

6. To maintain subject in meetings:

Set-MailboxCalendarSettings "##TOW700_HERITAGE_CONF_RM" – DeleteSubject $False

7. To Process External meeting requests:

Set-MailboxCalendarSettings "##TOW700_HERITAGE_CONF_RM" – ProcessExternalMeetingMessages $True

8. To test the settings:

Get- MailboxCalendarSettings "##TOW700_MARKETING_CONF_ROOM" |fl

Get-Mailbox "##TOW700_MARKETING_CONF_ROOM" |ft Name, RecipientTypeDetails

 Should be RoomMailbox

Get-MailboxCalendarSettings "##TOW700_HERITAGE_CONF_RM" |ft AutomateProcessing, DeleteSubject, ProcessExternalMeetingMessages

 Should be AutoAccept, False, True

9. Login to the mailbox server on which the converted mailbox resides and Restart the “Microsoft Exchange Mailbox Assistants” service for these settings to take effect.

10. Grand permissions to self in EMC

11. Now, Configure Outlook for the Conference room mailbox.

12. Close Outlook and open with the Outlook switch  Outlook /resetfolders

13. This will fix the issue “You do not have permission to view this calendar”