Microsoft Exchange – techspeeder

Disable Phone Pin Lock Exchange Policy on Exchange Server 2010

Merlin Halteman — Tue, 15 Sep 2015 22:59:44 +0000

I upgraded one of our Microsoft Exchange 2010 servers to Exchange 2010 Service Pack 2. After the upgrade one of the users complained that they now had to create a pin or password on their phones’ lock screens. Although I think this is a good idea for security purposes, this company didn’t want this hassle. This is how you disable the Exchange ActiveSync Mailbox policy from requiring a device password or pin .

Step One: Open Exchange Management Console

Step Two: Expand Organization Configuration > Client Access

Step Three: Click Exchange ActiveSync Mailbox Polices tab and open the default policy.

Step Four: Click on the Password tab and uncheck Require Password. Apply your settings.

These changes will automatically take affect across all of the devices.

If this post helped you, please consider sharing with your friends or following my blog. This was posted by techspeeder.

How to make a Vacation Responder with Office 365 OWA

Merlin Halteman — Wed, 09 Jul 2014 22:17:58 +0000

Office 365 allows you to make a vacation responder in the Outlook web app. This is very useful if you are on the road and don’t have your work computer handy. Or if you don’t feel like setting up a rule in Outlook.

Here are the steps: Go to mail.office365.com .

Click on the settings gear and select “Set Automatic Replies”.

You can now make a vacation responder message. You can specify how long the vacation responder lasts. OWA even lets you set a custom message for the people inside your organization. Pretty cool, eh?

Make sure you click “save”. You will be all set!

If you have Outlook 2013, it is smart enough to let you know you have a vacation responder (automatic reply) turned on.

Like us on Facebook if this helps. This was posted by techspeeder.

Microsoft Outlook: Delivery has failed to these Recipients or Groups

Merlin Halteman — Sat, 08 Feb 2014 01:39:37 +0000

Our customer recently switched to Microsoft’s Office 365 exchange service as their email provider. Previously to this transition, this company was hosting their own exchange server. After the upgrade some of the employees would get an error message when emailing within the organization. Here is the message:

The email address you entered couldn’t be found. Please check the recipient’s email address and try to resend the message. If the problem continues, please contact your helpdesk.

The email addresses didn’t change during the upgrade to Office 365. The users were correctly entering the email addresses as well.

So the first thing to try is to delete the autocomplete in Outlook. When you enter the recipient in Outlook , delete the autocomplete suggestion that pops up.

See if that fixes the issue, it didn’t for me .

I then downloaded this NK2View tool from here. I ran this cool little utility and it brought up the autocomplete cache. I scrolled down to the email recipient my customer was having trouble emailing and deleted that entry. I then tried sending a test email and it worked like a charm.

Resolution: When I used the NK2View utility to delete the entry it actually deleted the autocomplete entry for real. Apparently, when they were trying to email within the organization the autocomplete had saved some information about their previous email servers and was trying to deliver the message to the old server. I just deleted the autocomplete entry and everything was fine.

This was posted by techspeeder.

Set up Office 365 Email Forwarding to External Email Addresses

Merlin Halteman — Mon, 27 Jan 2014 23:15:14 +0000

Problem: A company split and they were using Office 365 for their email provider. Company A kept the domains. Company A kept all the existing user accounts and email addresses. Company B created a new Office 365 account with their own domain and new email addresses. We needed to be able to forward Company B’s emails to their new addresses, but Company A didn’t want to pay for their Office 365 licenses. Here is the resolution we came across. It worked quite well.

Resolution: I logged into Company A’s portal. I deleted the Company B’s user accounts that were no longer being used.

I then went into the Exchange admin center and clicked on Contacts.

I then created a new mail user.

I filled in the credentials for the new mail users. Note, make sure you keep the alias and the user ID the same (ex. Alias: test.user and then user ID: would be test.user@domain.com). In the external email address field I put in their new email address. I clicked save

and then sent an email to the alias. It wasn’t long and an email showed up in my inbox. The forwarder worked without a hitch!

This was posted by techspeeder.

Source: Office 365 Forum