event id 4098 when applying printers via user group policy

After a reboot of my domain controller, I got a lot of event ID 4098 warnings in my appliucation event log as seen below.  I was getting several dozen errors per day - one for each printer.  My user GPO had been assigning printers for months with no problems, but after a reboot, this started coming up:

I fixed this by editing the group policy.  Go into the group policy for each printer and go to the common tab.and check the option for "run in logged in user's security context" as show below:

Windows could not start the DNS server service on the local computer. Error 1717: The interface is unknown.

I ran into an issue the other week where my SBS 2008 box lost power.  There's a bunch of irrelevant backstory that I won't go into.  But the next day, more than a dozen services were not started - including all the Exchange services.  In the end, I tracked it down to the DNS Server service not being started.  When I attempted to start it manually, I got "Windows could not start the DNS server service on the local computer. Error 1717: The interface is unknown."

I found two solutions.  I applied them both simultaneously, so I don't know which one worked, but I'm documenting them here:

Solution 1:

I set my group policy back to defaults as per this page:
http://forums.whirlpool.net.au/archive/1533833
I did this (copying the solution in case that page ever goes away):

• dcgpofix /ignoreschema
• Press OK twice and run gpupdate /force
• Reboot

Interestingly, my drive mappings group policy stayed in effect.  However, my password policy group policy settings were removed.

Solution 2:

I removed all of my event logs as per this page:

http://vittoriop77.blogspot.com/2007/10/error-1717-interface-is-unknown.html#.UDmCEsFlTB-

I'm writing this a couple weeks after the incident.  I don't remember not being able to open the event log, but I was in a panic as the issue was occurring during work hours, so I was throwing the kitchen sink at the problem.  To accomplish this task (copying the solution in case that page ever goes away), I did this:

• Stopped the event log service
• moved all files from %systemroot%\system32\winevt\logs to another location
• Started the event log service