Active Client For Mac Os X Download

Posted : admin On 07.04.2020

mg8.netlify.com › ▀ ▀ ▀ Active Client For Mac Os X Download

Active Client For Mac Os X Download 6,3/10 9220 reviews

Active Client Cac For Mac. Download32 is source for active client cac for mac shareware, freeware download - Classic FTP Free for Mac, Classic FTP Plus for Mac, Ondesoft Screen Capture for Mac, Express Invoice Plus for Mac, Tipard AVI Converter Suite for Mac, etc. You can use Google Sync if your Google Apps administrator allows it. There are some limitations but it runs on Active Sync (Exchange account) so most of the. Apr 02, 2018 I am needing to run ActiveX to use some billing software for my medical practice. Is there any way to use ActiveX on mac? The 'software' is a web based client but it has to run ActiveX on IE. Which is completely frustrating. I did a bit of searching but most of the info was old.

Active Client For Mac Os X Download Software
Active Client For Mac Os X Download Free
Active Client Cac For Mac

TouchDown for OS X. TouchDown® for Mac is the very first ActiveSync enabled desktop client for the Mac OS/X platform. It provides Mac Users with push email against ActiveSync enabled servers. OS X mail app and all famous apps including Outlook 2011 for Mac don't support Active Exchange, but TouchDown adds Active Exchange to OS X. Mac OS X Active Directory, Group Policy & Single Sign-On. ADmitMac ® turns a Mac into a true Active Directory client. Today, a decade after becoming the world's first non-Windows Active Directory integration product, ADmitMac is a one-stop solution for Mac-Windows management and security needs, ensuring compliance with standards such as SOX, PCI DSS, FFIEC, HIPAA or HITEC. Active x for mac free download - Apple Mac OS X Mavericks, R for Mac OS X, Apple Mac OS X Snow Leopard, and many more programs. Active x for mac free download - Apple Mac OS X Mavericks, R for Mac. Folx is a powerful torrent client for Mac. Apart from making torrent download simple and efficient, the app offers a number of benefits: download tasks can be assigned different priorities, you can regulate download and upload speed to optimize Internet traffic allocation, tag downloaded content to make files management and search easier.

-->

Applies to: Configuration Manager (current branch)

This article describes how to deploy and maintain the Configuration Manager client on Mac computers. To learn about what you have to configure before deploying clients to Mac computers, see Prepare to deploy client software to Macs.

When you install a new client for Mac computers, you might have to also install Configuration Manager updates to reflect the new client information in the Configuration Manager console.

In these procedures, you have two options for installing client certificates. Read more about client certificates for Macs in Prepare to deploy client software to Macs.

Use Configuration Manager enrollment by using the CMEnroll tool. The enrollment process doesn't support automatic certificate renewal. Re-enroll the Mac computer before the installed certificate expires.
Use a certificate request and installation method that is independent from Configuration Manager.

Important

To deploy the client to devices running macOS Sierra, correctly configure the Subject name of the management point certificate. For example, use the FQDN of the management point server.

Configure client settings

Use the default client settings to configure enrollment for Mac computers. You can't use custom client settings. To request and install the certificate, the Configuration Manager client for Mac requires the default client settings.

In the Configuration Manager console, go to the Administration workspace. Select the Client Settings node, and then select Default Client Settings.
On the Home tab of the ribbon, in the Properties group, choose Properties.
Select the Enrollment section, and then configure the following settings:
1. Allow users to enroll mobile devices and Mac computers: Yes
2. Enrollment profile: Choose Set Profile. Bendigo bank app for mac computer.
In the Mobile Device Enrollment Profile dialog box, choose Create.
In the Create Enrollment Profile dialog box, enter a name for this enrollment profile. Then configure the Management site code. Select the Configuration Manager primary site that contains the management points for these Mac computers.
Note
If you can't select the site, make sure that you configure at least one management point in the site to support mobile devices.
Choose Add.
In the Add Certification Authority for Mobile Devices window, select the certification authority server that issues certificates to Mac computers.
In the Create Enrollment Profile dialog box, select the Mac computer certificate template that you previously created.
Select OK to close the Enrollment Profile dialog box, and then the Default Client Settings dialog box.
Tip
If you want to change the client policy interval, use Client policy polling interval in the Client Policy client setting group.

