• Notes De Publication Pour Endpoint Security For Mac
• Notes De Publication Pour Endpoint Security For Mac Uninstall

Note This change only applies to iOS. There continues to be only one Cisco AnyConnect option for Android, Android Enterprise work profiles, and macOS platforms. Jamf-enrolled macOS devices can now register with Intune Versions 1.3 and 1.4 of the macOS company portal did not successfully register Jamf devices with Intune. Version 1.4.2 of the macOS portal fixes this issue.

Week of April 9, 2018 Updated help experience in Company Portal app for Android We've updated the help experience in the Company Portal app for Android to align with best practices for the Android platform. Now when users encounter a problem in the app, they can tap Menu Help and:.

Upload diagnostic logs to Microsoft. Send an email that describes the problem and incident ID to a company support person. To check out the updated help experience go to. New enrollment failure trend chart and failure reasons table On the Enrollment Overview page, you can view the trend of enrollment failures and the top five causes of failures.

By clicking on the chart or table, you can drill into details to find troubleshooting advice and remediation suggestions. Update where to configure your app protection policies In the Azure portal within the Microsoft Intune service, we’re going to temporarily redirect you from the Intune App Protection service blade to the Mobile app blade. Note that all of your app protection policies are already on the Mobile app blade in Intune under app configuration. Instead of going to Intune App Protection, you’ll just go to Intune. In April 2018, we will stop the redirection and fully remove the Intune App Protection service blade, so that there's only one location for app protection policies within Intune. How does this affect me?

This change will affect both Intune standalone customers and hybrid (Intune with Configuration Manager) customers. This integration will help simplify your cloud management administration. What do I need to do to prepare for this change?

Please tag Intune as a favorite instead of the Intune App Protection service blade and ensure you’re familiar with the App protection policy workflow in the Mobile app blade within Intune. We’ll redirect for a short period of time and then remove the App Protection blade. Remember, all app protection policies are already in Intune and you can modify any of your conditional access policies. For more information about modifying conditional access policies, see. For additional information, see Week of April 2, 2018 Intune apps User experience update for the Company Portal app for iOS We've released a major user experience update to the Company Portal app for iOS.

The update features a complete visual redesign that includes a modernized look and feel. We've maintained the functionality of the app, but increased its usability and accessibility. You'll also see:. Support for iPhone X.

Faster app launch and loading responses, to save users time. Additional progress bars to provide users with the most up-to-date status information. Improvements to the way users upload logs, so if something goes wrong, it's easier to report. To see the updated look, go to.

Protect on-premises Exchange data using Intune APP and CA You can now use Intune App Policy Protection (APP) and Conditional Access (CA) to protect access to on-premises Exchange data with Outlook Mobile. To add or modify an app protection policy within the Azure portal, select Microsoft Intune Client apps App protection policies. Before using this feature, make sure you meet the. Notices Plan for change: Performance updates to Intune for Education We’re adding some updates to Intune for Education to increase speed and reliability when you assign settings to your users or devices. As part of this change, towards the end of November, we’ll be moving your policies or settings assignments to new groups.

How does this affect me? As an Intune for Education customer, you have two dynamic Azure Active Directory (Azure AD) groups: “All Users” and “All Devices”. With these updates, these “All Users” and “All devices” Azure AD groups will not be visible in the Intune for Education console.

Notes De Publication Pour Endpoint Security For Mac

They will, however, still be visible in the Intune on Azure console and will be renamed as “All Users (Obsolete, do not use)” and “All Devices (Obsolete, do not use)”. When the updates roll out, you will no longer need to use Azure AD groups to assign apps and settings in Intune. Instead, we will move your Settings assignments to new groups in the Intune for Education console that we’ll create for you that will still show up as “All Users” and “All Devices” as before.

These changes are in the backend, so you will not notice anything different in the Intune for Education console. There is no impact anticipated to your end users or enrolled devices. What do I need to do to prepare for this change? You do not need to do anything while we move your policy assignments. If you currently assign policies in the Intune for Education console, continue doing so. If you currently assign policies to the Azure AD groups mentioned above in Intune on Azure, start assigning these to the All Users and All Devices group in the Intune for Education console instead.

When you see the Azure AD groups renamed as obsolete in the console, stop assigning policies in Azure AD. If you are not currently using the renamed groups for any other purpose, you should delete them. Plan for Change: Intune will move to support macOS 10.12 and higher in December Apple has just released macOS 10.14. Subsequently, Intune will move to support macOS 10.12 and higher in December 2018. How does this affect me? Starting in December, end users on devices with macOS 10.11 and prior won’t be able to use the Company Portal to enroll into Intune. They will need to upgrade their device to macOS 10.12 or higher and upgrade the Company Portal app to the latest version to continue to receive support and new features.

MacOS versions 10.12 and higher are currently supported on:. MacBook (late 2009 or newer).

