So that would indeed be your configuration of the LCM. I'm not certain why it's needing a reboot, unless the node had some underlying dependency missing or turned off, which itself required a reboot. I've not personally seen this happen. We'll see if someone else pops in with a different experience.
That's a v4 pull server thing if I remember right. If you go into task scheduler there are two dsc jobs, one of which says something to the effect of "register after reboot" or something. It seemed to be registered fine without a reboot, so I always assumed that was a bogus message. v5 got away from the scheduled tasks I believe.