Environment Resource: sets windows environment variables
User
Group
Mount
File
Gem Package
Remote File
Cookbook File
Template
Service
Ruby Block
Execute
也就是说，这些是 Chef 本身包含的资源。由于 Chef 可通过说明书进行扩展，因此可以通过各种特定于 Windows 的说明书添加更多资源。请继续阅读以了解更多信息。
Chef is supported on Windows by Opscode. While we don't run Windows for any of our infrastructure, we do have developers who are continually improving our Windows support. We also get community contributions, and most of the early phase Windows functionality for Chef was contributed by the community.
While we have a lot of Unix/Linux background across our teams, our intention is that Windows is treated as a first class citizen. 2012 will be a big year for Chef and Windows. Keep an eye on the Opscode blog for announcements.
Environment Resource: sets windows environment variables
User
Group
Mount
File
Gem Package
Remote File
Cookbook File
Template
Service
Ruby Block
Execute
That is, these are resources included in Chef itself. As Chef is extensible with cookbooks, many more resources are added through a variety of Windows specific cookbooks. Read on for more information.
You can get started with using Chef and Windows here:
Documentation is available in the README.md included in the cookbook tarball.
Additional cookbooks for installing 7-zip, managing IIS and SQL Server have been added. Our "database" cookbook has been extended with a resource/provider for managing SQL Server databases and users (with the tds rubygem).
The knife-windows plugin for knife adds functionality for interacting with Windows systems to provision them with Chef installation.
Cfengine Nova has had stable native support for Windows for years (i.e. no Cygwin is needed).
Everything that is possible on Unix (e.g. run commands, file copy, file edit, etc.) can also be done on Windows, with addition to Windows-specific features like
Registry management
File ACL permissions
Windows service management
Event log support
Advanced OS discovery (version, arch, service pack, network, domain, etc.)
Having had a deal of experience here i think that it really depends what you need to manage on a given box. Find your most common use case and ask a more specific question in terms of: whats the best tool for managing that. Things like IIS can be tricky (on older windows builds at least) and finding modules for CM tools to manage things like IIS settings and app pools can be hit and miss - especially when it comes to advanced settings (worker thready recycling springs to mind)
However Puppet has forge modules for more basic IIS settings which largely worked for me - and i really like the declarative format here - especially if you are managing large numbers of IIS servers
Also one of the major issues with Windows and configuration management is the lack of a proper package management solution - what actually comes in really handy here is something called Chocolatey (see http://chocolatey.org/) there is a plugin to use this as a provider in puppet - making the whole management process particularly easy. However i imagine that this can be integrated with other CM tools aswell - but does a great deal to help with installing software automatically in a windows environment
Though it is worth stating that whatever you end up using you will have to spend a while figuring out some odd bugs - windows and scripting/automation is not the best.
我不推荐 Chef，除非您是了解 ruby 的软件开发人员。 Chef 专为想要管理 IT 基础设施的软件开发人员而设计。不适合真正最终管理它的系统运营人员。它试图将 IT 基础设施视为代码，这与其实际工作方式相反，更像是数据。
恕我直言，Puppet 对于 SysOps 人员来说更友好，但仍然可能很复杂。
好消息是还有其他选择。对于 Windows 来说情况不太如此，但像 Puppet 这样的项目确实很好地支持它。
I don't recommend Chef unless you are a software developer who knows ruby. Chef is designed for software developers who want to manage IT infrastructure. Not for SysOps people who are the ones that actually end up managing it. It tries to treat IT infrastructure like code which is counter intuitive to how it actually works which is more like just data.
Puppet is more friendly for SysOps people imho but still can be complicated.
The good news is that there are other options as well. Less so for windows but projects like Puppet do support it reasonably well.
发布评论
评论（7）
Opscode 在 Windows 上支持 Chef。虽然我们的任何基础设施都不运行 Windows，但我们确实有开发人员在不断改进我们的 Windows 支持。我们还得到了社区的贡献，Chef 的大部分早期 Windows 功能都是由社区贡献的。
重要：Opscode现在为 Windows 上的 Chef 提供 MSI 安装程序。这使得在 Windows 上安装 Chef 和 Ruby 变得比以往更容易。
虽然我们的团队有很多 Unix/Linux 背景，但我们的目的是 Windows 被视为一等公民。 2012 年对于 Chef 和 Windows 来说将是重要的一年。请密切关注 Opscode 博客以获取公告。
以下 Chef 资源 适用于 Windows：
也就是说，这些是 Chef 本身包含的资源。由于 Chef 可通过说明书进行扩展，因此可以通过各种特定于 Windows 的说明书添加更多资源。请继续阅读以了解更多信息。
您可以在此处开始使用 Chef 和 Windows：
最初，Doug MacEchern 也编写了一些食谱来实现 Windows 自动化。
此信息及更多信息可在 Chef Wiki 上找到：
更新
以下说明书向 Chef 添加了新资源以管理 Windows：
这是对 Doug 上面链接的存储库中的优质资源的更新/重写。文档可在 Chef Wiki 上找到。
以下食谱部署 PowerShell 并提供直接在 Chef Recipes 中运行 PowerShell 命令/脚本的资源：
文档可在食谱 tarball 中包含的 README.md 中找到。
用于安装 7-zip、管理 IIS 和 SQL Server 已添加。我们的“数据库”说明书已通过用于管理 SQL Server 数据库和用户的资源/提供程序进行了扩展（与
tdsrubygem）。Knife 的 knife-windows 插件添加了与 Windows 系统交互的功能，以便为它们提供 Chef 安装。
更新：我们现已向 Chef 添加了Windows 的文件 ACL 支持 ，对于所有常见的文件/目录嫌疑人。
Chef is supported on Windows by Opscode. While we don't run Windows for any of our infrastructure, we do have developers who are continually improving our Windows support. We also get community contributions, and most of the early phase Windows functionality for Chef was contributed by the community.
Important: Opscode now provides an MSI installer for Chef on Windows. This makes it easier than ever to get Chef and Ruby installed on Windows.
While we have a lot of Unix/Linux background across our teams, our intention is that Windows is treated as a first class citizen. 2012 will be a big year for Chef and Windows. Keep an eye on the Opscode blog for announcements.
The following Chef Resources work on Windows:
That is, these are resources included in Chef itself. As Chef is extensible with cookbooks, many more resources are added through a variety of Windows specific cookbooks. Read on for more information.
You can get started with using Chef and Windows here:
Originally, Doug MacEchern wrote some cookbooks to do a number of things to automate windows, too.
This information and more available on the Chef Wiki:
Update
The following cookbook adds new resources to Chef to manage Windows:
It is an update/rewrite of Doug's fine resources from his repository linked above. Documentation is available on the Chef Wiki.
The following cookbook deploys PowerShell and provides a resource to run PowerShell commands/scripts directly in Chef Recipes:
Documentation is available in the README.md included in the cookbook tarball.
Additional cookbooks for installing 7-zip, managing IIS and SQL Server have been added. Our "database" cookbook has been extended with a resource/provider for managing SQL Server databases and users (with the
tdsrubygem).The knife-windows plugin for knife adds functionality for interacting with Windows systems to provision them with Chef installation.
Update: We have now added File ACL support for Windows to Chef, for all the usual file/directory suspects.
Cfengine Nova 多年来一直对 Windows 提供稳定的本机支持（即不需要 Cygwin）。
Unix 上可能的一切（例如运行命令、文件复制、文件编辑等）也可以在 Windows 上完成，此外还有 Windows 特定的功能，如
有关简短介绍，请参阅 Nova 补充手册的第 11 节： http://cfengine.com/files/Nova_Supplement.pdf
Cfengine Nova has had stable native support for Windows for years (i.e. no Cygwin is needed).
Everything that is possible on Unix (e.g. run commands, file copy, file edit, etc.) can also be done on Windows, with addition to Windows-specific features like
For a short introduction, look in Section 11 of the Nova supplement manual: http://cfengine.com/files/Nova_Supplement.pdf
我一直在寻找完全相同的东西。
我遇到了 Windows PowerShell Desired State Configuration ，它声称可以执行许多操作您希望使用 Chef/Puppet 完成的 CM 任务。
我不会对此发表任何意见，因为我还处于评估阶段 - 但如果您仍在寻找某些东西，请尝试一下。
I have been looking for exactly the same thing.
I ran across Windows PowerShell Desired State Configuration which purports to do many of the CM tasks you'd want to do with Chef/Puppet.
I am not going to give any opinion on it because I am still early in evaluating it - but if you're still looking for something, give this a shot.
在这里有了丰富的经验，我认为这实际上取决于您需要在给定的盒子上管理什么。找到您最常见的用例，并提出一个更具体的问题：管理该用例的最佳工具是什么。像 IIS 这样的东西可能很棘手（至少在较旧的 Windows 版本上），并且寻找 CM 工具的模块来管理 IIS 设置和应用程序池等东西可能会碰运气 - 特别是当涉及到高级设置时（我会想到工作线程回收）
然而，Puppet 有用于更基本 IIS 设置的锻造模块，这在很大程度上对我有用 - 我真的很喜欢这里的声明式格式 - 特别是如果您管理大量 IIS 服务器
另外，Windows 和配置管理的主要问题之一是缺乏一个合适的包管理解决方案 - 这里真正有用的是名为 Chocolatey 的东西（参见 http://chocolatey.org/) 有一个插件可以将其用作 puppet 中的提供者 - 使整个管理过程特别容易。然而，我认为这也可以与其他 CM 工具集成 - 但对于在 Windows 环境中自动安装软件有很大帮助，
尽管值得一提的是，无论您最终使用什么，您都必须花一些时间来弄清楚一些奇怪的错误 - 窗口和脚本/自动化不是最好的。
Having had a deal of experience here i think that it really depends what you need to manage on a given box. Find your most common use case and ask a more specific question in terms of: whats the best tool for managing that. Things like IIS can be tricky (on older windows builds at least) and finding modules for CM tools to manage things like IIS settings and app pools can be hit and miss - especially when it comes to advanced settings (worker thready recycling springs to mind)
However Puppet has forge modules for more basic IIS settings which largely worked for me - and i really like the declarative format here - especially if you are managing large numbers of IIS servers
Also one of the major issues with Windows and configuration management is the lack of a proper package management solution - what actually comes in really handy here is something called Chocolatey (see http://chocolatey.org/) there is a plugin to use this as a provider in puppet - making the whole management process particularly easy. However i imagine that this can be integrated with other CM tools aswell - but does a great deal to help with installing software automatically in a windows environment
Though it is worth stating that whatever you end up using you will have to spend a while figuring out some odd bugs - windows and scripting/automation is not the best.
根据我的经验，我很高兴使用这样的工具集：
使用 powershell 来管理 Windows 配置。如果只有windows服务器，可以远程执行ps脚本。
如果您愿意，建议使用 Puppet 或 Chef 将您的 powershell 脚本分发到客户端。
如果您愿意，建议使用 cygwin + (windows sshd) + crond 来管理在 Windows 中运行的类似 shell 的脚本。
Based on my experience, I am glad to use such toolset:
Use powershell to manage the windows configuration. If only windows server, you can remotely execute the ps script.
If you like, suggest to use Puppet or Chef to distribute your powershell script into client.
If you like, suggest to use cygwin + (windows sshd) + crond to manage the shell-likely scripts which run in windows.
我认为如果您可以使用 Microsoft System Center 会更好。
它是 Microsoft 的解决方案，用于管理从桌面到服务器等所有 Microsoft 基础产品。应该尝试一下...
如何在配置管理器中部署应用程序
< a href="http://technet.microsoft.com/en-us/library/gg699393.aspx" rel="nofollow">在 System Center 2012 中部署软件和操作系统
I think its better if you can use Microsoft System Center.
It a solution from the Microsoft to manage Microsoft base products form desktops to servers and all. Should give a try ...
How to Deploy Applications in Configuration Manager
Deploying Software and Operating Systems in System Center 2012
我不推荐 Chef，除非您是了解 ruby 的软件开发人员。 Chef 专为想要管理 IT 基础设施的软件开发人员而设计。不适合真正最终管理它的系统运营人员。它试图将 IT 基础设施视为代码，这与其实际工作方式相反，更像是数据。
恕我直言，Puppet 对于 SysOps 人员来说更友好，但仍然可能很复杂。
好消息是还有其他选择。对于 Windows 来说情况不太如此，但像 Puppet 这样的项目确实很好地支持它。
I don't recommend Chef unless you are a software developer who knows ruby. Chef is designed for software developers who want to manage IT infrastructure. Not for SysOps people who are the ones that actually end up managing it. It tries to treat IT infrastructure like code which is counter intuitive to how it actually works which is more like just data.
Puppet is more friendly for SysOps people imho but still can be complicated.
The good news is that there are other options as well. Less so for windows but projects like Puppet do support it reasonably well.