In the app properties window, switch to the Deployment Types tab. Requirements specify conditions that must be met before an application is installed on a device. You can choose from built-in requirements or you can create your own. In this example, you add a requirement that the application will only get installed on devices that are running Windows Select Add to open the Create Requirement window.
Specify the following information:. Select OK to close each property page that you opened. Then return to the Applications list in the Configuration Manager console. Requirements can help reduce the number of Configuration Manager collections you need. Because you just specified that the application can only get installed on devices that are running Windows 11, you can later deploy this to a collection that contains PCs that run many different operating systems.
But the application will only get installed on Windows 11 devices. Next, to deploy the application to PCs, make sure that the application content is copied to a distribution point. PCs access the distribution point to install the application. To find out more about distribution points and content management in Configuration Manager, see Manage content and content infrastructure. In the Software Library workspace, expand Applications. Then, in the list of applications, select the CMPivot that you created.
On the Home tab, in the Deployment group, choose Distribute Content. On the General page of the Distribute Content Wizard , check that the application name is correct, and then choose Next.
On the Content page, review the information that will be copied to the distribution point, and then choose Next. On the Content Destination page, choose Add to select one or more distribution points, or distribution point groups on which to install the application content. Next, deploy the application to a device collection in your hierarchy. In this example, you deploy the application to the All Systems device collection. Remember that only Windows 11 computers will install the application because of the requirements that you selected earlier.
This behavior requires that language to be synchronized, and to exist for the specific application. Default language : If the user's language is unavailable, select a default language to use. Configuration Manager doesn't synchronize the app icon from the store. If you need an icon to display for this app in Software Center, manually add it in the app properties. For more information, see Manually specify application information.
After synchronization, create and deploy the Microsoft Store for Business and Education apps similar to any other Configuration Manager application. Choose the app you want to deploy, then select Create Application in the ribbon.
Then deploy and monitor this application as you would any other Configuration Manager application. For more information, see the following articles:. After deploying online apps, any updates to that app come directly from the Microsoft Store.
Furthermore, Configuration Manager doesn't check version compliance of online apps, just that Windows reports the app as installed.
When deploying offline apps to Windows devices with the Configuration Manager client, don't allow users to update applications external to Configuration Manager deployments. Control of updates to offline apps is especially important in multi-user environments such as classrooms. One option to disable the Microsoft Store is by using group policy. After the Microsoft Store for Business and Education administrator acquires an offline app, don't publish the app to users via the store.
This configuration makes sure that users can't install or update online. Users only receive offline app updates via Configuration Manager. In previous versions of Configuration Manager, you would create a collection of devices to deploy an application to. Although you can still create a collection, use requirements to specify more detailed criteria for an application deployment.
For example, specify that an application can only install on devices that run Windows When you deploy the application to all of your devices, it only installs on devices that run Windows Configuration Manager evaluates requirements to determine whether it installs an application and any of its deployment types.
Then it determines the correct deployment type by which to install an application. Every seven days, by default, the Configuration Manager client reevaluates requirement rules to determine compliance according to the client setting Schedule re-evaluation for deployments.
For more information, see Create and deploy an application and Deployment type Requirements. While you use requirements with a specific deployment type in a single application, you can also create global conditions. These conditions are a library of predefined requirements that you can use with any application and deployment type.
Configuration Manager includes a set of built-in global conditions, or you can create your own. For more information, see Create global conditions.
A simulated deployment evaluates the requirements, detection method, and dependencies for an application. A client reports the results without actually installing the application.
For more information, see Simulate application deployments. A deployment action specifies whether you want to install or uninstall the application you're deploying. Not all deployment types support the uninstall action. For more information, see Deploy applications. The deployment purpose specifies whether the deployment app is Required or Available :. The client automatically installs a required deployment according to the schedule that you set. If the application isn't hidden, a user can track its deployment status.
They can also use Software Center to install the application before the deadline. If you deploy the application to a user as available , they see it in Software Center, and can request it on demand. When you make revisions to an application or a deployment type, Configuration Manager creates a new version of the application.
Take the following actions in the Configuration Manager console:. Use one of the methods provided by the ConfigurationManager class to open a configuration file such as SampleApp. These methods return a Configuration object that in turn exposes methods and properties you can use to work with the associated configuration files. The methods perform read or write operations and create the configuration data every time that a file is written.
Support configuration tasks. The following types are used to support various configuration tasks:. In addition to working with existing configuration information, you can create and work with custom configuration elements by extending the built-in configuration types such as the ConfigurationElement , ConfigurationElementCollection , ConfigurationProperty , and ConfigurationSection classes. For an example of how to extend a built-in configuration type programmatically, see ConfigurationSection.
For an example of how to extend a built-in configuration type that uses the attribute-based model, see ConfigurationElement. The Configuration class enables programmatic access for editing configuration files. You use one of the Open methods provided by ConfigurationManager.
These methods return a Configuration object, which in turn provides the required methods and properties to handle the underlying configuration files. You can access these files for reading or writing. The user or process that reads must have the following permissions:. If your application needs read-only access to its own configuration, we recommend that you use the GetSection String method. This method provides access to the cached configuration values for the current application, which has better performance than the Configuration class.
To write to the configuration files, use one of the Save methods.
0コメント