October 25, 2017 at 9:07 am #82832
I have small issue with DSC.
Running a configuration interactively can give a clear display as to its progress (if the right commandline switches used) but if the server reboots (before the configuration has completed and with LCM configured to rebootifneeded=true and ActionAfterReboot=ContinueConfiguration) as soon as the server boots up the configuration continues (whether you logon or not) which is great. Whats not so good is after that there is no visual indication a configuration is in progress post reboot. During ongoing configuration maintenance I can see you may want to suppress any display but the first time you apply a configuration or during troubleshooting you may want to view the progress end-to-end.
Has anyone figured a way around this?
October 25, 2017 at 1:51 pm #82856
It's not so much that you would want to "suppress any display," but the way the LCM is designed is to not provide visual feedback. Especially with servers, Microsoft assumes nobody is logged onto the console, since that's their recommended practice. So, no – the LCM is expressly not designed to provide visual feedback to an interactively logged-on user. If you needed to troubleshoot, you'd use the event logs.
October 25, 2017 at 7:38 pm #82909
I'd say that this is part of the change on mentality, where you shouldn't care for the server anymore, not log into the server, not watching it, but interacting with the framework to query the status. I don't think it'll ever be a way of "displaying" that config is being done.
October 26, 2017 at 8:55 am #82924
Agree with the first two replies. I'll just add that for troubleshooting/authoring purposes, I have had situations where I needed to debug errors that occur after reboot, and I typically use one of three choices.
1 – Register the node with Azure DSC service. It will upload status information in real time, including after reboot, so you don't need to log in to see the problem. Just check the details in a browser, iterate on your code, and run the deployment again.
2 – Enable the debug logs and use event viewer.
3 – Temporarily set LCM to not reboot automatically, and manually run the Configuration again after reboot using -wait -verbose.
You must be logged in to reply to this topic.