Upgrading to Windows 10 or upgrading an existing version of Windows 10 using Software Management Solution

book

Article ID: 178784

calendar_today

Updated On:

Products

Software Management Solution

Issue/Introduction

 

Resolution

Upgrading to Windows 10 or upgrading an existing version of Windows 10 using Software Management Solution
This article covers a process to upgrade a Windows 8 client to Windows 10 using Software Management Solution.
This same process can also be used to upgrade an existing Windows 10 version to a newer version.
Please note that not all environmental circumstances may have been seen during the processes, so you may experience other issues not covered here.

To obtain an ISO, please see: https://www.microsoft.com/en-us/software-download/windows10
You can determine if you need to use the media creation tool to build the .ISO file or go to the Volume Licensing Service Center if needing an Enterprise Edition.

The following process was used successfully to upgrade. Please pay attention to the notes as they cover important items to consider.

  1. Using a Windows 10 DVD or Windows 10 .iso file, extract the contents to a package repository folder that you will use as the source of your Package.
  2. If using ITMS version 8.1 or higher, compress the contents of the folder from inside the folder and give it any name
  3. In the Symantec Management Console, browse under Manage > Software.
  4. In the upper left pane, right-click in the white space and choose Import.

        

  1. In the selector dialog, browse to the folder you created. NOTE: do not only select the folder, but select all the files and folders before clicking OK. If on ITMS version 8.1, select the compressed file created above. It will then prompt you asking if you want to extract the archived content - choose yes.

        

  1. Under the Package Server tab be sure to stage your package as needed. Since the package is very large, having it on the appropriate Package Servers will save time.
  2. Click OK to import the Package.
  3. On the next screen, the default should be to create a New Software Resource. Check the box to Open the Software Resource upon creation.
  4. Under the Package tab, select the Command line and click Edit (pencil icon).
  5. There are several options to consider when generating the command-line for the upgrade. Note the following:
    • Command-line option 1:
      • "setup.exe" /Auto:Upgrade /showoobe none /DynamicUpdate Disable /Copylogs %SystemDrive%\ProgramData\temp
      • /Auto:Upgrade is vital to ensure this is an upgrade scenario.
      • The /Copylogs switch was used for testing, but can be used to provide data if an upgrade fails.
      • If properly configured, you can use the /Unattend:unattend.xml switch in order to provide an answer file to any prompts you may get.
    • Command-line option 2:
      • "setup.exe" /Auto:Upgrade
  6. Click OK to save the Command line, and click OK to save the Software Resource.
  7. Go under the Manage > Policies section (or click the Policies blade in the lower left-hand pane).
  8. Browse under Software, and right-click on the Managed Software Delivery (or custom folder) and choose New > Managed Software Delivery.
  9. Provide a Name, such as “Windows 10 Upgrade”.
  10. Under Policy Rules/Actions > Software, Click Add > Software.
  11. Choose the new Windows 10 component created previously.
  12. Double click on the name of the software package in the blue bar, go to the Rules tab, click * New, then create a detection rule like the following but appropriate to the version of Windows 10 being installed (double check this in the registry on a Windows 10 computer):

  1. The default Run As is the System Account. If this will not be sufficient in your environment, please change to Specified User under the Advanced options.
  2. Under the Applied to section, carefully target those systems to be upgraded.
  3. Under the Schedule section, use a Scheduled Time, do not have it repeat. NOTE: When you are done upgrading a client, remove that client from the policy to avoid any unintentional repeat run of the policy.

           

  1. Click Save changes to save the policy.

The policy is now ready. However this may not be all that is required. During my first run of the test, I got a prompt on the client that some software installed was not compatible with Windows 10. Run a test to find out if this will be the case for you and take any appropriate actions. Options include:
   •    Add Uninstall Software components before the upgrade to remove incompatible software.
   •    Use the unattend switch to choose what the upgrade should do in those circumstances (I am not sure what is supported with this option).
   •    Have someone available at the system to uninstall or skip what is not compatible.
This article may be updated as more is learned about Windows 10 upgrades.

Attachments

Upgrading a Windows 8 client to Windows 10.docx get_app