Month: November 2012
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 you may know, in BPOS using DirSync that Security Groups (SGs) are converted into Distribution Groups(DGs) as BPOS did not have Security Groups as a type. Many administrators who needed SGs for use in Outlook Delegation and/or SharePoint groups (assign permissions to groups and manage users in the group for effective management) had to request BPOS Operations to make this conversion back to SGs on behalf of the customer/administrator.
Customers who Transitioned from BPOS into Office 365 may fall into the following scenario:
- Transitioned into Office 365 from BPOS
- Ran DirSync V2 against Office 365 and found that their on-premises Active Directory Security Groups (SGs) are STILL listed as Distribution Groups in the new Exchange Online 365 environment, effectively not able to be used for security purposes.
When BPOS DirSync converts SGs to DGs for use, when the BPOS to Office 365 Transition completed, the DGs are brought over as DGs because that is the groupType set. Once you run Directory Synchronization V2 against Office 365, Directory Synchronization does not check the groupType setting and finds the group already in the cloud and as such will NOT convert the group back to a Security Group (SG).
To fix this issue without needing to delete the on-premises Active Directory groups (delete, recreate and start over), you can use Directory Synchronization Filtering to have these groups removed in the cloud, so they can be created as SGs instead of being stuck as a DG. For more information on Directory Synchronization Filter, please refer to:Configure Filtering for Directory Synchronization http://technet.microsoft.com/en-us/library/jj710171.aspx
Use the above approach to put the DGs into a separate OU and configure DirSync Filtering to NOT synchronize that OU. This will instruct DirSync to tell O365 MSODS that the groups have been removed and to remove them from the cloud. Once done and verified that the groups are no longer available, DirSync Filtering can be removed by putting the groups back into the normal OU container and run DirSync. It will pick up these groups, find they are SGs and synchronize them into the cloud.
Once the above has been done you will have effectively replaced the old DGs (converted during the BPOS DirSync operation) with the proper groupType as Security Group(s).
For customers who have limited Internet Bandwidth, it may become a challenge for all users to stream the Office 2013 installation, as all the binaries, configurations, etc are streamed for each individual. For administrators who need to shield their bandwidth, they can download the Office 2013 suite installation bits and allow for an internal Office 2013 installation, without the need for each user to stream the install, also known as Click-2-Run (C2R).
Download Office 2013
To download Office product and language files to your local network and then deploy those products and languages to Office 365 users, you use the Office Deployment Tool.
To specify which products and languages are downloaded and installed by the Office Deployment Tool, you create a customized Configuration.xml file. When you run the Office Deployment Tool, the tool reads the information in the customized Configuration.xml file and then downloads or installs the specified products and languages.
A common deployment method is to place the downloaded Office product and language files on a network share on the local network. Then users can install Office from that location. You can simplify and automate the process for the users by using a script or batch file. The script or batch file can also be used by a software distribution product, such as System Center Configuration Manager, or in a Group Policy computer startup script.
For more information about how to use the Office Deployment Tool, see the following articles:
- Office Deployment Tool for Click-to-Run
- Click-to-Run for Office 365 Configuration.xml file
- Download Click-to-Run for Office 365 products by using the Office Deployment Tool
- Deploy Click-to-Run for Office 365 products by using the Office Deployment Tool
Question: Is there an .msi file I can download instead of using the above information?
Answer: No, C2R is a streaming application using the following endpoints: