4 of 4 people found this helpful
Taken from KB #17447 article (Issue and Resolution)
1. Please use the OS Installation wizard (not the os installation set wizard)
Note: at the moment the Windows 10 preview sources are not recognized by HEAT DSM 2015.1. After you finished the wizard you can copy the sources manually into the project extern$ directory of the os setup file package manually.
2. Microsoft sometimes change the name of the Windows 10 image. You can change the name manually in the OS configuration package. Therefore you can get the info out of the install.wim with tools like "imagex" or "dism" and enter the name as a new option value in the installation parameter "edition" of the os configuration package. You should set the value "as default".
Note: The OS recognition doesn´t work correctly (as Windows 10 is currently only available as preview version). So it´s important that you flag all packages assigned to the Win 10 client for Windows 10 and Windows 8.1!
...or wait for DSM 2015.2.1
1 of 1 people found this helpful
Well, the main question is always the same when talking about packaging: "How would I do it manually?"
In this case, it sounds rather easy:
- Insert Windows 10 November DVD or ISO
- launch setup while Windows is active
Transferring this into DSM this would basically result in:
- create a new escript package
- copy the entire DVD into the package directory (subfolder named Extern$)
- add a command like Executex that calls ".\Extern$\setup.exe /auto upgrade" and check for errors after the command execution
- you might want so set the platforms of the package to Win10 only
- assign the package
- execute the NIInst32 on the client or wait for the polling interval
My little test script looks like this:
ExecuteEx('.\Extern$\setup.exe /auto upgrade','ReturnCode','120') running in UserContext, service-executed
If not %ReturnCode%='0'
ExitProcEx(Failed,'The execution of %CurrentPackage.Object.Name% failed with Error Code %ReturnCode%')
This script appears to work pretty fine.
In a productive environment I would add some reboot control or ask the enduser for permission before upgrading :-)
Remaining issue is, that due to the fact that the setup process reboots the computer several times, no ReturnCode will be available and - much more important - the policy instance will remain pending restarting the installation with the next installer execution.
So I will most likely add a registry key before running the setup and check this key for existance at the top of the script end then exit. Or I could check for existance of the "Windows.old" folder... or... or... or...