Is there a script I can use to get the quantity of emails in a week or month, or longer within my Exchange Org?
↧
Is there a script I can use to get the quantity of emails in a week or month, or longer within my Exchange Org?
↧
disable forwarding email to external address
Hi,
We are using Exchnage 2013 and management requested to disable forwarding email to external address.
How can disable it.
Kindly advice
Regards
Ashraf
Ashraf
↧
↧
Exchange 2013 Mailboxes Size Report
Hello,
Is it possible to run a report in 'Exchange 2013' that will list the usage size of each mailbox and export the results to a TXT or CSV file?
Kind regards,
Glen
↧
Investigate who removed the exchange server forwarding address from the mailbox
Anyone can assist me into looking who removed the exchange server forwarding address from the mailbox. Any tool or logs which can give me this information.
↧
EMS keeps losing connection to the server....which is itself.
I've been working more often these days with EMS than I used to. The EMS I'm using is directly on the Exchange 2013 server but I'm plagued with a recurring issue.
I'm typically using EMS for 3 to 4 hours sending commands through when suddenly it needs to create a new session. When it attempts to get a new session, it throws an error.
**********************************************************
New-PSSession : [MyExServer.MyDomain.com] Connecting to remote server MyExServer.MyDomain.com failed with the following error message : WinRM cannot complete the operation. Verify that the specified computer name is valid, that the computer is accessible over the network, and that a firewall exception for the WinRM service is enabled and allows access from this computer. By default, the WinRM firewall exception for public profiles limits access to remote computers within the same local subnet. For more information, see the about_Remote_Troubleshooting Help topic.
**********************************************************
It tries to establish a new connection several times but eventually fails. I can close the EMS window the open a new one but it still fails to connect. If I wait several hours or even sometimes till the next day, it will connect again and I can work for 3-4 more hours until it fails again.
What would cause the connection to work OK for a while then suddenly stop? Am I overrunning some buffer or something?
Frustrated is an understatement.
↧
↧
Send-As for Distribution groups couldn't resolve users in ECP
Hello,
We have this strange issue, when trying to set Send-As users in ECP. User is found, but upon applying the change an error pops up saying the trust relationship failed. The user and the group are both in the forest root domain. It's interesting that the Set-Adpermission cmdlet is working great. When assigning Send-As to a single user via ECP it is working too, we only have problems when using ECP+Distribution Group. The problem occured shortly after 2013 CU20 upgrade.
What has been done so far:
- checked replication - everything looks OK. There are some issues with Sysvol version mismatch on one DC in a child domain, but this seems unrelated.
- Set static DCs, GCs and ConfigDomainController to be the DCs in the same site as the Exchange servers
- run Setup.exe /PrepareAD
- Checked default users redirection - pointing to CN=Users,DC=domain,DC=com
What can be different in the operation of the PS cmdlets and the way ECP queries AD?
The error I'm getting:
38416 w3wp#MSExchangeECPAppPool124
00:00:00.0300094
View Entire Forest: 'True', Configuration Domain Controller: 'DC1.domain.com', Preferred Global Catalog: 'DC1.domain.com', Preferred Domain Controllers: '{ DC1.domain.com }'
Microsoft.Exchange.Data.Common.LocalizedException: Couldn't resolve the user or group "Username." If the user or group is a foreign forest principal, you must have either a two-way trust or an outgoing trust. ---> System.SystemException: The trust relationship between the primary domain and the trusted domain failed. at System.Security.Principal.NTAccount.TranslateToSids(IdentityReferenceCollection sourceAccounts, Boolean& someFailed) at System.Security.Principal.NTAccount.Translate(IdentityReferenceCollection sourceAccounts, Type targetType, Boolean forceSuccess) at System.Security.Principal.NTAccount.Translate(Type targetType) at Microsoft.Exchange.Configuration.Tasks.SecurityPrincipalIdParameter.GetUserSidAsSAMAccount(SecurityPrincipalIdParameter user, TaskErrorLoggingDelegate logError, TaskVerboseLoggingDelegate logVerbose) --- End of inner exception stack trace --- at Microsoft.Exchange.Configuration.Tasks.Task.ThrowError(Exception exception, ErrorCategory errorCategory, Object target, String helpUrl) at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target) at Microsoft.Exchange.Configuration.Tasks.SecurityPrincipalIdParameter.GetUserSidAsSAMAccount(SecurityPrincipalIdParameter user, TaskErrorLoggingDelegate logError, TaskVerboseLoggingDelegate logVerbose) at Microsoft.Exchange.Configuration.Tasks.SecurityPrincipalIdParameter.GetSecurityPrincipal(IRecipientSession session, SecurityPrincipalIdParameter user, TaskErrorLoggingDelegate logError, TaskVerboseLoggingDelegate logVerbose) at Microsoft.Exchange.Management.RecipientTasks.SetPermissionTaskBase`3.InternalValidate() at Microsoft.Exchange.Management.RecipientTasks.SetADPermissionTaskBase.InternalValidate() at Microsoft.Exchange.Management.RecipientTasks.AddADPermission.InternalValidate() at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b() at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)
7
System.SystemException: The trust relationship between the primary domain and the trusted domain failed. at System.Security.Principal.NTAccount.TranslateToSids(IdentityReferenceCollection sourceAccounts, Boolean& someFailed) at System.Security.Principal.NTAccount.Translate(IdentityReferenceCollection sourceAccounts, Type targetType, Boolean forceSuccess) at System.Security.Principal.NTAccount.Translate(Type targetType) at Microsoft.Exchange.Configuration.Tasks.SecurityPrincipalIdParameter.GetUserSidAsSAMAccount(SecurityPrincipalIdParameter user, TaskErrorLoggingDelegate logError, TaskVerboseLoggingDelegate logVerbose)
Ex19B768
False
0 objects execution has been proxied to remote server.
0
ActivityId: 6f442e62-1494-47ac-9428-9d026565f036
ServicePlan:;IsAdmin:True;
en-US
↧
Exchange 2013 stops receiving external email after about 8 hours
Hello,
Just installed 2013 excahnge server 3 days ago. We noticed after the first night that we did not receive any external emails throughout the night. I could not find anything wrong with receive connectors. Telnet works internally when this happens but NO access from public side testing with telnet. After I reboot the exchange server everything functions just fine and normal for about 8 hours until it happens again.
I dont know what to check or look for at this point. Very new to exchange 2013. Any kind of advice would be helpful at this time.
It is not a firewall issue. Same firewall and set of rules that we use for other/old mail servers. We only have 1 exchange server that has all roles.
Lead Pusher
↧
Event ID 4023 and 4028: Users Iphone are getting error cannot get mail. The connection to the server failed.
Process w3wp.exe (AirSync) (PID=9504). The budget for user 'User_iPhone' is locked out until 04/10/2018 10:27:14. Max Burst: 480000, Recharge Rate: 1800000, CutoffBalance: -600000
These are events i am getting in exchange server event logs and while checking user mailbox throttling policy i see blank:
Multiple users are getting this error.
Please advise me how to fix this issue.
Ankit Singh
↧
Exchange 2013 OAB issues
Currently around 50% of the time our users are unable to access the GAL from Outlook. Users with Outlook cached mode cannot download the OAB (event 27 OAB download failed). Users on Citrix without cached mode get an error "The operation failed" when they try to access the address book. If a user closes and opens Outlook the GAL will either work or not work until they next close and open Outlook. The failures do not seem to be affected by who the user is or what database they are on. This has only started happening recently, shortly after we introduced some Server 2016 DCs but I don't know if this is just a coincidence.
Our Exchange environment consists of two CAS servers and two DAG members all running Exchange 2013 CU21
So far we have tried -
Restarting Exchange mailbox assistants service and BITS service
Restarting both CAS servers
Updating Offline address book
Activating database containing OAB generating arbitration mailbox on the other DAG member
Create new Offline address book
Create new arbitration mailbox for OAB generation
Checked autoconfiguration OAB URL
Checked permissions on OAB website in IIS
We are starting to run out of ideas. Any assistance would be greatly appreciated.
↧
↧
Exchange 2013/2016 coexistance OWA not working externally
We are running Exchange 2013 CU15 Hybrid. We have recently installed Exchange 2016 CU4 in our environment. Created virtual directories same as Exchange 2013. Everything is working fine internally. OWA user can login to their mailboxes either on Exchange
2013 or 2016. But external OWA users whose mailboxes are on Exchange 2016 gettingbad request error. Users with mailboxes on Exchange 2013 can login fine.
↧
MSExchange Mailbox Replication 1008
I have two mail servers 2016 + one mail server 2013 in another site, it logically keeps the network archive.
Recently import/export mailbox stopped working
In Windows log: MSExchange Mailbox Replication с ID 1008
The mailbox replication service has deleted a lost move request.
Mailbox Database GUID: d927f5fe-a0de-4965-bcd4-0178087649b9
Mailbox GUID: 08320a19-5ab6-48ce-b40e-90279632213a
Mailbox ID: d927f5fe-a0de-4965-bcd4-0178087649b9\08320a19-5ab6-48ce-b40e-90279632213a
Verification message: Could not find valid index entry for query 'd927f5fe-a0de-4965-bcd4-0178087649b9\08320a19-5ab6-48ce-b40e-90279632213a'.
Get-MailboxExportRequest/Get-MailboxImportRequest status is stuck in Queued
Get-MailboxImportRequest | Get-MailboxImportRequestStatistics -IncludeReport | flCouldn't find a move request that corresponds to the specified identity '08320a19-5ab6-48ce-b40e-90279632213a'
New-MailboxRepairRequest -databasedid not give a result
↧
CAS Server in Maintenance Mode accepting Outlook Anywhere connections
Hi Everyone,
I'm having some trouble understanding what maintenance mode on a Exch2013/2016 CAS server does.
Once I place a server into maintenance mode, I can see all the Component states set to Inactive (RPCProxy, OWAProxy etc), I'm still seeing the CAS server in Maintenance Mode servicing Outlook Anywhere traffic via the IIS logs with RPC_IN_DATA/RPC_OUT_DATA /rpc/rpcproxy.dll entries.
Its not a huge deal as we have a common namespace and a load balancer, but I'm curious to know why you cannot stop all traffic when an Exchange Server is in maintenance mode?
Thanks,
BTL
↧
Configuring standby CAS in Exchange 2013
Hello
We have Exchange server 2013 environment with single CAS server. To avoid issues, we have now configured another CAS server in the same environment.
As we do not have load balancer in place, we plan to use this secondary server as a standby. Basically if the primary CAS server goes down, we plan to manually point DNS to to the secondary server and make it primary.
Basically my concern is, if we provide network connectivity between this secondary CAS server and our clients, will requests start going to this secondary CAS server and cause connectivity issues?
Also will this concept work in case of issues with the primary server/
Thanking You
↧
↧
Exchange delivers old (non-existent) cert
Hi.
I encountered a strange problem when renewing a certificate that is about to expire,
I encountered a strange problem when renewing a certificate that was about to expire:
As usual, the CSR was created, the Cert imported from Comodo, services enabled (all via ECP), the key exported, the Cert imported from the second DAG member, checked to see if OWA was delivering the new one - and the old Cert deleted on both DAG member servers.
Which I haven't checked:
What it looks like for Outlook clients on PC and Mac and here it comes:
You still get the old (expired) certificate that no longer exists on both servers:
- local certificate store
- List in /ecp => Certificates
- Get-ExchangeCertificate -Server xxx | Format-List
- IIS Management Console
In all these places I see only the new one with the right bindings and OWA / ECP do deliver this one. Why do Outlook-Clients getting that old one?
What am I missing?
(Of course rebooted both DAG members and clients, too. Just in case there is a cache somewhere...)
Thank you - F.One
↧
Error is [0x80004005-00000000-00000000]
HI,
Some users are getting below error when sending mails to external accounts. we have exchnage 2010 and issue occurs only when sending mails outside the org.
The following recipient(s) cannot be reached:
'abc@xyz.com' on 6/7/2013 11:20 AM
This message could not be sent. Try sending the message again later, or contact your network administrator. Error is [0x80004005-00000000-00000000].
Some articles i found were pointing to max. recipients limits issue. But the issue happens even when sending mail to a single recipient ( SO i guess this is not the issue here ). Also mails are going out fine when sent throught through OWA.
Recreation of outlook cache profile also seems to resolve the issue.
Exchange Admin
↧
Import OST file to Exchange
Hi
If I have OST file and I want to import this file to a mailbox user
what should I do
Mahmoud
↧
New user email - Recreated: 550 Error
Hi,
We have an issue where a new users email was created, deleted and recreated. For some internal users it works because they never emailed her but other had a bad cached copy of her email it seemed.
Diagnostic information for administrators:
Generating server: ERA-EX1.server.net
IMCEAEX-_o=EMMS_ou=Exchange+20Administrative+20Group+20+28FYDIBOHF23SPDLT+29_cn=Recipients_cn=233bfde1c7c947dea874b9070b1653cc-Melissa+20Burciaga@server.net Remote Server returned '550 5.1.1 RESOLVER.ADR.ExRecipNotFound; not found'
However, some users are still having the issue after we cleared their cache in Outlook.
From the server I ran a couple shell commands to update the address book and some users still get a bounceback.
Get-AddressList | Update-AddressList
Get-GlobalAddressList | Update-GlobalAddressList
Are there any commands I'm missing that would force an update on the database so that the SID of the first email would be cleared and users emailing her going forward get the correct email address?
Any help or even opinions on the issue would be appreciated.
↧
↧
Healthset Errors after CU 20 Upgrade
Hello everyone,
I am getting Compliance health set unhealthy (ComplianceOutlookLogonToArchiveRpcCtpMonitor) andOutlook health set unhealthy (OutlookRpcCtpMonitor) Errors after CU20 Upgrade.
I recently Upgrade the Exchange server from CU 5 to CU 20. When I received this alerts I recreated the HealthMailboxes Twice but still getting it. Error is the same as mentioned in this article.
I ran this command on all 4 servers and see some differences.. I think my Exchange Servers are not creating correct HealthMailboxes. See the Display name and the corresponding Database name. Server names are mismatch.
Get-Mailbox -Monitoring | ?{$_.DisplayName -like "*-ExchangeServer01-*"} | ft name,displayname,database
Name, DisplayName, Database
HealthMailbox9a6e570630d54409bc494cdc9f8ce24c HealthMailbox-ExchangeServer02-010 MB01-DB05
HealthMailboxc80b8ed9e3794f4696fc1908f4f3a78e HealthMailbox-ExchangeServer03-002 MB02-DB10
HealthMailbox6c47a1741d284ee19ef8fac85125a378 HealthMailbox-ExchangeServer03-003 MB04-DB16A
HealthMailbox928f7139b3504766b89096253381c966 HealthMailbox-ExchangeServer03-004 MB01-DB16
HealthMailbox47420e751ad044e6a47ed3d66220f81f HealthMailbox-ExchangeServer03-005 MB01-DB07
HealthMailboxf34df20287304dc7bf39a7c7f9272971 HealthMailbox-ExchangeServer03-006 MB01-DB17
HealthMailboxc78b6a8099a54c8bb77c614584ae7f87 HealthMailbox-ExchangeServer03-007 MB04-DB05A
HealthMailbox22a5bed8a4814cf38107d5173c5c2c83 HealthMailbox-ExchangeServer03-008 MB02-DB12
HealthMailbox92dec56e500d43e2bb1a01ce643053bf HealthMailbox-ExchangeServer03-009 MB02-DB03
HealthMailbox11cfc1c912254917be3ecc9cc2b2e84a HealthMailbox-ExchangeServer03-010 MB01-DB25
Correct one looks like this
HealthMailbox3be7bd9fd33143e6abc0c36c08b2e00e HealthMailbox-ExchangeServer03-MB03-DB16 MB03-DB16
HealthMailbox39d1d72c1998435e950e54dce9b4209d HealthMailbox-ExchangeServer04-MB04-DB17A MB04-DB17A
ZakBhai
↧
Office 365 / Exchange 2000 Hybrid Setup - multiple connected domains
We have an Exchange 2000 / Office 365 hybrid setup. We have had this in place now for about 4 years. We have all mailboxes migrated to Office 365. The admin of these mailboxes is still done via the local Exchange servers Exchange Management Console and synched via AD Connect. Since creating this hybrid setup, the company has purchased other businesses which we have added to the hybrid setup. These businesses have kept their own domains but have used our hybrid setup for email using the Office 365 / Hybrid system. So they have their own domain completely separate to ours but share our email system.
The IT guys in these other domains have to remotely login to our Exchange server when they have to create an account or make some changes that cant be done via the Office 365 portal. Also, remote users not connected to the domain cannot change their passwords as they are not connected to our domain. We have an ADFS website setup so that they can change their passwords but this isn’t forced like it is when connected to a domain with group policy. It causes problems for both users and admins to maintain passwords, manage emails and so on.
Essentially what I am asking is, is there an easier way to do all this, what other options do I have? We need to make things easier for our overseas IT administrators and also password changes / forced password changes more effective.
Thanks all in advance.
↧
Issues changing permissions on Exchange 2013 distribution group
Issue, when user “AdminOne” (Exchange Admins, Exchange Organization Admins, Domain Admins, Enterprise Admins) tries to change the “Send As” permissions of any distribution group they get an error of:
“Couldn't resolve the user or group "User_to_add." If the user or group is a foreign forest principal, you must have either a two-way trust or an outgoing trust.”
This even happens when “AdminOne” tries to add themselves to the “Send As” permissions.
However, “AdminOne” can change other properties, like the actual members of the distribution group without errors. Now, “AdminTwo” (Exchange Organization Admins, Domain Admins) can make the same attempted changes (add the same users) to the same distribution groups without any errors.
Does anyone know what could be causing this or how I can even start troubleshooting it?
We are on Exchange 2013 using the Exchange Control Panel; both admins are in the same domain / forest / enterprise.
↧