Planning to Deploy Windows 8 Apps in Configuration Manager
Updated: April 1, 2013
Applies To: System Center 2012 Configuration Manager SP1
Note |
|---|
| The information in this topic applies only to System Center 2012 Configuration Manager SP1. |
Use the information in the following table to help you plan and prepare to deploy Windows 8 applications (apps) to System Center 2012 Configuration Manager SP1 clients in your organization.
| Process | Reference | ||||
|---|---|---|---|---|---|
|
Review the available information about the basic concepts for application management in Configuration Manager. |
For introductory information about application management, see Introduction to Application Management in Configuration Manager. |
||||
|
Review and implement the prerequisites to deploy applications in Configuration Manager. |
For information about the prerequisites for application management, see Prerequisites for Application Management in Configuration Manager. |
||||
|
Configure and test the Application Catalog and Software Center to enable users to browse for and install software. |
For information about how to configure the Application Catalog and Software Center, see Configuring the Application Catalog and Software Center in Configuration Manager. |
||||
|
Review the two different available methods that you can use to deploy software to computers that run Windows 8:
|
No additional information. |
||||
|
Review the requirements and recommendations to deploy Windows 8 apps to computers in the company. If you are deploying a line of business application, work with the application developers to ensure that the following requirements are met:
|
For information about how to validate the technical compliance of Windows 8 apps, see Testing your app with the Windows App Certification Kit in the Windows Dev Center. For information about how to sign apps by using Microsoft Visual Studio, see Signing an app package (Windows Store apps) in the Windows Dev Center. |
||||
|
Configure Windows 8 computers to allow direct installation of Windows 8 apps. To do so, use group policy to configure the following sideloading registry settings:
|
For more information about how to configure group policy preferences in order to configure registry settings, see your Windows documentation. |
||||
|
When you create an application of the type Windows app package (in the Windows Store), you must browse to a reference computer and select the application in order to create a link. Before you can do this, you must prepare the reference computer to receive Web Service Management (WS-Management) requests from the Configuration Manager console. |
See Prepare the Reference Computer for Application Browsing in this topic. |
Use the following information when the steps in the preceding table require supplemental procedures.
Perform the following procedure to configure an HTTPS connection between the computer that runs the Configuration Manager console and the reference computer, which is the Windows 8 computer that contains the Windows Store applications to be browsed.
-
Ensure that the account you use to log on to the computer that runs the Configuration Manager console has Administrator permissions on both the computer running the console and on the reference computer.
-
At a command prompt on the reference computer, enter the following command to create an HTTPS-based listener:
winrm qc –Transport:HTTPS
-
On the reference computer, enter the following command to allow Windows PowerShell to make remote connections to the computer:
enable-psremoting
-
On the reference computer, enter the following command to remove the HTTP-based listener that was enabled by the previous command:
winrm delete winrm/config/Listener?Address=*+Transport=HTTP
-
On the reference computer, configure a Windows Firewall inbound rule for port 5986, which is the default HTTPS port that will be used for communication.
Use the following table to understand when you must configure the sideloading keys in Windows 8 or Windows Server 2012 to enable the direct installation of applications:
Important |
|---|
| The Desktop Experience feature of Windows Server 2012 must be enabled if you want to install applications from the Windows Store. |
| Windows version | Configure AllowAllTrustedApps registry key | Domain joined | Sign .appx file with trusted enterprise code signing certificate | Sideloading key required |
|---|---|---|---|---|
|
Windows 8 Enterprise |
Yes |
Yes |
Yes. Code signing certification authority is trusted on Windows 8 clients. |
Required if Enterprise client is not joined to a domain |
|
Windows 8 Professional |
Yes |
Not required |
Yes. Code signing certification authority is trusted on Windows 8 clients. |
Yes |
|
Windows RT |
Yes |
Not required |
Yes. Code signing certification authority is trusted on Windows 8 clients. |
Yes |
|
Windows Server 2012 |
Yes |
Yes |
Yes. Code signing certification authority is trusted on Windows Server 2012 clients. |
Does not support sideloading key |
Note |
|---|
| Windows 8 Home versions do not support enterprise sideloading. |
See Also
-----
For additional resources, see Information and Support for Configuration Manager.
Tip: Use this query to find online documentation in the TechNet Library for System Center 2012 Configuration Manager. For instructions and examples, see Search the Configuration Manager Documentation Library.
-----

Note