@george1421 Are you talking more about the client than simply deploying an image? Will 1709, without the client, still deploy just fine with the current stable version of FOG?

In regards to the other stuff: yeah, there are several bugs related to SetupComplete.cmd and cleanup of defaultuser0 in 1709. Some of the issues were (apparently) fixed in the January cumulative updates, but I know of at least one person who continued to have related issues even with the update applied.

SCCM administrators are having the exact same issues, mostly with Task Sequences, which use some of the same mechanisms to work.

@loosus456 They (M$) did something with disk structure, as well as other numerous changes under the hood. Some changes caused several rounds of rework to the fog client. I don’t have specifics, but based on some of the threads we’ve seen the issues started with 1709. I’d have to go back through the change log to pin point the fixes specifically related to 1709.

I think one from my testing was I had to move starting of the fog client from the setupcomplete.cmd to a first login step in the unattend.xml because the windows was doing some additional things after the setupcomplete.cmd. If the fog client was started too early (in the setupcomplete.cmd) I would end up with a botched install. This is different than all of the win10 releases before.

@foglalt Understand this is all subject to change, but I think the plan was RC13 to be the last before 1.5.0 stable was pushed out in a couple of weeks. Internal changes in Windows 10 1709 has caused unexpected delays with 1.5.0 being finalized. GUI performance improvements were pulled from 1.5.0 and moved into the 1.6.0 branch which should be released in the first half of 2018 (maybe).

Fog 2.0 IS a bit out there yet. The devs have said that they are seeing some pretty impressive deployment speeds with the pre-alpha code.