A couple of days ago Microsoft released a new Configuration Manager 2012 SP1 and R2 clients that support the new version 10.10 of Mac OS X. Together with a hotfix (KB3013398) for Configuration Manager 2012 SP1 and R2 you will be all set to support your updated Mac OS X clients.

One of the (many) big changes in Configuration Manager 2012 SP1 is the ability to enrol and manage Mac OS X clients using a native agent. As you’d expect with any sort of cross-platform, non-Windows management story, you won’t be able to do all the same things with Configuration Manager that you can do with a Windows platform. NSX Installation and Upgrade Guide Overview of NSX NSX Capabilities NSX Components NSX Manager NSX vSwitch NSX Controller. If you are a new customer, register now for access to product evaluations and purchasing capabilities. Need access to an account? If your company has an existing Red Hat account, your organization administrator can grant you access.

Factors for Surface area and Program Center Configuration Manager. 8 a few minutes to go through. Members.

In this article Fundamentally, management and deployment of Surface gadgets with Program Center Construction Manager is usually the same as the administration and deployment of any additional Personal computer. Like any additional Personal computer, a deployment to Surface devices contains importing drivers, importing a Home windows image, preparing a deployment task sequence, and then deploying the task series to a selection. After deployment, Surface area devices are like any various other Windows client - to publish apps, settings, and procedures, you make use of the same procedure that you would use for any various other gadget. You can discover more details about how to use Configuration Supervisor to set up and manage gadgets in the.

AIthough the deployment ánd management of Surface area devices will be fundamentally the exact same as any other PC, there are usually some situations that may need additional considerations or methods. This post provides descriptions and guidance for these scenarios; the options recorded in this content may utilize to some other products and producers as well. Take note For management of Surface gadgets it is definitely recommended that you use the Current Part of Program Center Settings Manager. Upgrading Surface device motorists and firmware For products that receive updates through Windows Update, drivers for Surface elements - and actually firmware improvements - are applied automatically as component of the Windows Update process. For gadgets with managed improvements, like as those up to date through Home windows Server Revise Providers (WSUS), the option to set up motorists and firmware through Home windows Update is certainly not available. For these managed products, the recommended drivers management process is certainly the deployment of drivers and firmware up-dates using the Windows Installer (.msi) files, which are usually provided through the Microsoft Download Center.

You can discover a checklist of these downIoads át. As.msi documents, deployment of drivers and firmware improvements is carried out in the exact same way as deployment of an software. Rather of installing an software as would usually occur when an.msi file is run, the Surface area drivers and firmware.msi will apply the motorist and firmware up-dates to the gadget. The individual.msi document consists of the motorist and firmware improvements needed by each component of the Surface area device. The improvements for firmware are usually applied the next time the device reboots. You can read more about the.msi installation method for Surface drivers and firmware in.

For even more details about how to deploy applications with Settings Manager, observe. Note Surface device motorists and firmware are agreed upon with SHA-256, which is not really natively supported by Home windows Server 2008 R2. A workaround is usually obtainable for Settings Manager environments operating on Home windows Server 2008 L2 - for even more information notice. Surface Ethernet, adapters and Settings Supervisor deployment The default mechanism that Settings Manager utilizes to recognize gadgets during deployment is certainly the Mass media Access Control (Mac pc) address. Because the MAC address is usually associated with the Ethernet controller, an Ethernet, adapter shared among several gadgets will trigger Configuration Supervisor to identify each of the gadgets as only a solitary gadget. This can cause a Settings Supervisor deployment of Home windows to not be applied to intended products.

To make certain that Surface area devices making use of the exact same Ethernet, adapter are usually determined as special products during deployment, you can teach Configuration Supervisor to recognize devices making use of another method. This additional technique could become the Mac pc address of the wireless network adapter or the Program Universal Unique Identifier (System UUID). You can specify that Settings Manager use other recognition methods with the using options:. Include an exemption for the Macintosh contact information of Surface Ethernet adapters, which factors Configuration Manager to ignore the Macintosh address in preference of the System UUID, as recorded in the blog site write-up. Prestage gadgets by Program UUID as recorded in the blog post.

Make use of a script to recognize a recently deployed Surface area gadget by the Macintosh address of its wireless adapter, as recorded in the blog post. Another consideration for the Surface Ethernet, adapter during deployments with Configuration Manager is the car owner for the Ethernet controller.

