?

Log in

Previous Entry

I'm writing this for the benefit of others administering Windows machines with Group Policies.  It's an issue I'd been tearing my hair out over for the last couple weeks or so.

Let's say you created (locally) and tested an event trigger using a custom XML events filter on a machine, and it's working just fine, and now you want to make it a group policy (GPO).
There are some important differences in the behavior of the task scheduler that's found locally on a machine, and its group policy preferences equivalent.  The local version will automatically convert HTML entities to the correct character (e.g. it will convert 
 to a newline, a.k.a. HTML Encoded Line Feed character).  The GPPreferences scheduler will not do this.  Make sure to be using the actual characters those entities represent.

Also, note there is a bug in the GP reports for the scheduler settings.  The report will always show those being set even if you actually uncheck all the settings, but it will behave correctly.

If you're still having problems, look in the event viewer for log entries from Group Policy Scheduled Task.  They might be helpful, maybe (although, honestly, most of the times those log entries just don't have enough information to diagnose the problem, just enough to see that there is one).

Comments

Latest Month

April 2016
S M T W T F S
     12
3456789
10111213141516
17181920212223
24252627282930

Tags

Powered by LiveJournal.com
Designed by Tiffany Chow