-
The Active Directory schema isn’t up-to-date, and this user account isn’t a member of the ‘Schema Admins’ and/or ‘Enterprise Admins’ groups.
I am busy installing Exchange 2016 in a test environment and received the below error when running Setup.exe /IAcceptExchangeServerLicenseTerms_DiagnosticDataON /PrepareSchema when trying to extend the domain schema. “The Active Directory schema isn’t up-to-date, and this user account isn’t a member of the ‘Schema Admins’ and/or ‘Enterprise Admins’ groups.” Thing is, my account is part of the Schema Admins and Enterprise Admins group. I then found the solution from this post (thanks Andy!) In short, open the group membership tab on your account in Active Directory Users and Computers and then check which group is set to default, then click on Schema Admins and click on Set Primary Group to make…
-
free/busy not working between EOL and on premise Exchange
We had an issue after adding a new domain to our tenant using the Hybrid Configuration Wizard which removed the URI and URL strings in the availability settings in Exchange Online. That was resolved but 2 days later free/busy from Exchange Online to on premise Exchange users broke again. We had to add a new SAN in the certificate for Exchange and suspect that the Federation Metadata did not properly update. One of my colleagues found this article which pointed us to the problem and advised us how to resolve the issue. In short running: Test-FederationTrust -UserIdentity yourcredentials showed the issue. To resolve my colleague ran: Get-FederationTrust |…
-
Unable to send mail through specific Send Connector
I’m finding it difficult to give this post a proper heading but hopefully the tags in the post would have led you to the solution of this problem I experienced. We have a specific Send Connector in Exchange 2016 that sends mail to one of our other companies in a different forest. I noticed that only on one server the queue for mail destined to this domain was queueing. The error in the queue destined to the other domain was stating that it failed to connect. I tested with telnet to the VIP IP and could not connect to the VIP on port 25. After restarting the Transport service and…
-
This operation requires a unique source object, but multiple objects have been found. Please remove any wildcard characters and check the data source for corruption.
You receive an error as per below when trying to restore a user’s mailbox in Exchange from a Recovery Database: This operation requires a unique source object, but multiple objects have been found. Please remove any wildcard characters and check the data source for corruption. I’m currently busy with a hand over at work and the engineer that will be taking over from me ran into this error when trying to restore a user’s mailbox. The Recovery Database has been created and the data has been restored to the database. The database is mounted and he was trying to run the below from the Exchange management Shell: Restore-Mailbox -Identity “UserSurname,…
-
There is currently no route to the distribution group expansion server
You see the error “There is currently no route to the distribution group expansion server” in a stuck message from your Exchange Hub Transport server submission queue. To resolve this: Make note of the distribution group in the recipient information tab. Search for the Distribution Group in Exchange Management Console Right click on the group and choose properties Go to the Advanced tab Untick the box next to “Set expansion server” You might have to restart the Hub Transport or SMTP service depending on your Exchange version. We found this happened because the Expansion server was removed from the environment and not accessible. Another cause could also be the deletion…
-
Unable to connect a disconnected mailbox – User not found error when trying to connect a mailbox to a user in Exchange
We’ve had a few instances where we need to disconnect a mailbox and reconnect it to a new user account for a user. This should be easy right? Well not always. It’s happened more than once where we try to use the Exchange Management Console to connect the mailbox to the user account but Exchange can’t find the user account. Have a look in Active Directory and the account shows up. You then try to connect the mailbox to the user account using the Exchange Management Shell with the same results. user not found. See below on how to get this issue resolved: 1. Open adsiedit.msc (start, run and type…
-
Meeting requests sent to a room mailbox, replaces the Subject, with the Senders name
We received a call today where a meeting request sent to a Room mailbox shows the meeting organiser’s name in the subject line. This can be rectified by running the following: Exchange 2010/2013: Set-CalendarProcessing -identity “meeting room name” -DeleteComments $true -AddOrganizerToSubject $true -DeleteAttachments $true -DeleteSubject $true Exchange 2007: set-mailboxcalendarsettings -identity “meeting room name” -deletesubject $false -addorganizertosubject $false Hope this makes your life a bit easier.
