Step 2. On the Specify Application page, click the Browse button to find the application exe or shortcut (.lnk). Click Next.
Step 3. Wait for the application to start, and then close the application. The template generator will run in the background and detect where the
application stores its settings. After the application is closed, click the Next button to continue.
Step 4. On the Review Locations page, check the Registry and Files locations
that were detected. You can uncheck the boxes for any location you do not want to include in the synchronization. Click Next.
Step 5. On the Edit Template page, shown in Figure 18-26, you can review the location settings detected and modify them if needed. Click the Registry tab to see Registry locations, and the Files tab to view the files used for the application’s settings. When you are satisfied, click Create.
Step 6. Select a location and save your XML template file.
Figure 18-26. UE-V Settings Location Template Generator Tool
You should test your template before deploying it to the organization. If you need to make changes after testing, you can use the UE-V template generator to edit the template and save your changes.
You can deploy your template using SCCM, Group Policy, or using the UE- V settings template catalog, which is a share location you set up on the server when deploying UE-V for your organization. Templates deployed to the settings template catalog location are automatically updated by the UE-V service.
Note
For more information about UE-V, planning for deployment in an
organization, and details for server and client configurations, start with the article “User Experience Virtualization (UE-V) for Windows 10 Overview”
at https://technet.microsoft.com/en-us/itpro/windows/manage/uev-for- windows.
Using Microsoft Intune for Desktop Apps
In Chapter 13, “Microsoft Intune,” you learned how to use the Microsoft Intune cloud-based management tool as a Mobile Device Management (MDM) solution, as well as how to enroll devices and Windows computers.
You also learned about adding apps to Microsoft Intune and side-loading apps to configured devices.
For Windows 10 computers that you manage with Microsoft Intune and the Intune client, you can also manage desktop applications and deployment for your managed computers. The process is similar to deploying apps and deep linking apps, which you learned about in Chapter 13.
You can deploy applications that use Windows Installer (.exe or .msi files) by publishing the application files to Microsoft Intune. Publishing your
applications is the first step. The process is the same as publishing a UWP (.appx) application. To install applications on PCs, they must be capable of silent installation without user interaction. Apps that cannot perform silent installation on computers will fail.
Use the following steps to publish desktop apps to Intune.
Step 1. Log in to the Intune portal, select the Apps menu, and then select Apps from the submenu. All your current apps are displayed.
Step 2. Click the Add App link. This launches the Intune Software Publisher Wizard.
Step 3. On the Software Setup page, in the Select How This Software Is Made Available to Devices box, select Software Installer. For the Select the Software Installer File Type, select Windows Installer. Click the Browse button and select the application setup file. If other files in the folder are required, check the Include Additional Files and Folders from the Same
Folder check box. Click Next.
Step 4. On the next page, enter the publisher in the Publisher box, if it is not filled in automatically. You can optionally select an image to use for the application’s icon. Click Next.
Step 5. On the Requirements page, you must select an architecture (32-bit or 64-bit) and an operating system if the application has minimum Windows version requirements. Select Any for these fields if the software runs on any version. Click Next.
Step 6. On the Detection rules page, you can tell Intune how it can tell if the software is already installed on a computer. This is useful for automatic deployment. Choose from either Default Detection Rules or add your own detection rule. You can add a rule based on whether a specific file exists, a Registry key, or an MSI product code, as shown in Figure 18-27. Click Next.
Figure 18-27. Selecting Software Detection Tools in the Intune Software Publishing Wizard
Step 7. If the application installer needs any command-line arguments when it runs, you can provide them on the Command-Line Arguments page. If it does not, select No. If it does, select Yes and enter the arguments in the box provided. For instance, if the application is an .msi, you can add the /s
parameter so that it will install silently.
Step 8. The Return Codes pages allows you to select return codes to
determine whether the installation was successful. Enter any return codes you want Intune to evaluate during the installation, or select No and then click Next.
Step 9. Review the Summary page to make sure all your selections are
correct, and then click the Upload button to upload your application installer to Intune.
After the upload of your application setup program is complete, the
application appears in the list of apps on the Intune portal. The next step is to make your desktop application available for users to install. From the Intune portal list of apps, select the new application and click the Manage
Deployment link to get started.
You can select the user groups that will be allowed to install the software, or select from device groups where you want the software deployed. You can use any combination of user and device groups for the deployment. When you click Next, you can select the Deployment Action for the groups you selected. For devices, you can only select Required Install. That means that Intune will automatically download the installer and install the application on those devices. For user groups, you can select Required Install or Available Install.
If you simply want to make the application available for users to download and install when they need it, you can select Available Install for the user group. Recall from Chapter 13 that user groups are managed in Azure AD.
When you are finished with your selections, click the Finish button on the Manage Deployment Wizard.
Users can access the Microsoft Intune Center from the Windows 10 system tray icon, and click the Get Applications from the Company Portal link.
The link will bring up the default browser so that the user can access the portal. After logging in, the user can view the apps available, as shown in Figure 18-28. Applications the user selects to install will be installed silently on the local computer.
Figure 18-28. User Installation of Desktop Applications That You Make Available in the Microsoft Intune Portal
Note
For more information on installing desktop applications in Microsoft Intune, see “Add Apps for Windows PCs That Run the Intune Software Client” at https://docs.microsoft.com/en-us/intune/deploy-use/add-apps-for-windows- pcs-in-microsoft-intune.
Exam Preparation Tasks Review All the Key Topics
Review the most important topics in the chapter, noted with the Key Topics icon in the outer margin of the page. Table 18-8 lists a reference of these key topics and the page numbers on which each is found.
Table 18-8. Key Topics for Chapter 18
Key Topic
Element Description Page
Number
Figure 18- 1
Enable or disable the fast startup option in Control Panel
Figure 18- 2
The startup tab of the Task Manager details view allows you to view and manage startup applications
Figure 18-
4 Assigning user roles in Windows Store for Business
Step List Managing global rules for Store for Business using Azure AD
Figure 18- 12
The Compatibility Administrator helps you to
configure compatibility settings for older programs.
List File types used with Windows Installer
List Describes available methods of software deployment using Group Policy
List Describes types of actions you can perform using Msiexec.exe
Figure 18- 17
Shows you how to set up default file types and protocols to be opened by a program
Figure 18- 18
Shows you how to select file extensions to be opened by a program by default
Figure 18- Selecting a default program to be used with a specific
20 file extension
Table 18-5 Application Compatibility Options
Figure 18- 23
Manage App-V applications from the App-V client management console
Table 18-6 PowerShell commands for managing App-V clients
Table 18-7 Components of UE-V
Figure 18-
24 UE-V Group Policies
Step List Publishing an application to Microsoft Intune
Complete the Tables and Lists from Memory
Print a copy of Appendix B, “Memory Tables” (found on the book website), or at least the section for this chapter, and complete the tables and lists from memory. Appendix C, “Memory Tables Answer Key,” also on the website, includes completed tables and lists to check your work.
Definitions of Key Terms
Define the following key terms from this chapter, and check your answers in the glossary.
application compatibility, Application Compatibility Manager, Application Compatibility Toolkit (ACT), App-V, Assessment and Deployment Kit
(ADK), default program, fast startup, .msi file, .msp file, .mst file, online licensing, offline licensing, private store, settings location template, shim, UE-V, Windows Store for Business