I am trying to find a way to script the purging/emptying of all "sync issues" folders in mailboxes on our Exchange 2010 server.
Search-Mailbox appears not to have a way to select a users folder.
Any ideas/suggestions are welcome.
I am trying to find a way to script the purging/emptying of all "sync issues" folders in mailboxes on our Exchange 2010 server.
Search-Mailbox appears not to have a way to select a users folder.
Any ideas/suggestions are welcome.
Hi Guys.
I am having this issues which came about after the server went off due to environment power issues. Kindly advice on how to go about it.
Process MSExchangeHMWorker.exe (ExHMWorker) (PID=10824). WCF request (Get Servers for asterisk.co.ke) to the Microsoft Exchange Active Directory Topology service on server (TopologyClientTcpEndpoint (localhost)) failed. Make sure that the service is running. In addition, make sure that the network ports that are used by Microsoft Exchange Active Directory Topology service are not blocked by a firewall. The WCF call was retried 3 time(s). Error Details
System.ServiceModel.Security.SecurityNegotiationException: Either the target name is incorrect or the server has rejected the client credentials. ---> System.Security.Authentication.InvalidCredentialException: Either the target name is incorrect...
Please share some real time issues, causes and troubleshooting approach for Exchange serve/ Active Directory/Outlook
that likely to ask in an interview
What are the daily duties of an Exchange on premise admin
What are the common issues facing and how to approach client issues
could someone share scenarios of exchange server disaster recovery
database recovery scenarios
disaster recovery
best practice approach for disaster recovery
Hi Spiceheads,
Not sure if anyone else has come across this but we patched our exchange 2013 VM running on server 2012 R2 in July and also installed .net 4.8, since then we have noticed that after restarting the server we see an issue with the Microsoft Exchange Active Directory Topology service not starting and if it does then all of the other MS Exchange services need to be manually started.
This is causing us issues and were wondering of anyone else has come across this, we are seeing Event ID 4027, MSExchange ADAccess (Process MSExchangeHMHost.exe (MSExchangeHM) (PID=1332). WCF request)
Thanks
I just made a compliance search and when I look at the attributes of the search, the timestamps are incorrect by 5 hours.
For instance:
CreatedTime : 8/18/2020 10:38:19 PM
LastModifiedTime : 8/18/2020 10:38:19 PM
JobStartTime : 8/18/2020 10:38:20 PM
JobEndTime : 8/18/2020 10:38:34 PM
Where is the configuration for timezone coming from? The server time and timezone is correct. The "get-date" command in powershell shows me the correct time and date on the server.
[PS] C:\Users\ciscoguru\Desktop>get-date
Tuesday, August 18, 2020 5:47:45 PM
Thanks for any help!
Hi,
Am unistalling the original mail server (2016), well original in that the mail was migrated to it from 2013 a while ago. It has been giving a lot of issues in migration of ailboxes as in another post. We solved this by putting in anew 2016 server.
I am now trying to uninstall the first one, has been an adventurre but last hurdle is this error in prerequisites:
"This computer is responsible for expanding the membership of 1 distribution groups. These groups must be reassigned to another server before Setup can continue."
All distribution groups are eithed deleted or moved to O365, in fact there is only one Distribution List ther that was just re-built on O365.
All mailboxes, resources, contacts etc are all either on the new server or in O365
THe EAC on this server keeps giving the error that something went wrong try again in a minute so...
I have an Exchange server and the server has OS problems, Can I create and new Exchange server and transfer all the emails and decommission the server?
Dear all,
I have an issue that looks like the one discussed here:
https://community.spiceworks.com/topic/2163155-exchange-management-shell-error
We're using Exchange 2016, and after upgrade on CU17, some of applications, that apparently use PowerShell to connect to Exchange (such as Adaxes Administrations Console and Acronis Backup) returns the same error: "Connecting to remote server failed with the following error message: The WinRM client received an HTTP status code of 301 from the remote WS-Management service."
On MS Technet I've been advised to disable HTTP redirect and URL rewrite for Power Shell website, but I have them disabled both.
In discussion on the link above,NDaszkie said, that he sikved the problem by removing redirection in web.config. Shame on me, but I have no idea what web.config is and how to modify it.
Could you help...
I am trying to plan a domain migration and am getting hung up on Exchange. Exchange lives in the old domain, and I'd like users/computers in the new domain to be able to access it. I have the users synced (with SID history) to the new domain. If I stand up a computer in the new domain and try to setup Outlook, it does not work, I'm told Outlook "could not setup my account automatically"
Is it possible for a user in another domain to access Exchange via Outlook in another domain? If so, what do I need to change to allow this to happen?
There is a two-way trust that's been setup, and I've also tested with linked mailboxes, but those have the same problem.
My company uses Mimecast. We are not the administrators of it. I am the administrator of the on-prem Exchange server however. There is currently a send connector to route all of our email through Mimecast, and it works. The problem is that we have some big Lanier MFCs that have a scan to email feature. I have configured these with a generic copier@domain.com email address and used receive connectors so no authentication is required. This feature works internally, but my users are unable to scan documents to email for external email addresses because the copier email address does not exist in Mimecast. If I could admin Mimecast, I would just permit those emails. Since I can't I'm wondering how to set up a send connector to route all outbound mail to Mimecast except the generic copier email address.
Hi,
My question is as per best practices exchange server 2016 standard edition maximum database size should be High Availability (replicated) a maximum of 2000 GB (2 TB) per database and Exchange Standalone (non-replicated) a maximum of 200 GB per database.
based on the above if i have a non replicated single server instance of exchange 2016 std edition which can maximum support 5 databases mounted at same time then maximum it can reach 1000 GB?
Last night I did the following task, then my Exchange 2016 is malfunction!
Environment: Exchange 2010 on Production, Exchange 2016 new install co-exist for migration
What I do on yesterday:
1. Move Exchange 2016 Arbitration mailbox to the new database (I do not know when finish)
2. Installed GFI MailEssential (After the install is still running and working)
3. Install Symantec Endpoint Protection Client 14.2
After finish the Endpoint Protection Client, I found out I can't log in to ECP, OWA, and Powershell.
Arbitration mailbox from C: default database using ECP Migration move to E: drive new Database.
Powershell can't connect to EX2016 and got error, then automatically connect to Exchange 2010
ECP and OWA also got error!!
Hi folks,
I'm new to this exchange challenge so I need your guideline please.
The scenario is that In my organization there is certificate that almost comes to is end. this certificate is "*.domain.local" and it using for the Internal URL (OWA, MAIL, Autodiscovery...) but after some checking i find out that the CA publisher was an old server that no longer exit and I have no way to revoke the certificate.
So basically I have two option: One, is to install a new CA and publish a new * Certificate.
The second is to combine between the two URLS External and the Internal.
My environment look like this:
Internal-URL: Autodiscovery.domain.local
External-URL: Autodiscovery.domain.org.il
The External is a different from the Internal.
After some searching I find out this script for converting the Internal URL to External:
Last night I did the following task, then my Exchange 2016 is malfunction!
Environment: Exchange 2010 on Production, Exchange 2016 new install co-exist for migration
What I do on yesterday:
1. Move Exchange 2016 Arbitration mailbox to the new database (I do not know when finish)
2. Installed GFI MailEssential (After the install is still running and working)
3. Install Symantec Endpoint Protection Client 14.2
After finish the Endpoint Protection Client, I found out I can't log in to ECP, OWA, and Powershell.
Then I quickly uninstall the Endpoint Protection Client, but the problem still keeps the same.
----
Arbitration mailbox from C: default database using ECP Migration move to E: drive new Database.
Powershell can't connect to EX2016 and got error, then automatically connect to Exchange 2010
ECP and OWA also got error!!
Hi, we are currently experiencing an issue where all external emails to our distribution group are getting a bounce back. Some but not all internal emails are receiving this bounce back to. Another strange thing is that I can send emails to the group using OWA just fine.
Below is the error message they’re receiving.
#550 5.1.1 RESOLVER.ADR.ExRecipNotFound; not found ##
Researching moving from our current hosting provided to a new one that offers Hosted Exchange. Have about 20 users and our current provider is just POP and IMAP. We would like something more robust for business use. I know I can just point my Domain Registrar to the new ISP. My question is what about emails? I assume new "accounts" will have to be setup on the new ISP. What about messages in their current inbox. Just export them in Outlook, setup new account and import old messages? What about downtime while the name is getting pointed to the new ISP? Any other pitfalls that I may come across? Suggestions and tips would be appreciated.
We added a signed SSL cert to an exchange server and users are unable to connect via outlook remotely. I updated the bindings in ISS on default and back end to the new cert. Local users can connect. the domain the server is in ends in .local. The .com has been added to external servers in virtual directories and I ensured the paths were correct. Also added the correct external path on the server edit under outlook anywhere. No issues with ECP or OWA remotely. Seems to be no issue with phone clients its just outlook the error is login failed. we are using forms based domain\username.
This is exchange 2019 and at this point I am rather lost on what to try next. SSL is from ssl.com
Hello
how i can change the default maximum allowed recipient policy for all users form Exchange online
regards