1. Update your DNS records in Office 365.  You must create the following records in order to have iPhones and iPads connect to Office 365.  Note if you have been on Office 365 for some time these records might be different than the records you originally created.

SRV Record

CNAME Records

Once these records are created, you should be able to sign into Lync on your iPhone or iPad using your username and password.

2. In the Exchange Control Panel, click Mail Control, and then in the Forefront Online Protection, click the link.

3. In Forefront, click on the Administration Tab, then Policy Rules and New Policy Rule.

4. In the Rule Settings area you can select an action that should take place when a message meets the criteria defined by the Match Settings (the center column).  When the rule is created you can click the Save Policy Rule to save the rule.

$o365cred=get-credential
$Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://ps.outlook.com/powershell/ -Credential $o365cred -Authentication Basic -AllowRedirection
Import-PSSession $session

After you are connected, you must run the following command to give Alan full access to Bob’s mailbox:

Add-MailboxPermission -identity Bob@domain.com -user Alan@domain.com -AccessRights FullAccess

If you wanted to give Alan full access to all mailboxes in your environment you would run:

Get-Mailbox | Add-mailboxpermission -user Alan@domain.com -AccessRights FullAccess

In our opinion the instructions on the Office 365 site are a bit confusing when it comes to the host name that should be entered which is probably the cause of most problems people encounter so we want to try and explain it another way.

In this example let’s say our domain is office365demo.com.  The instructions tell you to create a host record called Office365demo.com in your existing domain.  To some people that would mean the name being checked by Microsoft during the verification process would be office365demo.com.office365demo.com.  The first office365demo.com is the host portion and the second office365demo.com is the domain portion.  What Microsoft is really looking up when they verify the domain is just the text record for the domain itself, office365demo.com.  In most DNS systems that means the host portion should be left blank or use an @ symbol.  In the GoDaddy interface that looks like:

In Microsoft’s defense, if you do enter office365demo.com in the host field GoDaddy does convert it to the @ sign, but we feel it’s still confusing, as there are lots of cases where the Domain is registered by GoDaddy (or some other provider), but the name servers are housed at another organization.  In that case, the instructions provided by Microsoft point you to update the reconds on GoDaddy, but what you really need to do is update at the organization that houses the name servers.

You also might be thinking, “I already have a @ text record, which is used by my SPF record”.  From our research, you can safely have an additional @ text record, without causing problems with the SPF.

To check the txt record, one of the easiest tests is nslookup.  To run nslookup go to a command prompt and type:

nslookup <hit enter>

at the > prompt type:

set q=txt <hit enter>

then type the domain name:

office365demo.com <hit enter>

It should return the verification value.  So the entire process looks like:

C:\Users\Chad>nslookup
Default Server:  UnKnown
Address:  192.168.1.254

> set q=txt
> office365demo.com
Server:  UnKnown
Address:  192.168.1.254

Non-authoritative answer:

office365demo.com       text =

“v=verifydomain MS=ms72051478″

Delivery has failed to these recipients or distribution lists:

donotreply@microsoftonline.com
An error occurred while trying to deliver this message to the recipient’s e-mail address. Microsoft Exchange will not try to redeliver this message for you. Please try resending this message, or provide the following diagnostic text to your system administrator.

This error is caused by having a disabled user as a member of the DL in your local Active Directory.  Disabled users are the only mail-enabled objects that don’t sync via Directory Sync.  The problem is that the Distribution List, when synced over, still has a record of the disabled user.  Since The Microsoft Online AD has a pointer to a user that doesn’t exist, it provides the NDR.

To resolve the issue, remove the disabled user from the DL in your local AD the error should go away when Directory Sync completes its next run.

For a list of the Microsoft Online Service Notification Feeds in different languages, visit the site for your region:

Americas
https://rss.microsoftonline.com/

EMEA
https://rss.emea.microsoftonline.com

APAC
https://rss.apac.microsoftonline.com

For a list of the ForeFront Feeds, visit
http://rss.messaging.microsoft.com/

