Desired state configuration (DSC) is v4 (many people call him only PowerShell v4) that ships natively with Windows Server 2012 R2 and a function of the Windows Management Framework. 8.1
One thing to be clear on; DSC is not a single thing, it is a feature with different components. And this is an exploration of the main components at a high level to understand all the concepts. the moving parts Can one look at it, working together to enable DSC; the configuration word, configuration Local Configuration Manager, resource provider, WinRM, PowerShell.
Before I want to get deep into it I some fellow MVPs thank the award range from PowerShell helped me with a few things as I worked through my understanding. I also want to record some time to thank the product team at MSFT, to sit with me and talk as customers enter to help me better understand and give them feedback in my scenarios and my customer scenarios.
The MVP Community give out is large produce resources and communications. Here are some good resources:
- The DSC-Book - A free resource from Don Jones and Steve Murarwski
- Windows PowerShell desired state configuration Revealed - of Ravikanth Chaganti
- PowerShell.org and PowerShellMagazine.com
let's start with the first stumbling block start: Windows remote management (WinRM)
WinRM is required for the DSC to a push receive and process configurations in or pull model (more on this later). Let me say here that if you learn and follow all of the examples and apply a configuration; You will probably use a configuration interactively at the console (push model). This will just work out of the box, if your goal is Server 2012 R2. This is out of the box does not, if your goal is the Windows 8.1.
The difference? WinRM is enabled by default on the server and is disabled by default on the client. So plan accordingly, or you will get error messages that you can not apply your configuration because WinRM is not running.
PowerShell is the basic technology and the owning product team at MSFT. If you follow the latest PowerShell developments you hear about OMI. And if you listen recently to Jeffry Snover on DSC They talk mention of Monad hear manifesto, and the DSC is a component of the original Monad vision that is implemented as a "PowerShell".
The Local Configuration Manager (LCM) may be used as the means to be thought that it happen.
, the LCM is essentially a service that handles the configuration, analyzes the configuration dependencies screened defined in the configuration, then the configuration makes happen. The key thing is to understand that the entire configuration will be applied in the security context of the local system. By default, this may not have access to anything outside of the machine, and can act only on objects that are local to the machine. For example; When a software package is installed, the package on the machine on site must be, or the machine must be able to gain access to its security context.
you have the DSC no management layer? It is the lowest level, the execution engine / Enabler / Riker Picard (this is the analogy that the PowerShell team originally used).
In fact, companies such as Puppet and Chef are already the advantages of DSC take to do to use it to not threaten their dirty work and be by him. And DSC has MSFT as VM extension allows configurations Azure apply IaaS virtual machines via the API. Even if you SCVMM service templates or Windows Azure Pack Gallery items; Also you can use DSC since then to end engine that performs the configuration actions.
Now we come down to the configuration itself.
The configuration is a MOF format document that defined the end result that the Local Configuration Manager needs to happen. The MOF can be generated in a number of ways, but the simplest is to use by far the configuration keyword within a PowerShell script.
The configuration keyword is almost the last Enabler. You can use it in a script call this particular matter to define a configuration called. This is then implemented as a MOF file. This is in turn applied to the LCM. Which in turn makes it that way.
Well, it's the last Enabler. The resource provider
These are special modules -. They are built object and all their work is to bring the state of some resource, Ask the state of some resource, and then test the state of some resource. The resource is the element manipulated
There are suppliers of resources, which are integrated into the operating system. Archives (handling ZIP files), file (file manipulation), package (install / uninstall packages), and so on. Each of them is in a configuration with the state you stated wish to have. And you can unpack actions as an archive to copy a file to a specific path, the installation / uninstallation of a specific MSI, and so on.
There is also a framework for the custom resource provider. This is to extend support for third-party applications such as XenDesktop or the community to make it possible to build modules of MSFT provided far more than those who do.
There are also provided MSFT 'x' resource provider. But frankly, I hope PowerShell v5 many of them will include at a release level of quality. Until then, they are just like any other user-defined resource.
Like what you read here? Read other posts about desired state configuration
0 Komentar