• How much bandwidth do I need for my users connecting to Exchange Online?

     

    This question was from a university in Chicago adopting Office 365 for faculty, staff, and students.

    Prerequisites


    The first data point you need to gather before you can determine client bandwidth required for Exchange Online is what is your mailbox usage profile?  Are your users light, medium, heavy, or very heavy email users?  How can you determine this?

    If you have Exchange 2003/2007/2010 on prem you can use a tool called the Exchange Profile Analyzer to run against your infrastructure to gather this crucial data point. See my other blog post here for more info.

    If you migrating from another email system, you will have to gather some mail usage data points either manually or using other message profile statistics. Once you gather the data points you can associate it with the daily mail profile in the matrix below.

    Here is a usage matrix we use to determine the mailbox usage profile:

    image

     

    What are the default bandwidth profiles?

    After you gather your mailbox usage profile data based on above, you need to associate it to a light, medium, heavy bandwidth profile.  This data was gathered by our internal teams and is still being finalized but it will provide you a rough estimation of bandwidth required for your institution.

     

    Exchange Online Light email user profile bandwidth

    image

     

    Exchange Online Medium email user profile bandwidth

    image

     

    Exchange Online Heavy email user profile bandwidth

    image

     

    Exchange Online Very Heavy email user profile bandwidth

    image

     

    New released Exchange Bandwidth calculator 

    We just shipped a very useful Exchange bandwidth calculator you can use with on prem Exchange 2010 or Exchange Online.

    Download the newly released beta Exchange client network bandwidth calculator here.

    Download the newly released Exchange client network bandwidth guide here.

     

    Plug in the numbers based on the site user mail profile determined above. NOTE: make sure you only use Outlook Anywhere cached (OA-cached column) and OWA 2010 column for Exchange Online. The other columns apply to Exchange on prem only.

     

    Bandwidth estimation examples:

    If I have a school that has 3000 Outlook 2010 light users and 1000 Outlook Web App light users connecting to Exchange Online. What estimated bandwidth do I need?

    image

    6.4 Mb/s Exchange to client traffic and .99 Mb/s client to Exchange.

     

    If I have a school with 50,000 faculty,staff and students with 8000 Outlook 2010 light faculty and 42000 Outlook Web App Light users for students connecting to Exchange Online. What estimated bandwidth do I need?

      

    image

    63 Mb/s Exchange to client traffic and 16.97 Mb/s client to Exchange

      

     

    What is the recommended maximum network latency?

    It recommended your network have no more than 320ms round trip latency.

  • Service Update: Sender Photo Enabled by Default

    Here’s a preview of the new Sender Photo feature that is enabled by default for all Outlook Live and Exchange Online users after the December 2011 Service Update. We’ve included some guidance on how to configure Sender Photo and how to disable it (in case a school requires that it be disabled).

    In the screenshots below, the Sender Photo appears in Global Address List (GAL) entries, email messages, and various other places in Outlook Web App and Microsoft Outlook 2010. 

     

                           

     

     

    Configure Sender Photo Settings

    The Sender Photo feature is enabled by default for all Outlook Live and Exchange Online users after the December 2011 Service Update. If you’ve not yet received the update, then please know that it is coming soon. The updates should be completed by April 2012.

    For additional information, please see Service Updates for Office 365 for enterprises and education.

    To confirm the current configuration, Connect Windows PowerShell to the Service and run the following Get-OwaMailboxPolicy command. The results will be slightly different for Outlook Live or Exchange Online.

    View Sender Photo Settings in Outlook Live (Live@edu)

    Get-OwaMailboxPolicy | FL Name,DisplayPhotosEnabled,SetPhotoEnabled,SetPhotoURL

    Name
    DisplayPhotosEnabled
    SetPhotoEnabled
    SetPhotoURL

    Name
    DisplayPhotosEnabled
    SetPhotoEnabled
    SetPhotoURL
    :
    :
    :
    :

    :
    :
    :
    :
    OwaMailboxPolicy-DefaultMailboxPlan
    True
    True


    OwaMailboxPolicy-GalDisabledMailboxPlan
    True
    True

    View Sender Photo Settings in Exchange Online (Office 365 for education) 

    Get-OwaMailboxPolicy | FL Name,DisplayPhotosEnabled,SetPhotoEnabled,SetPhotoURL

    Name
    DisplayPhotosEnabled
    SetPhotoEnabled
    SetPhotoURL
    :
    :
    :
    :
    OwaMailboxPolicy-Default
    True
    True

    The DisplayPhotosEnabled, SetPhotoEnabled, and SetPhotoURL attributes make up part of an OWA Mailbox Policy. An OWA Mailbox Policy is assigned to each user mailbox.

    In Outlook Live, a user mailbox will have either OwaMailboxPolicy-DefaultMailboxPlan or OwaMailboxPolicy-GalDisabledMailboxPlan. The OWA Mailbox Policy is set on the mailbox at the time of creation and corresponds to the original Mailbox Plan, e.g. DefaultMailboxPlan or GalDisabledMailboxPlan.

    In Exchange Online, a user mailbox may have OwaMailboxPolicy-Default or may have a custom OWA Mailbox Policy. Exchange Online Administrators can create new policies using the New-OwaMailboxPolicy cmdlet and can assign policies to user mailboxes using the Set-CASMailbox cmdlet.

     

    How to Disable Sender Photo in Outlook Web App

    An Outlook Live or Exchange Online Administrator can restrict the Sender Photo in OWA feature:

    1. Prohibit users from uploading their own photo using the SetPhotoEnabled parameter;
    2. Prevent users from viewing photos in OWA using the DisplayPhotosEnabled parameter; and/or
    3. Redirect users to an alternate URL when attempting to upload a photo using the SetPhotoURL parameter.

    Disable Sender Photo in OWA on Outlook Live (Live@edu)

    With Outlook Live, there are two OWA mailbox policies, OwaMailboxPolicy-DefaultMailboxPlan and OwaMailboxPolicy-GalDisabledMailboxPlan.

    An Outlook Live administrator can change the settings of these existing OWA mailbox policies with the Set-OwaMailboxPolicy cmdlet, However, an Outlook Live administrator cannot create new policies with the New-OwaMailboxPolicy cmdlet and cannot assign a different policy to an existing user mailbox with the Set-CASMailbox cmdlet.

    What does this mean? An Outlook Live admin is limited to using the two built-in policies and cannot change the existing policy assigned to a user mailbox. If a mailbox is created using the DefaultMailboxPlan and is later changed to the GalDisabledMailboxPlan, the mailbox may still have the OwaMailboxPolicy-DefaultMailboxPlan OWA mailbox policy assigned to it.

    The following Remote PowerShell commands disable (for all mailbox-enabled users) the ability to change the picture and the ability to view Sender Photos in OWA.  

             
    # Configure the policies. Disable Sender Photo for ALL.
    Set-OwaMailboxPolicy –Identity OwaMailboxPolicy-DefaultMailboxPlan –DisplayPhotosEnabled $false –SetPhotoEnabled $false;            
    Set-OwaMailboxPolicy –Identity OwaMailboxPolicy-GalDisabledMailboxPlan–DisplayPhotosEnabled $false–SetPhotoEnabled $false;

    The following Remote PowerShell commands enable (for some mailbox-enabled users) the ability to change the picture and the ability to view Sender Photos in OWA. And it disables Sender Photo for mailboxes with the OwaMailboxPolicy-GalDisabledMailboxPlan assigned to the mailbox.


    # Configure the policies. Enable Sender Photo for OwaMailboxPolicy-DefaultMailboxPlan.
    Set-OwaMailboxPolicy –Identity OwaMailboxPolicy-DefaultMailboxPlan –DisplayPhotosEnabled $true –SetPhotoEnabled $true;             

    # Configure the policies. Disable Sender Photo for OwaMailboxPolicy-GalDisabledMailboxPlan.
    Set-OwaMailboxPolicy –Identity OwaMailboxPolicy-GalDisabledMailboxPlan –DisplayPhotosEnabled $false–SetPhotoEnabled $false;

    Disable Sender Photo in OWA on Exchange Online (Office 365 for education)

    With Exchange Online, there is one default OWA mailbox policy, OwaMailboxPolicy-Default.  

    An Exchange Online administrator can change the settings of this existing OWA mailbox policy with the Set-OwaMailboxPolicy cmdlet. And, an Exchange Online administrator can create new policies with the New-OwaMailboxPolicy cmdlet and can assign a different policy to an existing user mailbox with the Set-CASMailbox cmdlet.

    What does this mean? An Exchange Online admin could create multiple custom policies and apply a different policy to multiple subsets of users. NOTE: While this does allow for some additional flexibility, it can be more difficult to manage over time.

    The following Remote PowerShell commands disable (for all mailbox-enabled users) the ability to change the picture and the ability to view Sender Photos in OWA (assumes there aren’t already any custom OWA mailbox policies in use).


    # Configure the policy. Disable Sender Photo for ALL.
    Set-OwaMailboxPolicy –Identity OwaMailboxPolicy-Default –DisplayPhotosEnabled $false –SetPhotoEnabled $false;

    The following Remote PowerShell commands enable (for some mailbox-enabled users) the ability to change the picture and the ability to view Sender Photos in OWA by creating a new OWA mailbox policies and assigning it to user mailboxes.  And it disables Sender Photo for mailboxes with the OwaMailboxPolicy-GalDisabledMailboxPlan assigned to the mailbox.

    For additional information, please see Create and Assign Outlook Web App Mailbox Policies in Office 365.

    // Create a new policy.
    New-OwaMailboxPolicy –Name OwaMailboxPolicy-Unrestricted;              

    // Configure the policies.
    Set-OwaMailboxPolicy –Identity OwaMailboxPolicy-Default –DisplayPhotosEnabled $false –SetPhotoEnabled $false;
    Set-OwaMailboxPolicy –Identity OwaMailboxPolicy-Unrestricted –DisplayPhotosEnabled $true –SetPhotoEnabled $true;

    // Assign the new policy.
    Set-CASMailbox –Identity chris.cannon@contoso.edu –OwaMailboxPolicy OwaMailboxPolicy-Unrestricted;
    Set-CASMailbox –Identity ann.beebe@contoso.edu –OwaMailboxPolicy OwaMailboxPolicy-Unrestricted;

    NOTE: You may receive an error message while creating the first custom policy, e.g. “This operation is not allowed for the organization with disabled customizations.” For additional information, please see Enable-OrganizationCustomization.

     

    How to Report on Users’ Sender Photo Settings

    Prior to configuring the Sender Photo feature, it may be useful to generate some reports on the current status of the environment.

    For example, an administrator might ask some basic questions, e.g. “If I enable Sender Photo for an OWA mailbox plan, what users will have Sender Photo enabled?” or “What users have already uploaded Sender Photos?”

    View the OWA mailbox policy assigned to user mailboxes

    The following Remote PowerShell commands will return the OWA mailbox policy that is currently assigned to user mailboxes that begin with the letters ‘a’, ‘b’, ‘c’ and ‘d’.


    # Get mailboxes that begin with a, b, c and d.
    $mailboxes = Get-Recipient -ResultSize unlimited –RecipientType UserMailbox -Filter {(Name -ge "a") -and (Name -lt "e")};

    # Get the OWA mailbox policy for each mailbox.
    foreach ($mailbox in $mailboxes) {Get-CASMailbox $mailbox.Identity | Select Name,PrimarySmtpAddress,OwaMailboxPolicy;};

    Example Results:

    Name
    ------
    Administrator
    Ann Beebe
    Chris Cannon
    PrimarySmtpAddress
    -----------------------
    admin@contoso.edu
    ann.beebe@contoso.edu
    chris.cannon@contoso.edu
    OwaMailboxPolicy
    ----------------
    contoso.edu\OwaMailboxPolicy-GalDisabledMailboxPlan
    contoso.edu\OwaMailboxPolicy-DefaultMailboxPlan
    contoso.edu\OwaMailboxPolicy-DefaultMailboxPlan

    View the Picture status of user mailboxes

    The following Remote PowerShell commands will help determine whether or not users have a Sender Photo. It lists the HasPicture property of all mailboxes that begin with the letters ‘a’, ‘b’, ‘c’ and ‘d’.


    # Get mailboxes that begin with a, b, c and d.
    $mailboxes = Get-Mailbox -ResultSize unlimited -Filter {(Name -ge "a") -and (Name -lt "e")};

    # Get the Picture status for each mailbox.
    foreach ($mailbox in $mailboxes) {Select -InputObject $mailbox -Property Name,PrimarySmtpAddress,HasPicture;};

    Example Results:

    Name
    ------
    Administrator
    Ann Beebe
    Chris Cannon
    PrimarySmtpAddress
    -----------------------
    admin@contoso.edu
    ann.beebe@contoso.edu
    chris.cannon@contoso.edu
    HasPicture
    -----------
    True
    True
    False

    Questions about the previous PowerShell commands

    Questions: “Why are we only reporting on mailboxes that begin with the letters ‘a’, ‘b’, ‘c’ and ‘d’? Why not use a pipeline and get ALL mailboxes at the same time?”

    Example with Pipelining:

    Get-Recipient –RecipientType UserMailbox –ResultSize unlimited | Get-CASMailbox | Select Name,PrimarySmtpAddress,OwaMailboxPolicy;
    Get-Mailbox –ResultSize unlimited | Select Name,PrimarySmtpAddress,HasPicture;

    Answer: Outlook Live and Exchange Online tenants (especially large tenants) will experience throttling and/or memory issues in PowerShell when piping large collections, lists or arrays. Using Filter to add a smaller collection of objects to a variable and using a foreach loop to execute a small script block is more efficient.

    Question: “Doesn’t this mean that I will have to execute multiple commands in order to get the results for ALL mailboxes?”

    Answer: Maybe. But the overall job may complete much faster this way.

    Question: “Isn’t there a better way?”

    Answer: Absolutely. One “better way” might be to create a script the runs the smaller batches in a specific order and exports the results to multiple CSV files, e.g. AThruD.csv, EThruH.csv, IThruL.csv. Another “better way” might be to open up multiple PowerShell sessions, and runs a different batch in each session. Or use Import-CSV instead of Get-Recipient/Get-Mailbox (requires a CSV file of mailbox Identities). Or…

    Do you have a “better way” to generate reports with PowerShell? We’d love to hear it! Leave us a Comment below.

     

    How to Change Sender Photo with OWA

    With DisplayPhotosEnabled $true and SetPhotoEnabled $true, an Outlook Live or Exchange Online mailbox-enabled user can add, change, and remove an image in Outlook Web App by selecting “Change Picture” from the menu in upper-right corner of OWA.

    gal-sender-photo-default-owa

    gal-sender-photo-selected-owa
    gal-sender-photo-change-picture-owa

    If the SetPhotoURL parameter is set to $null in the OWA mailbox policy assigned to the user’s mailbox (this is the default), then the user will see the following “Change Picture” dialog box.

    gal-sender-photo-change-current-picture-owa

    For Exchange Online tenants, if the SetPhotoURL parameter is set to https://portal.microsoftonline.com/EditProfile.aspx, the user will be redirected to the “My profile” dialog in the Office 365 Portal. According the this Help Article here, the My profile picture ”will appear in all services that display a photo.”

    In our testing, the My profile pictures are not currently sync’ing from the Office 365 Portal to Exchange Online. Coming soon?

    gal-sender-photo-portal-profile
    gal-sender-photo-portal-profile-change
    gal-sender-photo-portal-profile-upload
    gal-sender-photo-portal-profile-selected
           

     

    How to Change Sender Photo with Active Directory

    If a school use directory synchronization, e.g. OLSync or DirSync, the Sender Photo can be sync’d from on-premises Active Directory. The photo stored in the thumbnailPhoto AD attribute is “pushed” to Outlook Live or Exchange Online. This allows for centralized management of Sender Photos from Active Directory.

    In this scenario, the user or admin requires a method to set the photo in AD.

    One recommendation is to deploy an Internet-facing website that allows a user to set one’s photo in on-premises AD. The URL for this website can be added to the OWA mailbox policy using the SetPhotoURL parameter. The website will set the photo in on-premises AD, and OLSync or Dirsync will synchronize the photo to Outlook Live or Exchange Online.


    # Redirect Change Picture requests in OWA to on-premises website
    Set-OwaMailboxPolicy –Identity OwaMailboxPolicy-Default –SetPhotoURL “https://www.contoso.edu/UserPhotoWizard.html”

    If an Internet-facing website is not an option, there are additional ways to add a user’s photo to your on-premises AD.

    A quick search on Bing for ‘thumbnailPhoto AD’ (or something similar) should return many options, e.g. third-party tools and various scripts.

    The following Windows PowerShell commands will set a user’s photo in on-premises AD using the ActiveDirectory module available on Windows Server 2008 R2. This script could be slightly modified to add user photos in bulk.


    # Add the school logo as the picture for two users.
    Import-Module ActiveDirectory;
    $photo = [byte[]](Get-Content “C:\Images\school_logo.jpg” -Encoding byte);
    Set-ADUser –Identity chris.cannon -Replace @{thumbnailPhoto=$photo};
    Set-ADUser –Identity ann.beebe -Replace @{thumbnailPhoto=$photo};

    NOTE: Sync’ing photos with OLSync is not configured by default. It requires changes to the OLSync Hosted MA. The changes are relatively minor. Basically, create an export flow for mailboxes in Configure Attribute Flow of the Hosted MA, e.g.  Picture (Hosted) <— thumbnailPhoto (MV).

    There is a little bit more to it, so we’ll update this post when we have some screenshots. In the meantime, you can Contact Us for additional information.

     

    ______________________________

    Thanks for joining us today!

    Zion Brewer

    ______________________________

  • Updated Message and Recipient Limits - Live@EDU

    Outlook Live accounts have historically been 500 recipients per day. Microsoft has recently updated this policy to be in line with the Exchange Online offering in Office 365. All newly provisioned tenants will see these new limits immediately. For those customers who are already on Live@EDU, you should either see these now or you will see the changes over the upcoming weeks.

    For some additional information about limits and options for supporting bulk email please refer to articles shown below.

    There is a recipient rate limit, often called a sender limit or sending limit, for cloud-based e-mail accounts. This limit defines the maximum number of recipients that can receive e-mail messages sent from a single cloud-based account in a 24-hour period. The recipient rate limit for Exchange Online is 1,500 recipients per day.

    http://help.outlook.com/140/ff381292.aspx

    http://help.outlook.com/en-us/140/Dd630704.aspx

  • How to integrate Live@edu into Moodle 2.0

    Moodlerooms, Inc., has developed an integration connecting Microsoft’s Live@edu services and Moodle, the world’s most widely-used Learning Management System. With this integration, Moodlerooms makes the rich functionality of Live@edu directly accessible within the Moodle 2.0 and 1.9 environments via single sign-on.

    The plug-in for Moodle allows users to log into courses using their Windows Live ID; view and compose emails and calendar events, chat using Windows Live Messenger and search using Bing™ all from within a Moodle class site.


    Microsoft’s Frank Chiappone talks about the new plugin.

    You can download the free plugin directly from Moodle.org. Give it a go today!


    Are you using Live@edu with Moodle?

    Are you currently using the Live Services Plugin? How do you use use Live@edu with your Moodle environment? Let us know in the comments!

  • Read twice, send once… Delaying outgoing mail with rules.

    Measure twice, cut once…

    “Keep it as long as you can, as long as you can”, the 6 Ps* – whichever adage you use to prevent making a mistake there’ll always be that time when you let one little thing slip. Maybe it’s accidentally hitting send on a email to your boss telling them what you really think of them, or sending sensitive information out to the wrong people. Chances are it has happened to all of us at one point or another. The good news is it doesn’t have to happen again!

    In Microsoft Outlook you can set up some simple rules to delay the delivery of a message so that you always have a safety window to go back and check or edit a message before it actually goes! Personally, I have my Outlook client set to delay by 1 minute, and it has never let me down! This is especially useful if you forgot to attach something, missed off a recipient or made a spelling mistake.

    You can find out more about how to configure this for your version of Outlook here:

    Total Recall

    Of course, sometimes even a delay isn’t enough – but there is one feature up our sleeve that might be able to help. The recall feature of Microsoft Outlook tries to stop delivery and, optionally, replace an email message that you have already sent to another Microsoft Exchange Server user within your institution. While not 100% guaranteed to stop a message being read, if you’re an Exchange user (if you’re using Outlook Live as part of Live@edu, or Exchange Online as part of Office 365, then that’s you!) you can always try it as a last resort.

    As above, you can find out more information about the message recall feature here:

    Now you should have all the safeguards in place to ensure that you always say what you mean to say, and to whoever you mean to say it!

    *Proper Planning Prevents Pretty Poor Performance


    How do you do it?

    Ever fallen foul of the send button? Do you have a different technique for delaying and avoiding embarrassment? Let us know in the comments!