Wmi Equivalent For Mac
WMI is based on WBEM (web-based enterprise management), which a quick Google (for wbem unix) reveals exists in at least HP-UX, with some vague rumblings of it being more generally available. Squillman is right though, it's not that great, although it can come in handy for some quick 'n' dirty reporting.
-->Features no longer available in PowerShell Core
Modules not shipped for PowerShell 6.x
For various compatibility reasons, the following modules are not included in PowerShell 6.
- ISE
- Microsoft.PowerShell.LocalAccounts
- Microsoft.PowerShell.ODataUtils
- Microsoft.PowerShell.Operation.Validation
- PSScheduledJob
- PSWorkflow
- PSWorkflowUtility
PowerShell Workflow
PowerShell Workflow is a feature in Windows PowerShell that builds on top ofWindows Workflow Foundation (WF) that enables the creation of robust runbooksfor long-running or parallelized tasks.
Due to the lack of support for Windows Workflow Foundation in .NET Core, we are not supportingPowerShell Workflow in PowerShell Core.
In the future, we would like to enable native parallelism/concurrency in the PowerShell languagewithout the need for PowerShell Workflow.
If there is a need to use checkpoints to resume a script after the OS restarts, we recommendusing Task Scheduler to run a script on OS startup, but the script would need to maintainits own state (like persisting it to a file).
Custom snap-ins
PowerShell snap-ins are a predecessor to PowerShell modules that do not have widespreadadoption in the PowerShell community.
Due to the complexity of supporting snap-ins and their lack of usage in the community, we no longersupport custom snap-ins in PowerShell Core.
Today, this breaks the ActiveDirectory and DnsClient modules in Windows and Windows Server.
WMI v1 cmdlets
Due to the complexity of supporting two sets of WMI-based modules, we removed the WMI v1 cmdletsfrom PowerShell Core:
Register-WmiEventSet-WmiInstanceInvoke-WmiMethodGet-WmiObjectRemove-WmiObject
Instead, we recommend that you the use the CIM (aka WMI v2) cmdlets which provide the samefunctionality with new functionality and a redesigned syntax:
Get-CimAssociatedInstanceGet-CimClassGet-CimInstanceGet-CimSessionInvoke-CimMethodNew-CimInstanceNew-CimSessionNew-CimSessionOptionRegister-CimIndicationEventRemove-CimInstanceRemove-CimSessionSet-CimInstance
Microsoft.PowerShell.LocalAccounts
Due to the use of unsupported APIs, Microsoft.PowerShell.LocalAccounts has been removed fromPowerShell Core until a better solution is found.
New-WebServiceProxy cmdlet removed
.NET Core does not support the Windows Communication Framework, which provide services for using theSOAP protocol. This cmdlet was removed because it requires SOAP.
*-Transaction cmdlets removed
These cmdlets had very limited usage. The decision was made to discontinue support for them.
Complete-TransactionGet-TransactionStart-TransactionUndo-TransactionUse-Transaction
Security cmdlets not available on non-Windows platforms
Get-AclSet-AclGet-AuthenticodeSignatureSet-AuthenticodeSignatureGet-CmsMessageProtect-CmsMessageUnprotect-CmsMessageNew-FileCatalogTest-FileCatalog
*-Computerand other Windows-specific cmdlets
Due to the use of unsupported APIs, the following cmdlets have been removed from PowerShell Coreuntil a better solution is found.
Get-ClipboardSet-ClipboardAdd-ComputerCheckpoint-ComputerRemove-ComputerRestore-ComputerReset-ComputerMachinePasswordDisable-ComputerRestoreEnable-ComputerRestoreGet-ComputerRestorePointTest-ComputerSecureChannelGet-ControlPanelItemShow-ControlPanelItemGet-HotFixClear-RecycleBinUpdate-ListOut-PrinterConvertFrom-StringConvert-String
*-Counter cmdlets
Due to the use of unsupported APIs, the *-Counter has been removed from PowerShell Core until abetter solution is found.
*-EventLog cmdlets
Due to the use of unsupported APIs, the *-EventLog has been removed from PowerShell Core. until abetter solution is found. Get-WinEvent and Create-WinEvent are available to get and createevents on Windows.
Cmdlets that use WPF removed
The Windows Presentation Framework is not supported on CoreCLR. The following cmdlets are affected:
Show-CommandOut-GridView- The showwindow parameter of
Get-Help
Some DSC cmdlets removed
Get-DscConfigurationPublish-DscConfigurationRestore-DscConfigurationStart-DscConfigurationStop-DscConfigurationTest-DscConfigurationUpdate-DscConfigurationRemove-DscConfigurationDocumentGet-DscConfigurationStatusDisable-DscDebugEnable-DscDebugGet-DscLocalConfigurationManagerSet-DscLocalConfigurationManagerInvoke-DscResource
Engine/language changes
Rename powershell.exe to pwsh.exe#5101
In order to give users a deterministic way to call PowerShell Core on Windows (as opposed toWindows PowerShell), the PowerShell Core binary was changed to pwsh.exe on Windows and pwsh onnon-Windows platforms.
The shortened name is also consistent with naming of shells on non-Windows platforms.
Don't insert line breaks to output (except for tables) #5193
Previously, output was aligned to the width of the console and line breaks were added at the endwidth of the console, meaning the output didn't get reformatted as expected if the terminal wasresized. This change was not applied to tables, as the line breaks are necessary to keep the columnsaligned.
Skip null-element check for collections with a value-type element type #5432
For the Mandatory parameter and ValidateNotNull and ValidateNotNullOrEmpty attributes, skipthe null-element check if the collection's element type is value type.
Change $OutputEncoding to use UTF-8 NoBOM encoding rather than ASCII #5369
The previous encoding, ASCII (7-bit), would result in incorrect alteration of the output in somecases. This change is to make UTF-8 NoBOM default, which preserves Unicode output with an encodingsupported by most tools and operating systems.
Remove AllScope from most default aliases #5268
To speed up scope creation, AllScope was removed from most default aliases. AllScope was leftfor a few frequently used aliases where the lookup was faster.
-Verbose and -Debug no longer overrides $ErrorActionPreference#5113
Previously, if -Verbose or -Debug were specified, it overrode the behavior of$ErrorActionPreference. With this change, -Verbose and -Debug no longer affect the behaviorof $ErrorActionPreference.
Cmdlet changes
Invoke-RestMethod doesn't return useful info when no data is returned. #5320
When an API returns just null, Invoke-RestMethod was serializing this as the string 'null'instead of $null. This change fixes the logic in Invoke-RestMethod to properly serialize avalid single value JSON null literal as $null.
Remove -Protocol from *-Computer cmdlets #5277
Due to issues with RPC remoting in CoreFX (particularly on non-Windows platforms) and ensuring aconsistent remoting experience in PowerShell, the -Protocol parameter was removed from the*-Computer cmdlets. DCOM is no longer supported for remoting. The following cmdlets only supportWSMAN remoting:
- Rename-Computer
- Restart-Computer
- Stop-Computer
Remove -ComputerName from *-Service cmdlets #5090
In order to encourage the consistent use of PSRP, the -ComputerName parameter was removed from*-Service cmdlets.
Fix Get-Item -LiteralPath a*b if a*b doesn't actually exist to return error #5197
Previously, -LiteralPath given a wildcard would treat it the same as -Path and if the wildcardfound no files, it would silently exit. Correct behavior should be that -LiteralPath is literalso if the file doesn't exist, it should error. Change is to treat wildcards used with -Literal asliteral.
Import-Csv should apply PSTypeNames upon import when type information is present in the CSV #5134
Previously, objects exported using Export-CSV with TypeInformation imported withConvertFrom-Csv were not retaining the type information. This change adds the type information toPSTypeNames member if available from the CSV file.
-NoTypeInformation should be default on Export-Csv#5131
This change was made to address customer feedback on the default behavior of Export-CSV toinclude type information.
Previously, the cmdlet would output a comment as the first line containing the type name of theobject. The change is to suppress this by default as it's not understood by most tools. Use-IncludeTypeInformation to retain the previous behavior.
Web Cmdlets should warn when -Credential is sent over unencrypted connections #5112
When using HTTP, content including passwords are sent as clear-text. This change is to not allowthis by default and return an error if credentials are being passed in an insecure manner. Userscan bypass this by using the -AllowUnencryptedAuthentication switch.
API changes
Remove AddTypeCommandBase class #5407
The AddTypeCommandBase class was removed from Add-Type to improve performance. This class isonly used by the Add-Type cmdlet and should not impact users.
Unify cmdlets with parameter -Encoding to be of type System.Text.Encoding#5080
The -Encoding value Byte has been removed from the filesystem provider cmdlets. A newparameter, -AsByteStream, is now used to specify that a byte stream is required as input or thatthe output is a stream of bytes.
Add better error message for empty and null -UFormat parameter #5055
Previously, when passing an empty format string to -UFormat, an unhelpful error message wouldappear. A more descriptive error has been added.
Clean up console code #4995
The following features were removed as they are not supported in PowerShell Core, and there are noplans to add support as they exist for legacy reasons for Windows PowerShell: -psconsolefileswitch and code, -importsystemmodules switch and code, and font changing code.
Removed RunspaceConfiguration support #4942
Previously, when creating a PowerShell runspace programmatically using the API you could use thelegacy RunspaceConfiguration or the newer InitialSessionState. Thischange removed support for RunspaceConfiguration and only supports InitialSessionState.
CommandInvocationIntrinsics.InvokeScript bind arguments to $input instead of $args#4923
An incorrect position of a parameter resulted in the args passed as input instead of as args.
Remove unsupported -showwindow switch from Get-Help#4903
-showwindow relies on WPF, which is not supported on CoreCLR.
Allow * to be used in registry path for Remove-Item#4866
Previously, -LiteralPath given a wildcard would treat it the same as -Path and if the wildcardfound no files, it would silently exit. Correct behavior should be that -LiteralPath is literalso if the file doesn't exist, it should error. Change is to treat wildcards used with -Literal asliteral.
Fix Set-Service failing test #4802
Previously, if New-Service -StartupType foo was used, foo was ignored and the service wascreated with some default startup type. This change is to explicitly throw an error for an invalidstartup type.
Rename $IsOSX to $IsMacOS#4700
The naming in PowerShell should be consistent with our naming and conform to Apple's use of macOSinstead of OSX. However, for readability and consistently we are staying with Pascal casing.
Make error message consistent when invalid script is passed to -File, better error when passed ambiguous argument #4573
Change the exit codes of pwsh.exe to align with Unix conventions
Removal of LocalAccount and cmdlets from Diagnostics modules. #4302#4303
Due to unsupported APIs, the LocalAccounts module and the Counter cmdlets in the Diagnosticsmodule were removed until a better solution is found.
Executing PowerShell script with bool parameter does not work #4036
Previously, using powershell.exe (now pwsh.exe) to execute a PowerShell script using -Fileprovided no way to pass $true/$false as parameter values. Support for $true/$false as parsedvalues to parameters was added. Switch values are also supported as currently documented syntaxdoesn't work.
Remove ClrVersion property from $PSVersionTable#4027
The ClrVersion property of $PSVersionTable is not useful with CoreCLR, end users should not beusing that value to determine compatibility.
Change positional parameter for powershell.exe from -Command to -File#4019
Enable shebang use of PowerShell on non-Windows platforms. This means on Unix based systems, you canmake a script executable that would invoke PowerShell automatically rather than explicitly invokingpwsh. This also means that you can now do things like powershell foo.ps1 orpowershell fooScript without specifying -File. However, this change now requires that youexplicitly specify -c or -Command when trying to do things like powershell.exe Get-Command.
Implement Unicode escape parsing #3958
`u#### or `u{####} is converted to the corresponding Unicode character. To output aliteral `u, escape the backtick: ``u.
Change New-ModuleManifest encoding to UTF8NoBOM on non-Windows platforms #3940
Previously, New-ModuleManifest creates psd1 manifests in UTF-16 with BOM, creating a problem forLinux tools. This breaking change changes the encoding of New-ModuleManifest to be UTF (no BOM) innon-Windows platforms.
Prevent Get-ChildItem from recursing into symlinks (#1875). #3780
This change brings Get-ChildItem more in line with the Unix ls -r and the Windows dir /snative commands. Like the mentioned commands, the cmdlet displays symbolic links to directoriesfound during recursion, but does not recurse into them.
Fix Get-Content -Delimiter to not include the delimiter in the returned lines #3706
Previously, the output while using Get-Content -Delimiter was inconsistent and inconvenient as itrequired further processing of the data to remove the delimiter. This change removes the delimiterin returned lines.
Implement Format-Hex in C# #3320
The -Raw parameter is now a 'no-op' (in that it does nothing). Going forward all of the outputwill be displayed with a true representation of numbers that includes all of the bytes for its type(what the -Raw parameter was formally doing prior to this change).
PowerShell as a default shell doesn't work with script command #3319
On Unix, it is a convention for shells to accept -i for an interactive shell and many toolsexpect this behavior (script for example, and when setting PowerShell as the default shell) andcalls the shell with the -i switch. This change is breaking in that -i previously could be usedas short hand to match -inputformat, which now needs to be -in.
Typo fix in Get-ComputerInfo property name #3167
BiosSerialNumber was misspelled as BiosSeralNumber and has been changed to the correct spelling.
Add Get-StringHash and Get-FileHash cmdlets #3024
This change is that some hash algorithms are not supported by CoreFX, therefore they are no longeravailable:
MACTripleDESRIPEMD160
Add validation on Get-* cmdlets where passing $null returns all objects instead of error #2672
Passing $null to any of the following now throws an error:
Get-Credential -UserNameGet-Event -SourceIdentifierGet-EventSubscriber -SourceIdentifierGet-Help -NameGet-PSBreakpoint -ScriptGet-PSProvider -PSProviderGet-PSSessionConfiguration -NameGet-PSSnapin -NameGet-Runspace -NameGet-RunspaceDebug -RunspaceNameGet-Service -NameGet-TraceSource -NameGet-Variable -NameGet-WmiObject -ClassGet-WmiObject -Property
Add support W3C Extended Log File Format in Import-Csv#2482
Previously, the Import-Csv cmdlet cannot be used to directly import the log files in W3C extendedlog format and additional action would be required. With this change, W3C extended log format issupported.
Parameter binding problem with ValueFromRemainingArguments in PS functions #2035
ValueFromRemainingArguments now returns the values as an array instead of a single value whichitself is an array.
BuildVersion is removed from $PSVersionTable#1415
Remove the BuildVersion property from $PSVersionTable. This property was tied to the Windowsbuild version. Instead, we recommend that you use GitCommitId to retrieve the exact build versionof PowerShell Core.
Changes to Web Cmdlets
The underlying .NET API of the Web Cmdlets has been changed to System.Net.Http.HttpClient. Thischange provides many benefits. However, this change along with a lack of interoperability withInternet Explorer have resulted in several breaking changes within Invoke-WebRequest andInvoke-RestMethod.
Invoke-WebRequestnow supports basic HTML Parsing only.Invoke-WebRequestalways returns aBasicHtmlWebResponseObjectobject. TheParsedHtmlandFormsproperties have been removed.BasicHtmlWebResponseObject.Headersvalues are nowString[]instead ofString.BasicHtmlWebResponseObject.BaseResponseis now aSystem.Net.Http.HttpResponseMessageobject.- The
Responseproperty on Web Cmdlet exceptions is now aSystem.Net.Http.HttpResponseMessageobject. - Strict RFC header parsing is now default for the
-Headersand-UserAgentparameter. This canbe bypassed with-SkipHeaderValidation. file://andftp://URI schemes are no longer supported.System.Net.ServicePointManagersettings are no longer honored.- There is currently no certificate based authentication available on macOS.
- Use of
-Credentialover anhttp://URI will result in an error. Use anhttps://URI orsupply the-AllowUnencryptedAuthenticationparameter to suppress the error. -MaximumRedirectionnow produces a terminating error when redirection attempts exceed theprovided limit instead of returning the results of the last redirection.- In PowerShell 6.2, a change was made to default to UTF-8 encoding for JSON responses. When acharset is not supplied for a JSON response, the default encoding should be UTF-8 per RFC 8259.
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 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
PolicyEnableUserPolicyOnTSproperty 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
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.
Oregon Scientific DS Overview – CNETOregon scientific digital camera quick start guide 13 pages. Ds6618 drivers for mac. Recharge the battery as it will run out shortly.
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.
Where is the tools menu in word for mac. 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 Enterprise
Note
Support 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