Roger H

Switching over to the new autoname-wpfx= seems to work just fine, so.. there's a viable workaround :)

<duplicate deleted=""></duplicate>

Might have just been timing... my suspicion, and I need to poke around some more to confirm, is that the name is pulling from the dns cache somehow. What mechanism do you use for autohostname??

Might have just been timing... my suspicion, and I need to poke around some more to confirm, is that the name is pulling from the dns cache somehow. What mechanism do you use for autohostname??

The autoclone is back to writing localhost.localdomain.mshome.net too.. weird

Well.. not sure what exactly happened in there, but after I rebuilt the source image with the new Ubuntu based image, my autoclone is behaving nicely again.

Well.. not sure what exactly happened in there, but after I rebuilt the source image with the new Ubuntu based image, my autoclone is behaving nicely again.

Hi All, I've been running a custom config for a couple years now, which writes out the image "automagically" from the start menu. Last week I started getting this error: "The input device [tpl-w10-2004.mshome.net-2021-03-18-1601-img] does NOT exist in this machine!" "We will not save this device [tpl-w10-2004.mshome.net-2021-03-18-1601-img] !" The command being issued and the error: "ocs-sr -q2 -j2 -z9p -i 4096 -sfsck -senc -p choose savedisk autohostname sda" finished with error! I tried running...