It features a simple interface with many customizable options:. Download multiple files at one time Download large files quickly and reliably Suspend active downloads and resume downloads that have failed. Yes, install Microsoft Download Manager recommended No, thanks. What happens if I don't install a download manager? Why should I install the Microsoft Download Manager? In this case, you will have to download the files individually. You would have the opportunity to download individual files on the "Thank you for downloading" page after completing your download.
Files larger than 1 GB may take much longer to download and might not download correctly. You might not be able to pause the active downloads or resume downloads that have failed. Microsoft ActiveSync 4. Details Note: There are multiple files available for this download. Once you click on the "Download" button, you will be prompted to select the files you need.
File Name:. Date Published:. When you evaluate the devices that are to be used in an Exchange Server organization that uses Exchange ActiveSync, you should make sure that you understand the features and capabilities of the devices. Not all devices support the same configuration options, and some devices may not support all features or versions of the Exchange ActiveSync protocol.
Administrators and Helpdesk personnel should use public information and their own testing to understand device capabilities. We will update this document as we identify new issues that apply to third-party devices that use the Exchange ActiveSync protocol. The following is a list of current issues that you may encounter when you use Microsoft Exchange Server or Microsoft Exchange Server together with third-party devices.
We recommend that you update third-party devices to the latest software version. Be aware that some devices cannot be updated in some circumstances.
Users of iOS devices can update their devices to the latest version of the iOS software. For more information, go to the Apple iOS website. The information and the solutions in this document represent the current view of Microsoft Corporation on these issues as of the date of publication. These solutions are available through Microsoft or through a third-party provider. Microsoft does not specifically recommend any third-party provider or third-party solution that this article might describe.
There might also be other third-party providers or third-party solutions that this article does not describe. Because Microsoft must respond to changing market conditions, this information should not be interpreted to be a commitment by Microsoft.
Microsoft cannot guarantee or endorse the accuracy of any information or of any solution that is presented by Microsoft or by any mentioned third-party provider. Microsoft makes no warranties and excludes all representations, warranties, and conditions whether express, implied, or statutory. These include but are not limited to representations, warranties, or conditions of title, non-infringement, satisfactory condition, merchantability, and fitness for a particular purpose, with regard to any service, solution, product, or any other materials or information.
In no event will Microsoft be liable for any third-party solution that this article mentions. The issues that are described in this article are divided into the following categories:.
When creating a contact with an anniversary date in Outlook, the information will be added in several MAPI properties such as :. This property is one of the properties that provides identification and access information about a contact. These properties are defined by the user and the user's organization. It is saved without any time zone conversions. The device shows the Birthdate as sent by the server without modification. The EAS protocol specification mentions explicitly that the time should be ignored to prevent shifts in Birthday dates when other time zones are used.
The Birthday element specifies the birth date of the contact. It is defined as an element in the Contacts namespace and is used in ActiveSync command requests and responses.
The time portion of the dateTime value might be and SHOULD be ignored, so that synchronizing between different time zones does not change the date.
The behavior observed might occur in situations where the time zone is different or greater than GMT and the application consulting this property does not have an appropriate configuration to calculate and add the time zone difference. Meeting attendees receive a forwarded meeting invite from another attendee for an existing meeting. An external attendee receives a meeting cancellation followed by a meeting update which corrects the original cancellation.
Internal users may receive an additional meeting update. The organizer of a meeting receives multiple responses from one or more attendees when they respond by using an iOS 9. For more information, go to the following article in the Microsoft Knowledge Base:. Attendees receive a meeting update without any changes from the organizer after the reminder is triggered.
Users of iOS 8. These issues were diagnosed as requiring changes to the iOS implementation of the Microsoft Exchange ActiveSync protocol. When a user syncs a mailbox by using an iOS device, the calendar on the device may be missing one or more appointments. These appointments are available when you view the calendar from Outlook or OWA.
There may also be duplicate instances of the appointment in the calendar if the appointment is accepted from the device. Apple has documented the issue in the following article in the Apple Knowledge Base:.
About iOS 8 Updates. Apple was made aware of this issue, and customers who experience any of the symptoms that are described here should contact Apple for help.
This is most noticeable with Lync meetings where the URLs will appear broken. This has been addressed in the iOS 8. For more information, see the following Apple Knowledge Base article:. Message body is truncated to characters long. Symptom 3 applies to iOS 7. Only iOS 8. It may be possible to correct the formatting of the meetings by having the Meeting Organizer send an update to the meeting. No changes to the meeting item is required. The new meeting object will overwrite the existing object.
Meeting truncation may be avoided if the attendee accepts the meeting before changing the meeting properties with their iOS 8. Meetings will be truncated if the attendee changes the meeting properties with their iOS 8. Specifically, one of the following properties:. CRA is attempting to correct a discrepancy introduced by the iOS 8. For more information, see the following article: Repair update messages received for TimeZoneMatchCheck failures.
Administrators can confirm truncation of the appointment body through a review of the ActiveSync mailbox log. By default, Exchange ActiveSync is enabled. All users who have an Exchange mailbox can synchronize their mobile device with the Microsoft Exchange server.
Set policies such as minimum password length, device locking, and maximum failed password attempts. Control which types of mobile devices can synchronize with your organization through device access rules. You can control which mobile devices can synchronize with Exchange Server. You do this by monitoring new mobile devices as they connect to your organization or by setting up rules that determine which types of mobile devices are allowed to connect.
Regardless of the method you choose to specify which mobile devices can synchronize, you can approve or deny access for any specific mobile device for a specific user at any time. In addition to the ability to configure security options for communications between the Exchange server and your mobile devices, Exchange ActiveSync offers the following features to enhance the security of mobile devices:.
Remote wipe : If a mobile device is lost, stolen, or otherwise compromised, you can issue a remote wipe command from the Exchange Server computer or from any Web browser by using Outlook Web App. This command erases all data from the mobile device.
Device password policies : Exchange ActiveSync lets you configure several options for device passwords. The device password options include the following:. Minimum password length characters : This option specifies the length of the password for the mobile device.
The default length is 4 characters, but as many as 18 can be included.
0コメント