some sent emails are missing and moving to "recover deleted items"
hello , we are using on-premises exchange server 2016 in my environment. and we are using microsoft outlook 2019 & 2021 . i have one question : i notice that the sent emails for all users are appear in "recover deleted items" , however these emails are not deleted and still exist in sent items folder . so it is appear the same emails in "sent item" folder and in "recover deleted items" , which i think very weird . i have one incident : one of my user is encounter a weird problem , that some sent emails are weirdly disappear from "sent item" folder but he never delete them , and we can found these items in "recover deleted items" , but the restore option in "recover deleted items" didn't restore the email to the user mailbox . however i don't have any problem mention in healthreport for my exchange server , all in good condition . what may be the problem ?
Event ID 12018 and Exchange 2019
We have recently migrated from on-premise Exchange 2016 to hybrid with Exchange 2016 server used primarily for management. I have been interested in switching from a commercial SAN certificate to LetsEncrypt, but the idea of having my event logs perpetually full of 12017 and 12018 events due to Lets Encrypt's 90 day certs has made that unattractive. Does Exchange 2019 behave any better in regards to how frequently it complains about certificates expiring 90 days in the future?
Decomission exchange 2010
We are decommissioning a 2-node DAG 2010 which has been migrated to a 2-node DAG 2016. The public folders have been successfully migrated to ex2016. Now we want to decommission the exchange 2010 nodes and the first task is to remove the public folder database running the following command on exchange 2016 we see the the mailbox databases have the ex2010 public folder configured [PS] C:\Windows\system32>Get-MailboxDatabase -IncludePreExchange2013 | ft name,public* Creating a new session for implicit remoting of "Get-MailboxDatabase" command... Name PublicFolderDatabase ---- -------------------- MBX2016_100GB Public Folder SRV10 MBX2016_8GB Public Folder SRV10 MBX2016_2GB Public Folder SRV10 MBX2016_5GB Public Folder SRV10 PF2016DB Public Folder SRV10 Following some thread and kb we tried to cleanup the "publicfolderdatabase" with the following command Set-MailboxDatabase MBX2016_100GB -PublicFolderDatabase $null but got the error Cannot validate argument on parameter 'PublicFolderDatabase'. The argument is null or empty. Provide an argument that is not null or empty, and then try the command again. + CategoryInfo : InvalidData: (:) [Set-MailboxDatabase], ParameterBindingValidationException + FullyQualifiedErrorId : ParameterArgumentValidationError,Set-MailboxDatabase + PSComputerName : xxxx.xxxxx.xxx So the question is how should we go on and dismiss the PF DAG ? thanks
SMTP relay - Client host rejected: AP0002
Hello everyone, We have to send emails to a Bouyges address (a french telecom company) and I got this back: Sorry, no SMTP connection got far enough; most progress: RCPT TO response; remote host said: 554 5.7.1 <...dsl.sta.abo.bbox.fr>: Client host rejected: AP0002 Please use your ISP mailserver. (#5.5.0) I searched on Google to find a way to send the emails and what I understand is that I have to configure the SMTP relay of Bouyges. What I found are only configurations for postfix and I don't know how to configure it on an Exchange On-premise server, do you have any info? The SMTP server of Bouyges is smtp.bbox.fr What I don't know if it's possible to do is to use this relay only for the bbox mails address. Thanks for any help!
Too many event id 4624 and 4634 why?
Hi, i've on prem 2016 cu19 2 node exchange with mapi over http connection enable protocol for client connection. in front of exchange an arraynetworks load balancer. Since about 3/4 days splunk show me that many event id 4624 and event id 4634 are logged on both server exhange. By the way, the 2 server are already restarted 4/5 days ago. I've check for http time reconnection option or something like this, some user are about 3000 connect and reconnect during 24 hours, some other user are about 19000/20000 connection/reconnection. all the client are win10 21h2 and office2016 both last patch. User with many connection/reconnection working only with pc with outlook. all works fine but my question is if is normal so many connection/reconnection tks, livio
Exchange 2016 - Event ID 2 - RestDeepTestProbe/MSExchangeRestAppPool
Hi, i'm troubleshooting a problem on our exchange server 2016 infrastructure (two servers in two different domains; so not related to each other in any way). On both servers the CU 2021-04 is currently installed on these servers. The problem occurs since the exchange servers have been setup (~6 and 9 month ago), the error occurs every 2-5 minutes. The problem which occurs is logged in the Event-Manager within "Windows\Exchange\ActiveMonitoring\ProbeResult" und only logs the error "Probe result (Name=RestDeepTestProbe/MSExchangeRestAppPool)". Because the error was not very helpful i digged a bit into it (thanks to this website this was not so hard: https://www.codetwo.com/admins-blog/managed-availability-in-exchange-2013/) And so i was able to pull out these information from the deep of the event viewer: auto-ns2 : http://schemas.microsoft.com/win/2004/08/events xmlns : myNs Id : 1019177704 AssemblyPath : D:\Exchange Server\V15\Bin\Microsoft.Exchange.Monitoring.ActiveMonitoring.Local.Components.dll TypeName : Microsoft.Exchange.Monitoring.ActiveMonitoring.ActiveMonitoring.Responders.EscalateWit hWatsonQueryResponder Name : PrivateWorkingSetError.msexchangerestapppoolEscalate WorkItemVersion : [null] ServiceName : Rest.Protocol DeploymentId : 0 ExecutionLocation : [null] CreatedTime : 2021-05-28T16:15:14.0167242Z Enabled : 1 TargetPartition : [null] TargetGroup : [null] TargetResource : msexchangerestapppool TargetExtension : [null] TargetVersion : [null] RecurrenceIntervalSeconds : 300 TimeoutSeconds : 300 StartTime : 2021-05-28T16:15:24.0167242Z UpdateTime : 2021-05-28T16:15:14.0167242Z MaxRetryAttempts : 3 ExtensionAttributes : <ExtensionAttributes LoadFromResourceAttributeValue="False" WatsonProcessName="w3wp#msexchangerestapppool" QueryTimeSpan="1.00:00:00" ExceptionName="M.E.M.A.A.Responders.WatsonResponder+PrivateWorkingSetException" /> AlertMask : PrivateWorkingSetError.msexchangerestapppool/msexchangerestapppool WaitIntervalSeconds : 14400 MinimumSecondsBetweenEscalates : 14400 EscalationSubject : Process isolation: Process error message for high memory usage: msexchangerestapppool. EscalationMessage : The msexchangerestapppool process exceeded the storage failure threshold. {Monitor.StateAttribute1} {Probe.Error}. EscalationService : [null] EscalationTeam : Web Services NotificationServiceClass : 2 DailySchedulePattern : AlwaysEscalateOnMonitorChanges : 0 Endpoint : [null] CreatedById : 0 Account : [null] AlertTypeId : PrivateWorkingSetError.msexchangerestapppool TargetHealthState : 8 CorrelatedMonitorsXml : [null] ActionOnCorrelatedMonitors : 0 ResponderCategory : ProcessIsolation ThrottleGroupName : [null] ThrottlePolicyXml : [null] UploadScopeNotification : 0 SuppressEscalation : 0 Version : 0 By troubleshooting some other errors on the exchange server, these are the steps i already tried to fix the error: recycle the application "MSExchangeRestAppPool" in IIS remove all monitoring mailboxes on the exchange server and recreate them uninstall the „Exchange Web Services Managed API“ I cannot find any further information, which memory limit is set, how can i increase it or any other information, how to get this problem fixed. Thanks for any helpExchange 2016 / 2019 demands to install a prerequisite on an OS not supported by the prerequisite
Hi there, I would like to get some feedback and raise awareness about an issue I have encountered at a customer which lead me to question the prerequisite UCMA 4.0 as part of Exchange 2016 / 2019 mail role on Server 2016 / 2019. by fact UCMA is not supported on either of these Windows Server OS (refer download prerequisites) The one that is supported is UCMA 6.0 The docs appear like nothing changed since Exchange Server 2013, which is not the case as there have been 2 subsequent major releases of UCMA since. "The UCMA 4.0 runtime is specifically required. If you’ve installed any other version of UCMA, you are in a non-supported state. The Exchange team is responsible for supporting their pre-requisites." Is this statement bonkers or would the Exchange Server seriously argue against your own mesh of supportability which seem to exclude your prerequisites? I would like to plea: change docs, change version checks of UCMA in setup / CUs. Update to UCMA 6.0 when Exchange is running on Server 2016 / 2019 (for Ex2019 no question as only 2019 is supported at the moment) Fix the UCMA 6.0 setup to no demanding the outdated C++ Redist 2015-2019 x64 14.12. but also accepting the currently secured version 14.28. Dear Exchange Team, thank you for your time and feedback.OWA Exchange 2016 Error - Something went wrong
Hi All, Trying to access to owa and receiving this error: A problem occurred while you were trying to use your mailbox. X-ClientId: B3A85E9BCF46437394BEF995B1565EF6 request-id a10342c5-22ca-4a8f-93c5-f8e7bc96b165 X-OWA-Error Microsoft.Exchange.Data.Storage.StorageTransientException X-OWA-Version 15.1.2106.2 X-FEServer TABARSRV X-BEServer TABARSRV Date:10/14/2020 7:51:34 AM InnerException: Microsoft.Mapi.MapiExceptionADPropertyError help pls.Mail Flow Rule Question
I'm NOT an Exchange expert but... Basically we have customers who are asking us to do DLP in Exchange such that information relevant to their company isn't sent to any of our other customers. As such I've been asked by management to find a way to do the following: 1. Outbound Mail contains specific words in the body/subject. -> Next Condition 2. All recipients are with company "A" or our own company. -> Send Message 3. Any recipient doesn't match above -> Reject Message. Repeat rule for Company B thru ... Anyone have any suggestions on how to go about this? It wouldn't be hard if I had a way to negate a condition but that doesn't exist.
