To install System Center 2012 Endpoint Protection for Mac, follow these steps: Note Running two antivirus programs on the same computer can cause performance problems and system instability. Uninstall any antivirus software that is currently installed on your computer before you install System Center 2012 Endpoint Protection for Mac. Chad, Looking online at Microsoft it appears that the Mac and Linux client support for SCEP 2012 was a separate add-on provided later than the original release and delivered through the Volume Licensing Center rather than the main support channel for SCEP itself.
Chad,
Looking online at Microsoft it appears that the Mac and Linux client support for SCEP 2012 was a separate add-on provided later than the original release and delivered through the Volume Licensing Center rather than the main support channel for SCEP itself.
What this says to me is that it may be difficult to find a direct answer to this question via any of the normal support sites like the TechNet forums as well, since the support may not be via these typical channels either.
What I'd do is to look in the documentation which according to the notification for the Mac/Linux client release was included with those Endpoint clients themselves. There may be some indication there where support for these could be found, which I suspect might be via the Volume Licensing Center itself?
If there's nothing there, then the best location to ask would be the TechNet forum(s) for System Center 2012, since those are for the business products since these Community forums are only intended for consumer products and so are manned by either volunteers like us or a handful of 1st level support technicians from other countries. Few of these even know what System Center is and even I had a very difficult time finding the little information I did about the SCEP for Mac client release, even though I've personally been involved with administering networks including Windows and using Microsoft websites to support them for nearly 25 years now.
Rob
In Part 1 of the Parallels Mac Management for SCCM series I installed the Parallels Configuration Manager Console Extension. I installed this on my site server ‘ConfigMgr’.
Part 2 focused on the installation of the Parallels Proxy which I installed on a remote server called ‘Parallels’ which I intend to use to install the Parallels roles.
Part 3 of the series concluded the ‘role’ installation, namely the NetBoot Server and OS X Software Update Service.
Part 4 of the Parallels series focuses on getting the Parallels Mac client onto a Mac OS X device.
There are various ways in which to get the Parallels Mac client installed on an end device.
I will be showing you the push install method in this blog post, however before I can proceed with the installation I need to activate my installation of Parallels Mac Management for SCCM.
To do this Parallels sent me a trial licence that I can use for 30 days from receiving it.
Head on over to https://account.parallels.com and register an account.
In the Dashboard click the ‘Register a Licence Key’
Enter the licence key details provided by Parallels.
You’ll get confirmation that the key was activated.
Next head over to the SCCM console. Navigate to the Administration>Parallels Mac Management>Licences node. Right click the Site Code in the main body and choose ‘Activate Licence’
Enter the licence key once again and select ‘Activate online’. Click Next.
At the summary screen click ‘Activate’.
Click Finish to complete the activation process.
Parallels will now report as being Activated
Parallels can leverage two methods to discover Mac devices in your environment. It can use the built-in ConfigMgr AD System Discovery, if the devices are domain joined or Parallels have their own Parallels Network Discovery. This can discover both AD join Macs and those that are not connected to a domain.
I will be using Parallels Network Discovery in this blog post since my Mac device is not installed in a domain.
Here’s a run through of the settings to get your Mac discovered.
Parallels Network Discovery is accessed from Administration workspace under Parallels Mac Management>Discovery Methods.
In the General tab ensure that ‘Enable network discovery’ is enabled. Ensure that ports to Mac client are open on one of the ports listed. The default Nmap settings provide the optimal balance between the quality of the results and the time it takes to scan the network.
The Accounts tab states that the client push installation will be used to install the client on to a Mac when a Network Discovery takes place. To configure this account go to Site Configuration>Sites. Right click your site and select ‘Parallels Mac Client Push Installation’
In the Accounts tab, click the Yellow starburst
Enter an account which has local admin rights on the Mac devices.
Back at the Parallels Network Discovery set up, in the Boundaries tab select the boundary in your ConfigMgr site that contains the Mac device.
You can also enter a Subnet to discover devices in.
In the schedule tab enter a relevant schedule for discovery.
When discovery runs a pma_discovery.log will be created in the WindowsLogs folder on the proxy server.
If devices are discovered they will appear in the ConfigMgr console.
Now that we have a Mac object discovered in ConfigMgr we can push the Parallels Mac client to the device. To achieve this however, the following must be enabled on the Mac device.
If you want to use a domain account to push install Parallels Mac Client, you need to grant administrative privileges to it on a Mac. You can do this as follows:
If you have Mac computers that are not members of a domain (or if you don’t want to use a domain account for any reason), you need to create a local OS X user with administrative privileges.
To add a user, open System Preferences > Users and Groups, click the plus-sign icon, select Administrator and specify the user information. The username password is used to configure the client push installation.
The Configuration Manager Proxy will connect to Mac computers over SSH, so you need to enable SSH access on each Mac. To do so:
After enabling SSH access on a Mac and granting a local or a domain user SSH access, you should verify that you can actually establish an SSH connection. The Mac should allow SSH connection with password authentication.
Once the above configuration is enabled on the Mac right click the discovered Mac object in the ConfigMgr console. Select Parallels Management Tools>Install Parallels Mac Client.
Click Next.
Click ‘Install Parallels Mac Client even if it is installed’ and click Install.
The client will being to install.
Once complete the device will report back to ConfigMgr and be assigned to the site.
You’ll also be able to check out HINV details of the Mac in Resource Explorer.
and the Mac will be added to the All Mac OS X Systems collection.
On the Mac device you will see that a Parallels Mac Management applet is now available in System Preferences.
When opened you’ll notice this appears similar to the ConfigMgr control panel applet. It gives information on the site code, proxy it is connected to and more. The ‘Connect’ button allows you to run something similar to a Machine Policy Retrieval.
In the Part 5 of the series, I will show you how to deploy software applications to the managed device.
댓글 영역