37 C
Dubai
Thursday, May 1, 2025
Home Blog Page 100

How to Setup Transport Moderation for Sensitive Emails sent to Sensitive Users in your Organization in Exchange 2010

Satheshwaran Manoharan
-
2

Lets say you have a Distribution Group which contains more sensitive users in your Organization

and you are more cautious on what emails are sent to that Distribution group and you feel it has to be approved by a person or a Delegate or yourself as a Admin

 

So that you can avoid unwanted emails are sent to the distribution Group (Which Contains sensitive users)

image

Then Transport moderation is the best setup you can go for in Exchange 2010, Which has more flexibility

 

I would explain the work flow , You can customize as per your thoughts and usability

 

In my case-

Distribution Group Name : “Sensitive Members in the Organization” Sensitive@careexchange.in

Moderator : Moderator < Moderator@careexchange.in>

 

Step 1:

 

lets See on how to do it.

Right Click –> New Transport Rule

 

image

 

Step 2:

Choose a friendly Name

image

Step 3:

 

Select – “Sent to a Member of Distribution list”

Choose the Distribution Group Name which has to be moderated

 

In my case  Distribution Group Name is “Sensitive Members in the Organization” Sensitive@careexchange.in

Choose Next

image

Step 4:

 

Select – “forward the message to addresses for moderation”

Choose the Moderator Name

In my case its “Moderator < Moderator@careexchange.in>”

Choose Next

image

Step 5:

Choose Next

image

 

image

 

Now the Transport Rule has been created Successfully !!

 

Lets test it , how it works

 

Am going to send an abusive or an unwanted mail from a random user (User1) to the Sensitive distribution group (Which contains sensitive users)

 

Now that mail does not going to reach the Distribution Group directly, Unless the moderator approves it

Its going to store in the arbitration mailbox until its gets approves or rejected

image

 

 

Now the Moderator Gets an Email to approve or Reject the mail which has been sent to the Sensitive Distribution Group

image

 

If moderator Approves. Mail will be sent to the members without any hassle

 

if User rejects

Sender will be intimated with an rejected email

 

image

 

Hope Transport moderation feature has been explained !!

Transport Moderation Not working in Exchange 2010 – NDR says ”No arbitration Address for approval process”

Satheshwaran Manoharan
-
2

User gets NDR – When the the mail has to be moderated by Exchange Transport

 

#550 5.2.0 Resolver.MT.NoArbitrationAddress; No arbitration address for approval process ##image

 

This is because of Missing arbitration mailboxes or Corrupted arbitration mailboxes

If you run the below command in Exchange management shell

Get-Mailbox –arbitration

image

You should see your arbitration mailboxes , If you see the above result

Then there is no problem with your arbitration mailboxes

 

If your are not seeing any arbitration mailboxes or you are seeing that your arbitration mailboxes are corrupted.

No wonder why Your Transport moderation does not work as expected and keeps generating NDR

 

You can recreate them , Even if they go corrupted

 

See –

How to recreate System Mailbox , FederatedEmail & DiscoverySearchMailbox in Exchange 2010

https://www.azure365pro.com/how-to-recreate-system-mailbox-federatedemail-discoverysearchmailbox-in-exchange-2010/

 

Arbitration mailbox The arbitration mailbox is used to store the original message that’s awaiting approval. By default, one arbitration mailbox is created for moderated transport during setup. It’s used for all moderated recipients. You can add additional arbitration mailboxes for load balancing purposes. If you’re using multiple arbitration mailboxes, you need to specify which mailbox to use for each moderated recipient.

Reference

http://technet.microsoft.com/en-us/library/dd297936(EXCHG.140).aspx

 

All the mails which has to be moderated are getting stored in your arbitration mailboxes.

 

Most common issue on why this happens –

When you delete your default databases abruptly using adsiedit.msc or any other tools

Then you end up missing your arbitration mailboxes

Result of it –Transport moderation does not going to work

