Email is one of the most important communications tools for businesses. When it stops working, people start to get nervous.

While there are many things that a user can do to mess up their email, many of these problems can be resolved with a restart of the software or the computer.

However when the old standby of restarting doesn’t work, it is time for the email administrator to start looking into the issue a bit more deeply.

Here are some of the more common errors found in Outlook 2007 along with some of the ways you can make things right again: Continue reading 5 Common Outlook Errors and How to Fix Them

Often, Exchange administrators will receive escalated help desk tickets from users complaining that Exchange is “slow” and demanding resolution. These sorts of tickets (slow being at best a relative term and never specific enough about what precisely is considered to be slow) can be extremely challenging to work, since the subjective nature of slowness is often combined with an inability to replicate the problem, or the problem is intermittent. The Exchange admin can take a look at the server(s) for high CPU utilization, low memory conditions, disk and network queue lengths exceeding the norm, and finding nothing, shrug it back off to the desktop support team as a client issue. While it is often a client issue, there are several places between Outlook and a user’s mailbox that can cause intermittent slowness, and are fair to call networking bottlenecks. In a six part series of articles, we’ll look at how Exchange interacts on the network with various other services to help you identify network issues, and troubleshoot them when they occur.

In many cases, troubleshooting Exchange network bottlenecks will require a network trace, and may also require performance monitor counters. This series of articles will talk about both of those in general terms; how to use NetMon or Wireshark, and PerfMon are out of scope. In Part 3 of this series, we’re going to discuss the connectivity you need to permit through firewalls for Exchange to function properly on the network. Continue reading Troubleshooting Exchange Networking: Firewalls (Part 3)

Google recently hung a ‘going out of business’ sign on its Message Continuity service for users of Microsoft Exchange. Google will continue to provide the service to its users until their contracts run out, but after that, they’re on their own.

Since the service was launched a little over a year ago, “hundreds” of businesses have subscribed to the offering, which uses Google’s cloud to provide email continuity when a Microsoft Exchange environment is interrupted for any reason.

Hundreds of users, though, can’t compete with the “millions” of businesses that have moved their entire email operation to Google Apps, so Searchzilla has decided to scrap its continuity product for Exchange  and concentrate all its resources on its application suite. Continue reading Google Deserts Exchange Users by Killing Message Continuity

Gates: Momentous security memo

For computer security experts, January 15 marked the anniversary of a red letter day. It was the 10th anniversary of the day that Microsoft decided to get serious about security.

On that day in 2002, a memo from Bill Gates to Microsoft employees declared the company would be entering a new era, an era of “Trustworthy Computing.”

“In the past,” Gates wrote, “we’ve made our software and services more compelling for users by adding new features and functionality, and by making our platform richly extensible. We’ve done a terrific job at that, but all those great features won’t matter unless customers trust our software.”

“So now,” he continued, “when we face a choice between adding features and resolving security issues, we need to choose security.” Continue reading Microsoft’s Trustworthy Computing Program Turns 10

Customize the Exchange Management Shell as an Exchange administrator, it’s only a matter of time before you embrace the dark side and come to know the true power of shell. The Exchange Management Shell is the direct interface between you and the underlying PowerShell cmdlets that are used to query, configure, and manage Exchange. Getting comfortable with a command line interface after years of GUI work is a big shift for many admins, but if you start out slow, and work your way through things step by step, you’ll soon find that you are a PowerShell Jedi. Making something your own is the first step towards getting comfortable with it, so in this post, we’ll see how to customize the Exchange Management Shell to make it your own. Continue reading Customize the Exchange Management Shell

In an age where millions of emails are sent every day it is hard to find someone who hasn’t made a mistake when sending a message.

If you are using Microsoft Outlook and Exchange, you can quickly recall a message and delete unread copies, if you are lucky that is and no one has opened the email. If someone has already opened your errant message, then it’s too late.

Companies have become a bit more cognizant that some employees are just a bit too quick to pull the Send trigger on their mail. To compensate, many have put into place a time delay that gives someone the opportunity to think twice about a message that was sent out and stop it before it is delivered. Continue reading Common Mistakes When Sending Emails

Often Exchange administrators will receive escalated help desk tickets from users complaining that Exchange is “slow” and demanding resolution. These sorts of tickets (slow being at best a relative term, and never specific enough about what precisely is considered to be slow) can be extremely challenging to work, since the subjective nature of slowness is often combined with an inability to replicate the problem, or the problem is intermittent. The Exchange admin can take a look at the server(s) for high CPU utilization, low memory conditions, disk and network queue lengths exceeding the norm, and finding nothing, shrug it back off to the desktop support team as a client issue. While it is often a client issue, there are several places between Outlook and a user’s mailbox that can cause intermittent slowness, and are fair to call networking bottlenecks. In a six-part series of articles, we’ll look at how Exchange interacts on the network with various other services to help you identify network issues, and troubleshoot them when they occur. Continue reading Troubleshooting Exchange Networking: Active Directory (Part 2)

I want you all to go grab your favourite marketing person and make them read this post. You know the ones I am talking about. The one that doesn’t understand why they have to take the 3600dpi 8GB PDF that could be blown up to the size of the Empire State Building without looking grainy, and reduce it for sending over email to a customer. The one who came in early last week to send an email blast to a 1000 person customer list that they bought from a guy they know, which resulted in your corporate network being placed on every RDNS blacklist on the planet. The one who doesn’t understand why when he sends an email, the customer doesn’t have it open to read before he lets goes of the mouse. The one whose laptop you secretly want to replace with an Etch-a-Sketch. Continue reading How to Lose Customers and Infuriate People

Gestures can replace passwords in Windows 8.

Why it has taken Microsoft so long to make password security more than an afterthought when it introduces a new operating system is anybody’s guess. Nevertheless, with Windows 8 it is making an effort to help users manage their passwords in an efficient and secure way.

Everyone has dozens of accounts they need for which they need to memorize passwords. Most people, though, only commit a few passwords to memory and just reuse them over and over again. A study in 2007, for example, found that the average Internet user had 25 accounts that required password access, but they only used six passwords to access their accounts.

Security pros decry the multiple use of passwords but there are plenty of sites on the web where if your password fell into the wrong hands, the consequences would be trivial. Reusing passwords for those sites should be acceptable. There are sites where unique passwords are a must, though, such as banking or credit card payment sites. Continue reading Windows 8 Offers New Password Features