I have configured WSUS to work out of our production SQL database, and it
seems to be connecting fine...
However, I had an issue when trying to approve updates so they would
download automatically. Seems as though the updates were wanting to store
themselves under c:\program files\update services\Content, when there was in
fact, no 'content' folder there - so then, I would receive the following
error in the event log every time I tried to download approved updates to
the server:
Source: Windows Server Update
Category: Synchronization
Type: Error
Event ID: 364
"Content file download failed. Reason: Error calling
[kernel32.dll]:CreateDirectory(C:\Program Files\Update Services\Content\E5)
Source File: Destination File: ."
When I manually created the 'content' folder, the update (I approved only
one as a test) downloaded fine. Obviously, this is a glitch that somehow
made it past the testing folks.
So, my question is: Will my updates be saving to this folder unless I
specify differently somehow (I assume by using the WSUSUtil.exe utility), or
will these files move to the proper location that I specified during setup,
which is 'D:\WSUS'?
Very strange, if you ask me.
Rob
maximillianx - 08 Jun 2005 05:17 GMT
Interesting - - -
I had to edit the SUSDB SQL database and change the
'LocalContentCacheLocation' field in the tbConfigurationB table to
"D:\WSUS\WSUSContent\" (it was set to c:\program files\update
services\content\) - and then I restarted my frontend WSUS server. Seems to
have done the trick.
I'm watching files download to that folder now with no issues (at least at
the moment).
Rob
Sidenote: I did uninstall and re-install the WSUS frontend server,
specifying content_dir in my command-line switches, but it had no affect.
I'm thinking since it actually isn't talking to the DB during installation
may be the reason why it failed.
>I have configured WSUS to work out of our production SQL database, and it
>seems to be connecting fine...
[quoted text clipped - 27 lines]
>
> Rob