Catastrophic Failure "JV"

Share calendar with PowerShell Office 365

Joannav — Mon, 17 Jun 2013 15:47:31 GMT

To share user’s calendar with another users in an origination, we can click the button “Share Calendar” on the top ribbon of menu bar, or run the command ” Add-MailboxFolderPermission” by using Windows PowerShell.

To do this, please perform the steps below:

1. Install and configure Windows PowerShell.
2. Connect Windows PowerShell to Exchange Online

Run the following to authenticate yourself and import PowerShell commands to your local session:

$LiveCred = Get-Credential
$Session = New-PSSession -ConfigurationName Microsoft.Exchange-ConnectionUri https://ps.outlook.com/powershell/ -Credential $LiveCred -Authentication Basic -AllowRedirection
Import-PSSession $Session

Image 1

3. Run the cmdlet below to grant appropriate permission to a user, who can view or edit another one’s calendar.

Add-MailboxFolderPermission –Identity <MailboxFolderId> -AccessRight <MailboxFolderAccessRight> -User < MailboxFolderUserId >

Note:
The Identity parameter specifies the recipient and folder that you want to change the permissions for, and the User parameter specifies who's granted permission to view or modify the folder contents of the user specified in the Identity parameter.

For example:
This example assigns permissions for Anna to access John's calendar mailbox folder and applies the readitems role to her access of that folder

Add-MailboxFolderPermission –Identity cf@losgrecos.onmicrosoft.com:\Calendar -AccessRight ReadItems -User joannav@losgrecos.onmicrosoft.com

Image 2

For more information about add mailbox folder permission, please refer to the article below:

Add-MailboxFolderPermission
http://technet.microsoft.com/en-us/library/dd298062.aspx

Microsoft Exchange 2013 Public Folders Migration Scripts

Joannav — Wed, 12 Jun 2013 06:47:07 GMT

Microsoft recently release the necessary support scripts to migrate Exchange 2007/2010 Public Folders to Office 365.

Microsoft Exchange 2013 Public Folders Migration Scripts

Use these scripts to migrate public folders from Exchange 2010 or 2007 to Exchange 2013.
In order to migrate Exchange 2010 or 2007 Public Folders to Exchange 2013 on O365, we need to analyze the existing
Public Folder hierarchy for size to figure out the number of Public Folder mailboxes that are required on O365 and the distribution of folders across mailboxes.

Microsoft Exchange 2013 Public Folders Directory Sync Support Scripts

Use this scripts if you need to do one of the following
Initial creation of mail enabled public folder objects in the destination Active Directory for public folder migration from Exchange 2007 or 2010 to Exchange 2013
Synchronization of mail enabled public folder objects from cloud to on premise Active Directory
Synchronization of mail enabled public folder objects from on premise to cloud Active Directory
Synchronization of public folder mailbox objects from cloud to on premise Active Directory

Mail Protection Reports for Office 365

Joannav — Thu, 06 Jun 2013 19:33:00 GMT

This reporting workbook provides you with a detailed view into the email protection data that is available in the Office 365 Reporting dashboard.
This workbook is available to all Exchange Online and Exchange Online Protection customers. The workbook provides summary graphs for a number of different types of email message filtering.
This includes messages identified as spam, malware, or good mail (mail that cleanly passed all filtering). It also shows graphs for messages that were identified by either a transport rule or DLP policy (Exchange Online customers only).
The data for the summary graphs is pulled locally via a web service call. After loading the summary data into the workbook, you can perform deeper analysis through the use of data slicers.
These allow you to change the view of the data in order to identify trends or unusual activity. When such a condition is found, you can click through from the summary to the detail data.
Another web service call will be made to pull the detail data that you can use to identify the actual messages that caused the condition seen in the summary graph.

Bellow you can see the installation instruction's

After completing the installation, open the workbook in Excel 2013 using the shortcut on your desktop and login with your Administrator Office 365 credential's and click on Query

