Wednesday, May 29, 2013

Server 2012 Event ID 13555

I ran into this one today.  It involved two brand new 2012 servers that had only been in service since December of 2012.  The error appears to have started on 4/27/2013 and didn't present itself as an issue (since there's no IT staff there to review server logs) until new workstations were being put in and group policy was not applying to some of them.

The event log gave error 1355.  In order to fix it you need to do a non-authoritative restore of the SYSVOL folder.  Just make a simple backup of it just in case from another good domain controller.  Follow the steps below and for me it fixed it right away.  There's no need to restart the server and I noticed the replication began and ran properly right away.

Here's the exact fix:

To back up and restore the SYSVOL data, follow these steps:
  1. Back up the following folders in a temporary location that is not in the SYSVOL folder:
    • %SystemRoot%\SYSVOL\Domain\Policies
    • %SystemRoot%\SYSVOL\Domain\Scripts
    Note To retain the permissions for these folders, back up these folders in a location that is on the same volume as the SYSVOL folder.
  2. Perform a non-authoritative restore on this replica set. To do this, follow these steps:
    1. Click Start, click Run, type cmd, and then click OK.
    2. At the command prompt, type the following command, and then press ENTER:
      net stop ntfrs
    3. Click Start, click Run, type regedit, and then click OK.
    4. Locate and then click the following registry subkey:
      HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\NtFrs\Parameters\Backup/Restore\Process at Startup
    5. Right-click the
      BurFlags
      entry, and then click Modify.
    6. In the Value data box, type D2, and then click OK.
    7. On the File menu, click Exit.
    8. At the command prompt, type the following command, and then press ENTER:
      net start ntfrs

Thursday, May 23, 2013

Windows Update Error Code 800B0001

When trying to update Server 2012 you may see the error below when using WSUS 3.0 SP2.


To fix the above issue there is an update for Windows Server Update Services 3.0 Service Pack 2 that is available. Download it from below link.
http://support.microsoft.com/default.aspx?scid=kb;en-us;2720211

Once downloaded just run the setup file



Check for updates again..


In my experience this fixes the problem every time.

If you'd rather use the Microsoft Fix it then use THIS link.  The reference page can be found at http://support.microsoft.com/kb/822798

Good luck!