Hi Sirirako! Dave has done a great job of try to isolate this. One of the challenges in using the preview release is that sometime bugs creep in. You may have found one. I’ll try a similar config when I get a chance this weekend and check it out. I do have a question, are you using resources downloaded from TechNet or the PSGallery?
Jason, I got xPSDesiredStateConfiguration from PSGallery. My configuration is very simple. When I said earlier about testing, I just remove a user from Administrator group but LCM has never reapplied or even checked the config. I understand that this is a preview but I would like to be able to troubleshoot LCM and understand it more. I can’t put a black box in the Production and hope it will work. Thank you!
“I can’t put a black box in the Production and hope it will work.” That’s sort of what you do with almost every piece of software, including the Windows OS. Sometimes there are bugs. (Or perhaps more cynical: there are always bugs; just some of them you may not notice.)
Have you tried this on a clean Windows install, by chance? Can you reproduce it across multiple computers, or is only this one lab machine somehow screwed up at the moment?
Yes, I put a black box in production and luckily most of the time it works. I need to see more though in this case. These jobs were in Task Scheduler and I used to be able to see exactly when it will happen and see the log in the event log. Now I don’t know what is happening inside LCM. I am guessing it is a job with a timer in it. In other product like SharePoint, I can see all timer jobs. I wish I can see it in LCM and be able to start them or a way to clear it up. If this happens in Production, I have no way to tell my manager what is happening. This is sort of feature request to make it a little more transparent. Even right now, this is a pilot project (but already communicated to customer that we are doing this). It won’t become real if I can’t explain what is happening.
I appreciate all your help. I will try one a new machine and see if it fixed. I have other 3 machines that was upgraded for WMF5 Nov. Two are having the same issue. One is working because for some reasons, the schedule task are still there.