We have a computer imaging process and part of this process lays down the “baseline” configs via a start-dscconfiguration cmdlet. Just after, we determine whether the computer is a desktop or laptop. If the computer is a laptop, we lay down our vpn client via another dsc configuration.
Not all the time, but often, the laptop dsc script fails. When it fails, we reboot the machine and attempt again until we hit 6 reboots. At six reboots, we let the machine stay there and a tech can go figure out what is wrong. Something about the time it takes for the tech to log in and look at the problem seems to allow something to clear and the same start-dscconfiguration cmdlet works with the laptop configuration.
Is there anything I could check before running the start-dscconfguration cmdlet for the laptop configuration to ensure that it is ready to process another configuration? I’m looking for any and all relevant pointers that I can go investigate. Just figured I would see if anyone has seen similar things before.