Меню

Ошибка 1055 group policy

  • Remove From My Forums

  • Question

  • This is a really odd problem because it happens to only some of the Windows 7 machines on my Domain. 

    I have two 2008 R2 DNS servers on the network, and all the client machines are Windows 7.

    The error from GPRESULT is as follows:

    Group Policy Infrastructure failed due to the error listed below.
    Logon failure: unknown user name or bad password. 
    Note: Due to the GP Core failure, none of the other Group Policy components processed their policy. Consequently, status information for the other components
    is not available.

    The Event ID associated with this is 1055 Error 5 (Access is denied). I’m not sure why the hardware is being denied access to the GP. But earlier today I wasn’t even able to ping the PC via the network, even removing it from the domain and re adding it didn’t
    help. I then proceeded to flush the DNS on the NIC and re register it, that’s when the functionality of being able to ping the computer via name returned.

    This only happens on the machine policy, not the user policy.

    Normally I would not care, however I’m trying to move toward pushing all our software via GPO so that I can remove everyones Administrative privileges and stop people from installing bad software.

    Thanks

Answers

  • So today I kind of figured out the solution.

    I was messing around with one of the spare machines and I re imaged it with a fresh Win 7 copy. Added it to the domain and everything went ok, all the drives mapped and printers mapped as well. Then I proceeded to add the account to the Local Administrators
    group, as soon as I added my network account to this local computer group and rebooted the script from the GPO failed to run, and no Network Drives or Printers. Removed the local admin and voila it all came back.

    I decided to test my theory on one of the messed up computers, so I removed the Local Admin privileges and Reset the Computer Account on the DC. Removed the computer from the domain, rebooted, and added to computer to the domain again. Rebooted and logged
    in as my network account, this time everything mapped and the policy applied successfully.

    Seems that when the users are local admins the policy fails to run.

    I think I might have found the solution here:http://social.technet.microsoft.com/Forums/en-US/w8itpronetworking/thread/e68de19c-9463-4202-adcb-541b856f35f3/

    Maybe not the above had a fix for Win 8, I’ll try a few things but if worse come to worse I will revoke everyone’s admin access on the network. Been meaning to do that anyways.

    • Marked as answer by

      Thursday, April 18, 2013 11:39 PM

    • Unmarked as answer by
      La Chupacabra
      Thursday, April 18, 2013 11:41 PM
    • Marked as answer by
      La Chupacabra
      Thursday, April 18, 2013 11:43 PM
    • Unmarked as answer by
      La Chupacabra
      Friday, April 19, 2013 12:02 AM
    • Edited by
      La Chupacabra
      Friday, April 19, 2013 12:03 AM
    • Marked as answer by
      La Chupacabra
      Friday, April 19, 2013 2:27 PM

Источник

29.12.201402:1329.12.2014 02:13:03

На одном из доменных компьютеров с Windows 7 столкнулся с проблемой — не применялась групповая политика компьютера, при этом в системном журнале компьютера регистрировалось событие с номером 1055:

Ошибка при обработке групповой политики. Не удалось разрешить имя компьютера. Возможные причины: 
a) Ошибка разрешения имен на текущем контроллере домена. 
b) Запаздывание репликации Active Directory (созданная на другом контроллере домена учетная запись еще не реплицирована на текущий контроллер домена).

При этом в Подробностях можно было видеть следующий дополнительный код ошибки:

ErrorCode 1331 
ErrorDescription Вход в систему не произведен: учетная запись в настоящее время отключена.  

На Технете существует

статья

по событию 1055, однако по ErrorCode 1331 там нет никакой информации.
Имена на контроллере домена разрешались нормально, dcdiag никаких ошибок не показывал, с репликацией проблем не было, sysvol была доступна с проблемного компа, учетная запись компьютера конечно же была включена.
При генерации Результирующей политики (RSoP) выдавалась следующая ошибка:

Инфраструктура групповой политики не удалось выполнить из-за указанной ниже ошибки.
Вход в систему не произведен: учетная запись в настоящее время отключена.
Примечание: из-за ошибки ядра групповой политики никакие другие компоненты групповой политики не выполнили обработку своей политики. Тем самым, информация о состоянии других компонентов недоступна.

В результате долгих раздумий и исканий выяснилось следующее — на компьютере под аккаунтом Локальная система (Local System аccount) были закэшированы реквизиты сторонней учетки для доступа к контроллеру домена. А именно от имени этого аккаунта идет обращение к КД для получения групповых политик компьютера. Т.е. при попытке получить групповые политики с контроллера домена обращение к нему шло от этой закэшированной учетки, которая действительно была отключена. Проблема решилась после удаления этой учетки из кэша, сделать это можно следующим образом:

1) С Технета качаем всем известный пакет  Sysinternals

PSTools

, из него нам потребуется утилита PsExec
2) Запускаем командную строку от имени администратора и выполняем в ней PsExec.exe -i -s cmd.exe, в результате запустится командная строка под системной учетной записью
3) В этой командной строке запускаем rundll32.exe keymgr.dll, KRShowKeyMgr, в результате откроется окно «Сохранение имен пользователей и паролей», в котором можно увидеть все закэшированные учетки под системной учетной записью:

event1055.png

4) Удаляем ненужные учетки. Прежде всего нужно обратить внимание на те, которые используются для авторизации на КД. В моем случае тут была только одна учетка.
5) Перезагружаем компьютер, проверяем, как отработалась политика компьютера, и наслаждаемся жизнью :)