How to Create a Public Folder Calendar in Exchange 2010

Satheshwaran Manoharan
-
3

If you are using a non admin account please refer the below link to give permissions to create Public folders using Outlook

How to Give Permission to a Client to Create Top Level Public Folder (Root Public Folder Tree) in Exchange 2010

 

You won’t able to use GUI or Power shell to create a public folder calendar

 

we need to use outlook to create that.

 

Right Click on Public Folder – New Folder

image

 

Type Name

Choose Folder Contains – Calendar items

Click on All Public Folders

image

Click ok

 

image

You have successfully created a Public folder calendar.

How to Disable Retention Policy from Applying on Calendar and Tasks in Exchange 2010 – (Calendar and Tasks Disappeared)

Satheshwaran Manoharan
-
1

Till Exchange 2010 Sp2 Ru3 – MRM never gets applied on Calendar and Tasks

 

But in the release of Exchange 2010 Rollup 4

This has been included.

Past –

Retention policies do not work for the Calendar and Tasks folders in an Exchange Server 2010 SP1 environment

Present – Exchange 2010 Sp2 Ru4 or above

what you should know is

Retention policies do work for the Calendar and Tasks folders in an Exchange Server 2010 SP2 Ru4 or above environment

 

So if you have a policy which is applied for all Folders in the mailbox in the past – Once you upgrade to Exchange 2010 Sp2 ru4 or above

Retention Policy will apply on “Calendar and Tasks” where the old items are going to expire and retention action will take place as per the policy

 

So all of a sudden your old calendars and tasks got disappeared or got deleted . This will be the most possible reason.

you can find the items as per the retention action has been taken place.

 

If you feel “Calendar and Tasks” should not get deleted , If you feel this will not suit your environment.

 

Before applying the Exchange 2010 sp2 Rollup 4  or upgrading above Exchange 2010 Sp2 Rollup 4

There is a registry tweak available to disable them from the server end. Where this design change won’t get effect in your environment.

 

Open Regedit on you all your mailbox servers

Start- Run – Regedit

 

Browse to the below location

HKLM\SYSTEM\CurrentControlSet\Services\MSExchangeMailboxAssistants\Parameters

 

Create a New “DWORD (32-bit) Value”

image

Enter the Value – ELCAssistantCalendarTaskRetentionEnabled

image

 

To disable this Design Change – (MRM won’t apply on Calendar and Tasks)

Type Decimal Value – 0

 

Later, To enable this Design Change – (MRM will apply on Calendar and Tasks)

Type Decimal Value – 1

 

 

Hope this article will clear some confusions !!

How to Use MFCMapi in Exchange 2010 Server itself

Satheshwaran Manoharan
-
8

By Default you cannot use MFCMapi in the Exchange 2010 server itself

You will end up with an error

MAPIInitialize failed with error 0x80004005 == MAPI_E_CALL_FAILED

 

Because of the missing component “ExchangeMapiCdo.EXE”

Where you don’t want to install Outlook to get that component , like earlier versions

 

Step 1:

Download and Install

Microsoft Exchange Server MAPI Client and Collaboration Data Objects 1.2.1

 

Install on Exchange 2010 Server

image

 

Step 2:

Now

Download MFCMAPI

You can download the 32bit version x86

 

Click on Session –> Logon

image

Choose Next

image

 

Enter Exchange Server FQDN and User Mailbox

image

You can Choose “No”

image

Click Finish

image

 

Now you could use MFCMapi , Without having installing outlook in the exchange server itself

image

Now you can click on session on logoff and logon

image

 

 

Great !! you can use MFCMapi in Exchange 2010 Server now !

Check How you can Recover Deleted Items using MfcMapi

https://www.azure365pro.com/recoverable-deleted-items-folder-showing-up-in-owa-and-outlook-as-normal-folders-in-exchange-2013/

 

How to Create a Recovery Database in Exchange Server 2010

Satheshwaran Manoharan
-
7

