The permissions on directory \WSUS\WsusContent are incorrect |
Pico
Site Admin
|
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:
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:
|
||||||||||||||
_________________ Site admin alias Labsy Vsi nasveti in tehnične rešitve so podani v dobri veri in za ljudi z razčiščenimi pojmi o veljavni zakonodaji. Odgovornost prevzemam izključno in samo za tiste posege, ki jih opravim lastnoročno. |
The permissions on directory \WSUS\WsusContent are incorrect |
|
||
Za pogon skrbi modificirana verzija php BB engine © 2001-2005 php BB Group
Stilska oprema foruma by Morpheus. Code edited by Pico.
HTML in XML verziji foruma: HTML forum | XML SiteMap
Stilska oprema foruma by Morpheus. Code edited by Pico.
HTML in XML verziji foruma: HTML forum | XML SiteMap