Set public folder to accept NDR

1.      Locate user A’s distinguishedName

Get-User “User A” | Fl DistinguishedName

2.      Launch ADSI Editor, go to “CN=Microsoft Exchange System Objects”, right-click the PF1 object, and then go to “Properties”

Notes: PF1 must be mail-enabled

3.      In the “Attribute Editor” tab, locate “publicDelegates” attribute, and then copy user A’s DistinguishedName into it

from 

https://social.technet.microsoft.com/Forums/office/en-US/d341ff3f-9a8c-40c7-ab04-0a1655047041/public-folder-not-accepting-ndr?forum=exchangesvrgenerallegacy

Exchange 2010: Public folder GUID

One of the Event in the Application log in Exchange 2010 is showing the following event 

Event id : 2028
The Delivery of a Message sent by Public Folder E0FG2CADACE66846A98A6C130CA3ER97-0000FA965FG85
has failed.\r\n To:first name, Last name\r\nCc:\r\n The Non-Delivery report has been deleted


Steps
---------
Getting which public folder is in picture finding is difficult here. 
so if you had tried this then it will not work and through's error

c:\>Get-MailPublicFolder -id E0FG2CADACE66846A98A6C130CA3ER97-0000FA965FG85 

is not showing proper error and message shows it couldn't be found



so instead of running the command using the whole Hexa-Decimal value, use the value before dash ( - ) so here in this example "E0FG2CADACE66846A98A6C130CA3ER97-0000FA965FG85"  we are going to use E0FG2CADACE66846A98A6C130CA3ER97 and to convert this value into proper GUID use the following command from Exchange management shell



c:\>[system.Guid] 'E0FG2CADACE66846A98A6C130CA3ER97'
Guid
--------
E0FG2cad-ace6-6846-a98a-6c130CA3ER97

and finally the command for getting public folder is 
c:\Get-MailPublicFolder -identity E0FG2cad-ace6-6846-a98a-6c130CA3ER97

or 
c:\Get-MailPublicFolder | Where {$_.LegacyExchangeDN -Match "E0FG2cad-ace6-6846-a98a-6c130CA3ER97"}



or using with complete GUID then you can use below command

[PS] C:\Windows\system32>Get-MailPublicFolder -resultsize unlimited | where {$_.Externalemailaddress -match "0ED914CAB4DA1243948B9AD6B0B27FDE-000000000014"}


Or to reveal the name of the public folder use the below command
[PS] C:\Windows\system32>Get-MailPublicFolder -resultsize unlimited | where {$_.Externalemailaddress -match "0ED914CAB4DA1243948B9AD6B0B27FDE-000000000014"} | Get-PublicFolder 

PS: Guid used here is only for illustration purpose only.

THANKS RAVI

If you encounter low disk space issues, you can perform the following actions to correct the issue: Exchange 2010

If you encounter low disk space issues, you can perform the following actions to correct the issue:

• Delete content from mailboxes. Specifically, you can delete messages from the Deleted Items and Sent Items folders.
• Purge items from the Recoverable Items folder. For details, see Clean Up the Recoverable Items Folder.
• Run database maintenance. For details, see Maintain Mailbox Databases.
• Purge transaction logs. For details, see Understanding High Availability Factors.
• Enable circular logging. For details, see Configure Mailbox Database Properties.
• Change the database path to a hard disk drive that has more space. For details, see Move the Mailbox Database Path for a Mailbox Database Copy.

from : https://technet.microsoft.com/en-us/library/bb331958(v=exchg.141).aspx

Unable to send message with Attachment even though Proper Message size limits 15 MB has been set on Receive, Send and at Transport Level which also includes MIME overhead of 37% still not able to send/receive message

Exchange 2010, Unable to send message with Attachment even though Proper Message size limits 15 MB has been set on Receive, Send and at Transport Level which also includes MIME overhead of 37% still not able to send/receive message.

then try this command 

Set-TransportConfig -ExternalDsnMaxMessageAttachSize 15MB -InternalDsnMaxMessageAttachSize 15MB

In Exchange 2013
New-SystemMessage is a command used to set the DSN (Delivery status Notification)

for reference
https://technet.microsoft.com/en-us/library/aa998878%28v=exchg.150%29.aspx



some Additional Knowledge and default Series for configuring limit is

• Organizational Level # Is the Highest level in an organization
• Send Connector
• Receive Connector
• AD Site Links
• Routing Group Connectors
• Mailbox Level      # Is the lowest level and take precedence over all the settings

Shell Commands where Message Limit can be checked

