Parallels Mac Management v4.5 Now Available for Microsoft System Center Configuration Manager
by Yury Averkiev, Program Manager, Parallels, Inc.
Parallels Mac Management 4.5 for Microsoft System Center Configuration Manager (SCCM) empowers IT administrators and system architects, as well as CIOs, to quickly and cost-effectively extend their current Microsoft SCCM infrastructure, controlling Mac and PC computers through one interface.
Parallels Mac Management 4.5 for Microsoft SCCM is available today, introducing new features that address top customer requests.
Added Parallels Mac Management 4.5 for Microsoft SCCM Features:
- OS X patch management
- Active Directory System Discovery support
- Inventory:
- Report LDAP (organizational unit membership) of Active Directory joined Mac devices
- Report logged on users
- OS X image deployment: Implemented Capture OS X Image task sequence step
- Automatic upgrade of Parallels Mac Client
- Reporting of deployment statuses of SCCM Applications
Apr 18, 2013 New to SP1 is the ability to deploy a SCCM agent onto Apple OS X computers that use an Intel 64-bit chipset, running Mac OS X 10.6, 10.7, and 10.8. While not all features of SCCM are available yet for OS X devices, Microsoft has enabled some key features to.
Let’s explore the new capabilities in more detail and see how these can help you easily configure, secure, and manage your Mac devices.
These updates will appear in the Configuration Manager console. Manage Apple Mac computers with the Configuration Manager client for macOS. To review OS file dependencies for the client for Linux and UNIX, see Prerequisites for client deployment to Linux and UNIX servers. The installer will extract a dmg file in C:Program Files (x86)MicrosoftSystem Center 2012 R2 Configuration Manager For Mac Client. Copy the Macclient.dmg to a Mac OSx client that has an existing ConfigMgr client installed (can be the old SP1 client). Open a Terminal and run sudo./cmapputil –c./macclient.dmg –0./. The following WQL query statement can be used to list all Apple Mac OS X Systems. To use you will need to create a new collection and add as a Membership Query Rule. Select SMSRSYSTEM.ResourceID,SMSRSYSTEM.ResourceType,SMSRSYSTEM.Name,SMSRSYSTEM.SMSUniqueIdentifier,SMSRSYSTEM.ResourceDomainORWorkgroup,SMSRSYSTEM.Client from SMSR. In the Configuration Manager console, navigate to the Software Library and select Applications. Right-click, select “Create Application”, select “Mac OS X” from the drop-down list and enter the UNC location of the.cmmac file created in Step 1.
OS X Patch Management
Patch management for Windows and other Microsoft products is one of the cornerstones of SCCM’s capabilities. With the release of Parallels Mac Management 4.5, we are extending SCCM’s powerful patching capabilities to Mac.
![Sccm Console For Mac Os X Sccm Console For Mac Os X](/uploads/1/2/6/5/126539833/733240719.png)
https://roboskyey.weebly.com/emoticons-for-mail-mac-os-x.html. As with most of the Parallels Mac Management features, our goal is to keep the management workflow of Windows and Mac devices within one pane of glass. The new OS X patch management feature is no exception.
The SCCM administrator will see the list of available patches from Apple under the “Software Updates All Software Updates” folder:
Figure 1. List of Apple and Microsoft updates in SCCM console
The administrator will then need to create a software update group…
…and deploy it to a collection with Mac computers. It’s that simple!
Active Directory System Discovery Support
Because we are seeing more customers enrolling their Mac devices into Active Directory, we have implemented support for SCCM Active Directory System Discovery to make it extremely easy for customers to enroll Mac machines into SCCM. Just as when you enroll Windows devices with Active Directory System Discovery, you will need to configure the discovery settings and then configure the Parallels Mac Client push installation settings:
Figure 3. Parallels Mac Client push installation properties
Inventory Improvements
Parallels Mac Management 4.5 contains two very important additions to the information that Parallels Mac Client reports to SCCM:
- Reporting User Logon Information
We have added the ability to report information about users who are logged into a Mac, as well as information about network login profiles available on Mac devices:
Sccm Client For Mac
- Reporting LDAP Patch of Active Directory-Joined Mac Devices
For Mac devices that are joined to Active Directory, Parallels Mac Client now reports its LDAP patch, which is shown as the Distinguished Name in the device properties:
Figure 5. Distinguished Name of an Active Directory-bound Mac
Capture OS X Image Task Sequence Step
Last year, Parallels Mac Management added support for SCCM task sequence steps, and in this latest update, we have implemented support for Capture OS X Image task sequence steps, which significantly simplifies the process of taking an image of a “golden” Mac:
Figure 6. Parallels Mac Management OS X task sequence editor
Automatic Upgrade of Parallels Mac Client
Every time a new version of Parallels Mac Management is released, it is highly recommended, and in some cases, required, to upgrade the Parallels Mac Client on managed Mac devices to the latest version. Parallels Mac Management 4.5 adds an auto-upgrade capability to the Parallels Mac Client. From now on, the process of upgrading the Parallels Mac Client is as simple as checking a box.
![Sccm Console For Mac Os X Sccm Console For Mac Os X](/uploads/1/2/6/5/126539833/664846955.png)
Figure 7. Parallels Mac Client auto-upgrade settings
Availability and Pricing
Parallels Mac Management 4.5 is available now. The pricing starts at $30 annually per Mac.
What’s Next?
We are already hard at work on the next Parallels Mac Management update. As we continue to introduce more managing capabilities for Mac devices via SCCM, we’ll share the latest updates on this blog.
Meanwhile, go ahead and try Parallels Mac Management for Microsoft SCCM and tell us via our web forum what additional Mac management capabilities you’d like to see added in future releases.
-->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 10For 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. https://roboskyey.weebly.com/need-vlc-for-mac-sierra-os-126.html. 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 totrue
.
Note
You can't use co-management with a client running Windows 10 Enterprise multi-session.
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
- Java 8 for mac high sierra. 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)
- Vector art software for mac os x. Unified Write Filters (UWF)
- The application catalog isn't supported for any Windows Embedded device.
Sccm Macbook
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)NoteSupport is deprecated for Windows CE 7.0 in Configuration Manager. For more information, see Removed and deprecated items for Configuration Manager clients.
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.
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.
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)
Linux and UNIX servers
Important
Configuration Manager version 1902 drops support for Linux and UNIX as a client. Deprecation was announced with version 1802. Consider Microsoft Azure Management for managing Linux servers. Azure solutions have extensive Linux support that in most cases exceed Configuration Manager functionality, including end-to-end patch management for Linux.
The Linux and UNIX client installation packages aren't supplied with the Configuration Manager media. Download the Clients for Additional Operating Systems from the Microsoft Download Center. In addition to client installation packages, the client download includes the script that manages the installation of the client on each computer.
Requirements and limitations
- To review OS file dependencies for the client for Linux and UNIX, see Prerequisites for client deployment to Linux and UNIX servers.
- For an overview of supported management capabilities for Linux or UNIX, see How to deploy clients to UNIX and Linux servers.
- For supported versions of Linux and UNIX, the listed version includes all subsequent minor versions. For example, CentOS version 6 includes CentOS 6.3. Similarly, support for an OS that uses service packs (such as SUSE Linux Enterprise Server 11 SP1) includes subsequent service packs for that OS version.
- For information about client installation packages and the Universal Agent, see How to deploy clients to UNIX and Linux servers.
Supported versions
The following versions are supported by using the indicated .tar file.
AIX
Version | TAR file |
---|---|
Version 6.1 (Power) | ccm-Aix61ppc.<build>.tar |
Version 7.1 (Power) | ccm-Aix71ppc.<build>.tar |
CentOS
Version | TAR file |
---|---|
Version 5 x86 | ccm-Universalx86.<build>.tar |
Version 5 x64 | ccm-Universalx64.<build>.tar |
Version 6 x86 | ccm-Universalx86.<build>.tar |
Version 6 x64 | ccm-Universalx64.<build>.tar |
Version 7 x64 | ccm-Universalx64.<build>.tar |
Debian
Version | TAR file |
---|---|
Version 5 x86 | ccm-Universalx86.<build>.tar |
Version 5 x64 | ccm-Universalx64.<build>.tar |
Version 6 x86 | ccm-Universalx86.<build>.tar |
Version 6 x64 | ccm-Universalx64.<build>.tar |
Version 7 x86 | ccm-Universalx86.<build>.tar |
Version 7 x64 | ccm-Universalx64.<build>.tar |
Version 8 x86 | ccm-Universalx86.<build>.tar |
Version 8 x64 | ccm-Universalx64.<build>.tar |
HP-UX
Version | TAR file |
---|---|
Version 11iv3 IA64 | ccm-HpuxB.11.31i64.<build>.tar |
Oracle Linux
Version | TAR file |
---|---|
Version 5 x86 | ccm-Universalx86.<build>.tar |
Version 5 x64 | ccm-Universalx64.<build>.tar |
Version 6 x86 | ccm-Universalx86.<build>.tar |
Version 6 x64 | ccm-Universalx64.<build>.tar |
Version 7 x64 | ccm-Universalx64.<build>.tar |
Red Hat Enterprise Linux (RHEL)
Version | TAR file |
---|---|
Version 5 x86 | ccm-Universalx86.<build>.tar |
Version 5 x64 | ccm-Universalx64.<build>.tar |
Version 6 x86 | ccm-Universalx86.<build>.tar |
Version 6 x64 | ccm-Universalx64.<build>.tar |
Version 7 x64 | ccm-Universalx64.<build>.tar |
Solaris
Version | TAR file |
---|---|
Version 10 x86 | ccm-Sol10x86.<build>.tar |
Version 10 SPARC | ccm-Sol10sparc.<build>.tar |
Version 11 x86 | ccm-Sol11x86.<build>.tar |
Version 11 SPARC | ccm-Sol11sparc.<build>.tar |
SUSE Linux Enterprise Server (SLES)
Version | TAR file |
---|---|
Version 10 SP1 x86 | ccm-Universalx86.<build>.tar |
Version 10 SP1 x64 | ccm-Universalx64.<build>.tar |
Version 11 SP1 x86 | ccm-Universalx86.<build>.tar |
Version 11 SP1 x64 | ccm-Universalx64.<build>.tar |
Version 12 x64 | ccm-Universalx64.<build>.tar |
Ubuntu
Version | TAR file |
---|---|
Version 10.04 LTS x86 | ccm-Universalx86.<build>.tar |
Version 10.04 LTS x64 | ccm-Universalx64.<build>.tar |
Version 12.04 LTS x86 | ccm-Universalx86.<build>.tar |
Version 12.04 LTS x64 | ccm-Universalx64.<build>.tar |
Version 14.04 LTS x86 | ccm-Universalx86.<build>.tar |
Version 14.04 LTS x64 | ccm-Universalx64.<build>.tar |
Version 16.04 LTS x86 | ccm-Universalx86.<build>.tar |
Version 16.04 LTS x64 | ccm-Universalx64.<build>.tar |
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 EnterpriseNoteSupport is deprecated for Windows 10 Mobile and Windows 10 Mobile Enterprise in Configuration Manager. For more information, see Removed and deprecated items for Configuration Manager clients.
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.
Supported versions of Exchange Server
- Exchange Online (Office 365): This version includes Business Productivity Online Standard Suite
- Exchange Server 2016
- Exchange Server 2013
- Exchange Server 2010 SP1 or Exchange Server 2010 SP2