Beginning in Windows 10, version 1511, the car owner for the Surface area Ethernet adapter is included by default in Windows. For agencies that need to deploy the latest version of Windows 10 and make use of the most recent edition of WinPE, use of the Surface Ethernet, adapter demands no extra actions. For variations of Home windows prior to Home windows 10, version 1511 (including Windows 10 RTM and Home windows 8.1), you may nevertheless require to set up the Surface Ethernet adapter car owner and include the drivers in your WinPE shoe press. With its addition in Windows 10, the car owner is no longer accessible for download fróm the Microsoft DownIoad Center. To download the Surface Ethernet adapter drivers, download it fróm the Microsoft Up-date Catalog as recorded in the blog site write-up from the Ask The Core Team blog site. Deploy Surface app with Settings Manager With the release of Microsoft Shop for Business, Surface area app will be no more time obtainable as a motorist and firmware download. Organizations that want to deploy Surface area app to maintained Surface devices or during depIoyment with the use of Construction Supervisor, must acquire Surface area app through Microsoft Store for Business and after that deploy Surface app with PowerSheIl.

You can find the PowerShell orders for deployment of Surface app, instructions to download Surface app, and must frameworks from Microsoft Store for Company in the content in the TechNet Library. Make use of prestaged mass media with Surface clients If your company utilizes prestaged media to pre-load deployment assets on to machines prior to deployment with Settings Supervisor, the nature of Surface area products as UEFI products may require you to get additional ways. Specifically, a native UEFI atmosphere requires that you create multiple partitions on the shoe cd disk of the system. If you are usually following along with the, the directions supply for only individual partition shoe devices and consequently will fall short when used to Surface area devices. Directions for using prestaged media to UEFI devices, such as Surface area gadgets, can end up being found in the blog site post.

Licensing conflicts with OEM Service 3.0 Surface devices come preinstalled with a certified copy of Windows. For illustration, Surface Pro 4 can be preinstalled with Windows 10 Expert.

The license essential for this preinstalled copy of Windows is inlayed in the firmwaré of the gadget with OEM Account activation 3.0 (OA 3.0). When you run Windows installation media on a device with an OA 3.0 essential, Windows setup automatically states the license essential and utilizes it to install and trigger Home windows. In most circumstances, this simplifies thé reinstallation of Home windows, because the consumer does not have to discover or get into a license essential. When you reimage a gadget by using Windows Organization, this stuck license essential does not result in a conflict. This is usually because the set up press for Home windows Enterprise can be set up to install only an Organization release of Home windows and thus is incompatible with the license key inlayed in the system firmware. If a product key is usually not stipulated (such as when you want to power up with Essential Management Providers (KMS) or Dynamic Directory Dependent Service), a Generic Volume License Essential (GVLK) is certainly utilized until Home windows is activated by one of those technologies. However, issues may arise when agencies plan to make use of variations of Windows that are compatible with the firmware embedded key.

For illustration, an firm that desires to set up Windows 10 Professional on a Surface area 3 gadget that originally delivered with Home windows 10 Home model may experience problems when Windows setup immediately says the Home edition key during installation and installs as House edition rather than Expert. To avoid this struggle, you can make use of thé Ei.cfg ór Pid.txt file (see ) to explicitly instruct Windows setup to prompt for a item essential, or you can enter a specific product essential in the deployment task series.

If you perform not possess a specific key, you can make use of the default item tips for Windows, which you can discover in on the Device Partner Center. Apply an asset tag during deployment Surface area Studio, Surface Book, Surface Professional 4, Surface Pro 3, and Surface 3 devices all support the program of an resource tag in UEFI.

This resource label can end up being used to determine the gadget from UEFI even if the operating system fails, and it can also end up being queried fróm within the opérating system. To read through even more about the Surface area Asset Label function, see the blog site write-up. To apply an resource tag using the during a Construction Manager deployment job sequence, make use of the script and guidelines found in the blog page write-up. Configure push-button reset When you set up Windows to a Surface area gadget, the push-button reset to zero functionality of Home windows is set up by default to revert the program back again to a state where the atmosphere is not really yet set up.

When the reset to zero function is definitely utilized, the system discards any installed applications and configurations. Although in some circumstances it can end up being beneficial to bring back the system to a state without programs and settings, in a expert environment this effectively makes the program useless to the end consumer.

Push-button reset can end up being configured, nevertheless, to recover the system configuration to a state where it will be prepared for make use of by the finish user. Stick to the process discussed in to personalize the push-button reset experience for your gadgets.