iMac (late 2009 or newer). MacBook Air (late 2010 or newer).

Notes De Publication Pour Endpoint Security For Mac Uninstall

MacBook Pro (late 2010 or newer). Mac Mini (late 2010 or newer).

Mac Pro (late 2010 or newer). After December, end users who have devices other than the ones listed above will not be able to access the latest version of the Company Portal app for macOS. Existing enrolled devices running unsupported versions below macOS 10.12 will continue to be managed and listed in the Intune Admin Console. What do I need to do to prepare for this change?.

Request your end users to upgrade their devices to a supported OS version before December 2018. Check your Intune reporting in the Intune on Azure console, to see what devices or users may be affected. Go to Devices All devices and filter by OS. You can add in additional columns to help identify who in your organization has devices running macOS 10.11. If you are using hybrid mobile device management (MDM), go to Assets and Compliance Devices in the Configuration Manager console, right-click the columns to add the Operating System and Client Version columns, and sort by OS. Note that hybrid MDM is now deprecated, and you should move to Intune on Azure as soon as possible.

Additional Information For more information, see. Plan for Change: New Intune support experience for Premier customers As a Microsoft Premier customer, you can currently use the Microsoft Premier Online (MPO) portal (premier.microsoft.com) and Intune on Azure (portal.azure.com) to create support requests for Intune. Starting on December 3, 2018, to continue enhancing the Premier support experience, you will be able to create support requests only in Intune on Azure. How does this affect me? After December 3, you will be not be able to create support requests in MPO. When you try to do this, you’ll see a prompt that you will not be able to dismiss, to be redirected to Intune on Azure. Here, you can create a support request which will be routed to Intune-dedicated Microsoft Support, to diagnose and resolve your issue in a timely manner.

Support requests created in the MPO portal cannot be viewed in the Azure portal, so you should stop creating support requests in MPO. If you use hybrid mobile device management (hybrid MDM) or use co-management, you can continue to use MPO to create support requests for ConfigMgr but use the Azure portal to create support requests for Intune. As a reminder, hybrid MDM is deprecated, and you should plan to move to Intune on Azure as soon as possible. For more information, see. Note that only users with Global Administrator, Intune Service Administrator, and Service Support Administrator roles can create support tickets in the Azure portal. What can I do to prepare for this change?.

Stop using MPO and use Intune on Azure to create and manage all your Intune support requests. Notify your helpdesk and update documentation if necessary. If you have users without Global administrator or Intune Service Administrator roles currently creating support requests in MPO, assign them the Service Support Administrator role in Azure Active Directory, so they can continue to create support tickets in the Azure portal. Click on Additional Information for more information and helpful links. Additional Information For more information, see the. Take action: Please update your Android device restriction or compliance policy password settings in Intune Intune will be removing the available password type “device default” for Android 4.4 and higher devices. Due to differences in Android platforms and device defaults, that policy is often treated as optional by the device.

To clear up confusion on when this setting is enforced on Android, we’ll remove this setting from the UI in an upcoming release. How does this affect me?. If your intent is to require a password on the devices, we recommend instead of using “device default” you edit your Android platform profile(s) to clearly articulate the required password type. If your intent is to let your end user to decide on whether to create a password, select the “Not configured” button.

When we remove this setting from the UI, if the setting is still set, you will be prompted to choose a value other than “Device default” on your next edit of the profile. What do I need to do to prepare for this change? Review the password settings in your Android and Android enterprise device restriction and compliance policies. These are listed under System security for Compliance policies and under either Device password or Work profile settings for Device restrictions.

Additional information has a link to more details and screenshots for where these settings are configured. Additional information Plan for Change: Change Password at Next Auth added to Intune In the September service release, Intune plans to integrate Apple’s newly-released Change Password at Next Auth setting for devices running macOS versions 10.13 and newer. Before this setting, MDM providers can't verify that the device passcode was changed to be compliant. Intune’s configuration and compliance policies only validate that the next time a device password is changed, that it's marked as compliant. When this new Apple feature is added, your macOS users will receive a request to update their password, even if their password is compliant.

How does this affect me? This impacts environments with a macOS device policy using Intune or a hybrid MDM. Now that Apple has this Change Password at New Auth setting, Intune can force users to update their password when a password policy is pushed. If you block company resources until the device is marked compliant, then your end users may be blocked from accessing company resources, such as email or SharePoint sites, until they reset their password. In the future, all updates to configuration and compliance password policies force targeted users to update their passwords. What do I need to do to prepare for this change?

Let your helpdesk know. If you don't want to enforce this macOS device policy, we recommend you un-assign or delete your existing macOS policy. Customer research suggests most customers aren't affected by this change. Most end users update their password after receiving a request to enroll with a password, or reset their password to remain compliant. Plan for Change: Intune moving to TLS 1.2 Starting on October 31, 2018, Intune will support Transport Layer Security (TLS) protocol version 1.2 to provide best-in-class encryption, to ensure our service is more secure by default, and to align with other Microsoft services such as Microsoft Office 365. Office communicated this change in MC128929.

