As you may know, the Exchange Online ActiveSync Protocol and configuration is set to limit messages attachments to 10MB or less. When sending an attachment that is close to 10MB, you will need to look at compressing/zipping the file to a smaller size before the EXO ActiveSync protocol will allow the message to be delivered. When using an ActiveSync device, such as a mobile phone, iOS (iPad, iPhone, etc) device, it may be difficult to get the attachment zipped and then sent, but at this time this is the only way in which you can work within the ~10MB ActiveSync configuration setting.
- Save the file to your desktop
- Zip/Compress the file to decrease the size of the file, the more compression the better to make sure you don’t hit this 10MB attachment limit
- Connect your ActiveSync device and bring the file back into the device or send mail, attaching the compressed attachment
As many administrators may know, Outlook 2011 for the Mac does not have Junk Mail management capabilities at this time. The MAC BU is working on an update for Outlook, so in the meantime Mac Outlook 2011 clients can use the following methodology to manage their Junk Mail and configuration settings:
When using Office 365 and initially connect into Office 365 services, whether that is the Microsoft Online Portal, OWA, SharePoint, etc, that identity is cached within iexplorer.exe, across all instances of IE, across each of the tabs. So if you attempt to login to Hotmail, for example, your Office 365 Identity will be presented, as it is cached, and will fail to open your Live services, such as Skydrive, Hotmail email, etc.
Internet Explorer has an “InPrivate” setting which gives you an additional session, but you may need more than two IE’s or Tabs using different Identities. To use more multipleidentities you can use This article, which explains how you can use Firefox to set up infinite sessions using separate Identities. You can now be logged into multiple online tenants simultaneously, while keeping each of the identities separate. Note – Office 365 does support Firefox.
You can use the below information to create a .vbs file, and pin to Taskbar, Start Menu or Desktop and when run, will launch 3 separate versions of FireFox, each able to maintain their own session and identity:
Dim objShell Set objShell = CreateObject("Wscript.Shell") objShell.Exec """C:\Program Files (x86)\Mozilla Firefox\firefox.exe"" -no-remote -P ""Session1""" objShell.Exec """C:\Program Files (x86)\Mozilla Firefox\firefox.exe"" -no-remote -P ""Session2""" objShell.Exec """C:\Program Files (x86)\Mozilla Firefox\firefox.exe"" -no-remote -P ""Session3"""
For those of you who use Exchange Online 365 and Outlook for your day-to-day messaging needs, you may have found a cap of 128k worth of rules that can be processed. This size comes from the size of the Outlook .rwz file which holds your Outlook rules. As you start to create additional rules, the size of this file will grow and once you have reached ~128k, any rules created after that will not fire/work. To reduce the size of this file and by extension be able to run a larger amount of rules, you can use the following approach, which significantly reduces the size of the rules, which mean more rules can be created and used:
- When creating Outlook rules, when prompted to browse to select a user alias/DL, etc MANUALLY type the alias
- When you browse and select a user/group, the entire Distinguished Name (DN) is used and populated into the .rwz file, which significantly increases the file size, thus limiting the amount of entries you can have/use.
Great article on how you can use Office 2003 with Office 365. As you may already know Outlook 2003 can be used with Exchange Online 365, however it can only be used with the POP3 or IMAP4 & SMTP protocols. this is because of the way Outlook 2003 leverages MAPI and RPC/HTTP, so a decision was made to support Outlook 2003 but only for these down-level protocols. So if you are using Office 2003 and Office 365, this is a great article on what you can expect with regards to your usage experience:
Outlook Password Notifications & Exchange Online 365 – Password Expiration Notifications are Coming!!!
Problem: Office 365 Customers using managed (OrgID Based) accounts will not know when passwords will expire (if enabled for expiration). Further, Outlook’s behavior when the password expires is to go into a disconnected state, without notifying the user of what the problem is or what is required to resolve it. Opening Outlook and providing an expired password will continually prompt the user just as if they had mistyped the password.
Solution Overview: Once customers deploy an upcoming Outlook update, they will receive a notification 14 days before their password will expire for managed accounts. The notification will include a link to a password change page hosted by OrgID. If they try to logon after the password has already expired (when returning from vacation for example), they will also receive notification that their password has expired and will be provided a link to use to change it.
Forecasted Resolution Date: With the Outlook August 2012 Cumulative Update.