sleep is not a built-in Windows command. This depends on Win2K3 resource kit. Suggest timeout be used instead.

[afilla]

chef/knife/lib/chef/knife/core/windows_bootstrap_context.rb

Line 376 in 8ab1377

@schtasks /create /f /sc once /st 00:00:00 /tn chefclientbootstraptask /ru SYSTEM /rl HIGHEST /tr \"cmd /c #{command} & sleep 2 & waitfor /s %computername% /si chefclientinstalldone\"

[afilla]

Suggest: @SCHTASKS /create /f /sc once /st 00:00:00 /tn chefclientbootstraptask /ru SYSTEM /rl HIGHEST /tr "cmd /c #{command} & timeout 2 & waitfor /s %computername% /si chefclientinstalldone"

[tpowell-progress]

@afilla Are you observing current breakage or just providing a suggestion of better practices? FWIW, I believe the sleep that is getting triggered might actually be from MSYS install with the ruby installer (git also includes a sleep of similar origin)

[afilla]

@tpowell-progress you are probably right. However, we are observing that when the Chef-Client is installed via the Windows Scheduled Task in the fallback function we are witnessing unpredictable behavior where we have two ruby processes running instead of a single ruby process. The first process locks the other up, preventing bootstrap.