w2k srv std rus
После неудачной перезагрузки каждые пять минут появляется сообщение
Тип события: Предупреждение
Источник события: SceCli
Категория события: Отсутствует
Код события: 1202
Дата: 06.09.2007
Время: 10:12:26
Пользователь: Н/Д
Компьютер: TD001
Описание:
Выполнено распространение политики безопасности с предупреждением. 0x2 : Не удается найти указанный файл.
Для диагностики этого события выполните вход с неадминистративной учетной записью и на
http://support.microsoft.com выполните поиск раздела "Troubleshooting 1202 events" ("Диагностика события 1202").
http://support.microsoft.com:0x2: The system cannot find the file specified.
This error is similar to 0x534 and to 0x6fc in that it is caused by an irresoluble account name. When the 0x2 error occurs, it typically indicates that the irresoluble account name is specified in a Restricted Groups policy setting.
To troubleshoot this issue, follow these steps:
1. Determine which service or which object is having the failure. To do this, enable debug logging for the Security Configuration client-side extension. To do this: a. Start Registry Editor.
b. Locate and then click the following registry subkey: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Winlogon\GPExtensions\{827D319E-6EAC-11D2-A4EA-00C04F7 9F83A}
c. On the Edit menu, click Add Value, and then add the following registry value: Value name: ExtensionDebugLevel Data type: DWORD Value data: 2
d. Quit Registry Editor.
2. 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 /enforceThis creates a file that is named Winlogon.log in the %SYSTEMROOT%\Security\Logs folder.
3. At the command prompt, type the following, and then press ENTER: find /i "cannot find" %SYSTEMROOT%\security\logs\winlogon.logThe Find output identifies the problem account names--for example, "Cannot find MichaelAlexander." In this example, the user account MichaelAlexander does not exist in the domain, or it has a different spelling--for example, MichelleAlexander.Determine why this account cannot be resolved. For example, look for typographical errors, a deleted account, the wrong policy applying to this computer, or a trust problem.
4. If you determine that the account has to be removed from the policy, find the problem policy and the problem setting. To find what setting contains the unresolved account, type the following at the command prompt on the computer that is producing the SCECLI 1202 event, and then press ENTER: c:\>find /i “account name” %SYSTEMROOT%\security\templates\policies\gpt*.*For this example, the syntax and the results are: c:\>find /i "MichaelAlexander" %SYSTEMROOT%\security\templates\policies\gpt*.*---------- D:\WINNT\SECURITY\TEMPLATES\POLICIES\GPT00000.DOM---------- D:\WINNT\SECURITY\TEMPLATES\POLICIES\GPT00001.INF---------- D:\WINNT\SECURITY\TEMPLATES\POLICIES\GPT00002.INFSeInteractiveLogonRight = TsInternetUser,*S-1-5-32-549,*S-1-5-32-550,JohnDough,*S-1-5-32-551,*S-1-5-32-544,*S-1-5-32-548---------- D:\WINNT\SECURITY\TEMPLATES\POLICIES\GPT00003.DOMThis identifies GPT00002.inf as the cached security template from the problem GPO that contains the problem setting. It also identifies the problem setting as SeInteractiveLogonRight. The display name for SeInteractiveLogonRight is “Logon locally.” For a map of the constants (for example, SeInteractiveLogonRight) to their display names (for example, Logon locally), see the Microsoft Windows 2000 Server Resource Kit, "Distributed Systems Guide." The map is in the "User Rights" section of the Appendix.
5. Determine which GPO contains the problem setting. Search the cached security template that you identified in step 4 for the text "GPOPath=." In this example, you would see the following: GPOPath={6AC1786C-016F-11D2-945F-00C04FB984F9}\MACHINEBetween "GPOPath=" and "\MACHINE" is the GUID of the GPO.
6. To find the friendly name of the GPO, use the Resource Kit utility Gpotool.exe. Type the following at the command prompt, and then press ENTER: gpotool /verboseSearch the output for the GUID you identified in step 5. The four lines that follow the GUID contain the friendly name of the policy. For example:Policy {6AC1786C-016F-11D2-945F-00C04FB984F9}Policy OKDetails:------------------------------------------------------------DC: domcntlr1.wingtiptoys.comFriendly name: Default Domain Controllers Policy
You have now identified the problem account, the problem setting, and the problem GPO. To resolve the problem, search the Restricted Groups section of the security policy for instances of the problem account (in this example, "MichaelAlexander"), and then remove or replace the problem entry.
----Настройка политики безопасности...
Предупреждение 2: Не удается найти указанный файл.
Ошибка открытия домена учетных записей SAM.
Ошибка при настройке системного доступа.
Настройка параметров протоколирования.
Настройка аудита/протоколирования выполнена успешно.
Настройка политики Kerberos.
Настройка политики Kerberos выполнена успешно.
……………………………………….
Как решить проблему!!!!!!?????????????????