After the scanning finished, check the results

Enjoy

Message Analyzer, an SMTP header analysis tool in Microsoft Remote Connectivity Analyzer

Joannav — Mon, 20 May 2013 18:13:00 GMT

Microsoft Remote Connectivity Analyzer is a web-based tool that provides administrators and end users with the ability to run connectivity diagnostics for our servers to test common issues with Microsoft Exchange, Lync and Office 365. Microsoft is excited to announce Message Analyzer, a brand new addition to the Remote Connectivity Analyzer. Message Analyzer makes reading email headers less painful.

Figure 1: The new Message Analyzer tab in RCA

SMTP message headers contain a wealth of information which allows you to determine the origins of a message and how it made its way through one or more SMTP servers to its destination. To use Message Analyzer, all you need to do is copy message headers from a message and paste them in the Message Analyzer tab on the RCA web site.

where are my message headers?

Outlook 2010 and Outlook 2013

Open Outlook 2010.
Select the email message for which you'd like to view the headers.
Click on File, see Figure 2.

Figure 2

4. Click on Properties as in Figure 3.

Figure 3

5. The new window contains the headers. See Figure 4.

Figure 4

Outlook 2007

Open Outlook 2007.
Open the email message.
Under the Message tab, in the Options group, click on the Dialog Box Launcher icon.
In the Message Options dialog box, the headers appear in the Internet headers box.

Outlook 2000, 2002 and 2003

Open Outlook.
Double-click to open the email message in a new window.
Select View > Optionsfrom the message's menu.

4. All header lines appear under Internet Headers at the bottom of the dialog box

To use Message Analyzer, all you need to do is copy message headers from a message and paste them in the Message Analyzer tab on the RCA web site.

Figure 2: Paste message headers in the Message Analyzer

Features of the Message Analyzer

Here's a quick look at what you can do with Message Analyzer.
View the most important properties and total delivery time at a quick glance.

Summary⇓⇑

Subject	TEST
Message Id	<6a04e107682548a297a4481a3f7c8aa5@AM2PR06MB592.eurprd06.prod.outlook.com>
Creation time	Thursday, March 28, 2013 5:10:09 PM (Delivered after 1 second)
From	Joanna Vathis <joannav@itprodev.onmicrosoft.com>
To	Joanna Vathis <joannav@itprodev.onmicrosoft.com>

Received headers⇓⇑

Hop↓↑	Submitting host↓↑	Receiving host↓↑	Time↓↑	Delay↓↑	Type ⇐ ⇒ ↓↑	ID↓↑	For↓↑	Via↓↑
1	AM2PR06MB592.eurprd06.prod.outlook.com ([169.254.11.40])	AM2PR06MB592.eurprd06.prod.outlook.com ([169.254.11.40])	Thursday, March 28, 2013 5:10:10 PM		mapi	15.00.0651.000
2	AM2PR06MB592.eurprd06.prod.outlook.com (10.255.61.35)	AM2PR06MB594.eurprd06.prod.outlook.com (10.255.61.37)	Thursday, March 28, 2013 5:10:11 PM	1 second	Microsoft SMTP Server (TLS)	15.0.651.16
3	AM2PR06MB594.eurprd06.prod.outlook.com (10.255.61.37)	AM2PR06MB592.eurprd06.prod.outlook.com (10.255.61.35)	Thursday, March 28, 2013 5:10:11 PM	0 seconds	Microsoft SMTP Server (TLS)	15.0.651.16		Mailbox Transport

Other headers⇓⇑

