Windows 11 IoT Enterprise LTSC 2024 Upgrade Guide

Deploying Windows 11 IoT Enterprise LTSC 2024 Upgrade Kit file using WMS

This chapter details the steps to remotely deploy the latest Windows 11 IoT Enterprise LTSC 2024 Upgrade Kit to devices registered with WMS, enabling the upgrade to Windows 11 IoT Enterprise LTSC 2024.

1. Log in to WMS as an administrator.
2. Go to Apps & Data > App Policies > Thin Client.
3. Click Add Advanced Policy.
   The Add Advanced App Policy page is displayed.
4. Enter the Policy Name.
5. From the Group drop-down list, select one or more groups to which you want to deploy the application.
6. Select the Include All Subgroups checkbox to apply the policy to subgroups.
7. From the Task drop-down list, select Install Application.
8. From the OS Type drop-down list, select Windows IoT Enterprise.
9. Select the Filter files based on extensions checkbox to filter the applications. If you select this option, only the applications that are associated with the selected operating system type are displayed.
10. From the Filter Devices drop-down list, select one of the following options:
    • Apply On All Devices: To apply the policy to all devices.
    • Filter already updated devices: To prevent previously deployed applications using WMS from being redeployed.
    • Filter devices with policy already applied: To exclude devices that have already received the same policy from the new application.
11. Click Add app.
    1. Select the package containing the latest Windows 11 IoT Enterprise LTSC 2024 Upgrade Kit from the Apps (Applied in the order shown.) drop-down menu.
    2. Enter --silent to set the Install Parameters for silent installation.
    3. Enter a value for Install Timeout. Allowed values range from 5 to 360 minutes, with a default value is of 60 minutes to support silent installations and safe exits.

    

12. Select Enable app dependency to stop the application policy at first failure.
13. From the OS Subtype Filter, select WIE10 (Windows 10 IoT Enterprise).
14. From the Platform Filter, select the device model to which you want to deploy the application.
15. In the Timeout field, enter the number of minutes the message dialog box should be displayed on the device. It allows the users to save work before the installation begins.
16. To enable delay in the implementation of the policy for the user, select the Allow delay of policy execution checkbox. If this option is selected, the following drop-down menus are enabled:
    • From the Max Hours per Delay drop-down list, select the maximum hours (1–24 hours) to delay the policy execution.
    • From the Max delays drop-down list, select the number of times (1–3) you can delay running the policy.
17. From the Apply Policy Automatically drop-down list, select any of the following options:
    • Do not apply automatically—This option does not apply a policy automatically to the devices.
    • Apply the policy to new devices—This option automatically applies the policy to a registered device. It applies the policy to devices that belong to the selected group or to devices moved to the selected group. When this option is selected, the policy is applied to all the new devices that are registered to the group. To run the job on the existing devices present in the group, you must schedule the policy. After you schedule the policy, the job status displays the count of devices that are already present in the group. The job status of the newly added device count that is registered is not displayed.
    • Apply the policy to devices on check in—This option is automatically applied to the device at check-in. When this option is selected, the policy is applied to all the devices present in the group. To run the job on existing devices present in the group immediately or at a scheduled time before the device check-in, you must schedule the policy. After you schedule the policy, the job status displays the count of devices that are already present in the group.
18. Select the Skip write filter check checkbox if you want to skip the write filter cycles.
    The option is applied only if the policy is applied using a job.
19. Click Save.
    An Alert window is displayed.
20. Click Later to exit. If you select Yes, then an App Policy Job window is displayed.

    
    
    

21. In the App Policy Job window, select the Policy.
22. Enter the description for the job.
23. From the Run drop-down list, select any of the following options:
    • Immediately
    • On selected time zone and date/time
    • On selected date/time(of device time zone)
24. Select the Exclude Offline Devices if you want to exclude the offline devices while creating the job.
    You can view the list of excluded offline devices on the Jobs page. You can later restart the job for the offline devices from the jobs list.
25. Select the time zone if you have selected On selected time zone and date/time in Step 23.
26. Enter or select the following details if you have selected On selected time zone and date/time or On selected date/time(of device time zone) in Step 23:
    • Effective—Enter the starting and ending date.
    • Start between—Enter the starting and ending time.
    • On day(s)—Select the days of the week.
27. Click the Preview option to view the details of the scheduled job.
    The job schedule preview is displayed.
28. Click the Schedule option to initiate the job.
29. Go to Jobs and filter by Configuration Groups to check the application policy job status for devices.
    When a WindowsUpgradeKit.exe job policy from WMS is applied as per the schedule, a Wyse Device Agent: Software Update Alert window is displayed on the devices.

    

    The implementation of the policy on device can be postponed based on displayed configurations. The options available include selecting a time to postpone the update, applying the update immediately, applying it later, or applying it upon rebooting the device.