The realities of Windows installations require that we reboot several times before finishing.
windev conceptually operates autonomously from a Chef server as a single Chef client invocation, so restarting the run is a complicated issue.
windev::chef_auto allows us to work around this problem: It registers "CHEF_SCRIPT CHEF_CONFIG" as a startup script, where CHEF_SCRIPT and CHEF_CONFIG environment variables.
(To do this it needs to do a lot more stuff: create an admin user, set auto login, register the script etc.)
The realities of Windows installations require that we reboot several times before finishing.
windev conceptually operates autonomously from a Chef server as a single Chef client invocation, so restarting the run is a complicated issue.
windev::chef_auto allows us to work around this problem: It registers "CHEF_SCRIPT CHEF_CONFIG" as a startup script, where CHEF_SCRIPT and CHEF_CONFIG environment variables.
(To do this it needs to do a lot more stuff: create an admin user, set auto login, register the script etc.)