#↓↑	Header↓↑	Value↓↑
1	Content-Type	application/ms-tnef; name="winmail.dat"
2	Content-Transfer-Encoding	binary
3	From	Joanna Vathis <joannav@itprodev.onmicrosoft.com>
4	To	Joanna Vathis <joannav@itprodev.onmicrosoft.com>
5	Subject	TEST
6	Thread-Topic	TEST
7	Thread-Index	AQHOK8ZWvL1pod5qCUm/1ztqQT/y7A==
8	Date	Thu, 28 Mar 2013 15:10:09 +0000
9	Message-ID	<6a04e107682548a297a4481a3f7c8aa5@AM2PR06MB592.eurprd06.prod.outlook.com>
10	Accept-Language	en-CA, el-GR, en-US
11	Content-Language	en-CA
12	X-MS-Has-Attach
13	X-MS-Exchange-Organization-SCL	-1
14	X-MS-TNEF-Correlator	<6a04e107682548a297a4481a3f7c8aa5@AM2PR06MB592.eurprd06.prod.outlook.com>
15	MIME-Version	1.0
16	X-MS-Exchange-Organization-AuthSource	AM2PR06MB592.eurprd06.prod.outlook.com
17	X-MS-Exchange-Organization-AuthAs	Internal
18	X-MS-Exchange-Organization-AuthMechanism	04
19	X-Originating-IP	[88.203.200.58]
20	X-MS-Exchange-Organization-Network-Message-Id	c34d8ff2-c78f-4f71-6a8a-08cff9dd79bb
21	Return-Path	joannav@itprodev.onmicrosoft.com
22	X-MS-Exchange-Organization-AVStamp-Service	1.0
23	X-Forefront-Antispam-Report	SFV:SKI;SFS:;DIR:OUT;SFP:;SCL:-1;SRVR:AM2PR06MB594;H:AM2PR06MB592.eurprd06.prod.outlook.com;LANG:;

Quickly collapse the sections that you don’t need.
All processing is done in your browser, and no private information is shared with Microsoft.
Useful for any header, whether generated by Exchange, Office 365, or any other RFC standard SMTP server or agent.

Note, we consider this feature to be in beta for the moment, try it

How To: Give Users Send As Permission

Joannav — Tue, 14 May 2013 10:09:38 GMT

Send As permission, also known as SendAs permission, gives a user permission to use another recipient's e-mail address in the From address. For example, when you give the user Chris Send As permission on the mailbox of a user named Michelle, Chris can send e-mail messages that appear to be sent by Michelle, with no indication to the recipient that anyone other than Michelle sent the message. Or, if your organization uses a Help Desk distribution group, you can give Help Desk staff Send As permission on the Help Desk distribution group. That way, replies to messages sent to the Help Desk group appear to come from the group instead of an individual Help Desk technician.

To give a user Send As permission, you use Windows PowerShell

Before you begin

To learn how to install and configure Windows PowerShell and connect to the service, see Use Windows PowerShell in Exchange Online.
The Send As permission is different than the Send on Behalf permission. If the user Chris has Send on Behalf permission on Michelle's mailbox, when Chris sends an e-mail as Michelle, the From address shows Chris on behalf of Michelle. Microsoft Outlook users can configure Send on Behalf permissions on their own mailbox using delegates. Administrators can configure Send on Behalf permissions on any recipient type using the GrantSendOnBehalfTo parameter.
Want more information about parameters? See An explanation of parameters.

Give a user Send As permission

Launch Windows PowerShell and perform the following steps:

001
002
003
004

Import-Module msonline
$cred = Get-Credential
Connect-MsolService -cred $cred
Get-Command –Module msonline

1) Import the module.
2) Create a credential-object stored in the variable $credimp
3) Create a new remote PowerShell connection against the PowerShell endpoint for Office 365
4) List the cmdlets available

A shortcut to the module is also available on the Start-menu (you can skip step 1 if launching this shortcut):

Run the following command:
Command:
Add-RecipientPermission <identity> -AccessRights SendAs -Trustee <user>

For example, to give the user named Joanna Vathis Send As permission for the Test mailbox , run the following command:
Example:
Add-RecipientPermission test@itprodev.onmicrosoft.com -AccessRights SendAs -Trustee joannav@itprodev.onmicrosoft.com