The Company Portal will also move to support TLS 1.2 on October 31, 2018. How does this affect me? As of October 31, 2018, Intune will no longer support TLS protocol versions 1.0 or 1.1. All client-server and browser-server combinations should use TLS version 1.2 to ensure connection without issues to Intune. Note that this change will impact end-user devices that are no longer supported by Intune but are still receiving policy through Intune, and that cannot use TLS version 1.2. This includes devices such as those running Android 4.3 and earlier. For a list of affected devices and browsers, see Additional Information below.

After October 31, 2018, if you experience an issue related to the use of an old TLS version, you will be required to update to TLS 1.2 or to a device that supports TLS 1.2 as part of the resolution. What do I need to do to prepare for this change? We recommend that you proactively remove TLS 1.0 and 1.1 dependencies in your environments and disable TLS 1.0 and 1.1 at the operating system level where possible. Begin planning your migration to TLS 1.2 today. Check the support blog post below for the list of devices that are not supported by Intune today but might still be receiving policy, and that will not be able to communicate using TLS version 1.2. You might need to notify those end users that they’ll lose access to corporate resources.

Additional Information: Plan for Change: Use Intune on Azure now for your MDM management Over a year ago, we announced and followed up six months ago with for Intune. Starting on August 31, 2018, we will turn off mobile device management (MDM) in the classic Silverlight console for those customers using Intune standalone. Instead, you can use for your MDM needs. If you're still using the classic console for MDM, please stop and familiarize yourself with Intune on Azure.

We do not expect any end user impact with this change. Classic PC management will remain in Silverlight. You can learn more about this change and how it affects you. Apple to require updates for Application Transport Security Apple has announced that they will enforce specific requirements for Application Transport Security (ATS). ATS is used to enforce stricter security on all app communications over HTTPS.

This change impacts Intune customers using the iOS Company Portal apps. We'll keep our with details. See also. Feedback.

PLEASE READ THIS AGREEMENT CAREFULLY. BY CLICKING ON THE 'DOWNLOAD' BUTTON, YOU EXPRESSLY AGREE TO BE BOUND BY THE TERMS AND CONDITIONS OF THIS DOWNLOAD AGREEMENT. This Software Download Agreement (“Agreement”) is between you (either as an individual or company) and Check Point Software Technologies Ltd. ('Check Point'), for the software and documentation provided by this Agreement (“Software”). Check Point grants to you the ability to download and access the Software and/or any modifications, corrections, and/or updates to the Software (“Software Subscription”) for which you have registered and paid the applicable fees, only if you fully comply with the terms and conditions set forth below.

Software Subscription is made available for downloading (i) solely for customers who purchase and register a Check Point Software Subscription Program in matching quantity and SKUs relative to the Check Point Product SKUs, and (ii) only for the duration of such active registered Software Subscription Program. The Software is licensed to you under the applicable Check Point End User License Agreement (“EULA”) which accompanied your product purchase. Any and all use of the Software and Software Subscription is governed exclusively by that EULA, the terms and conditions of which are incorporated by reference herein. See the EULA for the specific language governing permissions and limitations under the EULA. In the event that you do not agree with the terms of the EULA or this Agreement, then you must immediately delete all copies of the Software from your computer system and back-up system(s). Failure to comply with the EULA limitations and this Agreement will result in termination of your right to use of the Software. All title and copyrights in and to the Software and Software Subscription are owned by Check Point and its licensors.

Any use, reproduction, or distribution of the components of the Software and Software Subscription to anyone that has not validly registered and purchased such items, or any dissemination not in accordance with the EULA, is expressly prohibited by law and may result in severe civil and criminal penalties. Violators will be prosecuted to the maximum extent possible.

If you are downloading a limited availability product, it may not be disseminated in any fashion. Unless you have procured support services from Check Point under the terms of Check Point’s applicable Service Level Agreement, Check Point has no obligation to provide to you any support for this limited availability product.This Software is subject to Israel and United States export control laws. Prior to exporting please inquire as to the Software’s export classification. Under no circumstances may Software be exported to: Cuba, Iran, North Korea, Sudan and Syria. SOFTWARE AND SOFTWARE SUBSCRIPTION IS PROVIDED 'AS IS', WITHOUT WARRANTY OF ANY KIND, INCLUDING, WITHOUT LIMITATION, THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND NON-INFRINGEMENT. IN NO EVENT SHALL CHECK POINT OR ITS SUPPLIERS OR DISTRIBUTORS BE LIABLE TO YOU OR ANY OTHER PERSON FOR ANY INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES OF ANY KIND INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF PROFITS OR ANY OTHER COMMERCIAL LOSS.