Get-ForeignConnector | fl Name,MaxMessageSize
Get-SendConnector | fl Name,MaxMessageSize
Get-ReceiveConnector | fl Name,MaxMessageSize
Get-ADSiteLink | fl Name,MaxMessageSize
Get-RoutingGroupConnector | fl Name,MaxMessageSize
Get-TransportConfig | fl MaxSendSize,MaxReceiveSize
Get-DistributionGroup | fl name,MaxSendSize,MaxReceiveSize
Get-DynamicDistributionGroup | fl name,MaxSendSize,MaxReceiveSize
Get-Mailbox | fl name,MaxSendSize,MaxReceiveSize
Get-MailContact | fl name,MaxSendSize,MaxReceiveSize
Get-MailPublicFolder | fl name,MaxSendSize,MaxReceiveSize
Get-MailUser | fl name,MaxSendSize,MaxReceiveSize

Get-Mailbox -FIlter {MaxSendSize -ne $null -OR MaxReceiveSize -ne $null} | ft Name,MaxSendSize,MaxReceiveSize

After rebooting Exchange 2010 server is stuck on "Applying Group Policy settings"

After rebooting server, Users are unable to send and receive Email

We are able to
All of the Exchange related services are in stopped state and after rebooting Exchange server, stuck on "Applying Group Policy settings"

We replicated DC from "AD sites and services", added Exchange server "SVR13" into Exchange server

Group from "Exchange Security Group"and suggest to reboot he box. still same issue.

Customer is able to boot Exchange server into Networking with Safe mode


http://www.exchangewarrior.com/exchange-2007/exchange-server-stuck-on-applying-group-policy-settings/

Troubleshooting Steps : DAG suddently failover

Exchange 2010 Service pack 3 with Update Rollup 2.

Understand that one of the DAG member stopped responding for the clients hence the users were unable to access their mailbox.

In order to overcome this situation, customer has moved all the resources to another node and rebooted the problem node


Diagnosis Given : Network issue, Network connectivity lost between FSW and Exchange

Exchange 2013 Installation on Windows 2012 Std R2

Installing only CAS role

In powershell (Run as Administrator) 

Install-WindowsFeature AS-HTTP-Activation, Desktop-Experience, NET-Framework-45-Features, RPC-over-HTTP-proxy, RSAT-Clustering, RSAT-Clustering-CmdInterface, RSAT-Clustering-Mgmt, RSAT-Clustering-PowerShell, Web-Mgmt-Console, WAS-Process-Model, Web-Asp-Net45, Web-Basic-Auth, Web-Client-Auth, Web-Digest-Auth, Web-Dir-Browsing, Web-Dyn-Compression, Web-Http-Errors, Web-Http-Logging, Web-Http-Redirect, Web-Http-Tracing, Web-ISAPI-Ext, Web-ISAPI-Filter, Web-Lgcy-Mgmt-Console, Web-Metabase, Web-Mgmt-Console, Web-Mgmt-Service, Web-Net-Ext45, Web-Request-Monitor, Web-Server, Web-Stat-Compression, Web-Static-Content, Web-Windows-Auth, Web-WMI, Windows-Identity-Foundation

Reboot will be required

2. Install Microsoft Unified Communications Managed API 4.0, Core Runtime 64-bit

3. Exchange setup




Installing MBX role or Mixed mode

In powershell (Run as Administrator) 

Install-WindowsFeature AS-HTTP-Activation, Desktop-Experience, NET-Framework-45-Features, RPC-over-HTTP-proxy, RSAT-Clustering, RSAT-Clustering-CmdInterface, RSAT-Clustering-Mgmt, RSAT-Clustering-PowerShell, Web-Mgmt-Console, WAS-Process-Model, Web-Asp-Net45, Web-Basic-Auth, Web-Client-Auth, Web-Digest-Auth, Web-Dir-Browsing, Web-Dyn-Compression, Web-Http-Errors, Web-Http-Logging, Web-Http-Redirect, Web-Http-Tracing, Web-ISAPI-Ext, Web-ISAPI-Filter, Web-Lgcy-Mgmt-Console, Web-Metabase, Web-Mgmt-Console, Web-Mgmt-Service, Web-Net-Ext45, Web-Request-Monitor, Web-Server, Web-Stat-Compression, Web-Static-Content, Web-Windows-Auth, Web-WMI, Windows-Identity-Foundation

reboot will be required

Need to install after Windows feature 

Microsoft Unified Communications Managed API 4.0, Core Runtime 64-bit

Microsoft Office 2010 Filter Pack 64 bit

Microsoft Office 2010 Filter Pack SP1 64 bit

and finally run Exchange setup