OR

Command:
Add-RecipientPermission "TEST" -AccessRights SendAs -Trustee "Joanna Vathis"
Joanna can now send messages that appear to come directly from the TEST mailbox.
Note By default, you are asked to confirm the addition of the Send As permission. To skip the confirmation prompt, use -Confirm:$false.

View Send As permissions

Use the Get-RecipientPermission cmdlet to display all the Send As permissions configured in your organization. You can filter the list to show Send As permissions granted to a specific user and to see the Send As permission on a specific recipient.

View Send As permission for a specific user

Run the following command:
Command:
Get-RecipientPermission - Trustee <user>

For example, to list the recipients for whom the user named Kim Akers has Send As permission, run the following command:
Command:
Get-RecipientPermission -Trustee joannav@itprodev.onmicrosoft.com
Joanna can send messages that appear to come directly from the recipients

View Send As permission on a specific recipient

Run the following command:
Command:
Get-RecipientPermission <identity>

For example, to list the users who have Send As permission on the TEST mailbox, run the following command:
Command:
Get-RecipientPermission "TEST"
The users listed can send messages that appear to come directly from the TEST mailbox.

View all Send As permissions you've configured in your organization

Run the following command:
Command:
Get-RecipientPermission | where {($_.Trustee -ne 'nt authority\self') -and ($_.Trustee -ne 'null sid')}

Note The filter hides the automatic Send As permission that allows a user to send messages from their own mailbox, and also any results from system objects like mailbox plans.

Revoke Send As permission

Run the following command:
Command:
Remove-RecipientPermission <identity> -AccessRights SendAs -Trustee <user>

For example, to revoke Joanna's Vathis Send As permission for the TEST mailbox, run the following command:
Command:
Remove-RecipientPermission "TEST" -AccessRights SendAs -Trustee joannav@itprodev.onmicrosoft.com

Now Joanna can't send messages that appear to come directly from the TEST mailbox.
To skip the confirmation prompt, use -Confirm:$false.

How people use the Send As permission

Individual users or members of security groups with Send As permission can open their own mailboxes and send messages using the From address of the recipient.
Send As permission doesn't give a user access to another user's mailbox. To give an individual or members of a security group access to a mailbox, use the following command:
Command:
Add-MailboxPermission <mailbox> -User <user or security group> -AccessRights FullAccess

When you give someone access to a mailbox and Send As permission on the mailbox, that person can open the mailbox using their own credentials, compose new messages, and reply to messages in the mailbox.
An explanation of parameters
You use the Add-RecipientPermission, Remove-RecipientPermission, and Get-RecipientPermission cmdlets to add, remove and view Send As permissions. These cmdlets use the same basic parameters:

Identity This parameter specifies the target recipient. The user or group specified by the Trustee parameter can operate on this recipient.
You can specify any type of recipient. For example:

Mailboxes
Mail users
External contacts
Distribution groups
Dynamic distribution groups
The Identity parameter is a positional parameter. The first argument on a cmdlet is assumed to be the Identity parameter when no parameter label is specified. This lets you specify the parameter's value without specifying the parameter's name.

Trustee This parameter specifies the user or group to whom you're granting the permission. This allows the user or group to operate on the recipient specified by the Identity parameter.
You can specify the following types of users or groups:

Mailbox users
Mail users with a user account
Security groups

For the Identity and Trustee parameters, you can use any value that uniquely identifies the recipient.

For example:

Alias
Distinguished name (DN)
GUID
Name
Display name
LegacyExchangeDN
E-mail address

Additional Information’s:

Give Users Send As Permission
http://help.outlook.com/en-us/140/ff852815.aspx

How to get the list for SMTP address and Last connection time for all the users

Joannav — Sat, 11 May 2013 05:03:57 GMT

Summary
This article describes how to use PowerShell Commandlet to get the list for SMTP address and Last connection time for all the users.

