Deploy content to device and user collections

With the Application model, you distribute the deployment to device collections and user collections.

1. Select the application you want to deploy from: \Software Library\Overview\Application Management\Applications\
2. Click Deploy in the navigation bar to start the Configuration Manager distribution process.
   
3. Start the collection you want to use:
   • User collection signed in to client machines
   • Online devices in the selected device collection
4. Select a point where to distribute the application, unless you've already distributed it.
5. Choose whether you want to make the application available for users to install or to automatically push and install it on the clients.
   • Available. You can require that users obtain administrator approval before installing the product. A notification will appear in the Software Center, where the administrator must approve the installation.
   • Required. If you also select Pre-deploy software to the user's primary device, the application is installed on the client designated as the user's primary device.
6. (Optional) Select when the application will be available.
7.  Specify which messages the Configuration Manager displays on the client.
8.  Determine whether to notify the System Center Operations manager when a product is installed or fails.
9.  Review the Summary page before committing the deployment.
10.  Click Next to deploy.

Deployments based on the Package model distribute content to devices, not users.

1. After you select your package in the Software Center and start the deployment wizard, select Device Collection from the drop-down menu.
2. Select the device collection to deploy. Make sure that you deploy to the device collection you created for the intended client machines.
3. Choose a deployment purpose setting:
   • Available. Select this option if you want to make the product available for the user to install from the Configuration Manager. This option makes the package available to the clients in the device collection. But the user must choose to install it.
   • Required. Select this option if you want to push and install the product on all devices in the device collection.
     
4. Consider options for waking up clients and continuing installation after the deadline:
   • Send wake-up packets. Select this option to start up clients (if they are turned off) and install the package on them. (Client machines must be configured for this option.)
   • Allow clients on a metered internet connection to download content after the installation deadline. Allow clients on slow networks to continue the installation even if the deadline elapses. (This option may incur extra costs.)
5. Choose Scheduling options. These options vary according to whether you selected Available or Required in the previous step.
   
   • If you selected Available: Specify the time and date you make the package available for users to install on their clients. Also indicate whether and when package availability expires. These options are not required.
   • If you selected Required: Create an assignment schedule. The quickest option is to select New and then choose to deploy as soon as possible.
6. Select a Rerun option, which determines when the installer will rerun.
   • Never rerun deployed program. The program will never rerun on a specific client under any circumstances.
   • Always rerun program. Tells the client to disregard previous execution status, such as removing a client and adding it back to a collection.
   • Rerun if failed previous attempt. Rerun determined by return codes.
   • Rerun if succeeded on previous attempt. The program runs again only if it has previously run successfully on the client. This setting is useful for recurring updates, which require the installation of a previous update before the installation of a later one.
7. Choose a Distribution Points deployment option:
   • Download content from distribution point and run locally. If you select this option, content files are downloaded to C:\Windows\ccmcache\ by default, but you can change the location.
     

   Note: To download the content and run it locally, make sure that the client cache has enough space. (To verify the cache size, go to Control panel > Configuration Manager > Cache.) To check for logged errors about cache limits, go to CAS.log in the C:\Windows\CCM\Logs\ folder. Also, there must be enough free storage space for the content to be downloaded and extracted locally.

   • Run the program from the distribution point. If you select this option, the installer runs remotely from the distribution point instead of downloading and running from the local cache. You don't have to set the cache size, but you do need to verify that you have enough free storage space.

Warning: This "run locally" setting is not recommended and doesn't work for Application and Hybrid mode deployments.

8. Review the Summary page to verify your deployment selections. You can go back to edit your settings.
9. Finish the deployment and view the Completion page. Your package is now deployed to the selected device collection.

Next topic: Distribute product updates