Client Management Suite

Expand all | Collapse all

Upgrade to 1909 using Software Management

  • 1.  Upgrade to 1909 using Software Management

    Posted 06-23-2020 03:55 AM
    Hello All,

    I would like to ask if someone has been able to apply the W10 build version 1909 using Software Management instead Patch Management, as was feasible with previous versions to 1809 (with 1809 we already had issues being unable to do it).

    For us it would be very useful because we need to apply the corresponding Language pack once the upgrade has been applied (we have more than 50 different countries), and additionally one KB that fix the issue with Search bar. We would prepare a job to install the three modules as a software.

    Thanks in advance for your help.

  • 2.  RE: Upgrade to 1909 using Software Management

    Posted 06-25-2020 06:01 PM
    Hi, Pablo,
    At some point I was asked to upgrade to Windows 10 build 1909, the procedure was done using software management:
    1.- Obtain the ISO of Windows 10 Build 1909.
    2.- Already with ISO I passed it to the Altiris (NS) server
    3.- Mount the ISO in the NS to view the folders and files.
    4.- Create folders in Add or Edit Package within the console and add all the files selecting as main Setup.exe (It is a laborious process)
    5.- At first instance just check that the package will be stored only on the default internet site.
    6.- As you create the folders and add all the files in the corresponding folder, add the following command line: C: \ TEMP \ setup.exe / auto upgrade / quiet (When creating the software deployment task configure to store in C: \ TEMP so that it does not conflict with the command line)
    7.- Once the update was validated on 5 computers, the software package was enabled on the different site servers one by one for and bandwidth control was established so as not to affect the network (The site servers must have with the role of package server).
    Note: Keep in mind that the site servers to download the packages take
    Note 2: In the same way when clients download the files it takes longer since they usually turn off their computer, however, when you turn on that computer, it resumes the download from where it stayed and does not start from the beginning
    Note 3: Keep in mind that when you start the silent installation, the computer will restart several times, so if it is in use and the files are not saved, information could be lost

    Industrial Solutions de México S.A. de C.V.

  • 3.  RE: Upgrade to 1909 using Software Management

    Posted 06-25-2020 10:23 PM
    A quick note on our experiences with feature updates in this way: we've found that the likelihood of the update throwing an error and rolling back to the starting OS version seems to increase with the age of the installer source compared to the patch level of the OS being upgraded - that is, a machine running quality and security updates released *after* the install source's patch level is increasingly unlikely to see a successful feature update using that install source as later patches are applied to the client's OS. The update error is usually presented as some generic catch-all failure code for which Microsoft's advice is, typically, less-than-helpful.

    As a result, we had to continually slipstream the most recent monthly updates into install.wim (reasonably straightforward) and allow the changes to replicate to all our remote package libraries. Doing so significantly reduced our failure rate.

    Apologies for going slightly off-topic. Hopefully it'll save people some time and tension headaches when diagnosing inexplicable upgrade failures.

  • 4.  RE: Upgrade to 1909 using Software Management

    Posted 25 days ago
    Thanks a lot @deemacgee and @jesus eduardo carbajal ledezma for your help​. We tried and worked fine. IS true that with old versions like 1809 it didnt work and I think that during wim build process we always used the most recen patches installed (at least the security ones), but is a good think to be taken into in account for next times.

    Thanks again for your valuable help.​​