Steps to implement the request

Step 1: Run the following to authenticate yourself and import PowerShell commands to your local session:

$LiveCred = Get-Credential
$Session = New-PSSession -ConfigurationName Microsoft.Exchange-ConnectionUri https://ps.outlook.com/powershell/ -Credential $LiveCred -Authentication Basic -AllowRedirection
Import-PSSession $Session

Image 1

Step 2: Run the Commandlet to get the SMTP address and Last connection time for all the users

Commandlet to get SMTP address:
Get-Mailbox | fl EmailAddresses, identity > C:\Emailaddress.csv

Image 2

Image 3

Image 4

Commandlet to get Last connection time:
Get-Mailbox -ResultSize unlimited | Get-MailboxStatistics | select-object identity,lastlogontime,lastlogofftime,DisplayName | sort-object DisplayName -descending | export-csv C:\Lastlogontime.csv

Image 5

Image 6

Image 7

Enjoy

How to configure user passwords to never expire in Office 365

Joannav — Fri, 10 May 2013 19:08:45 GMT

Setup Office 365 PowerShell Management Interface

The Office 365 PowerShell Management Interface offers the ability to administer service-wide features, and is not limited to a specific service like i.e. Exchange Online. The initial features that can be administered using this interface include the following:

Account SKUs
Company info
Contacts
Domains
Domain Federation
Groups
Partner Contracts
Role-based Access Control
Subscriptions
Users

This interface is available through a PowerShell Module available from here:

The Microsoft Online Services Sign-In Assistant 7.0 is a prerequisite for installing the Microsoft Online Services Module for Windows PowerShell, and is available from here:

When installed you can launch Windows PowerShell and perform the following steps:

001

002

003

004

Import-Module msonline

$cred = Get-Credential

Connect-MsolService -cred $cred

Get-Command –Module msonline

1) Import the module.

2) Create a credential-object stored in the variable $credimp

3) Create a new remote PowerShell connection against the PowerShell endpoint for Office 365

4) List the cmdlets available

Here is an overview of the available cmdlets:

Run command in Office 365 PowerShell Management Interface
For users who are not synchronized through directory synchronization
In Office 365, customers can use the Microsoft Online Services Module for Windows PowerShell (MOSMWP) to configure their user passwords to never expire. The following steps can be provided to customers who want to configure these settings for their users.

How to check if the "Password never expires" setting is enabled or disabled for a user

Connect to the Microsoft Online Services Module for Windows PowerShell by using your company administrator credentials.
Run the following command by using the user principal name (UPN) or the Microsoft Online Services ID of the user you want to check

Command:
Get-MSOLUser -UserPrincipalName <Microsoft Online Services ID> | Select PasswordNeverExpires

Additional, to check if the users "Password never expires setting" are set true, you can run the following PowerShell command:

Command:
Get-MSOLUser -UserPrincipalName joannav@itprodev.onmicrosoft.com | FL

Alternatively, to see all users and their "Password never expires setting", you can run the following PowerShell command:

Command:
Get-MSOLUser | Select UserPrincipalName, PasswordNeverExpires

How to enable the "Password never expires" setting

Connect to the Microsoft Online Services Module for Windows PowerShell by using your company administrator credentials.
Run the following command by using the user principal name (UPN) or the Microsoft Online Services ID of the user to configure the password for that user to never change:

Command:
Set-MsolUser -UserPrincipalName joannav@itprodev.onmicrosoft.com -PasswordNeverExpires $true

Note If you want to change the setting for all the users in an organization, run the following command:

Command:
Get-MSOLUser | Set-MsolUser -PasswordNeverExpires $true

How to disable the "Password never expires" setting

Connect to the Microsoft Online Services Module for Windows PowerShell (MOSMWP) by using your company administrator credentials.
Run the following command by using the user principal name (UPN) or the Microsoft Online Services ID of the user to disable the Password never expire setting for that user:

