One of the first problems I encountered after Installing Exchange 2013 on Windows Server 2012 ( and R2 ) was that my security log grew to 200k events in just a few days. Event ID 4625 Unknown user name or bad password coming from your Healthmailox usually under the name of HealthMailbox4d14f344f…@domainname. The process producing it was “C:\Program Files\Microsoft\Exchange Server\V15\Bin\MSExchangeHMWorker.exe”. The problem itself is a bit masked. On the client side you can barely notice any problems but your Event Viewer is a different story. The problem indicates problems with your Health mailboxes even without upgrading or migrating. It happens with new installs too. So searching the web I found the solutions which at this point are very limited for such new technologies as Windows Server 2012 R2 and Exchange 2013.
I found the solution of re-creating your Health monitoring mailboxes to be working well for me. Here is how :
Open Exchange Management Shell as Administrator and type :
Get-Mailbox -monitoring | Get-MailboxStatistics
As you can see the ItemCount is large. We will be removing these mailboxes but we don’t have the full names displayed here. So we will run the same command put “| fl” it.
Have you ever wondered why you can’t close down your additional mailboxes in Outlook, returning you this error :
Only to find out that your Account Settings tab is empty?
Well there is still hope. There are two options. You can just re-create the Outlook profile and hope that this fixes it or you can choose to explore more options. One of these options is called Auto Mapping and is introduced in Exchange 2010 and 2013.
It basically automatically adds any mailboxes you have Full Access to directly into your Outlook client. This is designed to reduce the administrative time to give such access especially for helpdesk teams where a single click can provide you with Full Access but you need still to do a remote session to the customer’s computer and add the mailbox into their Outlook.This is for the customers that don’t know how to do it themselves and believe me 90% of them don’t.
However touching the automapping cannot be done through the GUI and would need Shell. Here is the command :
Add-MailboxPermission -Identity User1 -user “User2” -AccessRights FullAccess -InheritanceType All -AutoMapping:$false
where User 1 is the mailbox owner and User 2 is the user receiving the FullAccess rights to User1’s mailbox. -AutoMapping:$false or true turns off and on the automapping.
Don’t worry if you run the command for users that already have Full Access to their mailboxes, it will still run the command properly.
For those of you who want to go even further here are the registry keys responsible for the Outlook profiles. Always backup your registry before editing !
Exchange 2013 Admin Center – Whether you like it or not, Exchange 2013 has ditched the all beautiful Management Console and has gone to a web based ( in a browser ) management called Exchange Admin Center. Still buggy for me in IE 10. Here is a video of going through the different menus without going deep in to the details.
Installing Exchange 2013 on Windows Server 2012 is new and interesting theme among the IT world nowadays and that’s why I tried installing it without reading what’s new and if anything else is required. I wanted to make a video of it and upload it unedited so it can show how a pure installation goes on without preparations and with any problems coming on the way. Installation is done on a virtual test machine with 8 GB of RAM. With a minimum requirements of 8 GB of RAM it was clearly not very optimal for running 2012 + Exchange 2013. Maybe a few more GB will make it run smooth. This time there are packages that need installing.