When you want to delete the first and original Mailbox Database in an Exchange Server 2010 (SP1) environment, you will receive an error that you cannot delete the database because of the fact that there are still mailboxes present. When you look in the Exchange Management console you probably won’t see any mailboxes that use the Mailbox Database that you want to delete. (If you do move them! ) The reason you are not able to delete the mailbox database is the fact that there are a couple of hidden mailboxes available, for instance the arbitration mailbox.
Last night I had to upgrade an Exchange 2007 CCR cluster to the latest Service Pack 3. Following the steps below, this error occurred while executing step 4.
The installation on node ‘CCR-Node2′ is inconsistent.
ConfiguredVersion = 184.108.40.206, 220.127.116.11 = UnpackedVersion. An upgrade might not have completed successfully.
Using ADSIEDIT.MSC browse to the user object and look for “adminCount” and set it either to <not set>.
Just a quick tip with thanks to an answer on Expert-Exchange.com.
Note, setting the value to zero is not working for me, setting the value to <not set> looks fine.
When migrating from Exchange 2003 often in the combination when a customer uses a third party utility to create user accounts you can get into trouble with trailing whitespaces in the Display name of the user. A user with a trailing whitespace in the display name cannot be managed by the Exchange Management Console (EMC) of Exchange Management Shell (EMS). The errors/warnings needs to be fixed.
WARNING: Object msexchangeblog.lan/Resources/Users/Johnson, has been corrupted and it is in an inconsistent state. The following
validation errors have occurred:
WARNING: The DisplayName property contains leading or trailing whitespace, which must be removed.
A quick tip found in a couple of forums. After installing Exchange 2010 into an Exchange 2003 environment, you need to manually add the new Exchange 2010 SP1 servers to the (legacy) “Exchange Domain Servers” group. You can find the group in the Users Organizational Unit. If you don’t add the servers to this group, you will receive an Object not found error when selecting a user (which resides on Exchange 2003) for a New Local Move Request.
Just bumped into some nice cool Exchange Server 2010 SP1 installation features . When installing Exchange Server 2010 with SP1 integrated into the source, an option is added to the installation.
From now you can automatically install the Windows Server roles and features that are a prerequisite for the installation of Exchange Server 2010 SP1. Just hit the checkbox in front of “Automatically install Windows Server roles and features required for Exchange Server”
While implementing Exchange 2010 SP1 and Microsoft Outlook 2010 I came across a bug in Outlook. When someone gives delegated access to their calendar, the delegate can add and modify appointments but not delete the appointments. The user receives this error; “Could not complete the deletion. The items may have been already deleted or moved. “. Continue Reading »
This week a customer had the following problem, some items in several mailboxes couldn’t be deleted in Outlook and Outlook Web App. When trying to delete the message in OWA, the following error was presented: “Some items cannot be deleted. They were either moved, already deleted, or access was denied”
Since Exchange 2010 it’s possible to assign a personal archive to a normal or shared mailbox. If you create a shared mailbox with a personal archive, and give a user Full Access Permissions, the personal archive of the shared mailbox and the shared mailbox become available in Outlook 2010 or Outlook Web App. This is a normal behavior.
If you want to give a bunch of users Full Access permissions to a shared mailbox, you can use a security group to give the access to the users who are member of the group. If you are member of the group you will be given access to the shared mailbox. You should expect that the personal archive also becomes available but unfortunately the permissions won’t flow down to the personal archive and the personal archive doesn’t come available in Outlook 2010 or Outlook Web App.
I don’t know if this is a bug or normal behavior, but if you know the possible answer don’t hesitate to drop me a line! In the mean while I will contact Microsoft to get more info about this behavior.
Update 18-1-2010: The Exchange 2010 SP1 Technet Help states the following: “In Exchange 2010 SP1, when you assign Full Access permissions to a mailbox, the delegate to which you assign the permissions can also access the user’s personal archive. Delegates must use Outlook 2010 to access the mailbox, and they must connect to an Exchange 2010 SP1 Client Access server for Autodiscover purposes….. When delegates use Outlook 2010 to access an Exchange 2010 SP1 mailbox, both the primary mailbox and the personal archive to which they have access are visible from Outlook 2010.” So I will be looking further and try to find out why it won’t work if you assign the full access permissions to a group.
Update 26-01-2011: The Microsoft Online Partner Support department reproduced the issue in their test environment and reported the issue to the Exchange Server Product Team for further investigation.
The function is there for ages, but I am always forget the following administrative feature.
Sometimes when a employee is unavailable for a longer time, due an extended holiday or sickness, you often will get the request to give access to the mail of the employee. You can do this like mentioned in an earlier blog, creating a Transport Rule to forward all email for one Exchange Mailbox to another person or you can add a forward address to an users mailbox.
You can do this by executing the following command line in the Exchange Management Shell;
set-mailbox -identity “John Johnson” -forwardaddress “email@example.com” -delivertomailboxandforward $true
In the Exchange Management Console you can find the option at the Mailflow Settings tab (Delivery Options) of an users mailbox.