zlacker

>>kenton+(OP)
> The machines all boot off of a network drive based on this image. Each machine gets a copy-on-write overlay on top of the main image, so that guests can make changes to their machine which won't be seen by any other, and will be deleted at the end of the party.

How do you deal with Windows licensing/activation in that scenario? I didn't see anything in the Github repository, and I can't imagine that not being the worst PITA.

>>mschus+0E1
Just buy licenses once on each machine and Windows figures it out from then on. I guess it phones home when it sees a hardware change and the server says "yep that serial number is licensed".

At least, that's how it worked for me in Palo Alto. For some reason with the new setup Windows complains about activation after every reimage, until I click "troubleshoot activation", and then it phones home and figures it out? I need to debug this.