ApplyandAutoCorrect –-> After initial application of a new configuration, if the target node drifts from the desired state, DSC reports the discrepancy in logs, and then re-applies the current configuration.
ApplyAndMonitor –> This is the default value. After initial application of a new configuration, if the target node drifts from the desired state, DSC reports the discrepancy in logs.DSC applies the configuration and that’s it. It does not check for drift from a previously configured state. If yes, change it back to defaults by adding ActionAfterReboot = ‘ContinueConfiguration’ Default is ContinueConfiguration so unless you didn’t change this you are good to go. There are 3 settings that are important to us: ActionAfterReboot, ConfigurationMode and RebootNodeIfNeededĪctionAfterReboot –> Specifies what happens after a reboot during the application of a configuration. So the first thing we need to do is to configure LCM. Make sure that the DSC resources exist on both source and target servers.Configure LCM (Local Configuration Manager) on the target servers.RDCB01 -> Will become Connection Broker and Licensing serverīefore we go deep into the configuration, there are some prerequisite that we need to fulfill before we can make this work. Be sure to protect the password with certificate in a production environment. INFO! In this demo I will use plain text password. We live in a world of automation and we don’t have time to click us through the wizard over and over again every time we need to rebuild our deplyoment and start from scratch. If you are working with RDS and if you are installing / re-installing it a lot then DSC is the perfect tool for you. In this part we will see how we can automate RDS deployment with Desired State Configuration (DSC).
0 kommentar(er)
