iPhone users: from Network World this morning is an article addressing reported syncing issues to Exchange with the new Apple IOS 4.0 for the iPhones. The article points to a current workaround that is posted on Apple’s site, and indicates a more “complete” solution is required or forthcoming.
The article goes on as to suggest that there is a further issue that is causing high network/usage spikes, and that this may force some companies to stop allowing iphones to retrieve emails!
Update: the Microsoft Exchange Team has addressed this issue from their perspective at their Team Blog Site.
I hear it all the time … my customer wants an SBS server, but they don’t want to use Exchange. I don’t know about you, but the only reason I can think of why either the customer or the IT consultant would suggest not using Exchange is because they’ve never used it themselves, and therefore are scared that it’s too difficult to install or manage. I have installed SBS servers for almost 9 years. I barely know how to spell Exchange, yet I find Exchange very easy to manage.
But, if you still need convincing, here is a short list of 8 reasons why you should consider using Exchange features with your SBS server.
- Group calendering
- Shared public folders
- Centralized storage and management of all emails
- Easy recovery of deleted emails
- Email archiving
- Centralized scanning of email for spam/viruses BEFORE they reach the user’s inbox
- Access to email remotely via OWA
- Access to email via ActiveSync for cellphones and PDA’s
Remember, if each user is using a POP3 account via Outlook, then those emails are generally only being stored on the user’s computer, and therefore they are probably NOT being backed up. With Exchange, the emails are being stored on the server as well as being cached onto the user’s workstation. Sbs and Exchange make a great team!
I’ve blogged previously about Exchange 2003 IMF (Intelligent Message Filter). One of the somewhat hidden features of Exchange 2003 and IMF is the ability to implement a custom weighting feature via an XML file. This feature first came out in IMF v2. MsExchange.org has a good article on how to implement the custom weighting feature of IMF.
However, there has always been a small issue with using the custom weighting feature — the custom XML file that you create has to be put inside a specific subfolder. The problem is that when Microsoft releases an update to IMF, the installation process creates a new sub folder automatically. However, the XML file is NOT autoimatically copied to the new folder.
What to do? Until recently, one had to remember to manually copy your XML file from the old folder to the new folder.
But now, Oliver Sommer (SBS/EBS MVP from Germany) has developed a free utility (Exchange Custom Weighting Feature XML Updater) that installs on your your server (works great with SBS 2003) and automatically copies your custom XML file to the new folder whenever a new IMF update has been installed. I’ve been personally running various beta and early versions of this utility successfully for more than a year.
Give it a try.
And if you like it, even though Oliver is offering the utiity for free, you may want to give him a small donation via PayPal. And while you are at his site, check out his Wake on Lan for SBS 2003 RWW utility!
For those using Outlook2007, two new hotfixes are now available that address specific speed and performance issues as well as a variety of other issues. Hotfixes, by nature, come with some warnings on their use. Hot fix 961752 and Hot fix 967688
Note #1: If you have never requested a hot fix from Microsoft, or it has been years since you have, you will be pleased to find that the process is quite fast and efficient. No longer do you need to even call Microsoft to request a hot fix!
Simply click on the links above to open up a new window with information on the hot fix. In the upper left of the window will be a clickable link” ‘View and request hotfix downloads’. Click on the link, enter your email address twice plus a security code and within five minutes you will receive an email containing a link to download the hotfix and a required password. The password is only good for a certain number of days (7 days maximum), so it is best that you download the hotfix as soon as you receive the email from Microsoft.
Those who have worked with SBS 2000 and SBS 2003 will find that many things are not where you expect them to be in SBS 2008! For example, let’s say you want Sally to receive all email addressed to firstname.lastname@example.org (in addition to receiving email as email@example.com). In prior versions of SBS, you would go to the SBS console, drill down to Users, go to properies for that user and make the change under the Email Addresses tab.
So, how do you do it with SBS 2008? Glad you asked!
Start up the Exchange 2007 management console, and click on Recipient Configuration > Mailbox. Double click on the desired user, click on the E-Mail Addresses tab, and then click on the green plus (+) tab and enter the additional email address.
Voila! Wasn’t that easy?
Enabling SBS 2008 to allow remote users to use their email clients (Outlook, Outlook Express, etc.) or phones to pull down email from the SBS2008 server via POP3 or IMAP4 is just slightly more involved than on SBS 2003. For all the step-by-step details and screen shots, visit the Official SBS Blog site which details these steps in two parts (part 1, part 2).
However, you may find it helpful to view the big picture in 5 easy steps, and I will also highligh several GOTCHAS to watch out for!
Step 1: Enabling the appropriate Microsoft Exchange IMAP4 or POP3 services on the server (Start > Run > Services.msc) should be easy enough. GOTCHA #1: Be sure that you change the startup type to Automatic, and then be sure to actually Start the service!
Step 2: Enabling the required ports again should be easy enough. Port 110-POP3, 995=POP3/SSL, 143=IMAP4, 993=IMAP4/SSL. GOTCHA #2: Remember that you also need to forward port 587 as this is the listener port for SMTP/TLS mail (instead of port 25!).
Step3: From ESM (click Server Configuration > Client Access > POP3 and IMAP4), and modify the X509 certificate under the Authentication tab to point to the proper exterNal FQDN of your server (eg., remote.servername.com).
Step 4: While in ESM, move down to Server Configuration > Hub Transport, and add a new Receive Connector. Name the connector ‘Client’ (short and simple). GOTCHA #3: Be sure to click on the drop down box and change the intended use of the Receive connector form Custom to Client! You can default through the rest of the prompts.
Step 5: Finally we are done with the server setup. The only thing left is to configure your email client and test things out. GOTCHA #4: When setting up your mail client for POP3 or IMAP4, be sure that you specifcy that the outgoing SMTP connection is to be encrypted, and set the port to 587.
I can’t believe it’s 2009 and we still have issues with DST and calendar items! Several of us just discovered (here on Feb-10-2009) that an event we are entering for August 2009 in Outlook 2007 is showing up an hour earlier on our WM6.1 phones. I’ve downloaded the latest WM/DST patch and installed it on my WM6.1 phone, but appointments are still showing up an hour earlier. I tried rebooting the phone, but no change. AFAIK, Outlook and my Exchange/SBS 2003 box are up to snuff with patches.
Very frustrating …
I’ve been install Calyptix AccessEnforcer units recently in several SBS shops, both SBS 2003 and SBS 2008. The AE is a fully featured network security appliance, and comes in various models to fit different size organizations. What I like about Calyptix is its single price — no extra costs for end user licenses or to enable various features. It interfaces nicely with Active Directory for user level filtering and email quarantine. I plan to do more posts in the future on implementing SBS and Calyptix together.
When SBS 2008 was first released, it included a 120 day trial of both Live OneCare (Server) and Forefront Security for Exchange (FSE). Since then, Microsoft has announced they would be dropping support for Live OneCare. When installing SBS 2008, you are asked whether you wanted to install the 120 day trial of these two products. If you did select to install them, and now wish to uninstall them, the process is very easy.
From the SBS console, click on Control Panel > Programs and Features. Click to highlight Live OneCare and then click Uninstall. The uninstall process is very straightforward, and no rebooting of the server is required to uninstall Live OneCare.
In a previous blog post, I provided instructions for uninstalling Live OneCare (Server) from SBS 2008. That was pretty straightforward. If you wish to also uninstall the 120 day trial of Forefront Security for Exchange (FSE), there’s a preliminary step you must perform. If you try to simply uninstall FSE, you will get a warning message saying that you need to first manually stop all Exchange services and the FSE administrator, and then the uninstall process terminates.
So, here’s what you do:
1. Click on Start > Administrative Tools > Services, and then locate and stop the FSCController service, which will also stop the Exchange Transport Service and the Exchange Information Store Service.
2. Then go to Control Panel > Programs and Features, click to highlight Forefront Security for Exchange Server, and then click uninstall.
3. After FSE is uninstalled, you will be required to reboot your server.
Note: After uninstalling FSE, you may find that a Microsoft Forefront Security subfolder with some files and a Quarantine folder still remains within the Program Files (x86) folder. If you are not planning on reinstalling FSE, you may safely delete this Microsoft Forefront Security folder and its contents.