Event ID 1202 0x4b8


  • On our Domain Controller running Server 2008 R2 I am seeing an event 1202 with an extended error of 0x4b8. After I run gpupdate /force, this is what is entered in the winlogon file...

    Process GP template gpt00001.inf.

    This is the last GPO : domain policy is ignored on DC.
    Friday, July 10, 2015 9:53:09 AM
    Administrative privileged user logged on.
    Parsing template C:\Windows\security\templates\policies\gpt00001.inf.
    Error 1208: An extended error has occurred.
    Error writing info for SeAssignPrimaryTokenPrivilege.
    Error 1208: An extended error has occurred.
    Error converting SeAssignPrimaryTokenPrivilege.
    Error 1208: An extended error has occurred.
    Error converting section Privilege Rights.
    ----Configuration engine was initialized with one or more errors.----

    ----Un-initialize configuration engine...

    Any Idea what I need to do to resolve this?

    Thank you

    Friday, July 10, 2015 3:12 PM


All replies

  • Hi,

    see if this helps: Troubleshooting SCECLI 1202 Events


    0x4b8: An extended error has occurred.

    The 0x4b8 error is generic and can be caused by a number of different problems. To troubleshoot these errors, follow these steps:
    Enable debug logging for the Security Configuration client-side extension. To do this:
    Start Registry Editor.
    Locate and then click the following registry subkey:
    HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Winlogon\GPExtensions\{827D319E-6EAC-11D2-A4EA-00C04F7 9F83A}
    On the Edit menu, click Add Value, and then add the following registry value:
    Value name: ExtensionDebugLevel 
    Data type: DWORD 
    Value data: 2
    Quit Registry Editor.
    Refresh the policy settings to reproduce the failure. To refresh the policy settings, type the following at the command prompt, and then press ENTER:
    secedit /refreshpolicy machine_policy /enforce
    This creates a file that is named Winlogon.log in the %SYSTEMROOT%\Security\Logs folder.
    See the following Microsoft Knowledge Base articles. These articles describe known issues that cause the 0x4b8 error. Click the following article numbers to view the articles in the Microsoft Knowledge Base:


    260715 Event ID 1000 and 1202 After Configuring Policies
    278316 ESENT Event IDs 1000, 1202, 412, and 454 Are Logged Repeatedly in the Application Event Log

    This post is provided AS IS with no warranties or guarantees, and confers no rights.
    Questo post non fornisce garanzie e non conferisce diritti

    • Edited by aperelli Friday, July 10, 2015 3:20 PM
    Friday, July 10, 2015 3:20 PM
  • > Error 1208: An extended error has occurred.
    Delete (or rename) %windir%\security\database\secedit.sdb

    Greetings/Grüße, Martin

    Mal ein gutes Buch über GPOs lesen?
    Good or bad GPOs? - my blog…
    And if IT bothers me - coke bottle design refreshment (-:
    • Marked as answer by Lonnie Abel Wednesday, July 15, 2015 7:41 PM
    Monday, July 13, 2015 9:00 AM
  • Perfect. Thank you.

    Renamed %windir%\security\database\secedit.sdb to secedit.sdb.old

    followed by gpupdate /force

    Log off/ log on.. No more errors

    Sunday, March 6, 2016 9:56 PM