Well… let me answer the technical question first. Create a new configuration on the pull server, and a new checksum file to go with it. This might be just entering an extra blank line at the end of the existing file, so it checksums differently, and “tricks” the node into re-pulling it. Ought to work.
There presently isn’t a way to set to ApplyAndMonitor, and then manually “poke” it to force it into Apply mode.
Potentially, you could also reconfigure the LCM to ApplyAndAutoCorrect, and once it reports back in as Compliant, switch it back to ApplyAndMonitor. Sounds awkward. Might work.
But… the bigger point, now. I completely understand your desire to not have machines reconfigure themselves randomly throughout the day, but you’re working contrary to what DSC wants to do. That’s completely your privilege, and you very likely have excellent reasons for it, but you’re going to find it difficult because that isn’t what the technology wants to do. It’s kind of like saying, “I really want to drive this old 1968 Chevy, but I’m opposed to using gas.” You’ve picked the wrong tool for the job. Something like Chef or Puppet, which offer more granular control, might be more suitable.
I’d argue that DSC making changes without you knowing isn’t the problem, it’s why the node isn’t configured the way it was supposed to be in the first place. If nothing changes on the node, DSC won’t do anything. If something changes, DSC is just putting it back. Presently, lacking any awareness of maintenance windows, DSC making changes can definitely be disruptive - but that’s what it does and where it is, technically, today. You’re finding yourself at cross-purposes with it, and it’s going to be awkward to work with because your processes don’t line up with what DSC wants to do. So I’d say the real answer is, “either change your processes to align with what DSC does, or use something that aligns with your processes.”
Very much not trying to be snarky here, but I run into a lot of people banging their heads against DSC because it isn’t the right tool to align with their processes, and they’re either not willing or not able to change those processes. Just want you to be aware that’s where you’ve gotten to :).
So: DSC isn’t designed, at present, to do what you want in a “clean” fashion. I’m not saying what you want is wrong, or trying to justify DSC’s perspective, just that you and DSC are in different playbooks.