Change updates drive on WSUS server
Genie75
I was just wondering how one would change the drive to which the updates
are downloaded to on the WSUS server, without having to reinstall WSUS.
Please let me know if you know.
Thanx, Genie75
Lawrence Garvin (MVP)
news:A6F0FD32-C2FD-4B09...@microsoft.com...
> Hello,
> I was just wondering how one would change the drive to which the updates
> are downloaded to on the WSUS server, without having to reinstall WSUS.
wsusutil movecontent logfile.log D:\WSUS
the D:\WSUS folder must exist before executing the command
documentation is in 'wsusutil /?'
--
Lawrence Garvin, M.S., MCTS, MVP-Software Distribution
Everything you need for WSUS is at
http://technet2.microsoft.com/windowsserver/en/technologies/featured/wsus/default.mspx
And, everything else is at
http://wsusinfo.onsitechsolutions.com
....
Genie75
wsusutil movecontent logfile.log f:\WSUS
and f: drive is NTFS mounted and WSUS exists, yet it fails with the
following error message:
Fatal Error: You must specify an existing absolute, local path on an NTFS
partit
ion for the new content file location.
So it looks like I will have to manually copy the files using xcopy. I am
unclear though as to exactly what I copy over. Do I copy everything in
c:\WSUS over to the new folder? Or just c:\WSUS\WSUScontent? (And then I run
the "wsusutil.exe -skipcopy" after I'm done the copy. )
"Lawrence Garvin (MVP)" wrote:
> .....
>
>
>
Lawrence Garvin (MVP)
>I tried what you said, namely:
>
> wsusutil movecontent logfile.log f:\WSUS
Perfectly functional syntax, presuming that F:\WSUS already exists.
> and f: drive is NTFS mounted and WSUS exists, yet it fails with the
> following error message:
> Fatal Error: You must specify an existing absolute, local path on an NTFS
> partit
> ion for the new content file location.
And that drive F: is a /LOCAL/ drive, and that the appropriate folder
creation and file write permissions exist in the F:\WSUS folder, and are
inheritable to all folders, subfolders, and files.
> So it looks like I will have to manually copy the files using xcopy.
That won't help. All that will do is break your WSUS installation. Assuming
you do use XCOPY, you'll still have to run this command:
wsusutil movecontent logfile.log f:\WSUS -skipcopy
which will just gripe, again, (possibly) about your F:\WSUS folder.
> I am
> unclear though as to exactly what I copy over. Do I copy everything in
> c:\WSUS over to the new folder? Or just c:\WSUS\WSUScontent? (And then I
> run
> the "wsusutil.exe -skipcopy" after I'm done the copy. )
xcopy C:\WSUS\WSUSContent F:\WSUS\WSUSContent /s /e /v /i /q /k /o
And yes.. then run the command with -skipcopy
But before you do all of that, you should verify that the permissions for
F:\WSUS are =identical= to the permissions for C:\WSUS.
Note, also, that C:\WSUS\MSSQL%WSUS (if it exists) will still contain your
WSUS database.
Lawrence Garvin (MVP)
news:uIHaC6VU...@TK2MSFTNGP05.phx.gbl...
> "Genie75" <Gen...@discussions.microsoft.com> wrote in message
> news:53F8318E-9379-477F...@microsoft.com...
>>I tried what you said, namely:
>>
>> wsusutil movecontent logfile.log f:\WSUS
>>
>> and f: drive is NTFS mounted and WSUS exists, yet it fails with the
>> following error message:
>
>> Fatal Error: You must specify an existing absolute, local path on an NTFS
>> partit
>> ion for the new content file location.
Or.... as I sheepishly have discovered....
the arguments are in the wrong order, and the wsusutil utility is trying
to find the pathname "logfile.log".
BTW... Note To Developers(!) -- this is an /excellent/ example of why
argument FLAGS should be defined.
wsusutil -o movecontent -l logfile.log -d F:\WSUS
or
wsusutil -o movecontent -d F:\WSUS -l logfile.log
would, neither one, care about the order of the parameters if FLAGS were
defined for the wsusutil command.
(I'll post a suggestion to the WSUS team to add FLAGS to the wsusutil
command line parsing code.)
fritz
I solve Fatal Error in this way:
i gave temporary "full control" to everyone on f:\wsus and wsusutil
movecontent works fine!
"Lawrence Garvin (MVP)" wrote:
> .....
>
>
>
>