Sccm For Mac Client



Sccm mac client install-->

In the Properties of New Template dialog box, on the General tab, enter a template name to generate the Mac client certificate, such as ConfigMgr Mac Client Certificate. The clients for UNIX and Linux extends the scope of your Configuration Manager environment to collect inventory, deploy software, and run reports about UNIX and Linux servers in your enterprise. The client operates as a workgroup client that is managed by Configmgr. Feature Bullet Summary: Mac Client. If your Mac does not appear, it’s a sign that the installation failed; Once the client is installed, you should be able to check the hardware inventory of the device. Note that the Microsoft Intune client Mac is not considered as a normal SCCM client, it’s considered like a mobile device.

  • Quick update - There is a new Microsoft Endpoint Configuration Manager macOS Client (64-bit) available for download. The 64-bit Configuration Manager macOS client allows you to manage Apple devices running the macOS using Configuration Manager.
  • SCCM uses SMBIOS to identify computers and fallback to MAC Addresses if SMBIOS is not available SMBIOS is the GUID stored in the device’s BIOS or UEFI. It’s unique to the device and SCCM uses it to recognize imported computers When computers are not imported, SCCM will use their Ethernet MAC Addresses by default.

Applies to: Configuration Manager (current branch)

Configuration Manager supports installing client software on Windows and macOS computers.

General requirements and limitations

Review the following requirements and limitations for all clients:

  • Changing the startup type or Log on as settings for any Configuration Manager service isn't supported. This change can prevent key services from running correctly.

Windows computers

To manage the following Windows OS versions, use the client that's included with Configuration Manager. For more information, see How to deploy clients to Windows computers.

Supported client OS versions

  • Windows 10

    For more detailed information, see Support for Windows 10.

  • Windows 8.1 (x86, x64): Professional, Enterprise

Windows Virtual Desktop

Windows Virtual Desktop is a desktop and app virtualization service that runs on Microsoft Azure. Starting in version 1906, use Configuration Manager to manage these virtual devices running Windows in Azure.

Similar to a terminal server, some of these virtual devices allow multiple concurrent active user sessions. To help with client performance, Configuration Manager now disables user policies on any device that allows these multiple user sessions. Even if you enable user policies, the client disables them by default on these devices, which include Windows 10 Enterprise multi-session and terminal servers.

The client only disables user policy when it detects this type of device during a new installation. For an existing client of this type that you update to this version, the previous behavior persists. On an existing device, it configures the user policy setting even if it detects that the device allows multiple user sessions.

If you require user policy in this scenario, and accept any potential performance impact, use one of the following methods to enable user policy:

  • In version 1910 and later, use client settings. In the Client Policy group, configure the following setting: Enable user policy for multiple user sessions.

  • In version 1906, use the Configuration Manager SDK with the SMS_PolicyAgentConfig server WMI class. Set the new PolicyEnableUserPolicyOnTS property to true.

Note

You can't use co-management with a client running Windows 10 Enterprise multi-session.

Starting in version 2006, the Windows 10 Enterprise multi-session platform is available in the list of supported OS versions on objects with requirement rules or applicability lists.

Note

If you previously selected the top-level Windows 10 platform, this action automatically selected all child platforms. This new platform isn't automatically selected. If you want to add Windows 10 Enterprise multi-session, manually select it in the list.

For more information, see the following articles:

Supported server OS versions

  • Windows Server 2019: Standard, Datacenter Note 1
    (Starting with Configuration Manager version 1806.)

  • Windows Server 2016: Standard, Datacenter Note 1

  • Windows Storage Server 2016: Workgroup, Standard

  • Windows Server 2012 R2 (x64): Standard, Datacenter Note 1

  • Windows Storage Server 2012 R2 (x64)

  • Windows Server 2012 (x64): Standard, Datacenter Note 1

  • Windows Storage Server 2012 (x64)

Server Core

The following versions specifically refer to the Server Core installation of the OS. Note 3

Windows Server semi-annual channel versions are Server Core installations, such as Windows Server, version 1809. As a Configuration Manager client, they're supported the same as the associated Windows 10 semi-annual channel version. For more information, see Support for Windows 10.

  • Windows Server 2019 (x64) Note 2

  • Windows Server 2016 (x64) Note 2

  • Windows Server 2012 R2 (x64) Note 2

  • Windows Server 2012 (x64) Note 2

Note 1

Configuration Manager tests and supports Windows Server Datacenter editions, but isn't officially certified for Windows Server. Configuration Manager hotfix support isn't offered for issues that are specific to Windows Server Datacenter Edition. For more information on the Windows Server certification program, see Windows Server Catalog.

Note 2

To support client push installation, add the File Server service of the File and Storage Services server role. For more information about installing Windows features on Server Core, see Install roles, role services, and features by using Windows PowerShell cmdlets.

Note 3

The new Software Center app isn't supported on any version of Windows Server Core.

Windows Embedded computers

Manage Windows Embedded devices by installing the Configuration Manager client on the device. For more information, see Planning for client deployment to Windows Embedded devices.

