Posts Tagged ‘microsoft exchange 2010’

Exchange 2010 Transport Protection Rules

February 1st, 2010

One of the most important improvements in Exchange 2010 in my opinion is the new toolkit that allows administrators to implement policies that works with Outlook 2010 and Outlook Web Access too. The fact is offers many different tools that make Email Hosting better and easier to manage.

This is a significant step forward, as previously OWA was something of a unsubtle beast. You could either restrict access to mailboxes altogether or it was open season on emails. Now policies can be enforced across the board, whatever client the users prefer.

The Transport Protection Rules enable Exchange administrators to create rules that control every aspect of email, from content restrictions, size, approved recipients for sensitive emails, no copy and pasting and other neat tricks. While most of these features have been around in other incarnations, they have never been so easy to implement or ever worked with Outlook Web Access. The TPR system is new to Exchange 2010 and a welcome addition to the platform.

In a real life example of the TPR in action, say a project manager send a detailed email to his team listing a new product, it’s benefits, features and proposed release date. He can mark he email confidential so his people knew not to share it, which has always been the case. The mail would have a flag on it marking it as confidential.

Now, with Transport Protection Rules, Exchange can enforce a policy on confidential emails that includes not being able to forward them, copy and paste to or from them and other niceties. This means if someone absent mindedly forwarded it as part of a conversation the Exchange server would refuse. This is a significant step forward in information security, and allows administrators to control the flow of information with much more granularity than before.

Drilling deeper into the Transport Protection Rules, it’s also possible to restrict emails, by email address, location, recipient, whether it’s internal or external and a raft of other criteria. It also works seamlessly with Outlook Web Access too. Which is handy because Office 2010 doesn’t even have a release date yet.

The biggest bonus with these rules, and the closer integration with OWA is that everything will work with browsers other than Internet Explorer. No more will you need plugins to be able to enforce rules, or add functionality. Everything works out of the box, so Opera, Firefox or Safari users will also have full access to the available features, and also be subject to the Transport Protection Rules.

The Exchange 2010 was the largest beta Microsoft have ever run. From where I’m sitting, it was worth every minute. They have listened to feedback and integrated many of the improvements into the new system. While it’s still a big, cumbersome beast, it’s now a bit more manageable at least.

Setting up Outlook to Connect to Exchange

September 16th, 2009

microsoft_exchange_server_2010

Exchange servers are used by companies all over the world to pass messages both internally and externally. Email is now the primary method of communication in business. We send hundreds of millions of emails every day, and the vast majority of them are sent and received by Microsoft Exchange Server.

Exchange is a platform that sits on a server and co-ordinates email clients throughout an organization. It accepts emails from users, translates them into binary, packages them up and sends them to the recipient. The receiving Exchange server will unwrap the email, build it again and forward it on to the recipient. As well as email, there are also calendar and contact functions as well as Outlook web access and mobile features that allow email to be sent to laptops, cell phones and PDA’s.

Users new to Exchange may find themselves in a position of trying to configure Outlook to connect to the server. In most organizations, this will be done for you, but there are some that will leave it up to you to figure out.

That’s where we come in, this article will describe how to connect your client to an Exchange server in no time at all so you can get on with emailing in the shortest time. The process is pretty straightforward, as Outlook is often installed by default on any machine with Office. If your machine doesn’t have Office either, Outlook Express may be there.

So, click Start then Control Panel then Mail. See? Easy so far. Select Email Accounts and then Add New Email Account and then Next. Choose the Microsoft Exchange Server then hit Next.

Here you have some options for which you need information. You will need the address of the Exchange server. If this hasn’t been provided for you, ask a colleague and copy their settings. Depending on how things are set up this may be enough to get you going.

You need to input the Exchange Server address, this is often something like “mail.company.com”, but can in fact be anything. You will also need to input your username and password, which the administrator will need to provide you. It may be different than your system login, but give it a try if you don’t have the details.

Once you have input the information, the application should do a quick check to ensure the details are correct then return it’s version of your email address. Once this happens click Finish.

Outlook should now chug away a bit and start downloading your emails and email settings. It will also install any corporate signatures, calendar events, contact books and rules. Depending on the organization, this could take a little while, but can be done in the background.

That is all there is to it. IT support may make a big deal out of setting you up with the connection, but once your account has been created in Exchange, the rest is easy.