Дополнение:

ErrorCode 5 — решилась аналогичным образом.

Полезная ссылка: список кодов системных ошибок Windows

Источник

RRS feed

  • Remove From My Forums

  • Question

  • Hi,

    I am getting intermittent issues with Windows 10 where the computer policies do not apply at startup and Group Policy 1055 error is logged in the system log along with Netlogon 5719 which having read online I didn’t think this was meant to be logged on Windows
    10.

    I have tried the startup wait time but this has had no effect.

    Please help.

All replies

  • Every time this happens their seems to be the following error starting it all off

    The nsi service was unable to log on as NT AuthorityLocalService with the currently configured password due to the following error:

    A specified logon session does not exist. It may already have been terminated.

    To ensure that the service is configured properly, use the Services snap-in in Microsoft Management Console (MMC).

    By the time I am able to login it is all started. I currently have this on 2 machines. I had it on another until I rebuilt it. Don’t know what to do just keep rebuilding them until they work. No problems like this until windows 10. Drivers are for Windows 10.

    • Edited by

      Tuesday, May 31, 2016 6:53 AM

  • No have reset computer account, completely deleted…. Thinking of trying putting in a dedicated NIC Card.

  • I have tried a new network card and it makes no difference.. It seems to be a race condition where the nsi service doesn’t start until a bit later followed by DHCP etc…presumably as long as nothing has changed the computer has the group policies anyway?
    I’m more worried about the loopback policy working as printers are deployed via the user policies on the computer policy…

    I haven’t actually had any complaints about things not working from users, I just feel I shouldn’t be receiving these errors? They are very intermittent, 1 in 10 startups I would say…

    Should I just not worry? I have rebuilt the machine, tried various registry keys and startup policy time policies, a new nic card…..

  • Any ideas this is still a problem just on a certain type of PC, have tried different drivers etc, is it possible to set group policy to reapply is it fails?

  • Hi John555444,

    «Group Policy 1055 error is logged in the system log along with Netlogon 5719 «
    I found a article that indicates this behavior is caused by a race condition between network initialization, locating a Domain Controller and processing Group Policy. To workaround the issue, you can set a registry value to delay the application of Group Policy.

    Please check the following link for detailed information. Hope it is helpful.
    https://support.microsoft.com/en-sg/kb/2421599

    Best regards

    Please
    mark the reply as an answer if you find it is helpful.

    If you have feedback for TechNet Support, contact
    tnmff@microsoft.com

Источник

RRS feed

  • Remove From My Forums

  • Question

  • Hi,

    I am getting intermittent issues with Windows 10 where the computer policies do not apply at startup and Group Policy 1055 error is logged in the system log along with Netlogon 5719 which having read online I didn’t think this was meant to be logged on Windows
    10.

    I have tried the startup wait time but this has had no effect.

    Please help.

All replies

  • Every time this happens their seems to be the following error starting it all off

    The nsi service was unable to log on as NT AuthorityLocalService with the currently configured password due to the following error:

    A specified logon session does not exist. It may already have been terminated.

    To ensure that the service is configured properly, use the Services snap-in in Microsoft Management Console (MMC).

    By the time I am able to login it is all started. I currently have this on 2 machines. I had it on another until I rebuilt it. Don’t know what to do just keep rebuilding them until they work. No problems like this until windows 10. Drivers are for Windows 10.

    • Edited by

      Tuesday, May 31, 2016 6:53 AM

  • No have reset computer account, completely deleted…. Thinking of trying putting in a dedicated NIC Card.

  • I have tried a new network card and it makes no difference.. It seems to be a race condition where the nsi service doesn’t start until a bit later followed by DHCP etc…presumably as long as nothing has changed the computer has the group policies anyway?
    I’m more worried about the loopback policy working as printers are deployed via the user policies on the computer policy…

    I haven’t actually had any complaints about things not working from users, I just feel I shouldn’t be receiving these errors? They are very intermittent, 1 in 10 startups I would say…

    Should I just not worry? I have rebuilt the machine, tried various registry keys and startup policy time policies, a new nic card…..

  • Any ideas this is still a problem just on a certain type of PC, have tried different drivers etc, is it possible to set group policy to reapply is it fails?

  • Hi John555444,

    «Group Policy 1055 error is logged in the system log along with Netlogon 5719 «
    I found a article that indicates this behavior is caused by a race condition between network initialization, locating a Domain Controller and processing Group Policy. To workaround the issue, you can set a registry value to delay the application of Group Policy.

    Please check the following link for detailed information. Hope it is helpful.
    https://support.microsoft.com/en-sg/kb/2421599

    Best regards

    Please
    mark the reply as an answer if you find it is helpful.

    If you have feedback for TechNet Support, contact
    tnmff@microsoft.com

Источник

0 0 голоса
Рейтинг статьи
Подписаться
Уведомить о
guest

0 комментариев
Старые
Новые Популярные
Межтекстовые Отзывы
Посмотреть все комментарии

А вот еще интересные материалы:

  • Яшка сломя голову остановился исправьте ошибки
  • Ясность цели позволяет целеустремленно добиваться намеченного исправьте ошибки
  • Ясность цели позволяет целеустремленно добиваться намеченного где ошибка
  • Ошибка 1054 эур приора
  • Ошибка 1054 эур гранта

    • ➤