We have upgraded to MDT 8456 (w/ADK 1903) and have started testing Win10 1909 in OSD. I have noticed that some task sequence steps which utilize a command prompt (Run Command Line) fail with exit code 1 and stop the task sequence.
For example, we have a step which creates C:\Temp and is set to continue on error. (cmd /c winrm quickconfig -quiet) When we image with 1809 or 1909 this step fails with exit code 1 - incorrect function - and the task sequence stops when that folder already exists.
Another step enables Remote Management (cmd /c winrm quickconfig -quiet). This step also dies with exit code 1 and stops the task sequence.
These steps work fine when imaging with Win10 1803 and other Run Command Line steps work fine such as those setting registry keys with reg.exe work without problem with 1809 and 1909.
Is there something in the newer OSes that throws MDT for a loop with certain command prompt commands?
Skip