Thanks Paul. I’ll try out the bootstrap. I want to basically run and
install a whole bunch of installers and configure them so that my builds
can run on them. This includes things like .Net , IIS, SQL server and other
items. My problem was that though the environment variable had the chef
install path appended, it just wasn’t reflecting till I went there manually
and clicked them. I’ll try what you have recommended here , which is to
hardcode the path variable separately and see if that works.
On Mon, Dec 12, 2011 at 11:49 PM, Paul Morton - BIA
Currently we are not using the MSI (directly) to deploy chef. By and large
we are using the knife bootstrap wine, command with the windows
-chef-client-msi (Default Now)
The nice part about using the knife bootstrap command is that it takes
care of doing all of the additional setup including transferring your
validation cert and client configuration. Once you bootstrap the windows
server with knife, chef-client should run fine.
WRT the windows cookbook, are there particualr things that you are trying
On Dec 12, 2011, at 5:06 AM, Madhurranjan Mohaan wrote:
I am using the .msi chef client across a few nodes right now .We will
potentially be using this across 70 odd boxes . I am currently looking at
trying out the resources specified here ->
Wanted to know what others are currently using for the same.