Command:
Set-MsolUser -UserPrincipalName <Microsoft Online Services ID> -PasswordNeverExpires $false

Note If you want to change the setting for all the users in an organization, use the following cmdlet:

Command:
Get-MSOLUser | Set-MsolUser -PasswordNeverExpires $false

For users who are synchronized through directory synchronization
The PasswordNeverExpires setting for synchronized users must be configured by using the steps earlier in this article.
There is no Active Directory property that can be synchronized to Office 365 to set the PasswordNeverExpires setting.

For more information
http://support.microsoft.com/kb/2666768

How to turn off blocked feature in OWA (Outlook Web App)

Joannav — Fri, 26 Apr 2013 08:30:46 GMT

PROBLEM

When you receive a new message in OWA (Outlook Web App), in receive address field appears the bellow message:
"To help protect your privacy, some content in this message has been blocked. If you're sure this message is from a trusted sender and you want to re-enable the blocked features, click here."

CAUSE

By default, OWA will block some external content in HTML messages, such as pictures or sounds linked within the message. These links are hidden references (not the underlined kind that you click to activate) in the HTML source code to an external location on the Internet, such as a website. They are triggered when the message is opened or previewed, which prompts a download of the external content. While some legitimate senders do this to avoid sending large messages, junk email senders use this technique to verify your email address as a legitimate one. Once verified, you will be targeted directly with more spam. If content is blocked, you will see this message: To help protect your privacy, some content in this message has been blocked. If you're sure this message is from a trusted sender and you want to re-enable the blocked features, click here.

SOLUTION

To work around this issue, you must create a test message without the blocked types of files, then send the test message to Exchange Online mailbox

Important: If it is not blocked, then, to help protect your privacy and prevent from any attack, it’s recommended not to change your default Outlook Web App Mailbox Policies.

If it is blocked, to check your Outlook Web App Mailbox Policies and change it, you can proceed with the following steps:

Install and Configure Windows PowerShell
Run the following command:

a. Run Get-OwaMailboxPolicy and check the BlockedMimeTypes and AllowedMimeTypes

b. Run Set-OwaMailboxpolicy to change the blocked and allowed file types:

3. Set-OwaMailboxPolicy -Identity OwaMailboxPolicy-Default -AllowedFileTypes ".pdf", ".doc" and click Enter

4. Run again Set-OwaMailboxPolicy and check AllowedFileTypes and you'll see that ".pdf", ".doc" are allow files

For additional information, please refer to the following pages:

PST Capture Tool 2.0 for Office 365

Joannav — Thu, 25 Apr 2013 07:01:31 GMT

Overview

PST Capture 2.0 is used to discover and import Outlook Personal Folder (.pst) File Format files into Exchange Server and Exchange Online. PST Capture helps an organization that wishes to gain more control over their email data repositories by placing them into Exchange. By optionally installing PST Capture Agents on target machines, administrators can determine where .pst files are located and who their file owner is via the PST Capture Console. Administrators can import .pst files via Import Lists to Exchange Server or Exchange Online. Data can be directly imported into the primary mailbox or associated archive mailbox.

PST Capture tool that allows you to hunt down PST files on client computers across your network. After it finds PST files on users’ computers, the tool consolidates the PST files to a central location, and then easily injects PST data to primary or archive mailboxes on your on-premises Exchange Servers or Exchange Online.

What’s new in PST Capture 2.0?

PST Capture 2.0 includes the following improvements:

Support for Microsoft Exchange Server 2013
Updated profile generation code to use Outlook Anywhere (RPC over HTTP).
Fixed Exchange Online import failure issue when PST Capture is not installed on an Exchange server.
Removed User Interface limit of 1,000 users when performing an import to Exchange Online.
General performance improvements

Download PST Capture 2.0 from the Download Center (aka.ms/getpstcapture), check out the PST Capture documentation (aka.ms/pstcapture) and then go get those PSTs!