• How to Share a Folder
• How to open a Shared Default Folder
• How to open a Shared Non-Default Folder
• How to open an additional mailbox
• How to give someone access to an entire mailbox
• How to Send As a Mailbox

There are other ways to do many of these tasks, but these instructions are written so they apply to Outlook 2003 – 2010.  The instructions were written using Outlook 2007, but the procedures for Outlook 2003 and 2010 are very similar.

How to Share a Folder

1. In Outlook, right click the folder you want to share and choose properties.

   
   

2. Click the Permissions tab.
3. Click the Add button and select the user(s) that you want to give access to.
4. After the users have been added, select the appropriate level of permissions for each.

   

5. Click Ok.

How to Open a Shared Default Folder

1. From the File Menu, choose Open->Other Users Folder

   
   

2. In the dialog box that appears, select the folder you would like to open.  Note, only the Default folders are shown, if you need to open a non-Default folder, see the section, “How to open a Shared Non-Default Folder”.

How to Open a Shared Non-Default Folder

1. Opening a Non-Default folder, first requires the user not only has permissions on the folder, but also Reviewer rights at the Root of the mailbox that contains the folder.   This can be set by opening the properties of the mailbox root in Outlook and setting the permissions.

   
   

2. The person sharing the folder, should grant the person Reviewer Rights on the Root level of the mailbox.
3. Once the permissions on the mailbox have been set, the person who wants access to the mailbox can follow the steps Outlined in the next section, “How to Open an additional Mailbox”.

How to Open an Additional Mailbox

1. Opening an additional mailbox, allows you to see the mailbox and its contents much like your normal mailbox.  Once added to a profile, it will remain in the profile, even if Outlook is closed. 

   
   

2. To add an additional mailbox to a profile, from the Tools menu, click Account Settings.

   
   

3. On the Account Settings Window, double click Microsoft Exchange.
4. Click the More Settings button.
5. Click the Advanced Tab.
6. Click Add and Select the mailbox you would like to add to the profile.

   

How to give someone access to an entire mailbox

In some cases you might want to give an individual access to an entire mailbox, not just a single folder in the mailbox.  One way to accomplish this would be to grant the user Owner permission to each folder in the mailbox they need to access.  While this would work, it could be time consuming, especially if you need to do it for a large number of users. 

The better way to do this is to use the Add-MSOnlineMailPermission PowerShell command.  To use this command you must have the Micrsoft Online Migration Tools installed on a workstation.  To grant a user full access to a mailbox, you must:

1. Launch the Migration PowerShell Command (Start->All Programs-> Microsoft Online Services -> Migration -> Migration Command Shell.

2. Run the following command, where user1@domain.com is the mailbox you want to give user2@domain.com access to:

Add-MSOnlineMailPermission -Identity user1@domain.com-grantfullaccess $true -Trusteduser user2@domain.com

After the permission has been set the user can follow the steps in “How to open an additional mailbox” to open the mailbox.

How to Send As a Mailbox

If you are working with Shared Mailboxes, in some cases you might want to send mail from the Shared Mailbox and have the message appear to come from the Shared Mailbox instead of the actual user’s account.  Setting this up requires 2 main things.

First, you must use the Add-MSOnlineMailPermission PowerShell command to set the send as Permission. To use this command you must have the Microsoft Online Migration Tools installed on a workstation.  To grant a user sendas access on mailbox mailbox, you must:

1. Launch the Migration PowerShell Command (Start->All Programs-> Microsoft Online Services -> Migration -> Migration Command Shell.

2. Run the following command, where user1@domain.com is the mailbox you want user2@domain.com to send as:

Add-MSOnlineMailPermission -Identity user1@domain.com-grantsendas $true -Trusteduser user2@domain.com

Second, when composing a message, you must select the option to show the From Address.

When the user sends the message it will appear to come from the account specified in the From Address instead of their own.  All replies will be sent to the mailbox in the From field.  One thing that is a bit strange about out Send As, is the sent message is kept in the Sent Items folder of the person who sent the message, not the shared mailbox. (This behavior changes in Outlook 2010).

The WebDAV injector has stopped migrating mail items for user SMTP:user@domain.com because the number of failures has exceeded the failure tolerance of 5. The injector will ignore any remaining items for this user’s mailbox during this migration session.

Here are some recommendations on what to do.

1. Try and remigrate the mailbox.  Depending on the errors, it might work the second time.  Typically remigrating should not create duplicates and should run must faster since it doesn’t have to remigrate what has already been migrated.  Errors that lend themselves to working the second time are errors that appear to be network related, such as:

• An existing connection was forcibly closed by the remote host.
• An established connection was aborted by the software in your host machine.
• The underlying connection was closed: A connection that was expected to be kept alive was closed by the server.

Rerunning the migration and reducing the thread count can also help with these types of errors.  Errors that typically don’t fix themselves are those that reference are particular object:

• The properties of item https://server.domain.local/exadmin/admin/domain.local/mbx/user/-FlatUrlSpace-/e6cac75a9a162d4fa70f83203eaa9129-dd2d/3ef7f6567d391245b5643e1f5b0aa3b6-2ca38d1 that are dated 2/22/2010 PM could not be read for user user@domain.com.

2. If the remigration fails and you are getting errors about individual items failing try moving the mailbox to another to another store on the source server and then remigrate the account.  The mailbox move will sometimes clear up mailbox corruption.

3. If it still doesn’t work, export the mailbox to PST and import the PST.  This way always works, but the problem is the messages aren’t replyable in Microsoft Online.

If you don’t want to export the mailbox to a PST and reimport there is another option, it’s just time consuming.  Using the migration PowerShell commands it is possible to get details on the messages that are failing.

You can download this script which will help you identify the messages.  There are a few things you’ll have to modify in the script before running it.  When running it you’ll need to provide the email address of user that is failing, and then the UID of the message that is faing.  The UID can be found in the error logs and will look similar to:

The item with SourceUID value ARgAAAAYbzngAAAAAAAAAAAAAAAA

The script will output additional details about the message.  You can then go into the mailbox and export or delete it.  Do this for all 5 messages that are failing and then try the migration again and hope you don’t get 5 more failures!

If you need assistance with the script, email support@messageops.com.  If you have other suggestions, please post them in the comments section below!

1. You will need to get the outbound IP address used by you datacenter.  This will be indicated in the Organization section of your BPOS domain (domain.microsoftonline.com). You can request Read-Only Admin access to your BPOS domain/organization and the information will be listed there (shown below)

Once you have this information you are ready for the cutover.  The next 3 steps should be performed when you are ready to cutover.

2.  Make your domain Authoritative in Microsoft Online.  You do not need to enable inbound mailflow.  If you try you will get an error.

3.  Set your Mail Server Address (in FOPE/EHS) to the appropriate SmartHost:

• NOAM: SMTP801.microsoftonline.com
• EMEA: SMTP201.microsoftonline.com
• APAC: SMTP601.microsoftonline.com

4. Set the Outbound IP to be the value that your Microsoft Online account is currently configured to use.  This is the information obtained in step #1.

This replication should be complete within 90 minutes and you should now see mail coming directly into Exchange Online

If simply opening IE and configuring the settings doesn’t work for you, you can try these steps to reset the IE configuration:

To use the Reset Internet Explorer Settings feature from Control Panel, follow these steps:
1. Exit all programs, including Internet Explorer (if it is running).
2. If you use Windows XP, click Start, and then click Run. Type the following command in the Open box, and then press ENTER:

inetcpl.cpl

The Internet Options dialog box appears.

3. Click the Advanced tab.
4. Under Reset Internet Explorer settings, click Reset. Then click Reset again.
5. When Internet Explorer finishes resetting the settings, click Close in the Reset Internet Explorer Settings dialog box.
6. Start Internet Explorer again.

Then, if it’s still not working:

1. Right Click on the Command Prompt Shortcut on the Start Menu and Choose Run As Administrator.
2. In the Command Prompt window, enter this text and press Enter:

regsvr32 actxprxy.dll

3. Restart your computer.