The next time the devices download client policy, Configuration Manager applies these settings for all users. To initiate policy retrieval for a single client, see Initiate policy retrieval for a Configuration Manager client.

In addition to the enrollment client settings, make sure that you have configured the following client device settings:

Hardware inventory: Enable and configure this feature if you want to collect hardware inventory from Mac and Windows client computers. For more information, see How to extend hardware inventory.
Compliance settings: Enable and configure this feature if you want to evaluate and remediate settings on Mac and Windows client computers. For more information, see Plan for and configure compliance settings.

For more information, see How to configure client settings.

Download the client for macOS

Download the macOS client file package, Microsoft Endpoint Configuration Manager - macOS Client (64-bit). Save ConfigmgrMacClient.msi to a computer that runs Windows. This file isn't on the Configuration Manager installation media.
Run the installer on the Windows computer. Extract the Mac client package, Macclient.dmg, to a folder on the local disk. The default path is C:Program FilesMicrosoftSystem Center Configuration Manager for Mac client.
Copy the Macclient.dmg file to a folder on the Mac computer.
On the Mac computer, run Macclient.dmg to extract the files to a folder on the local disk.
In the folder, make sure that it contains the following files:
- Ccmsetup: Installs the Configuration Manager client on your Mac computers using CMClient.pkg
- CMDiagnostics: Collects diagnostic information related to the Configuration Manager client on your Mac computers
- CMUninstall: Uninstalls the client from your Mac computers
- CMAppUtil: Converts Apple application packages into a format that you can deploy as a Configuration Manager application
- CMEnroll: Requests and installs the client certificate for a Mac computer so that you can then install the Configuration Manager client

Enroll the Mac client

Enroll individual clients with the Mac computer enrollment wizard.

To automate enrollment for many clients, use the CMEnroll tool.

Enroll the client with the Mac computer enrollment wizard

After you install the client, the Computer Enrollment wizard opens. To manually start the wizard, select Enroll from the Configuration Manager preference page.
On the second page of the wizard, provide the following information:
- User name: The user name can be in the following formats:
  - domainname. For example: contosomnorth
  - user@domain. For example: mnorth@contoso.com
    Important
    When you use an email address to populate the User name field, Configuration Manager automatically populates the Server name field. It uses the default name of the enrollment proxy point server and the domain name of the email address. If these names don't match the name of the enrollment proxy point server, fix the Server name during enrollment.
    The user name and corresponding password must match an Active Directory user account that has Read and Enroll permissions on the Mac client certificate template.
- Download onyx for mac. Server name: The name of the enrollment proxy point server.

Client and certificate automation with CMEnroll

Use this procedure for automation of client installation and requesting and enrollment of client certificates with the CMEnroll tool. To run the tool, you must have an Active Directory user account.

On the Mac computer, navigate to the folder where you extracted the contents of the Macclient.dmg file.
Enter the following command: sudo ./ccmsetup
Wait until you see the Completed installation message. Although the installer displays a message that you must restart now, don't restart, and continue to the next step.
From the Tools folder on the Mac computer, type the following command: sudo ./CMEnroll -s <enrollment_proxy_server_name> -ignorecertchainvalidation -u '<user_name>'
After the client installs, the Mac Computer Enrollment wizard opens to help you enroll the Mac computer. For more information, see Enroll the client by using the Mac computer enrollment wizard.
Example: If the enrollment proxy point server is named server02.contoso.com, and you grant contosomnorth permissions for the Mac client certificate template, type the following command: sudo ./CMEnroll -s server02.contoso.com -ignorecertchainvalidation -u 'contosomnorth'
Note
If the user name includes any of the following characters, enrollment fails: <>'+=,. Use an out-of-band certificate with a user name that doesn't include these characters.
For a more seamless user experience, script the installation steps. Then users only have to supply their user name and password.
Type the password for the Active Directory user account. When you enter this command, it prompts for two passwords. The first password is for the super user account to run the command. The second prompt is for the Active Directory user account. The prompts look identical, so make sure that you specify them in the correct sequence.
Wait until you see the Successfully enrolled message.
To limit the enrolled certificate to Configuration Manager, on the Mac computer, open a terminal window and make the following changes:
1. Enter the command sudo /Applications/Utilities/Keychain Access.app/Contents/MacOS/Keychain Access
2. In the Keychain Access window, in the Keychains section, choose System. Then in the Category section, choose Keys.
3. Expand the keys to view the client certificates. Find the certificate with a private key that you installed, and open the key.
4. On the Access Control tab, choose Confirm before allowing access.
5. Browse to /Library/Application Support/Microsoft/CCM, select CCMClient, and then choose Add.
6. Choose Save Changes and close the Keychain Access dialog box.
Restart the Mac computer.