How to install and configure it to work with an on-premise Exchange environment and Office 365

Installation

The PST Capture Tool is made of the Console (which includes the Central Service) and one or more Agents. First, let’s start by downloading the tool and installing the PST Capture Console.

In the folder where you downloaded the .msi files for the PST Capture tool, double click PSTCapture.msi. This opens the Microsoft Exchange PST Capture Setup wizard.
On the Welcome screen, click Next.

Figure 1: Console Installation - Welcome

3. On the End-User License Agreement screen, tick the “I accept the terms in the License Agreement” box and then click Next.

Figure 2: Console Installation - End-User License Agreement

4. On the Destination Folder screen, chose the folder where you want to install the PST Capture Console and then click Next.

Figure 3: Console Installation - Destination Folder

5. On the Service account screen, specify the user name and password for the service account that you want the Central Service to use to import PST files (refer to the Permissions table in the first article of this series) and then click Next.

Figure 4: Console Installation – Service Account

6. On the Ready to install Microsoft Exchange PST Capture screen, review your installation choices and then click Install.
7. When the installation completes, click Finish to close the Microsoft Exchange PST Capture Setup wizard.

Figure 5: Console Installation Completed

You should now see a new Microsoft Exchange PST Capture Service service installed:

Figure 6: PST Capture Service

As I mentioned before, you can manually specify the file names of PSTs to import, thus overcoming the need for an agent. However, one of the main purposes of this tool is to help with the discovery of e-mail data (in this case PSTs) in your organization. After all, do you know exactly where all the PSTs are on your network?

Configuration

Before we start looking for PST files and importing them into Exchange, let’s first have a look at the available configuration options by clicking on Tools and then Settings in the main window:

Figure 7: PST Capture Console main window

The first options screen available refers to Online Connection Settings - how we connect to Office 365:

Username: this is the username the tool will use to import PSTs to your mailboxes. Remember, if importing to Office 365, this account must be assigned the Organization Management role and if importing to Office 365, Exchange Online Administrator permissions
Password: type the password for the account mentioned above
Grant delegate access to this mailbox: this option allows the PST Capture to grant the specified user account Full Access permissions to the mailboxes to which PSTs will be imported to (be aware that these permissions are not removed after the import!). If you don’t select this option, you will need to grant Full Access permissions manually
Server: this is the server the tool will connect to for importing PST files. To determine what your server is in Office 365, login to Outlook Web App and then click in Options > See All Options > Account > My Account > Settings for POP, IMAP, and SMTP access
The above is an Office 365 server: select this option if you are importing data into mailboxes in Office 365. If you are importing into BPOS, clear this check box.
Check password and connectivity: use this to verify that you can successfully connect to Office 365. If all goes well as in the screenshot below, the OK button will be enabled

Figure 8: Settings – Online Connection

On the Message Import Settings screen, we can specify whether to import PSTs to a new folder at the root of the mailbox, or to another folder of our choice. We can also chose a name for the folder or create it with the same name of the PST file. Finally, we decide what to do in case a folder or subfolders already exists:

Figure 9: Settings – Message Import

Next, we have Archive Mailbox Settings which allows us to select where to import PSTs to. By default none of the boxes are ticked and, as such, PSTs are imported to the user’s “normal” mailbox. I am guessing most organizations will use this tool so they can import PST files directly to users’ archive mailboxes so I ticked the first box. This way, PSTs will only be imported if users are enabled for archiving (probably not the best option, but it will allow us to test the behavior of the tool when a user is not enabled for archiving):

Figure 10: Settings – Archive Mailbox

In Non-mail Items Settings we decide if we want to import non-mail items, meaning calendar items, contacts, tasks, notes and journal items. If in the Message Import Settings page I hadn’t selected the Create a subfolder for each PST file check box, non-mail items will be placed in their respective folder. For example, contacts will be placed in the Contacts folder and meetings in the Calendar folder.

