Chris Long

It's definitely intermittent on Win10, at least with VMware Workstation ``` ==> win10: Machine booted and ready! ==> win10: Setting hostname... ==> win10: Waiting for machine to reboot... ==> win10:...

OK, I'll try to summarize where I think things are at: 1. The Win2016 box does not appear to have VMware tools installed at all. However, it's clear the installer...

OK, 1 isn't true either because I was just able to successfully provision DC without any issues and VMtools was present, which means this is problem is definitely intermittent (yay)

Ah, new theory! The machine boots up and does a login and reboot when it attempts to set the hostname. During that time, VMware tries to configure itself. If it's...

As an attempted workaround, I could try disabling synced folders, calling a powershell script inline to ensure vmware tools is installed correctly and then re-enabling it once that's complete. I'll...

Workaround doesn't work, pops up a dialog box about a previous failed installation of VMware Tools by SYSTEM. Only solution here is to somehow delay the reboot during the hostname...

@OlafHaalstra @coffeegist @tuedenn @n0leptr Are any of you able to reproduce this issue reliably? I totally believe it exists, I just need someone to help me test the fix if...

I'm working on a fix for this at the moment

Hi folks, there's more context here (https://github.com/clong/DetectionLab/issues/720) but the long story short is there's a race condition when the hostname is getting set. When the VM boots for the first...

This might be solvable by disabling the Vagrant hostname setting and just using powershell to do it via `Rename-Computer`