Create a CSV file that contains the following columns: ExternalEmailAddress Name Alias FirstName LastName OrganizationalUnit Then from the Exchange Management Shell run the following command: Import-CSV C:scriptsMyCSV.csv | ForEach-Object{New-MailContact -ExternalEmailAddress…
Category: <span>Exchange</span>
I just created some new databases on our Exchange 2010 server and moved some BlackBerry users to those new databases. I started getting calls from people saying they weren’t getting emails on the BlackBerry’s. I did some checking and found some event logs on the BES server that said the users could not be started. I did a search and came across a KB article on BlackBerry’s web site. Apparently, you need to run the following command on your Exchange servers when you add new databases. It will grant the needed permissions to the database and its users for the BES Admin account. I thought this was done globally when we setup the Exchange 2010 server, but I guess that isn’t the case.
So we have just migrated our users over to Exchange 2010 a couple of months ago. When we started we purchased a new server and set it up with Windows 2008 R2 and Exchange 2010. The plan was to migrate all of our users from the old Exchange 2007 server to the new Exchange 2010 and then rebuild the old one with Exchange 2010 also so we could take advantage of the new DAG options. It all sounded easy enough.
We had a user that had a very large mailbox (313,000+ items and a size over 50GB) and we couldn’t figure out why. My first thought was that it was a corrupt mailbox and it was just reporting the wrong size. However, when I moved the mailbox to a new server the size remained the same and the move didn’t show any corrupted messages.
I sat down and looked at the mailbox on the users computer and checked the Inbox, Sent Items, and Deleted Items. None of those had any large messages. The largest message may have been 1MB. The user did have a lot of folders, but I didn’t want to take the time to go through each one individually and try to figure out where the messages were at.
Up until today at work we didn’t have any size limits set for our email. I know this is unheard of now a days, but we couldn’t get them approved. We didn’t run into a lot of problems, but would have someone try and send really large attachments once or twice a year which would slow things down for awhile. Today; however, that changed. We had a user try to send an email that had 1.6GB worth of attachments. So once we got Exchange back up and running limits were put into affect.
I was looking in Event Viewer on our Exchange 2007 server. I noticed the following entries in the Application Log.
Event ID: 12014
Source: MSExchangeTransport
Description:
Microsoft Exchange could not find a certificate that contains the domain name ourserver.domain.local in the personal store on the local computer. Therefore, it is unable to support the STARTTLS SMTP verb for the connector From PureMessage with a FQDN parameter of ourserver.domain.local. If the connector’s FQDN is not specified, the computer’s FQDN is used. Verify the connector configuration and the installed certificates to make sure that there is a certificate with a domain name for that FQDN. If this certificate exists, run Enable-ExchangeCertificate -Services SMTP to make sure that the Microsoft Exchange Transport service has access to the certificate key.
I should start by expanding the title a bit. This isn’t just about how to create a Distribution Group in Exchange 2007. It goes one setp further and explains how to set permissions on that Distribution Group so that more than one user can edit the group membership. Doing this allows a few end users (non-domain admins) the ability to mangae group memberhip without having to have a Domain Admin/Exchange Admin make the changes.
I had a user call a while back and say they were unable to login to OWA. They could get to the login screen, and would type their username and password, but when they clicked login they would get the following error:
“A problem occurred while trying to use your mailbox. Please contact technical support for your organization.”
If they clicked the Show Details button, this is what was displayed:
We haven’t run into this problem yet, but I don’t know how many of our users have iPhones and sync with Exchange. This will just be nice to have listed.
Symptoms
Immediately after updating to iOS 4, some users may notice that Exchange ActiveSync Mail, Contacts, or Calendars do not sync, or sync very slowly. In addition, some Exchange Server administrators may notice their servers running slowly.
Yesterday and today I worked on getting a new server setup running Sophos PureMessage 3.1.0. We have used PureMessage for several years and have had pretty good luck with it when it comes to blocking spam. The interface hasn’t changed much since the last upgrade.
We run PureMessage on a seperate box and don’t run it on our Exchnage server. This way it helps keep the spam load isolated and doesn’t hurt performance on our Exchange server.