Con più domande
Group Policy Not Appying Event Id 1058 Error Code 1326

Domanda
-
Tutte le risposte
-
Hi,
Please make sure the user have the appropriate permission to the path specified in the event.
Then refer to the following link.
You may also delete the cathed profile and try again.
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ” -
This is very erratic and doesn't seen to be tied to a particular DC - there are 6 and I have seen it happen on a couple of them but I've also seen success on these same ones. The same user can then log into another pc near by and all works for them.
I haven't checked the rights as it seems to come and go.
-
Hi,
Have you tied created a new user or deleted the catched profile for a test? If you have not, Please perform this and let me know the result.
Thanks.
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ” -
-
Hi,
Please refer to the following link and follow the article to check the issue.
http://support.microsoft.com/default.aspx?scid=kb;EN-US;887303
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ” -
None of the above responses help with the error code indicated (1326). I have the same issue and one of the above recommendations help. Has anyone figured this out? I have one Windows 7 client that fails to update the computer policy during gpupdate but sill manages to update the user policy. I have tried everything above and reset the AD computer account. Name resolution and permissions are NOT the problem. I can even directly access the policy via the UNC without a problem. The event ID is 1058 with a source of Group Policy and the error code is 1326 which indicates a logon failuer. I wonder if it would be beneficial to delete the computer account from AD or remove the computer from the domain and re add it? However I don't know the consequences that may lead to for the end-user profiles and such. Any insight would be greatly appreciated.
GPResult Error:
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.
Additional information may have been logged. Review the Policy Events tab in the console or the application event log for events between 5/12/2011 1:38:12 PM and 5/12/2011 1:38:12 PM.
-
Yes, might be worth deleting the computer account in AD and waiting to be sure it has replicated to all your DCs.
Before doing that, make sure you CAN actually log on to the computer with a local account so you can join it back to the Domain afterwards. :-)
Ha®®y -
Tried it. Still can't update the Computer Policy. I have done everything in this thread (most things 2 or 3 times) and I still have no love from microsoft. Event ID 1056 from GroupPolicy with error code 1326. How can the Computer Account have a login failure?
-
Try this on an affected computer. This worked for me:
There are passwords that can be stored in the SYSTEM context that can't be seen in the normal Credential Manager view.
Download PsExec.exe from http://technet.microsoft.com/en-us/sysinternals/bb897553.aspx and copy it to C:\Windows\System32 .
From a command prompt run: psexec -i -s -d cmd.exe
From the new DOS window run: rundll32 keymgr.dll,KRShowKeyMgr
Remove any items that appear in the list of Stored User Names and Passwords. Restart the computer.
also, there are scripts that you can run (i did not test, found them on stack exchange) to do this if they are run as system user:
Script one:
cmdkey.exe /list > "%TEMP%\List.txt"
findstr.exe Target "%TEMP%\List.txt" > "%TEMP%\tokensonly.txt"
FOR /F "tokens=1,2 delims= " %%G IN (%TEMP%\tokensonly.txt) DO cmdkey.exe /delete:%%H
del "%TEMP%\List.txt" /s /f /q
del "%TEMP%\tokensonly.txt" /s /f /q
Script 2
for /F "tokens=1,2 delims= " %G in ('cmdkey /list ^| findstr Target') do cmdkey /delete %H
I hope this helps. I found this solution for something completely unrelated, and it resolved this months old problem for me :) -
Try this on an affected computer. This worked for me:
Was dealing with Event 1058, Error Code 1326 for a couple days and tried pretty much everything. Including removing and readding to the domain. Turns out there was a cached credential from an administrator who had been disabled. Removed that credential and GPO's are flowing again. Thanks for your post!
There are passwords that can be stored in the SYSTEM context that can't be seen in the normal Credential Manager view.
Download PsExec.exe from http://technet.microsoft.com/en-us/sysinternals/bb897553.aspx and copy it to C:\Windows\System32 .
From a command prompt run: psexec -i -s -d cmd.exe
From the new DOS window run: rundll32 keymgr.dll,KRShowKeyMgr
Remove any items that appear in the list of Stored User Names and Passwords. Restart the computer.