Yup, I had already found that one, as a matter of fact, before even stumbling upon the final solution. At one point I had tried to set a trigger on user session disconnect, but using the earlier version of the command lines which didn't succeed at the desired task. I had been hoping that somehow the RDP session was still in its last stages of being active when the trigger got fired, but the session is instead completely disconnected by that time, so only the later-discovered versions of the command would work in that case. In any case, now I've got the correct information and commands, and I can implement then as triggers at RDP logoff or I can implement them in the program right before it does the ghosting, either way, or both.