I'm trying to set up a group policy to create a scheduled task that will reboot computers on Wednesdays and Saturdays. There's an older GPO version that worked for the machines that were already on the domain, but newly added computers don't seem to be picking it up. After doing some digging, I discovered that a part of the policy had become outdated, which might be causing the problem. Since it's a legacy GPO, I rebuilt it from scratch with the same configurations, just leaving out the deprecated message. I tested the new GPO in my test Organizational Unit (OU), and it worked perfectly on my test computer. However, when I linked it to the production OUs today, the scheduled task didn't appear on any of the new domain-joined computers. GPResult indicates that the GPO was applied successfully, but there's nothing in the task scheduler or logs in the event viewer to show that the task was created. I'm looking for insights on what might be going wrong.
5 Answers
You could try using the RSOP (Resultant Set of Policy) tool on one of the new machines. It's often more informative than GPResult and can help identify any errors with the GPO application. It might shed some light on what's actually being applied versus what should be.
Honestly, I'm not sure a GPO is the best solution for this kind of task. Do you have any other management tools available that might work better? Also, why are you needing to reboot computers so frequently? It's a bit unusual.
Have you thought about using something like Emco Remote Shutdown? It might not fix your GPO issue directly, but it can be another workaround for managing reboots remotely if the GPO isn't cutting it.
Have you checked how you're implementing the GPO? Adding it via a .bat file to run as System might still function properly, but using a small PowerShell script could be a better approach for this scenario. It just offers more flexibility and insight into what's happening behind the scenes.
All I can say is that something must be off in your approach. AI tools can do wonders in helping pinpoint issues like this and validating your steps, so maybe consider leveraging those for some troubleshooting.
I totally agree with that! I often use a short PowerShell script to remotely push scheduled tasks to my servers when needed. It makes the whole process smoother.