» Выполнено распространение политики безопасности

дело такое . каждые 5 мин выдаёт ошибку
Выполнено распространение политики безопасности с предупреждением. 0x4b8 : Ошибка расширенного типа.

Справка по данному вопросу размещена на веб-узле http://support.microsoft.com. Запросите "troubleshooting 1202 events".

Дополнительные сведения можно найти в центре справки и поддержки, в "http://go.microsoft.com/fwlink/events.asp".


я понял что изменять имя АДМИНИСТРАТОР на контроллере домена на что то другое не хорошо но поменяв его обратно эта ошибка за....ла мне все мозги.
что уже только не пробовал
заметил что откуда не возьмись в некоторых папках тоесть в правай на них есть теперь какойто юзер с именем непойми каким. пологаю что это и есть то имя но уже не то
сам короча запутался но думаю меня поняли
как проверить скопом накакие папки ещё действует это удалённо старое имя администратора ?

людиии неужно нету мылсёв ?((

Вот что есть на event.net пробуй:

Error code 0x4b8 (decimal 1208) - "An extended error occurred". See M260715 - A conflict in Group Policy can cause these events to occur. These error messages can occur if the "Rename Administrator Account" security policy is enabled and then set to an account name that is already in use. Also, as per M285903, to resolve this behavior, remove all references to the Power Users group in the Local Security settings.

- Error code: 0x4b8 (Error code 1208) - In my case, this event was accompanied by event 1085 from source Userenv. To fix this, I simply went to the "C:\WINDOWS\security\Database" folder and renamed the files *.bak. I manually ran "gpupdate /force" and the secedit.sdb file was recreated. I rebooted and all was well. For some reason the old secedit.sdb file had a very old date. My guess is it was not updating.


Daniel Vasilciu (Last update 5/31/2006):
- Error code: 0x4b8 (Error code 1208) - In our case, we received this event at every 5 min GPO refresh cycle. To fix the problem, we just deleted the following files:
%SystemRoot%\Security\Edb.*
%SystemRoot%\Security\Res*.*
The files will recreate themselves the next time you go into the Local Security Policies.

Rob Willman (Last update 8/14/2005):
- Error Code: 0x4b8 - I was receiving this error every 5 minutes on our two W2k domain controllers. I tried all the listed fixes with no success. Winlogon.log was giving me "Error 1208: An extended error has occurred. Error creating database". It looks like my security policy database was corrupt. Renaming and copying secedit.sdb in the C:\winnt\security\database from a working domain controller, in a separate domain, fixed the problem.

Ionut Marin (Last update 8/6/2005):
- Error code: 0x4b8 = "An extended error has occurred" - See M296854, M827012, M835744, M835901, and M837166.

Nicholas (Last update 2/3/2005):
- Error code: 0x4b8 - In our case, we had the error occurring at every 5 min GPO refresh cycle. We set up logging per M324383. The problem turned out to be with Restricted Groups; it was attempting to remove a user ID whose Primary Group was set to that of the Restricted Group and so it failed and did not process the rest of that GPO. Changing the Primary Group back to the default of Domain Users immediately fixed the problem.


Peter Mrack
Error code: 0x4b8 (Decimal 1208) = "An extended error has occurred." - This problem is caused by applying policies with defined restricted groups, i.e. the specified restricted group contains a local administrator account which doesn't exist on your local machine. Depending on your needs choose either to delete the entry of that account from the specified group in restricted groups or establish that account on the local machine. The important issue is a match of the accounts mentioned in restricted groups with those on the machine(s).

denis255
спасибо тебе ДРУХ ) всё заработало
проделал вот это

- Error code: 0x4b8 (Error code 1208) - In my case, this event was accompanied by event 1085 from source Userenv. To fix this, I simply went to the "C:\WINDOWS\security\Database" folder and renamed the files *.bak. I manually ran "gpupdate /force" and the secedit.sdb file was recreated. I rebooted and all was well. For some reason the old secedit.sdb file had a very old date. My guess is it was not updating.

странно. сразу вкралось подозрение на то что то фал был создан 3 месяца назад
теперь всё пучком
примного блогодарен