Can the build of windows 10 be upgraded from 1511 to 1607 using bigfix?
We tried creating a software distribution package and editing the action script of the original fixlet as the original fixlet said BES MANUAL CACHING REQUIRED.
We deployed the created package and it executed successfully but there was no change in the build.
This was the script used:-
//SOFTWARE DISTRIBUTION PACKAGE
prefetch 18ff35b4c88771e343184a90b9c924cfdfdc336e sha1:18ff35b4c88771e343184a90b9c924cfdfdc336e size:4215273891 http://abc.companyname.com:52311/Uploads/18ff35b4c88771e343184a90b9c924cfdfdc336e/Win10_1607_English_x64.iso.tmp sha256:ecdac8a0d896121608d0f136c41d9a68f2238d291a6389210fe6532fc008fc2a
extract 18ff35b4c88771e343184a90b9c924cfdfdc336e
//wait __Download\Win10_1607_English_x64.iso
//ORIGINAL FIXLET
parameter “workISO” = "{pathname of client folder of current site & “__Download\Win10_1607_English_x64.iso”}"
continue if {exists file (parameter “workISO”)}
// prepare a workpath to temporary files.
parameter “workPath” = "{(value of variable “SystemDrive” of environment) & “\win10_upgrade_temp”}"
waithidden cmd /C rmdir /S /Q "{parameter “workPath”}"
waithidden cmd /C mkdir “{parameter “workPath”}”
// Create the cleanup file.
delete __appendfile
delete setupcomplete.cmd
appendfile @echo off
appendfile SET WindowsISO="{parameter “workISO”}“
appendfile powershell.exe “Dismount-DiskImage “”%WindowsISO%””"
appendfile rmdir /S /Q “{parameter “workPath”}”
move __appendfile setupcomplete.cmd
// Create a debug invocation batch to help in case of failures.
// This batch does not perform an update but with the scanonly option allows you to determine what the problem is.
delete __appendfile
appendfile @echo off
appendfile SET WindowsISO="{parameter “workISO”}“
appendfile FOR /F “skip=3” %%I IN ('powershell.exe “Get-DiskImage “””%WindowsISO%”"" | Get-Volume | Select-Object {{$_.DriveLetter}"’) DO %%I:\setup.exe /auto upgrade /Compat ScanOnly /DynamicUpdate disable /noreboot"
appendfile echo %errorlevel% > “{parameter “workPath”}\out.log”
move __appendfile “{(parameter “workPath”) & “/upgradeCheck.bat”}”
// Create the actual invocation script
// Sleep and Dir were added or command would fail with %errorlevel% 183. Possibly a delay on mount.
delete __appendfile
delete mount.and.install.bat
appendfile @echo on
appendfile SET WindowsISO="{parameter “workISO”}“
appendfile powershell.exe “Mount-DiskImage “”%WindowsISO%””“
appendfile TIMEOUT 10
appendfile FOR /F “skip=3” %%I IN ('powershell.exe “Get-DiskImage “””%WindowsISO%”"" | Get-Volume | Select-Object {{$_.DriveLetter}"’) DO dir %%I: > “{parameter “workPath”}\dir.log” && %%I:\setup.exe /auto upgrade /Quiet /DynamicUpdate disable /noreboot /postoobe "{pathname of client folder of current site & “\setupcomplete.cmd”}"
appendfile echo %errorlevel% > "{parameter “workPath”}\out.log"
move __appendfile mount.and.install.bat
wait mount.and.install.bat > “{parameter “workPath”}\cmd.log”
// setup must finish with RC=0 at this stage if things are ok. If that is not the case content of C:"\win10_upgrade_temp dir holds useful info.
// Apart from log files, you can run upgradeCheck manually to check with the UI what the problem is.
action requires restart “18ff35b4c88771e343184a90b9c924cfdfdc336e”