To verify that the client installation is successful, open the Configuration Manager item in System Preferences on the Mac computer. Also update and view the All Systems collection in the Configuration Manager console. Confirm that the Mac computer appears in this collection as a managed client.

Tip

To help troubleshoot the Mac client, use the CMDiagnostics tool included with the Mac client package. Use it to collect the following diagnostic information:

A list of running processes
The Mac OS X operating system version
Mac OS X crash reports relating to the Configuration Manager client including CCM*.crash and System Preference.crash.
The Bill of Materials (BOM) file and property list (.plist) file created by the Configuration Manager client installation.
The contents of the folder /Library/Application Support/Microsoft/CCM/Logs.

The information collected by CmDiagnostics is added to a zip file that is saved to the desktop of the computer and is named cmdiag-<hostname>-<datetime>.zip

Manage certificates external to Configuration Manager

You can use a certificate request and installation method independent from Configuration Manager. Use the same general process, but include the following additional steps:

When you install the Configuration Manager client, use the MP and SubjectName command-line options. Enter the following command: sudo ./ccmsetup -MP <management point internet FQDN> -SubjectName <certificate subject name>. The certificate subject name is case-sensitive, so type it exactly as it appears in the certificate details.
Example: The management point's internet FQDN is server03.contoso.com. The Mac client certificate has the FQDN of mac12.contoso.com as a common name in the certificate subject. Use the following command: sudo ./ccmsetup -MP server03.contoso.com -SubjectName mac12.contoso.com
If you have more than one certificate that contains the same subject value, specify the certificate serial number to use for the Configuration Manager client. Use the following command: sudo defaults write com.microsoft.ccmclient SerialNumber -data '<serial number>'.
For example: sudo defaults write com.microsoft.ccmclient SerialNumber -data '17D4391A00000003DB'

Renew the Mac client certificate

This procedure removes the SMSID. The Configuration Manager client for Mac requires a new ID to use a new or renewed certificate.

Important

After you replace the client SMSID, when you delete the old resource in the Configuration Manager console, you also delete any stored client history. For example, hardware inventory history for that client.

Create and populate a device collection for the Mac computers that must renew the computer certificates.
In the Assets and Compliance workspace, start the Create Configuration Item Wizard.
On the General page of the wizard, specify the following information:
- Name: Remove SMSID for Mac
- Type: Mac OS X
On the Supported Platforms page, select all Mac OS X versions.
On the Settings page, select New. In the Create Setting window, specify the following information:
- Name: Remove SMSID for Mac
- Setting type: Script
- Data type: String
In the Create Setting window, for Discovery script, select Add script. This action specifies a script to discover Mac computers configured with an SMSID.
In the Edit Discovery Script window, enter the following shell script:
Choose OK to close the Edit Discovery Script window.
In the Create Setting window, for Remediation script (optional), choose Add script. This action specifies a script to remove the SMSID when it's found on Mac computers.
In the Create Remediation Script window, enter the following shell script:
Choose OK to close the Create Remediation Script window.
On the Compliance Rules page, choose New. Then in the Create Rule window, specify the following information:
- Name: Remove SMSID for Mac
- Selected setting: Choose Browse and then select the discovery script that you previously specified.
- In the following values field: The domain/default pair of (com.microsoft.ccmclient, SMSID) does not exist.
- Enable the option to Run the specified remediation script when this setting is noncompliant.
Complete the wizard.
Create a configuration baseline that contains this configuration item. Deploy the baseline to the target collection.
For more information, see How to create configuration baselines.
After you install a new certificate on Mac computers that have the SMSID removed, run the following command to configure the client to use the new certificate:

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 preview feature of Microsoft Azure and Microsoft 365. 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.

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)
Note
Support 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.