Figure 11: Settings – Non-mail Items

To specify where all PSTs should temporarily be kept while being imported, as well as the maximum size of the folder that will hold them, we use the Staging Area Settings screen. The maximum size for the folder doesn’t have to be huge as after every successful or failed import, PSTs are automatically deleted.

Figure 12: Settings – Staging Area

The next option is similar to the –BadItemsLimit parameter when exporting or moving mailboxes in Exchange – it sets the limit of failed items to be skipped before the import process is cancelled. If this box is cleared, the PST Capture tool will try to import PSTs regardless of how many errors it finds.

Figure 13: Settings – Import Tolerance

Finally, we get to the General Settings screen. This is where we can change the default port that agents and the console use to communicate and how often the agents poll information from the Central Service. In my case I left the default values as I am testing this in a lab environment. In production I would probably increase the PST Agent polling interval to 15 minutes or more.

Figure 14: Settings – General

Enjoy..

Troubleshoot email delivery using the Exchange Online message trace tool

Joannav — Wed, 24 Apr 2013 12:18:09 GMT

Office 365 Small Business admins can troubleshoot mail flow
problems by using the Exchange Online message trace tool in the Exchange admin
center. The tool helps admins track specific messages sent in the past seven
days. After you run a message trace, if you can’t diagnose the problem
yourself, you can use the detailed information from the tool to post a question
to the Office 365 Community or to submit a service request.

Run a message trace

The message trace tool is located in the Exchange admin center
(EAC), which is connected to the Office 365 portal.

Access the EAC

In the Office 365 portal, at the top of the page, select Admin and choose Exchange.

In Outlook Web App, go to the address bar in your browser and replace the URL to the right of https://outlook.office365.com/ with ECP.
For example, if your Outlook Web App URL is https://podxxx.outlook.com/owa/..., change it to https://podxxx.outlook.com/ECP, and hit ENTER. That will take you to the Exchange admin center.
Bookmark the EAC in your browser for future access.

Set up the message trace

In the EAC, go to Mail flow > Message trace.

5. Fill out the following fields, as needed. None of these fields is required. If you click Search without entering anything, you’ll get all message trace data for the default time period, which is the last 48 hours.

Sender Narrow the search to specific senders by adding users to the Sender field.
Click Add users, select one or more senders from your organization, and then click Add. To add external users who aren’t on the list, in the Check names box, type their email addresses and click Check names. When you are done, click OK.
Recipient Narrow the search to specific recipients by adding users to the Recipient field.
Click Add users, select one or more recipients from your organization, and then click Add. To add external users who aren’t on the list, in the Check names box, type their email addresses and click Check names. When you are done, click OK.
Message was sent or received Select the time interval during which a message was sent or received. Choose among:
Last 24 hours
Last 48 hours This is the default value.
Last 7 days For messages sent or received within the last seven days, starting at 12:00 A.M. on the day you run the message trace.
Custom Select the time zone and the time interval you want.

Note Data is retained by the service for seven days.

Delivery status You can search by the specific status of a message or messages. Leave this field blank to cover all statuses. Otherwise, choose among:
Delivered The message or messages were successfully delivered to the intended destination.
Failed The message or messages weren’t delivered. Either delivery was attempted and failed, or delivery was prevented by the filtering service. For example, the filtering service may have determined that a message contained malware.
Pending Delivery of the message or messages is still being attempted or re-attempted.
Expanded The message or messages were sent to a distribution group and was expanded so the members of the group can be viewed individually.
Unknown Delivery status is unknown and no details are available.
Message ID The Internet message ID (also known as the client ID) found in the header of the message with the Message-ID: token. Its format varies depending on the sending mail system. The following is an example: <08f1e0f6806a47b4ac103961109ae6ef@server.domain>. If you know the message ID, it may help in troubleshooting.

6. Click Search to run the message trace. To change your search criteria, click Clear.