Pico
Joined: 18 Jan 2004
Posts: 250
Location: HostMachine.net
|
Posted: 17.2.2008, 20:09 Post subject: The permissions on directory \WSUS\WsusContent are incorrect |
|
|
Tipical error for WSUS 3.0 starts like all-of-the-sudden. WSUS works fine for few months, then, all of the sudden, it starts reporting problems in Application log:
Code: Event Type: Error
Event Source: Windows Server Update Services
Event Category: Core
Event ID: 10012
Date: 17.2.2008
Time: 19:38:55
User: N/A
Computer: SERVER
Description:
The permissions on directory E:\WSUS\WsusContent are incorrect.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
---
Event Type: Error
Event Source: Windows Server Update Services
Event Category: Clients
Event ID: 13042
Date: 17.2.2008
Time: 19:38:55
User: N/A
Computer: SERVER
Description:
Self-update is not working.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
The main problem is, that WSUS creates folder with correct permissions, but has no tool to repair permissions, if something goes wrong.
In addition, WSUS has tool to check its functionality:
wsusutil checkhealth
This tool can only report wrong permissions, but not which permissions are missing. Also, there is no /PleaseRepairPermissions switch, which is a bit un-professional from MS.
So, what you need to do is:
FIRST, check if all permissions are set correctly, following the guides here:
http://technet2.microsoft.com/windowsserver/en/library/94d1385f-4872-4c29-8822-3a4ec5e45ae41033.mspx?mfr=true
SECOND, if your \WSUS folder is NOT on your Windows SYSTEM drive, you need to add READ permissions for NETWORK SERVICE to the whole drive, where \WSUS folder resides.
This is a bug from .NET FrameWork, which does not update permissions on non-system drives.
THIRD, if you still get ERROR The permissions on directory \WSUS\WsusContent are incorrect, try this workaround, which I invented by myself:
go to folder \WSUS\WsusContent and create a blank file, named ContentFolderAclsCheck.txt
assign Read/Write/Modify permissions to this file for NETWORK SERVICE account
then restart Update Services service
run wsusutil checkhealth from command-line and then check Application event log; there should be no WSUS-related errors anymore
also, ContentFolderAclsCheck.txt file should vanish from \WSUS\WsusContent folder
|
|