So we have Exchange 2016 on-prem with Outlook 2016

Our staff have notebooks, and happily gad about the place having meeting and doing important stuff, with their wifi on.
Sometimes the WiFi may drop, or they may go out to a coffee shop for a latte. - or even go home (heaven forbid) and VPN in later.

If exchange isn’t connected when they send a message, the Mail that can’t be sent will go to the Outbox (yay!), but when Exchange is reachable again, the result can be 'unpredictable'. I've tested this by using a wired network, and unplugging it and plugging it back in again.


1) The message may send with apparent sent time when connectivity was retuned.  (I'd say this is preferred)

2) The message may send with apparent time when you clicked send. (this sucks, and leads to arguments featuring yesIdid/noyoudiddent), and requires looking at exchange logging to resolve it.

3) Sometimes the message will appear with the "edit" icon in the Outbox instead of the "sending" Icon, and be stuck. (this sucks, too)

then: if the user opens it and click send:

It might send, or; It might go itallic for a moment, and remain stuck in the outbox (this double sucks).

Then if the user puts Outlook in offline mode, then back online, it will usually be sendable again.


All in all, the users are thinking Outlook is like a box of chocolates.

Please help.

I am attempting to create a partner send connector for our third party encryption. The third party uses a smart host with opportunistic tls. However, the option to choose smart host is greyed out. Microsoft was less than helpful. Any ideas?  Thank you.

A clients users are experiencing certificate error popups when using outlook that relate to remote.****.com

The certificates on the Exchange 2010 server have indeed expired however I am struggling to get it resolved.

I have attempted to renew the certificate but cannot get onto the IIS default cert server site to complete the pending request. I am not sure however if this is indeed the correct solution.

I have a dead Exchange 2007 SP3 with Rollout update 21 in a 2007-2013 coexistence.

I downloaded an Exchange 2007 SP3 ISO from MS but it is an earlier version.

When running the setup.com /M:recoverserver for exchange 2007, how can I install SP3 with Rollout update 21?

Is it necessary for the ISO being used to be the same version as the original 2007 installation?

In a test environment, having the RU21 update in the update folder caused the install to fail.

Regardless of the RU21 update, the recover server install fails in the test environment.  Are there any common causes for a recover server failure?

Thanks!