Its a Guest Post

There are several ways Exchange 2010 administrators can protect their users’ critical data, and a mix of approaches may be the best way to do this, depending upon your users’ needs. You can create Database Availability Groups (DAGs) to ensure that that mail remains available even if you suffer a server failure. You can span a WAN with a DAG to keep mail available even if you have a data Center outage. You can implement Exchange archiving to capture a copy of every email message that goes in or out of your environment to ensure you have a copy. You can create regular backups and store the tapes offsite to ensure you can restore content even after a user has accidentally deleted something critical. In this post we are going to take a look at how to create a recovery database in Exchange Server 2010 so that you can recover data from a backup in the event something happens.

Recovery databases are similar to other Exchange mailbox databases in that they require storage, will have both database and log files, and will consume the same amount of space for the same amount of data. However, that is where the similarities end. How recovery databases differ is important to understand.

1. A recovery database doesn’t count against any maximum number of databases your license entitles you to, so if you are using Exchange 2010 Standard, you can still have your five mailbox databases plus one recovery database.

2. You can only have one recovery database per server.

3. Client connections are blocked to recovery databases. You can mount a database and access mailboxes using MAPI based tools, but no client can connect.

4. Recovery databases aren’t treated like other mailbox databases. You cannot enable circular logging, retention policies are not applied, and you cannot run online maintenance.

5. ACLs are not maintained when you restore data to a recovery database. You get the content, but not the permissions.

You should also note that recovery databases are intended only to restore mailbox data. Public folder content cannot be recovered to a recovery database. You can recover data from the regular mailbox database or databases used for Exchange archiving, but not for public folders.

When you create a recovery database, consider that even with the limitations above, it is still an Exchange database. It will have a database file and also log files, and the I/O demands will be similar. You will also want to ensure that the volumes you use for the database and the log files have more free space than the largest mailbox database you may need to recover, as it will be a waste of time to start a recovery only to find you don’t have enough space to restore the backup database.

When you are ready to begin, open an Exchange Management Shell and run the following command, where you specify the full path for both the database and log files (different volumes are recommended) and you use the –recovery keyword to designate this as a recovery database:

 

New-MailboxDatabase –recovery –name “Recovery Database” –server MBXServer01
-edbfilepath d:\exchange\databases\ -logfolderpath l:\exchange\logfiles\ [enter]

 

While you can have multiple recovery databases in your Exchange organization, remember that you can have only one per server. Ensuring that the volume has enough space to accommodate the largest mailbox database you may need to recover will help speed those operations along, so consider reserving space on the fastest mailbox server you have so that if you do need to perform a recovery, you can do so as quickly as possible.

To enhance your backup and recovery plans, you should also implement Exchange archiving for users. You can copy all messages to the archive, or use DAGs to provide high availability to the most recent mail and provide each user with access to Exchange archiving to store messages that are older. Retention policies can move data from the primary mailbox to the Exchange archive as needed, so you get the best mix of high availability for the newest content, and you can use backups to ensure content store in Exchange archiving is safe as well.

 

This guest post was provided by Casper Manes on behalf of GFI Software Ltd. Read more on how to improve your Exchange archiving.

All product and company names herein may be trademarks of their respective owners.

1...99100101...113Page 100 of 113

EDITOR PICKS

POPULAR POSTS

POPULAR CATEGORY

ABOUT ME

Satheshwaran Manoharan - Microsoft MVP - Award-winning Technology Leader with a wealth of experience running large teams and diversified industry exposure in cloud computing. From shipping lines to rolling stocks.In-depth expertise in driving cloud adoption strategies and modernizing systems to cloud native. Specialized in Microsoft Cloud, DevOps, and Microsoft 365 Stack and conducted numerous successful projects worldwide. Also, Acting as a Technical Advisor for various start-ups.

Contact : Info@Azure365Pro.com

FOLLOW US

© Azure365Pro.com

× How can I help you?