This article describes how to use Ivanti Patch Manager to upgrade to Windows 10 Creators Edition using Ivanti Patch Manager.

Windows 10 Creators Edition is also known as Windows 10 RS2 or Windows 10 1703.

Goal

Upgrade the clients to Windows 10 version 1703.

Steps

These steps use the LANDESK Patch and Compliance Manager definition called "W10V1703". A prerequisite for installing this version to a client computer is that the target computer must have 2GB of memory or higher.  If the client computer does not have 2GB of memory or higher it will be detected but it will not attempt to install the update.

1. Download or otherwise acquire the Windows 1703 media for the version of Windows that you are updating (Education, Professional, or Enterprise)
   
   This can be done by following the instructions in this link.
   
   If using a copy from MSDN this is likely an all-in-one image, only the product key changes the version.
   
   
2. Place this .ISO into the \ManagementSuite\LDLogon\Patch\ directory on your core server.  If you have changed the patch storage location, place it in the equivalent directories.
3. Open the Ivanti Endpoint Manager Console and go to the Security and Compliance Tool group
4. Open the Patch and Compliance Tool
5. Ensure that you have downloaded the latest updates in the Vulnerabilities category.
   
   
6. After downloading the vulnerabilities category, find the "W10V1703" definition.  This is the definition that we will be using to upgrade Windows.
   
   
   
   
7. Next, examine the properties of the definition by double-clicking it.
   
   

   You will notice that there is a list of rules in the definition.  You need to select the correct rule that matches the version of Windows you are trying to upgrade.

8. Note the following in the description tab of the definition:
   
   
9. Double-click the rule that matches the version of Windows you are trying to upgrade.  Be careful to choose the selectx86 or x64 version.
   
   
   
   
10. You will need to make sure that your .ISO file for the Windows upgrade matches exactly the filename within the rule in the Patch information section under Unique filename.  In order to do this highlight the filename and make sure to go all the way to the end just prior to ".ISO" and then press Ctrl-C to copy the file name except for the extension.
11. Right-click and rename your .ISO file from step 1 and paste in the name you just copied from the definition rule.  Make sure it still has the .iso extension and that it is not named ".iso.iso" or anything like that.  It must match exactly with the Unique Filename in the rule.
12. Run Download Updates one more time to ensure that the "Downloaded" Yes/No column in the rule is updated to "Yes".  If it does not update, check your storage location and the name of the .ISO to make sure it matches.
13. Run a scan and repair as usual.

How to block automatic update to the Creators Edition of Windows on client systems

In order to block Windows 10 systems from automatically installing Operating System Upgrades, the following methods may be used:

Group Policy

Computer Configuration / Administrative Templates / Windows Components / Windows Update Policy

Setting: Turn off the upgrade to the latest version of Windows through Windows Update

Registry

HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate

DWORD value: DisableOSUpgrade = 1

LANDESK Patch and Compliance Definition

The DISABLEWIN10UPGRADE can be sent as a repair job to turn off the Windows 10 auto-updates to newer OS versions.

This definition sets the Registry key listed above.