Requirements and limitations

  • All client features are supported on Windows Embedded systems that don't have write filters enabled.

  • Clients that use one of the following are supported for all features except power management:

    • Enhanced Write Filters (EWF)

    • RAM File-Based Write Filters (FBWF)

    • Unified Write Filters (UWF)

  • The application catalog isn't supported for any Windows Embedded device.

Supported OS versions

  • Windows 10 Enterprise (x86, x64)

  • Windows 10 IoT Enterprise (x86, x64)
    This version includes the long-term servicing channel (LTSC). For more information, see Overview of Windows 10 IoT Enterprise.

  • Windows Embedded 8.1 Industry (x86, x64)

  • Windows Embedded 8 Standard (x86, x64)

  • Windows Thin PC (x86, x64)

  • Windows Embedded POSReady 7 (x86, x64)

  • Windows Embedded Standard 7 with SP1 (x86, x64)

Windows CE computers

Manage Windows CE devices with the Configuration Manager mobile device legacy client that is included with Configuration Manager.

Requirements and limitations

  • The mobile device client requires 0.78 MB of storage space for installation. Sign-in can require up to 256 KB of additional storage space.

  • Features for these mobile devices vary by platform and client type. For information about which management functions are supported, see Choose a device management solution.

Supported OS versions

  • Windows CE 7.0 (ARM and x86 processors)

    Important

    Configuration Manager version 2006 drops support for Windows CE 7.0 as a client. Deprecation was announced with version 1906.

Supported languages include

  • Chinese (simplified and traditional)

  • English (US)

  • French (France)

  • German

  • Italian

  • Japanese

  • Korean

  • Portuguese (Brazil)

  • Russian

  • Spanish (Spain)

Extended Security Updates and Configuration Manager

The Extended Security Updates (ESU) program is a last resort option for customers who need to run certain legacy Microsoft products past the end of support. For example, Windows 7. It includes Critical and/or Important security updates (as defined by the Microsoft Security Response Center (MSRC)) for a maximum of three years after the product's End of Extended Support date.

Products that are beyond their support lifecycle aren't supported for use with Configuration Manager. This includes any products that are covered under the ESU program. Security updates released under the ESU program will be published to Windows Server Update Services (WSUS). These updates will appear in the Configuration Manager console. While products that are covered under the ESU program are no longer supported for use with Configuration Manager, the latest released version of Configuration Manager current branch can be used to deploy and install Windows security updates released under the program. The latest released version can also be used to deploy Windows 10 to devices running Windows 7.

Sccm Mac Client Remote Control

Client management features not related to Windows software update management or OS deployment will no longer be tested on the operating systems covered under the ESU program and we don't guarantee that they'll continue to function. It's highly recommended to upgrade or migrate to a current version of the operating systems as soon as possible to receive client management support.

Tip

Sccm

Starting in Configuration Manager 2010, you'll be notified in-console about devices with operating systems that are past the end of support date and that are no longer eligible to receive security updates. For more information, see Console notifications. This information is provided for your convenience and only for use internally within your company. You should not solely rely on this information to confirm update or license compliance. Be sure to verify the accuracy of the information provided to you.

Mac computers

Manage Apple Mac computers with the Configuration Manager client for macOS.

The macOS client installation package isn't supplied with the Configuration Manager media. Download it from the Microsoft Download Center, Microsoft Endpoint Configuration Manager - macOS Client (64-bit).

For more information, see How to deploy clients to Macs.

Requirements and limitations

  • Installing or running the Configuration Manager client for macOS on computers under an account other than root isn't supported. Doing so can prevent key services from running correctly.

Supported versions

  • macOS Catalina (10.15) (requires Configuration Manager site version 1910 or later, and Configuration Manager client for macOS version 5.0.8742.1000 or later)

  • macOS Mojave (10.14)

  • macOS High Sierra (10.13)

On-premises MDM

Configuration Manager has built-in capabilities for managing mobile devices that are on-premises without installing client software. For more information, see Manage mobile devices with on-premises infrastructure.

Supported operating systems

  • Windows 10 Pro (x86, x64)

  • Windows 10 Pro Enterprise (x86, x64)

  • Windows 10 IoT Enterprise (x86, x64)
    This version includes the long-term servicing channel (LTSC). For more information, see Overview of Windows 10 IoT Enterprise.

  • Windows 10 IoT Mobile Enterprise

  • Windows 10 Team for Surface Hub

  • Windows 10 Mobile

  • Windows 10 Mobile Enterprise

    Important

    Configuration Manager version 2006 drops support for Windows 10 Mobile and Windows 10 Mobile Enterprise as a client. Deprecation was announced with version 1906.

Exchange Server connector

Configuration Manager supports limited management of devices that connect to your Exchange Server, without installing the Configuration Manager client. For more information, see Manage mobile devices with Configuration Manager and Exchange.

Sccm For Mac Client Login

Supported versions of Exchange Server

Sccm For Mac Client Portal

  • Exchange Online (Microsoft 365): This version includes Business Productivity Online Standard Suite

  • Exchange Server 2016

  • Exchange Server 2013

  • Exchange Server 2010 SP1 or Exchange Server 2010 SP2