I was asked to find out which user in the organisation was receiving the info@ email for my company the other day. Without wanting to go and check on each user manually, you can simply run the command below form the Exchange Powershell command line.
Exchange 2007 and Exchange 2010: – simply replace email@domain.com with the email address you are looking for.
get-recipient | where {$_.emailaddresses -match “email@domain.com”} | select name,emailaddresses
We had a problem where any new user mailboxes that were added to the Exchange server were not appearing in the address books of Outlook 2007 clients running in cached mode.The address book was up to date in OWA, but our cached Outlook clients wouldn’t update even after forcing a download of the OAB. If I took the Outlook 2007 client out of cached mode, they would see the latest address book.
The way we fixed this was by going into Exchange Management Console (EMC) , Organization Configuration , Mailboxand then clicking on the Offline Address Book tab. Double click on the Default Offline Address Book then click on the Distribution tab and untick “enable web based distribution” .OK out of this menu, then go back in and retick the “enable web based distribution” , add the servers that you want to use for web distirbution and OK back out again.
You should now have an updated OAB when you download it again.
Another point to note is that if you have multiple Exchange servers is that you should have all of the servers are added in for “web based distribution”
My task today at work was to consolidate a clients two exchange 2003 servers down to a single meaty Exchange 2007 server.
During the course of the migration I checked the default recipient policy to see what domains where included.
For the purposes of this post, lets say that the client had two domains, abc.com and abc.co.uk, as well as their local domain, abc.local.
I noticed that the default domain was set to be abc.co.uk, but that each individual user had had their email address set manually to abc.com, and the option to not inherit settings enabled…
After I migrated the mailboxes over, I noticed that the new server didn’t pick up on these settings and reset each users default email address to be abc.co.uk…
Not a problem so much as a foible.
Another day… another seemingly random problem with Exchange 2007.
In case you didn’t see my post yesterday, I am currently migrating a client from Exchange 2003 to Exchange to 2007.
The install went ok, and last night I moved all users mailboxes across to the new server.
Happy that everything had gone to plan I visited the client expecting no problems to have be reported.
However, no user had received any mail in outlook since the previous day, including e-mails sent internally, but they were all receiving their emails on thier BlackBerry handsets (which were all setup on BIS to get mail from OWA).
I logged onto the exchange 2007 box, expecting to see that some of the exchange service were not started, but they were all on and working.
I sent a message to myself from one users Outlook, and it arrived in my own (external) mail account fine.
I sent one back…. it never arrived…
Then i noticed that her Outlook was displaying a message in the bottom right hand corner stating that it was connected, but that it had last updated at 9am, but it was now actually 9:40am.
I logged into Outlook web access as an affected user, and low and behold my reply mail was sitting there, just not appearing in her outlook.
So outlook was connected, but not updating. The mail was actually getting in and out fine, just not into Outlook.
It ws then I noticed a heap of “sync errors” in outlook. Reading the message, it indicated that I had too many emails open, and an error code that when googled pulled up a single result.
That single result did however lead me to another article that helped me solve the problem.
The problem was that all users were in cached mode…. each open folder, additional mailbox, calendar reminder etc constitutes a “session” between Outlook 2007 and Exchange 2007.
In thier wisdom, Microsoft have hard coded a very small number of permitted simultaneous sessions, so as to try and stop the Exchange server becoming overloaded…
You can of course override this setting, but adding some items to the registry… which I did and it solved the problem immediately.
The Microsoft article I followed is here: http://support.microsoft.com/kb/830836
I had a strange problem at work today when installing a new Exchange 2007 server.
A client of mine has an existing Windows 2003 Small Business Server running Exchange 2003, and even though there are only 12 users, their mailstore is approaching 70 GB.
As there is nothing wrong with the existing SBS box the recommendation was made to put in a separate box running Exchange 2007, to allow them to use the additional storage limits and extra functionality that Exchange 2007 offers them.
Running Exchange 2007 in an SBS environment is not your every day occurance, but tehre is no reason not to do it.
Having run up my new box running Windows 2003 Server Standard Edition R2 (64 Bit), promoted it to be a domain controller, made the box a global catalogue server, moved the schema master role over (as you must do when you are installing it into an SBS environment) I went about installing Exchange 2007.
Unfortunately I got a strange error message half way through the checking process stating:
“Access control list (ACL) inheritance is blocked”
After Googling the problem, I came across a Microsoft Technet article that indicated that the problem was being caused by the fact that one or more of my Public Folders (on the Exchange 2003 box) was not inheriting permissions and thus the install was failing.
http://technet.microsoft.com/en-gb/library/bb643112.aspx
I opened up Exchange System Manager on the SBS box and tried to navigate to the “Folders” section but couldn’t find it. I restarted the system attendant service but it still did not appear.
I knew that public folders existed and were working, as I could access them in Outlook, but Exchange System Manager seemed unable to find them or display them.
Following the article, I opened up the registry editor, added the suggested DWORD and BINGO… back came my “folders” section in Exchange System Manger…
Just as the article sugested, permissions were not propergating to any of the Public Folders…
I ticked the box to allow permissions to propagate down, went for a cigarette, then re-ran the setup wizard which completed perfectly.
Hopefully this might help someoene else in the future.
The Windows 2008 built in backup is not exchange aware as you may or may not know. This means that whilst you can back up and restore the data on your server, it will not clear your Exchange transaction logs.
To get rid of these logs and to save some disk space, it may be an idea to periodically turn on circular logging to get rid of the log files taking up your valuable disk space. To this, follow the steps below.
Log into the Exchange management console, then in the conolse tree on the left, expand Server Configuration and then click on Mailbox.
In the bottom right pane, right click on the storage group that you wish to modify and choose properties, then tick the box that says Enable circular logging.
To make this change apply, you need to either restart the Microsoft Exchange Information Store service, or mount and dismount the storage group you just modified.
You can then simply go back in and re-tick the option once the logs have gone from the folder containing the transaction logs for that storage group.