Windows application deployment steps

Quality Assurance and Productivity. CodeRush Classic. TestCafe Studio. Controls WinForms. UWP Windows Tools WinForms Skin Editor. WPF Theme Designer. Coded UI Test Extension. Frameworks and Libraries. XPO Profiler. Core Libraries. Controls and Extensions ASP. NET Core Controls. NET Bootstrap Controls.

DevExtreme ASP. Blazor Components. Tools ASP. NET Theme Builder. NET Theme Deployer. Maintenance Mode ASP. Free Xamarin. Forms UI Controls. Enterprise and Analytic Tools. Report and Dashboard Server. The Package Support Framework is an open-source kit that helps you apply fixes to your existing Win32 application when you don't have access to the source code, so that it can run in an MSIX container. The Package Support Framework helps your application follow the best practices of the modern runtime environment.

App Installer allows Windows 10 apps to be installed by double-clicking the app package. This means that users don't need to use PowerShell or other developer tools to deploy Windows 10 apps. The App Installer can also install an app from the web, optional packages, and related sets. In this example, we'll use a Windows Forms app. To start, add a new project to your solution, select the Windows Application Packaging Project, and give it a name. You'll see the structure of the packaging project and note a special folder called Applications.

Inside this folder, you can specify which applications you want to include in the package. It can be more than one. Right-click on the Applications folder and select the Windows Forms project you want to package from the Visual Studio solution. At this point, you can compile and generate the package but let's examine a couple of things.

To have a better user experience, Visual Studio can autogenerate all the visual assets a modern application needs to handle icons and tile assets for the tile bar and start menu. Open the Package. You can then generate all the visual assets from a given image present on your project just by clicking Create. If you open the code for the Package. This is where your packaged application is going to get its identity, which will be managed by the OS.

Set the packaging project as the startup project for the solution and select Run. This is going to:. With this, you have the clean install and uninstall experience that MSIX provides fully integrated into Windows Right-click on the packaging project, select the Store menu, and then select the Create App Packages option.

Then, you can choose between creating a package to upload to the store or creating packages for sideloading. In most modernization scenarios, you'll choose I want to create packages for sideloading.

There you can select the different architectures you want to target as you can include as many as you want into the same MSIX package.

You can choose to use a web server of a shared UNC path on your enterprise file servers. Pay attention to the settings to specify how you want to update your application.

For example:. Double-click Zero Touch WinPE x64 under Content Status in the console tree and verify that a status of Successfully distributed content is displayed on the Success tab. Review the distmgr. The third is the new boot image with DaRT.

If you have already completed steps in Deploy Windows 10 in a test lab using Microsoft Deployment Toolkit then you have already created a Windows 10 reference image. In this case, skip to the next procedure in this guide: Add a Windows 10 operating system image.

If you have not yet created a Windows 10 reference image, complete the steps in this section. The first step in creating a deployment share is to mount this file on SRV1. To open the deployment workbench, click Start , type deployment , and then click Deployment Workbench. Right-click the Operating Systems node, and then click New Folder. Name the new folder Windows Complete the wizard using default values and click Finish. Right-click the Windows 10 folder created in the previous step, and then click Import Operating System.

For purposes of this test lab, we will not add applications, such as Microsoft Office, to the deployment share. For information about adding applications, see the Add applications section of the Create a Windows 10 reference image topic in the TechNet library.

The next step is to create a task sequence to reference the operating system that was imported. Use the following settings for the New Task Sequence Wizard:. To edit the task sequence, double-click Windows 10 Enterprise x64 Default Image that was created in the previous step. Click the Task Sequence tab. A new group will be added under Tattoo. To see the name change, click Tattoo , then click the new group again.

Under Select the roles and features that should be installed , select. NET Framework 3. NET 2. Enable Windows Update in the task sequence by clicking the Windows Update Post-Application Installation step, clicking the Options tab, and clearing the Disable this step checkbox. Note: Since we are not installing applications in this test lab, there is no need to enable the Windows Update Pre-Application Installation step. However, you should enable this step if you are also installing applications.

The next step is to configure the MDT deployment share rules. Click Apply and then click Edit Bootstrap. Replace the contents of the Bootstrap.

The update process will take 5 to 10 minutes. When it has completed, click Finish. Accept the default values on the Capture Image page, and click Next.

Operating system installation will complete after 5 to 10 minutes and then the VM will reboot automatically. Allow the system to boot normally do not press a key. The process is fully automated. Additional system restarts will occur to complete updating and preparing the operating system. Setup will complete the following procedures:.

This step requires from 30 minutes to 2 hours, depending on the speed of the Hyper-V host and your network's download speed.

After some time, you will have a Windows 10 Enterprise x64 image that is fully patched and has run through Sysprep. Distribute the operating system image to the SRV1 distribution point by right-clicking the Windows 10 Enterprise x64 operating system image and then clicking Distribute Content.

Refresh the view with the F5 key or by right-clicking Windows 10 Enterprise x64 and clicking Refresh. Processing of the image on the site server can take several minutes. This adds a new action immediately after Set Status 5. Configure the Request State Store action that was just added with the following settings:. Configure the Release State Store action that was just added with the following settings:. In this case, skip the first four steps below and begin with step 5 to edit CustomSettings.

Click the Monitoring tab, select the Enable monitoring for this deployment share checkbox, and then click OK. As noted previously, if you wish to migrate accounts other than those in the Contoso domain, then change the OSDMigrateAdditionalCaptureOptions option.

For example, the following option will capture settings from all user accounts:. In this first deployment scenario, we will deploy Windows 10 using PXE. In this section, you'll take a quick look at the deployment status of the application that you deployed.

On the Home tab, in the Deployment group, choose View Status. Error : An error occurred installing the application on the indicated PCs. Further information about the error is also displayed. Requirements Not Met : No installation attempt was made on the indicated devices because they didn't meet the requirements you configured.

In this example, because they don't run on Windows Unknown : Configuration Manager was unable to report the status of the deployment. Check back again later. There are a few ways you can monitor application deployments. For more information, see Monitor applications. Users who have PCs that are managed by Configuration Manager and running Windows 11 see a message telling them that they must install the CMPivot application. Once they accept the deployment, the application gets installed.

Skip to main content. This browser is no longer supported. Download Microsoft Edge More info. Contents Exit focus mode. Please rate your experience Yes No. Any additional feedback? Tip Some of the fields on this page of the wizard might have been filled in automatically when you imported the application installation files.

Tip Requirements can help reduce the number of Configuration Manager collections you need. Tip To find out more about distribution points and content management in Configuration Manager, see Manage content and content infrastructure. Tip Remember that only Windows 11 computers will install the application because of the requirements that you selected earlier. Tip By setting the deployment purpose to Required , you make sure that the application is installed on PCs that meet the requirements that you set.