Guest KWME Posted December 17, 2007 Posted December 17, 2007 I'm totally baffled by the following error that I'm getting every 5 minutes on my server. Group policies are not applying to client computers. I'm running Server 2003 with one dc. Here is the error message: Event Type: Warning Event Source: SceCli Event Category: None Event ID: 1202 Date: 12/16/2007 Time: 10:01:32 PM User: N/A Computer: STUDENT3 Description: Security policies were propagated with warning. 0x4b8 : An extended error has occurred. Advanced help for this problem is available on http://support.microsoft.com. Query for "troubleshooting 1202 events". For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. The kb's mention that changing the administrator account name can be the cause of this, but this policy isn't set anywhere. Ideas? Help would be much appreciated.
Guest KWME Posted December 17, 2007 Posted December 17, 2007 RE: SceCli Error 1202 - 0x4b8 I'm thankful to be able to answer my own post. I looked up SecCli Error 1202 on EventID.net and worked my way down the list. Rob Willman's idea of copying a working copy of the secedit security database from a working server in a different domain did the trick. I renamed the apparently corrupt file oldsecedit and pasted in the secedit file from another server. I rebooted the offending machine and the error message has gone away. I ran RSOP and received no errors. I'm on top of the world. "KWME" wrote: > I'm totally baffled by the following error that I'm getting every 5 minutes > on my server. Group policies are not applying to client computers. I'm > running Server 2003 with one dc. Here is the error message: > > Event Type: Warning > Event Source: SceCli > Event Category: None > Event ID: 1202 > Date: 12/16/2007 > Time: 10:01:32 PM > User: N/A > Computer: STUDENT3 > Description: > Security policies were propagated with warning. 0x4b8 : An extended error > has occurred. > > Advanced help for this problem is available on http://support.microsoft.com. > Query for "troubleshooting 1202 events". > > For more information, see Help and Support Center at > http://go.microsoft.com/fwlink/events.asp. > > The kb's mention that changing the administrator account name can be the > cause of this, but this policy isn't set anywhere. Ideas? Help would be > much appreciated. > >
Recommended Posts