ITMS Administrator Group

Expand all | Collapse all

SBSP-Windows10_1803

Jump to Best Answer
  • 1.  SBSP-Windows10_1803

    Posted 05-08-2018 04:17 AM

    Does anyone has some inside information when the Windows 10 Feature Update 1803 is available in Patch Management?
     



  • 2.  RE: SBSP-Windows10_1803

    Posted 05-09-2018 11:43 AM

    spritchet,

    Windows 10 feature updates are not like other patches.  You must manually download the ISO from MS and add it to the package.  Instructions here:  https://support.symantec.com/en_US/article.DOC9422.html

    Joe



  • 3.  RE: SBSP-Windows10_1803

    Posted 05-11-2018 04:46 AM

    Works fine for us. 

    At least after I managed to download the right language ISO from MS. 

    "International English" is not the same as "English" apparently :-)



  • 4.  RE: SBSP-Windows10_1803

    Posted 05-11-2018 02:42 AM

    There must be a mistake with 1803. Previous version no issue.



  • 5.  RE: SBSP-Windows10_1803

    Posted 05-11-2018 02:43 AM

    Same here. Not working like previous versions.



  • 6.  RE: SBSP-Windows10_1803
    Best Answer

    Posted 05-08-2018 07:11 AM

    Hi Stefan,

     

    I see SEP already supports Windows 10 FU 1803, so I could only assume that PMS would also support it soon, if not already.

    Symantec don't publish a roadmap for support unfortunately.

    Thanks!



  • 7.  RE: SBSP-Windows10_1803

    Posted 05-09-2018 04:13 AM

    Cool. Just downloaded it...



  • 8.  RE: SBSP-Windows10_1803

    Posted 05-11-2018 03:45 AM

    I noticed the difference as well. However, I just started the update and it seems to go through fine...

    Seems like the update process has slighty changed as I can see differences in the log files as well.



  • 9.  RE: SBSP-Windows10_1803
    Best Answer

    Posted 05-08-2018 02:25 PM

    Run your PMImport again. Ours runs at 6 AM EDT and I see it as available today.



  • 10.  RE: SBSP-Windows10_1803

    Posted 05-10-2018 12:06 PM

    We just attempted to deploy the 1803 update to a couple of 1709 systems and get an exit code of 193. We ran the PMImport this morning at 4:30am PDT. Comparing the batch files and command lines used for the 1709 and 1803 packages, they are vastly different. The 1803 package does not work.

    Package command lines:

    1709:  Windows10x64HomeN1709.bat

    1803:  swuenv.bat && call "%InstallToolsPath_832C527C-B9C9-46FB-B1F1-2F35434FF90D%\AeXPatchDeployment.exe" -DeploymentId=00001ce4-0001-0000-0000-000000000000 -LanguageGroup=1

     

    The 1709 batch file is extensively configured while the 1803 has the handful of lines referenced in the earlier post.



  • 11.  RE: SBSP-Windows10_1803

    Posted 05-11-2018 12:10 PM

    We may have resolved the issue by shortening the file name of the iso. We has been using the file as named by Microsoft in the Volume Licensing portal.

    Original name:  SW_DVD5_Win_Pro_Ent_Edu_N_10_1803_64BIT_English_-2_MLF_X21-79647.ISO

    Renamed file:  Windows10x64Enterprise1803.ISO

    I will update the post if the upgrade is successful.



  • 12.  RE: SBSP-Windows10_1803

    Posted 05-11-2018 12:45 PM

    The rename of the file has now resulted in a successful upgrade. We are good to go.



  • 13.  RE: SBSP-Windows10_1803

    Broadcom Employee
    Posted 06-11-2018 06:20 AM

    It does work as before, but with a subtle differences.

    As mentioned above the command line is changed, and looks like normal patch command lines.

    This is hiding what is actually happening, which is that the patch files are created in "%programdata%\symantec\patch\InstallationSandbox#date and time" and a batch file called Windows10x64Professional1803.iso_install.bat is running - the contents of which are remarkably similar the the batch file used in previous feature updates.

     

    Question is where is it and how would I modify this batch file if I needed to on NS?

     



  • 14.  RE: SBSP-Windows10_1803

    Posted 05-09-2018 11:04 AM

    Odd, when I downloaded it the batch file basically just has some Echo commands in it, for all the varioius versions, like this.  Than

    Thanks

    @echo off
    Setlocal

    set iso_name=%~n0.iso

    if exist %~dp0\%iso_name% (
        echo Deployment image %iso_name% found
    ) else (
        echo Expected deployment image %iso_name%
        echo https://support.symantec.com/en_US/article.DOC9422.html
    )