I have an Exchange 2007 installation on a server running Server 2008 Enterprise (not R2). The server is a Domain Controller as well. (I know, not best practice but don't have extra hardware).

The goal is to remove Exchange 2007, demote the server, and retire it.

There are no more mailboxes on Exchange 2007.

Due to reasons, I cannot uninstall exchange 2007 to remove it from the 2013 environment. See below link for the reasons:

https://social.technet.microsoft.com/Forums/en-US/42e3331c-0b10-4221-9c92-279ab134a5c5/server-manager-encountered-an-unexpected-error-while-collecting-data-about-the-status-of-this?forum=winservermanager

How do I properly use the RecoverServer switch so I can build a new server and properly remove 2007 from my network? If needed, I can cobble together some temporary hardware.

Thanks!

Hi all,
My environment : 2 Exchange servers 2013 CU19 (CAS + Mailbox roles both) in 1 DAG, 5 mailbox databases.
During peak hours I notice that there are several dozen to several hundred messages are stuck in "SMTP Delivery to Mailbox" of "mailbox database A", this "mailbox database A" has more mailboxes than 4 others.
These messages are delivered after awhile (not error or stuck forever) but my users complain about emails delivery slowly.

We have about 1300 mailboxes and total messages delivery (send + receive , external + internal) may up to 50k in morning or 100k in day during peak hours.
So I decide to increase some limit parameter in transport service to improve the situation. After searching Google I tried to increase these parameters : PickupDirectoryMaxMessagesPerMinute (default 100) , PickupDirectoryMaxRecipientsPerMessage (default 100) , MaxConcurrentMailboxDeliveries (default 20) , MaxConcurrentMailboxSubmissions (default 20).

Get-TransportService myservers | fl *maxcon*

MaxConcurrentMailboxDeliveries  : 100
MaxConcurrentMailboxSubmissions : 100
MaxConnectionRatePerMinute      : 1200

Get-TransportService myservers | fl *pick*

PickupDirectoryMaxHeaderSize           : 64 KB (65,536 bytes)
PickupDirectoryMaxMessagesPerMinute    : 400
PickupDirectoryMaxRecipientsPerMessage : 200
PickupDirectoryPath                    : C:\Program Files\Microsoft\Exchange Server\V15\TransportRoles\Pickup

Get-MailboxTransportService myservers | fl *maxcon*

MaxConcurrentMailboxDeliveries  : 100
MaxConcurrentMailboxSubmissions : 100

Do I have to restart "Microsoft Exchange Transport" and "Microsoft Exchange Mailbox Transport Delivery" services to make it effect ? Or increase more or something else ?
This is more information about transport service if you need

Get-TransportService myservers | fl *max*

ConnectivityLogMaxAge                         : 30.00:00:00
ConnectivityLogMaxDirectorySize               : 1000 MB (1,048,576,000 bytes
ConnectivityLogMaxFileSize                    : 10 MB (10,485,760 bytes)
MaxConcurrentMailboxDeliveries                : 100
MaxConcurrentMailboxSubmissions               : 100
MaxConnectionRatePerMinute                    : 1200
MaxOutboundConnections                        : 1000
MaxPerDomainOutboundConnections               : 40
MessageTrackingLogMaxAge                      : 30.00:00:00
MessageTrackingLogMaxDirectorySize            : 1000 MB (1,048,576,000 bytes
MessageTrackingLogMaxFileSize                 : 10 MB (10,485,760 bytes)
IrmLogMaxAge                                  : 30.00:00:00
IrmLogMaxDirectorySize                        : 250 MB (262,144,000 bytes)
IrmLogMaxFileSize                             : 10 MB (10,485,760 bytes)
ActiveUserStatisticsLogMaxAge                 : 30.00:00:00
ActiveUserStatisticsLogMaxDirectorySize       : 250 MB (262,144,000 bytes)
ActiveUserStatisticsLogMaxFileSize            : 10 MB (10,485,760 bytes)
ServerStatisticsLogMaxAge                     : 30.00:00:00
ServerStatisticsLogMaxDirectorySize           : 250 MB (262,144,000 bytes)
ServerStatisticsLogMaxFileSize                : 10 MB (10,485,760 bytes)
PickupDirectoryMaxHeaderSize                  : 64 KB (65,536 bytes)
PickupDirectoryMaxMessagesPerMinute           : 400
PickupDirectoryMaxRecipientsPerMessage        : 200
QueueMaxIdleTime                              : 00:03:00
ReceiveProtocolLogMaxAge                      : 30.00:00:00
ReceiveProtocolLogMaxDirectorySize            : 250 MB (262,144,000 bytes)
ReceiveProtocolLogMaxFileSize                 : 10 MB (10,485,760 bytes)
RoutingTableLogMaxAge                         : 7.00:00:00
RoutingTableLogMaxDirectorySize               : 50 MB (52,428,800 bytes)
SendProtocolLogMaxAge                         : 30.00:00:00
SendProtocolLogMaxDirectorySize               : 250 MB (262,144,000 bytes)
SendProtocolLogMaxFileSize                    : 10 MB (10,485,760 bytes)
MaxNumberOfTransportSyncAttempts              : 3
MaxActiveTransportSyncJobsPerProcessor        : 16
HttpProtocolLogMaxAge                         : 7.00:00:00
HttpProtocolLogMaxDirectorySize               : 250 MB (262,144,000 bytes)
HttpProtocolLogMaxFileSize                    : 10 MB (10,485,760 bytes)
TransportSyncLogMaxAge                        : 30.00:00:00
TransportSyncLogMaxDirectorySize              : 10 GB (10,737,418,240 bytes)
TransportSyncLogMaxFileSize                   : 10 MB (10,485,760 bytes)
TransportSyncHubHealthLogMaxAge               : 30.00:00:00
TransportSyncHubHealthLogMaxDirectorySize     : 10 GB (10,737,418,240 bytes)
TransportSyncHubHealthLogMaxFileSize          : 10 MB (10,485,760 bytes)
TransportSyncMaxDownloadSizePerItem           : 36 MB (37,748,736 bytes)
TransportSyncMaxDownloadSizePerConnection     : 50 MB (52,428,800 bytes)
TransportSyncMaxDownloadItemsPerConnection    : 1000
IntraOrgConnectorSmtpMaxMessagesPerConnection : 20
QueueLogMaxAge                                : 7.00:00:00
QueueLogMaxDirectorySize                      : 200 MB (209,715,200 bytes)
QueueLogMaxFileSize                           : 10 MB (10,485,760 bytes)
WlmLogMaxAge                                  : 7.00:00:00
WlmLogMaxDirectorySize                        : 250 MB (262,144,000 bytes)
WlmLogMaxFileSize                             : 10 MB (10,485,760 bytes)
AgentLogMaxAge                                : 7.00:00:00
AgentLogMaxDirectorySize                      : 250 MB (262,144,000 bytes)
AgentLogMaxFileSize                           : 10 MB (10,485,760 bytes)
FlowControlLogMaxAge                          : 7.00:00:00
FlowControlLogMaxDirectorySize                : 200 MB (209,715,200 bytes)
FlowControlLogMaxFileSize                     : 10 MB (10,485,760 bytes)
ProcessingSchedulerLogMaxAge                  : 7.00:00:00
ProcessingSchedulerLogMaxDirectorySize        : 200 MB (209,715,200 bytes)
ProcessingSchedulerLogMaxFileSize             : 10 MB (10,485,760 bytes)
ResourceLogMaxAge                             : 7.00:00:00
ResourceLogMaxDirectorySize                   : 200 MB (209,715,200 bytes)
ResourceLogMaxFileSize                        : 10 MB (10,485,760 bytes)
DnsLogMaxAge                                  : 7.00:00:00
DnsLogMaxDirectorySize                        : 100 MB (104,857,600 bytes)
DnsLogMaxFileSize                             : 10 MB (10,485,760 bytes)
JournalLogMaxAge                              : 7.00:00:00
JournalLogMaxDirectorySize                    : 200 MB (209,715,200 bytes)
JournalLogMaxFileSize                         : 10 MB (10,485,760 bytes)
TransportMaintenanceLogMaxAge                 : 7.00:00:00
TransportMaintenanceLogMaxDirectorySize       : 200 MB (209,715,200 bytes)
TransportMaintenanceLogMaxFileSize            : 10 MB (10,485,760 bytes)

Few users complaining that some of the emails they sent previously not appears in Sent items now. It happens to random emails.No specific patterns, no connection between these emails. Checked on OWA sent folder the emails not shows up there as well. suggestions?

Hello,

What is best practice for creating system account, only for sending. User needs to be verified by Exchange Server.

Thanks for idea.

My manager gave me access to their Outlook 2016 account. I can see their inbox just fine. However, I can't see their sent items, deleted items or subfolders. The manager granted me the "owner" permission level and checked the All Details options and checked all the read/view/write boxes. Now what?

Hello,

i migrated an Exchange 2010 Server (single Server with all Roles) to a Exchange 2013 CAS Cluster (2x Exchange 2013 Multi-Role Servers).

After migrating the Public Folders from Exchange 2010 to Exchange 2013 User reported me that they are not able to open/redirect/accept/decline an meeting which was send to a mail-enabled Public Folder.

For Explaination: Some departments have a own Public Folder (e. g. "HR-Department"). Other Exchange Users creating a meeting and send it to this PF. A Secretary takes a look at this meeting and redirect it to the correct User.
Using Outlook i am getting the Error "Free/Busy Information not available" in the down right corner.
Using OWA i also getting similar error (not able to check conflict between your calendar and this meeting) but i am still able to redirect/open/accept the metting-request.

Free/Busy Information between normal Exchange Users works without any issues.
Calender Permission for Default is set to "Read" for "Free/busy time".
Meanwhile i have checked Event Log and all settings and don't know, where the Problem is. It seems that the Public Folder (or Public Folder Mailbox) want's to read the Free/Busy Information of the User who tries to open the Meeting-Request.

If someone has any idea how to analyse this issue, please help.
I translated the error Message from a german Exchange Installation. So i may be possible that the original englisch error are a little bit different.

Thanks and KR
Marco

Hi,

We have a problem with On-Premises Exchange 2013 and the correct configuration for use with Outlook (web)Add-ins doing external calls to our Exchange server.

We have implemented Salesforce sales Cloud (CRM) in our company, and when trying to use the Outlook (web)Add-ins called "Lightning for Outlook" it fails and saying: "We encountered a problem. Try again, or contact your administrator andmention there was a communication error with Exchange."

The requirements stated from Salesforce are: 

Ensure that the following are exposed to calls from Salesforce on the Exchange server:
- Exchange metadata URL.
- Exchange Web Services URL.
- the jwt generated by the Exchange server shows these URL's properly.
- Certificates on the Exchange servers are up-to-date (often generates a 500 error in the Debug Tool output)

What I am wondering about in general is the configuration/setup for the "autodiscover/metadata/json/1" URL.

Should this be open externally (No authentication)?

If you try to access the same URL on Office 365 (autodiscover-s.outlook.com/autodiscover/metadata/json/1) it is open.

What is the requirements/configuration for using a Outlook (web)Add-ins doing external calls?

Any suggestions, guidance and help would be very appreciated.

Best Regards,

Kenneth Soerense

Hello. 

I have an installation of Exchange 2013 SP1, and since a few days I continually receive this error message.

MS Filtering Engine Update process was unsuccessful in contacting the Primary Update Path. Update Path: http://forefrontdl.microsoft.com/server/scanengineupdate

Any solution?

Thanks.

MCSA: Windows Server 2008

Hello,

User have 2016 Mailbox, using Outlook 2019. When He gets e-mail notification of missed call from or missed message lync, this e-mails, which belongs to user mailbox ends wrong mailbox. He has full access on shared mailbox, and these emails ends up in this mailbox. It is rly pain for the user.

Thanks for ideas

in our organization some of the users are sending bulk email to customers ,at that time mostly ISP will make our ip reputation as bad and blacklist., to avoid this,  is there any method for delaying delivery of email  ? make per minute 5 then rest next minutes another 5 like that

please help

Hi,

I'm migrating some users from one Exchange 2013 SP1 CU6 database to another one. Some users fail with warnings:

Error:MigrationPermanentException: Warning: Target mailbox unlock operation was not replicated. If a lossy failover occurs after the target mailbox was unlocked, the target mailbox could remain inaccessible. Error details: Mailbox changes failed to replicate. Database doesn‎'t satisfy the constraint SecondCopy because the commit time 7/12/2014 4:22:54 PM isn‎'t guaranteed by replication time 7/12/2014 4:14:25 PM.

Part of the problem is likely that on the passive DAG member, the Microsoft Exchange Migration Workflow service keeps crashing and restarting.

I migrated probably 300 users no problem prior to CU6 (we were on CU4/SP1), this issue now happens on 1/10 migrated users. As far as I've seen, this causes the users no issues what so ever, however I haven't had a fail over to the passive DAG member since these migrations.

Simply re-running the migration jobs don't help. Thinking of CU7 but can't see anything in the release notes mentioning this at all.

1. Is it possible to send a terms and condition email to new exchange email account user?

1a. Can it also contain a disagree or agree option that disables the mailbox if disagree is selected?

Hi,

We have migrated all our mailboxes to Exchange 2013 server from Exchange 2007. We have some mailboxes configured to forward mails to other users. After migration, users started complaining that when they receive a forwarded mail from mailboxes, they can't see the original e-mail address but their names.

Please advise.

Mr.POP

Hello All,

I just found some abnormal error event in our Exchange 2013 Mailbox Server. This error is similar to articles I found. but none of these articles describe the issue in MBX server.

Touchwood no service impact to Exchange server but these error appears in a rapid rate

Thanks in Advance.

First a Warning event 

Then follows an Error for MSExchange Error Logging Module

(Process w3wp.exe, PID 9720) "Unhandled exception 'Object reference not set to an instance of an object.' when processing request /powershell?ping=probe." 

hi all,

is it posible to connect a Mailbox from a Backup to other User?

example:

RDB Database has a Mailbox UserA. I will Connect it to Demo11

My try:

I disable Mailbox Demo11

New-MailboxRestoreRequest -SourceStoreMailbox "demo10" -SourceDatabase "RDB" -TargetMailbox "Demo11" -AllowLegacyDNMismatch

The operation couldn't be performed because 'Demo11' couldn't be found.
    + CategoryInfo          : NotSpecified: (:) [New-MailboxRestoreRequest], ManagementObjectNotFoundException
    + FullyQualifiedErrorId : [Server=EX2,RequestId=03aadaa1-4461-415d-beeb-a8226a48d75e,TimeStamp=28.03.2019 07:29:59] [FailureCategory=Cmdlet-ManagementObjectNotFoundExcept

Chris