Microsoft windows grouppolicy 1130
Профиль | Отправить PM | Цитировать
Доброго времени суток уважаемые коллеги!
На новой работе достался в наследство домен с двумя контроллерами, один из них хозяин Windows 2012
Встала необходимость настроить аудит, и тут то собственно и возникла ошибка.
При попытке зайти через управление групповой политикой возникает ошибка — следующего характера:
указанный домен не доступен или к нему невозможно подключится,
если отказаться от данного мастера — то появляется диалог с выбором другого контроллера или изменением Роли текущего
и если отказаться от этого мастера то в оснастке видна групповая политика к которой подключится невозможно.
в Журнале постоянно видны ошибки с кодом 1030:
Ошибка при обработке групповой политики.
Windows пыталась получить новые параметры групповой политики для этого пользователя или компьютера.
На вкладке «Подробности» можно найти код и описание
подскажите как можно восстановить работоспособность GPO?
| Меня настораживает все таки мысль о том что про просмотре GPO в оснастке мастером — пытается искать КД в домене csoft.ru хотя лес у нас org и не находит ни одного КД » |
| 192.168.0.2 — должен быть (это адрес приходящий от Провайдерского роутера) » |
| но выбрав КД выходит ошибка что КД нет в домене csoft.ru » |
| 192.168.0.2 это адрес на внешней сетевушке » |
| Product: | Windows Operating System |
| ID: | 1130 |
| Source: | Microsoft-Windows-GroupPolicy |
| Version: | 6.0 |
| Symbolic Name: | gpEvent_SCRIPT_FAILURE |
| Message: | %5 failed. %tGPO Name : %6%tGPO File System Path : %7%tScript Name: %8 |
Resolve
Correct a scripts extension failure
Possible resolutions include:
- Logon and logoff scripts: Ensure the user has the proper file permissions to read and run the script. Users must have the Read and Execute NTFS permission. If the script is located on a network share, the user must also have Read share permissions.
- Startup and shutdown scripts: Ensure the computer account has the proper file permissions to read and run the script. Computers must have the Read and Execute NTFS permission. If the script is located on a network share, the computer must also have Read share permissions.
- Verify the user or computer can start the script from %SystemRoot%\system32 folder.
Group Policy applies during computer startup and user logon. Afterward, Group Policy applies every 90 to 120 minutes. Events appearing in the event log may not reflect the most current state of Group Policy. Therefore, you should always refresh Group Policy to determine if Group Policy is working correctly.
To refresh Group Policy on a specific computer:
- Open the Start menu. Click All Programs and then click Accessories.
- Click Command Prompt.
- In the command prompt window, type gpupdate and then press ENTER.
- When the gpupdate command completes, open the Event Viewer.
Group Policy is working correctly if the last Group Policy event to appear in the System event log has one of the following event IDs:
Microsoft windows grouppolicy 1130
Вопрос
We have many Win7 and Win10 and all work fine, but two PC with Windows 10 cannot apply software installation GP and startup script GP with these errors:
We try set policy:
«Always wait for the network at computer startup and logon» = Enabled
«Specify startup policy processing wait time» = 90 sec
We try set registry:
reg add HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\NetworkProvider\HardenedPaths /v «\\*\SYSVOL» /d «RequireMutualAuthentication=0» /t REG_SZ
reg add HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\NetworkProvider\HardenedPaths /v «\\*\NETLOGON» /d «RequireMutualAuthentication=0» /t REG_SZ
We try re-join this PC to domain, but its not help.
How to resolve this issue?
- Перемещено Carey Frisch MVP 4 апреля 2018 г. 10:18 Relocated
Все ответы
Please try to login the 2 computers with other work well user accounts to check again.
Then please try to leave domain, delete and reinstall network drivers on the 2 computers.
Clean the group policy cache with the following command line.
RD /S /Q «%WinDir%\System32\GroupPolicyUsers»
RD /S /Q «%WinDir%\System32\GroupPolicy»
After that, join domain again to check the issue.
If the issue persists, please disable antivirus software and firewall to check again.
Microsoft windows grouppolicy 1130
Вопрос
I’m trying to apply the following computer startup script
I’ve set up the following powershell script to disable NetBIOS
The script works fine locally. I added a schedule task under the SYSTEM account and it ran with no problems. It only fails in the computer startup via GPO
This is the error I’m receiving via event viewer
Any help would be appreciated.
extra info. I’m testing this GPO on a windows 8.1 machine. This script works fine on a server 2008, server 2012, and server 2012 R2
Ответы
Based on the description, where is the startup script stored? Please double make sure that the computer account in question has enough permissions to access the script.
Regarding Event ID 1130, the following article can be referred to for more information.
Event ID 1130 — Group Policy Scripts Processing
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.
Все ответы
I see that you have created another thread here: http://community.spiceworks.com/topic/988490-gpo-computer-startup-script-fails-to-run-eventid-1130-error-code-267
If the recommendations still do not fix your problem then please update the thread here.
This posting is provided AS IS with no warranties or guarantees , and confers no rights.
>>The script works fine locally. I added a schedule task under the SYSTEM account and it ran with no problems. It only fails in the computer startup via GPO
Did we allow remote PowerShell scripts to run the clients? If not, we can try to enable the following policy setting and select proper option to allow PowerShell script to be executed:
Computer Configuration> Administrative Templates> Windows Components>Windows Powershell> Turn on Script Execution
If the issue persists, on the client, we can try to directly navigate to where the script is stored and run the script to see if it can be successfully run.
