Windows Server 2019 support?

[arizvisa]

It looks like the younger version of this repository over at boxcutter/windows-ps has support for Windows Server 2019. It might be worth integrating it into this repository as well.

https://github.com/boxcutter/windows-ps/blob/master/win2019-eval.json

[boxcutter-robot]

It’s not ready yet. Still working on it. It will be changing radically soonish. The best approach to doing windows templates is to perform windows updates and so forth BEFORE the packer run, during sysprep. While you can do controlled reboots of windows under packer control it’s far from reliable. The automation is going to be changed accordingly.

…

On Jul 14, 2020, at 8:26 AM, Ali Rizvi-Santiago ***@***.***> wrote: It looks like the younger version of this repository over at boxcutter/windows-ps has support for Windows Server 2019. It might be worth integrating it into this repository as well. https://github.com/boxcutter/windows-ps/blob/master/win2019-eval.json <https://github.com/boxcutter/windows-ps/blob/master/win2019-eval.json> — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#248>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AC7FMA6DBSXMGPYHKBPLUD3R3R2LVANCNFSM4OZUFKMA>.

[arizvisa]

PR #250 contains some preliminary work on this issue.

Linking this issue to it...

[dragon788]

I wonder if Boxstarter.org is compatible with Windows 2019 as it has some nice Windows Update and reboot handling that can be triggered from the FirstBootCommand to keep the sysprep/Autounattend.xml file as generic and broadly applicable as possible.

[annawake]

ATM I’m leaning more towards automation that creates slipstream ISOs to incorporate into the sysprep rather that trying to make sysprep/Autounatted.xml generic. To me this seems the approach that will require the least maintenance, as itself could be packer-ized and combined together like Russian dolls. I’ve been down the path of trying to make FirstBootCommand/Autounattend.xml generic. This is where the Windows templates started out actually, but that also got complicated pretty fast, again because of the reboot handling and ordering. My thoughts now is that a more robust way to do this is to make a binary artifact ISO with all the installs in it, then slipstream that into sysprep. No controlled reboots required, two packer runs, one to create the slipstreamed ISO, the then next to run sysprep against the ISO. That’s what I’m noodling with at present.

…

On Jul 18, 2020, at 7:45 PM, dragon788 ***@***.***> wrote: I wonder if Boxstarter.org is compatible with Windows 2019 as it has some nice Windows Update and reboot handling that can be triggered from the FirstBootCommand to keep the sysprep/Autounattend.xml file as generic and broadly applicable as possible. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#248 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACSKXZFEXGXU2B2EXAKUXRDR4JM3VANCNFSM4OZUFKMA>.

[Fi6uDvGWucFv]

Considering the reference to the win2019-eval.json file in the boxcutter/windows-ps repository, it might be beneficial to analyze how the configuration is structured there for compatibility with the existing setup in this repository. Specifically, looking into how the provisioning steps differ for Windows Server 2019 might reveal necessary adjustments for integration.