-->
- Mac Os X Software Update
- Property Management Software Mac
- Property Management Software Mac Os X Lion 10 7 5 11g63 11g63 Upgrade To 10 8
- Latest Mac Os X Software
- Mac Os Software List
- Property Management Software For Mac
Mac Os X Software Update
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.
May 27, 2020 You can download Property Manager 1.7 for Mac from our application library for free. The most popular versions of Property Manager for Mac are 1.7 and 1.6. This Mac app was originally created by Orion Transfer Ltd. Our antivirus check shows that this Mac download is safe.
MuCommander, Path Finder, and Leap are probably your best bets out of the 18 options considered. 'Available on Linux, Mac, and Windows' is the primary reason people pick muCommander over the competition. This page is powered by a knowledgeable community that. Hello, we're Mac Property Management, LLC Mac Properties provides rental apartment homes and retail spaces in the historic neighborhoods of Hyde Park, in Chicago, IL and Kansas City, St. We provide residents with modern amenities to facilitate contemporary lifestyles and preserve our neighborhoods' rich architectural heritage through. Property Management Software for Mac Property management software is used by landlords and professional property managers to manage rental properties. The software typically provides the ability to track all aspects of property maintenance as well as manage tenant records.
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:
- Allow users to enroll mobile devices and Mac computers: Yes
- Enrollment profile: Choose Set Profile.
- 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.NoteIf 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.TipIf 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:[email protected]
ImportantWhen 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.
- 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.
Property Management Software Mac
- 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'
NoteIf 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:
- Enter the command
sudo /Applications/Utilities/Keychain Access.app/Contents/MacOS/Keychain Access
- In the Keychain Access window, in the Keychains section, choose System. Then in the Category section, choose Keys.
- Expand the keys to view the client certificates. Find the certificate with a private key that you installed, and open the key.
- On the Access Control tab, choose Confirm before allowing access.
- Browse to /Library/Application Support/Microsoft/CCM, select CCMClient, and then choose Add.
- 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:
See also
Those of you who are already familiar with writing device drivers for Mac OS 9 or for BSD will discover that writing drivers for OS X requires some new ways of thinking. In creating OS X, Apple has completely redesigned the Macintosh I/O architecture, providing a framework for simplified driver development that supports many categories of devices. This framework is called the I/O Kit.
From a programming perspective, the I/O Kit provides an abstract view of the system hardware to the upper layers of OS X. The I/O Kit uses an object-oriented programming model, implemented in a restricted subset of C++ to promote increased code reuse.
By starting with properly designed base classes, you gain a head start in writing a new driver; with much of the driver code already written, you need only to fill in the specific code that makes your driver different. For example, all SCSI controllers deliver a fairly standard set of commands to a device, but do so via different low-level mechanisms. By properly using object-oriented programming methodology, a SCSI driver can implement those low-level transport portions without reimplementing the higher level SCSI protocol code. Similar opportunities for code reuse can be found in most types of drivers.
Part of the philosophy of the I/O Kit is to make the design completely open. Rather than hiding parts of the API in an attempt to protect developers from themselves, all of the I/O Kit source is available as part of Darwin. You can use the source code as an aid to designing (and debugging) new drivers.
Instead of hiding the interfaces, Apple’s designers have chosen to lead by example. Sample code and classes show the recommended (easy) way to write a driver. However, you are not prevented from doing things the hard way (or the wrong way). Instead, attention has been concentrated on making the “best” ways easy to follow.
Redesigning the I/O Model
You might ask why Apple chose to redesign the I/O model. At first glance, it might seem that reusing the model from Mac OS 9 or FreeBSD would have been an easier choice. There are several reasons for the decision, however.
Neither the Mac OS 9 driver model nor the FreeBSD model offered a feature set rich enough to meet the needs of OS X. The underlying operating-system technology of OS X is very different from that of Mac OS 9. The OS X kernel is significantly more advanced than the previous Mac OS system architecture; OS X needs to handle memory protection, preemption, multiprocessing, and other features not present (or substantially less pervasive) in previous versions of the Mac OS.
Although FreeBSD supports these features, the BSD driver model did not offer the automatic configuration, stacking, power management, or dynamic device-loading features required in a modern, consumer-oriented operating system.
By redesigning the I/O architecture, Apple’s engineers can take best advantage of the operating-system features in OS X. For example, virtual memory (VM) is not a fundamental part of the operating system in Mac OS 9. Thus, every driver writer must know about (and write for) VM. This has presented certain complications for developers. In contrast, OS X has simplified driver interaction with VM. VM capability is inherent in the OS X operating system and cannot be turned off by the user. Thus, VM capabilities can be abstracted into the I/O Kit, and the code for handling VM need not be written for every driver.
OS X offers an unprecedented opportunity to reuse code. In Mac OS 9, for example, all software development kits (SDKs) were independent of each other, duplicating functionality between them. In OS X, the I/O Kit is delivered as part of the basic developer tools, and code is shared among its various parts.
In contrast with traditional I/O models, the reusable code model provided by the I/O Kit can decrease your development work substantially. In porting drivers from Mac OS 9, for example, the OS X counterparts have been up to 75% smaller.
In general, all hardware support is provided directly by I/O Kit entities. One exception to this rule is imaging devices such as printers, scanners, and digital cameras (although these do make some use of I/O Kit functionality). Specifically, although communication with these devices is handled by the I/O Kit (for instance, under the FireWire or USB families), support for particular device characteristics is handled by user-space code (see For More Information for further discussion). If you need to support imaging devices, you should employ the appropriate imaging software development kit (SDK).
The I/O Kit attempts to represent, in software, the same hierarchy that exists in hardware. Some things are difficult to abstract, however. When the hardware hierarchy is difficult to represent (for example, if layering violations occur), then the I/O Kit abstractions provide less help for writing drivers.
In addition, all drivers exist to drive hardware; all hardware is different. Even with the reusable model provided by the I/O Kit, you still need to be aware of any hardware quirks that may impact a higher-level view of the device. The code to support those quirks still needs to be unique from driver to driver.
Although most developers should be able to take full advantage of I/O Kit device families (see Families), there will occasionally be some who cannot. Even those developers should be able to make use of parts of the I/O Kit, however. In any case, the source code is always available. You can replace functionality and modify the classes yourself if you need to do so.
In designing the I/O Kit, one goal has been to make developers’ lives easier. Unfortunately, it is not possible to make all developers’ lives uniformly easy. Therefore, a second goal of the I/O Kit design is to meet the needs of the majority of developers, without getting in the way of the minority who need lower level access to the hardware.
I/O Kit Architecture
The I/O Kit provides a model of system hardware in an object-oriented framework. Each type of service or device is represented by a C++ class; each discrete service or device is represented by an instance (object) of that class.
There are three major conceptual elements of the I/O Kit architecture:
Families
A family defines a collection of high-level abstractions common to all devices of a particular category that takes the form of C code and C++ classes. Families may include headers, libraries, sample code, test harnesses, and documentation. They provide the API, generic support code, and at least one example driver (in the documentation).
Families provide services for many different categories of devices. For example, there are protocol families (such as SCSI, USB, and FireWire), storage families (disk), network families, and families to describe human interface devices (mouse and keyboard). When devices have features in common, the software that supports those features is most likely found in a family.
Common abstractions are defined and implemented by the family, allowing all drivers in a family to share similar features easily. For example, all SCSI controllers have certain things they must do, such as scanning the SCSI bus. The SCSI family defines and implements the functionality that is common to SCSI controllers. Because this functionality has been included in the SCSI family, you do not need to include scanning code (for example) in your new SCSI controller driver.
Instead, you can concentrate on device-specific details that make your driver different from other SCSI drivers. The use of families means there is less code for you to write.
Families are dynamically loadable; they are loaded when needed and unloaded when no longer needed. Although some common families may be preloaded at system startup, all families should be considered to be dynamically loadable (and, therefore, potentially unloaded). See the Connection Example for an illustration.
Drivers
Property Management Software Mac Os X Lion 10 7 5 11g63 11g63 Upgrade To 10 8
A driver is an I/O Kit object that manages a specific device or bus, presenting a more abstract view of that device to other parts of the system. When a driver is loaded, its required families are also loaded to provide necessary, common functionality. The request to load a driver causes all of its dependent requirements (and their requirements) to be loaded first. After all requirements are met, the requested driver is loaded as well. See Connection Example for an illustration.
Latest Mac Os X Software
Note that families are loaded upon demand of the driver, not the other way around. Occasionally, a family may already be loaded when a driver demands it; however, you should never assume this. To ensure that all requirements are met, each device driver should list all of its requirements in its property list.
Most drivers are in a client-provider relationship, wherein the driver must know about both the family from which it inherits and the family to which it connects. A SCSI controller driver, for example, must be able to communicate with both the SCSI family and the PCI family (as a client of PCI and provider of SCSI). A SCSI disk driver communicates with both the SCSI and storage families.
Nubs
A nub is an I/O Kit object that represents a point of connection for a driver. It represents a controllable entity such as a disk or a bus.
A nub is loaded as part of the family that instantiates it. Each nub provides access to the device or service that it represents and provides services such as matching, arbitration, and power management.
The concept of nubs can be more easily visualized by imagining a TV set. There is a wire attached to your wall that provides TV service from somewhere. For all practical purposes, it is permanently associated with that provider, the instantiating class (the cable company who installed the line). It can be attached to the TV to provide a service (cable TV). That wire is a nub.
Each nub provides a bridge between two drivers (and, by extension, between two families). It is most common that a driver publishes one nub for each individual device or service it controls. (In this example, imagine one wire for every home serviced by the cable company.)
It is also possible for a driver that controls only a single device or service to act as its own nub. (Imagine the antenna on the back of your TV that has a built-in wire.) See the Connection Example for an illustration of the relationship between nubs and drivers.
Connection Example
Figure 12-1 illustrates the I/O Kit architecture, using several example drivers and their corresponding nubs. Note that many different driver combinations are possible; this diagram shows only one possibility.
In this case, a SCSI stack is shown, with a PCI controller, a disk, and a SCSI scanner. The SCSI disk is controlled by a kernel-resident driver. The SCSI scanner is controlled by a driver that is part of a user application.
This example illustrates how a SCSI disk driver (Storage family) is connected to the PCI bus. The connection is made in several steps.
Mac Os Software List
- The PCI bus driver discovers a PCI device and announces its presence by creating a nub (
IOPCIDevice
). The nub’s class is defined by the PCI family. - The bus driver identifies (matches) the correct device driver and requests that the driver be loaded. At the end of this matching process, a SCSI controller driver has been found and loaded. Loading the controller driver causes all required families to be loaded as well. In this case, the SCSI family is loaded; the PCI family (also required) is already present. The SCSI controller driver is given a reference to the
IOPCIDevice
nub. - The SCSI controller driver scans the SCSI bus for devices. Upon finding a device, it announces the presence of the device by creating a nub (
IOSCSIDevice
). The class of this nub is defined by the SCSI family. - The controller driver identifies (matches) the correct device driver and requests that the driver be loaded. At the end of this matching process, a disk driver has been found and loaded. Loading the disk driver causes all required families to be loaded as well. In this case, the Storage family is loaded; the SCSI family (also required) is already present. The disk driver is given a reference to the
IOSCSIDevice
nub.
For More Information
For more information on the I/O Kit, you should read the document IOKit Fundamentals, available from Apple’s developer documentation website, http://developer.apple.com/documentation. It provides a good general overview of the I/O Kit.
In addition to IOKit Fundamentals, the website contains a number of HOWTO documents and topic-specific documents that describe issues specific to particular technology areas such as FireWire and USB.
Property Management Software For Mac
Copyright © 2002, 2013 Apple Inc. All Rights Reserved. Terms of Use | Privacy Policy | Updated: 2013-08-08