Updates are being downloaded on to C:\SCE\WSUSContent\6F....CA...69 etc....

I want to move above from C drive to G drive I named WSUS.

Please help me with this as simple steps.

Thanks

Hi,

You can use wsusutil.exe command to accomplish it. Navigate to %programfiles%\update services\tools and the syntax is following:

WSUSUtil.exe movecontent g:\<content path> g:\<log path>.

You also can add -skipcopy switch to skip updates.

HTH.

I am typing the following and not working:

c:\program files\update service\tools>wsusutil.exe movecontent G:\ <content path> g:\ <log path> -skincopy

What shoud I type in <content path>?

What should I type in <log path>?

All I have is this: c:\program files\update service\tools>wsusutil.exe and Microsoft.updateservices.helathmontiring.dll

and I have created a G drive called WSUS (G

Thanks

Hi,

In this case, you can type following syntax:

WSUSUtil.exe movecontent g:\wsus g:\*.log -skipcopy

For your reference:

http://technet2.microsoft.com/windowsserver/en/library/8cca6fab-163e-451d-ab78-70b39fdb14551033.mspx?mfr=true

HTH.

I tried the above and got this error message:

C:\Program Files\Update Services\Tools>wsusutil.exe movecontent g:\wsus g:\*.log
-skipcopy

Fatal Error: You must specify an existing local directory on an NTFS partition a
s an absolute path or specify an existing UNC path for the new content file loca
tion.

Hi,

You can not move updates content to aanother remotedisk. The target WSUS folder need to exist onthesamelocal disk with original WSUS folder.You can move Wsus folder to different partition.

HTH.

This is what I had orginally:

E:\SCE\UpdateServicesPackages

E:\SCE\WsusContent\6F\CA so on folders in here.

This E: drive was getting out of disk space everyday so I decided to move this E drive to a Network Drive called G: as follow:

Wsusutil.exe movecontent g:\<content path> g:\ <log path>

And now have this:

G:\UpdateServicesPackages

G:\WsusContent\5A\6F so on folders in here.

G:\move.log

Is this looks right?

Do I have to re-configure anything on the SCE 2007 to let MS knows where to downloads updates?

Please advised.

Thanks

Hi,

From your outputs, it looks fine. You can try to re-run syschronization with Microsoft updates to verify the updates can be downloaded into the new wsuscontent properly.

HTH.

Deep,

Did I understand you right - are you trying to move the WSUS content from a local e:\ to a networkdrive g:\? I don't think (and I wouldn't recommend) storing the wsus contect on a network drive.

I would recommend adding a new disk to the server and move it to this one or to do a full backup of the existing and do a replace of it.

Hope this helps!

Bjrn Axll MVP - Advisec AB

http://blog,advisec.com

I'm trying to move the content over to a 200 gig external HD. are these the steps to follow to move this and will WSUS keep syncing.Thanks

Yes, please follow these steps and this is the recommended way to do it so yeh you are doing in the right way.

You can use wsusutil.exe command to accomplish it. Navigate to %programfiles%\update services\tools and the syntax is following:

WSUSUtil.exe movecontent g:\<content path> g:\<log path>.

You also can add -skipcopy switch to skip updates.

Thanks

Thanks deep...here is the results..But my c:\wsus\WsusContent is still taking up 32 gigs...can I just delete this sub-dir ?

TIA

C:\Program Files\Update Services\Tools>wsusutil.exe movecontent F:\wsus\WsusCont
ent f:\susmove.log
Content location is being moved. Please do not stop this program.
Content move has successfully finished.

Tia,

Congrats!

Please make sure your check your new location and it's content to make sure everything is there and record the total space at the present and then comapre it in few days and if it's more then the present then it is working 100% and also the 32 GB leave it for few days and then delete it.

Thanks and please mark this question answered.

Have a good day.

Since this thread helped me, I'd like to take the liberty of updating it a little ...

We have System Center Essentials 2010, and had a need to move the updates folder.  As this thread indicated, the wsusutil.exe movecontent command seemed to help.  But I spent quite some time trying to find documentation on using wsusutil with SCE ... wasn't entirely sure it would work. 

I found wsusutil.exe under c:\program files\update services\tools

wsusutil.exe /? yielded:

Windows Server Update Services administration utility. Try:
 wsusutil.exe help checkhealth
 wsusutil.exe help configuressl
 wsusutil.exe help configuresslproxy
 wsusutil.exe help deletefrontendserver
 wsusutil.exe help listinactiveapprovals
 wsusutil.exe help removeinactiveapprovals
 wsusutil.exe help export
 wsusutil.exe help healthmonitoring
 wsusutil.exe help import
 wsusutil.exe help listfrontendservers
 wsusutil.exe help movecontent
 wsusutil.exe help reset
 wsusutil.exe help usecustomwebsite
 wsusutil.exe help listunreferencedpackagefolders
movecontent command details:

Changes the file-system location where the WSUS server stores content, and
optionally copies any content from the old location to the new location.

and wsusutil.exe help movecontent yielded:

movecontent <content path> <log file> [-skipcopy]
<content path>: The new root for content files. The path must exist.
<log file>    : Path and filename of the log file to create.
-skipcopy     : Indicates that only the server configuration should be changed
                 and that the content files should not be copied.

 

So in our scenario, I wanted to move UPDATES from E:\data\updates to the F: partition (both locally attached hard disks). 

I had to first create f:\data\updates. While I was at it, I created f:\data\logs

Then I ran

wsusutil.exe movecontent F:\data\UPDATES F:\data\logs\movcon.log

Seems to have worked like a charm!

Edited to add:  I also noticed that the e:\data\updates had two subfolders, each of which was shared out.  The wsusutil seems to have taken care of the un-sharing from the old location and re-sharing at the new location.  One other item of note was that I had to be logged on as the serivces account to run the utility. Regular run of the mill admin didn't do it. 

• Proposed as answer by NoufalQA Wednesday, June 11, 2014 8:17 AM
• Unproposed as answer by NoufalQA Wednesday, June 11, 2014 8:18 AM

Since this thread helped me, I'd like to take the liberty of updating it a little ...

We have System Center Essentials 2010, and had a need to move the updates folder.  As this thread indicated, the wsusutil.exe movecontent command seemed to help.  But I spent quite some time trying to find documentation on using wsusutil with SCE ... wasn't entirely sure it would work. 

I found wsusutil.exe under c:\program files\update services\tools

wsusutil.exe /? yielded:

Windows Server Update Services administration utility. Try:
 wsusutil.exe help checkhealth
 wsusutil.exe help configuressl
 wsusutil.exe help configuresslproxy
 wsusutil.exe help deletefrontendserver
 wsusutil.exe help listinactiveapprovals
 wsusutil.exe help removeinactiveapprovals
 wsusutil.exe help export
 wsusutil.exe help healthmonitoring
 wsusutil.exe help import
 wsusutil.exe help listfrontendservers
 wsusutil.exe help movecontent
 wsusutil.exe help reset
 wsusutil.exe help usecustomwebsite
 wsusutil.exe help listunreferencedpackagefolders
movecontent command details:

Changes the file-system location where the WSUS server stores content, and
optionally copies any content from the old location to the new location.

and wsusutil.exe help movecontent yielded:

movecontent <content path> <log file> [-skipcopy]
<content path>: The new root for content files. The path must exist.
<log file>    : Path and filename of the log file to create.
-skipcopy     : Indicates that only the server configuration should be changed
                 and that the content files should not be copied.

 

So in our scenario, I wanted to move UPDATES from E:\data\updates to the F: partition (both locally attached hard disks). 

I had to first create f:\data\updates. While I was at it, I created f:\data\logs

Then I ran

wsusutil.exe movecontent F:\data\UPDATES F:\data\logs\movcon.log

Seems to have worked like a charm!

Edited to add:  I also noticed that the e:\data\updates had two subfolders, each of which was shared out.  The wsusutil seems to have taken care of the un-sharing from the old location and re-sharing at the new location.  One other item of note was that I had to be logged on as the serivces account to run the utility. Regular run of the mill admin didn't do it. 

• Proposed as answer by NoufalQA Wednesday, June 11, 2014 8:17 AM
• Unproposed as answer by NoufalQA Wednesday, June 11, 2014 8:18 AM

Since this thread helped me, I'd like to take the liberty of updating it a little ...

We have System Center Essentials 2010, and had a need to move the updates folder.  As this thread indicated, the wsusutil.exe movecontent command seemed to help.  But I spent quite some time trying to find documentation on using wsusutil with SCE ... wasn't entirely sure it would work. 

I found wsusutil.exe under c:\program files\update services\tools

wsusutil.exe /? yielded:

Windows Server Update Services administration utility. Try:
 wsusutil.exe help checkhealth
 wsusutil.exe help configuressl
 wsusutil.exe help configuresslproxy
 wsusutil.exe help deletefrontendserver
 wsusutil.exe help listinactiveapprovals
 wsusutil.exe help removeinactiveapprovals
 wsusutil.exe help export
 wsusutil.exe help healthmonitoring
 wsusutil.exe help import
 wsusutil.exe help listfrontendservers
 wsusutil.exe help movecontent
 wsusutil.exe help reset
 wsusutil.exe help usecustomwebsite
 wsusutil.exe help listunreferencedpackagefolders
movecontent command details:

Changes the file-system location where the WSUS server stores content, and
optionally copies any content from the old location to the new location.

and wsusutil.exe help movecontent yielded:

movecontent <content path> <log file> [-skipcopy]
<content path>: The new root for content files. The path must exist.
<log file>    : Path and filename of the log file to create.
-skipcopy     : Indicates that only the server configuration should be changed
                 and that the content files should not be copied.

 

So in our scenario, I wanted to move UPDATES from E:\data\updates to the F: partition (both locally attached hard disks). 

I had to first create f:\data\updates. While I was at it, I created f:\data\logs

Then I ran

wsusutil.exe movecontent F:\data\UPDATES F:\data\logs\movcon.log

Seems to have worked like a charm!

Edited to add:  I also noticed that the e:\data\updates had two subfolders, each of which was shared out.  The wsusutil seems to have taken care of the un-sharing from the old location and re-sharing at the new location.  One other item of note was that I had to be logged on as the serivces account to run the utility. Regular run of the mill admin didn't do it. 

• Proposed as answer by NoufalQA Wednesday, June 11, 2014 8:17 AM
• Unproposed as answer by NoufalQA Wednesday, June 11, 2014 8:18 AM

Since this thread helped me, I'd like to take the liberty of updating it a little ...

We have System Center Essentials 2010, and had a need to move the updates folder.  As this thread indicated, the wsusutil.exe movecontent command seemed to help.  But I spent quite some time trying to find documentation on using wsusutil with SCE ... wasn't entirely sure it would work. 

I found wsusutil.exe under c:\program files\update services\tools

wsusutil.exe /? yielded:

Windows Server Update Services administration utility. Try:
 wsusutil.exe help checkhealth
 wsusutil.exe help configuressl
 wsusutil.exe help configuresslproxy
 wsusutil.exe help deletefrontendserver
 wsusutil.exe help listinactiveapprovals
 wsusutil.exe help removeinactiveapprovals
 wsusutil.exe help export
 wsusutil.exe help healthmonitoring
 wsusutil.exe help import
 wsusutil.exe help listfrontendservers
 wsusutil.exe help movecontent
 wsusutil.exe help reset
 wsusutil.exe help usecustomwebsite
 wsusutil.exe help listunreferencedpackagefolders
movecontent command details:

Changes the file-system location where the WSUS server stores content, and
optionally copies any content from the old location to the new location.

and wsusutil.exe help movecontent yielded:

movecontent <content path> <log file> [-skipcopy]
<content path>: The new root for content files. The path must exist.
<log file>    : Path and filename of the log file to create.
-skipcopy     : Indicates that only the server configuration should be changed
                 and that the content files should not be copied.

 

So in our scenario, I wanted to move UPDATES from E:\data\updates to the F: partition (both locally attached hard disks). 

I had to first create f:\data\updates. While I was at it, I created f:\data\logs

Then I ran

wsusutil.exe movecontent F:\data\UPDATES F:\data\logs\movcon.log

Seems to have worked like a charm!

Edited to add:  I also noticed that the e:\data\updates had two subfolders, each of which was shared out.  The wsusutil seems to have taken care of the un-sharing from the old location and re-sharing at the new location.  One other item of note was that I had to be logged on as the serivces account to run the utility. Regular run of the mill admin didn't do it. 

• Proposed as answer by NoufalQA Wednesday, June 11, 2014 8:17 AM
• Unproposed as answer by NoufalQA Wednesday, June 11, 2014 8:18 AM

Since this thread helped me, I'd like to take the liberty of updating it a little ...

We have System Center Essentials 2010, and had a need to move the updates folder.  As this thread indicated, the wsusutil.exe movecontent command seemed to help.  But I spent quite some time trying to find documentation on using wsusutil with SCE ... wasn't entirely sure it would work. 

I found wsusutil.exe under c:\program files\update services\tools

wsusutil.exe /? yielded:

Windows Server Update Services administration utility. Try:
 wsusutil.exe help checkhealth
 wsusutil.exe help configuressl
 wsusutil.exe help configuresslproxy
 wsusutil.exe help deletefrontendserver
 wsusutil.exe help listinactiveapprovals
 wsusutil.exe help removeinactiveapprovals
 wsusutil.exe help export
 wsusutil.exe help healthmonitoring
 wsusutil.exe help import
 wsusutil.exe help listfrontendservers
 wsusutil.exe help movecontent
 wsusutil.exe help reset
 wsusutil.exe help usecustomwebsite
 wsusutil.exe help listunreferencedpackagefolders
movecontent command details:

Changes the file-system location where the WSUS server stores content, and
optionally copies any content from the old location to the new location.

and wsusutil.exe help movecontent yielded:

movecontent <content path> <log file> [-skipcopy]
<content path>: The new root for content files. The path must exist.
<log file>    : Path and filename of the log file to create.
-skipcopy     : Indicates that only the server configuration should be changed
                 and that the content files should not be copied.

 

So in our scenario, I wanted to move UPDATES from E:\data\updates to the F: partition (both locally attached hard disks). 

I had to first create f:\data\updates. While I was at it, I created f:\data\logs

Then I ran

wsusutil.exe movecontent F:\data\UPDATES F:\data\logs\movcon.log

Seems to have worked like a charm!

Edited to add:  I also noticed that the e:\data\updates had two subfolders, each of which was shared out.  The wsusutil seems to have taken care of the un-sharing from the old location and re-sharing at the new location.  One other item of note was that I had to be logged on as the serivces account to run the utility. Regular run of the mill admin didn't do it. 

• Proposed as answer by NoufalQA Wednesday, June 11, 2014 8:17 AM
• Unproposed as answer by NoufalQA Wednesday, June 11, 2014 8:18 AM

Since this thread helped me, I'd like to take the liberty of updating it a little ...

We have System Center Essentials 2010, and had a need to move the updates folder.  As this thread indicated, the wsusutil.exe movecontent command seemed to help.  But I spent quite some time trying to find documentation on using wsusutil with SCE ... wasn't entirely sure it would work. 

I found wsusutil.exe under c:\program files\update services\tools

wsusutil.exe /? yielded:

Windows Server Update Services administration utility. Try:
 wsusutil.exe help checkhealth
 wsusutil.exe help configuressl
 wsusutil.exe help configuresslproxy
 wsusutil.exe help deletefrontendserver
 wsusutil.exe help listinactiveapprovals
 wsusutil.exe help removeinactiveapprovals
 wsusutil.exe help export
 wsusutil.exe help healthmonitoring
 wsusutil.exe help import
 wsusutil.exe help listfrontendservers
 wsusutil.exe help movecontent
 wsusutil.exe help reset
 wsusutil.exe help usecustomwebsite
 wsusutil.exe help listunreferencedpackagefolders
movecontent command details:

Changes the file-system location where the WSUS server stores content, and
optionally copies any content from the old location to the new location.

and wsusutil.exe help movecontent yielded:

movecontent <content path> <log file> [-skipcopy]
<content path>: The new root for content files. The path must exist.
<log file>    : Path and filename of the log file to create.
-skipcopy     : Indicates that only the server configuration should be changed
                 and that the content files should not be copied.

 

So in our scenario, I wanted to move UPDATES from E:\data\updates to the F: partition (both locally attached hard disks). 

I had to first create f:\data\updates. While I was at it, I created f:\data\logs

Then I ran

wsusutil.exe movecontent F:\data\UPDATES F:\data\logs\movcon.log

Seems to have worked like a charm!

Edited to add:  I also noticed that the e:\data\updates had two subfolders, each of which was shared out.  The wsusutil seems to have taken care of the un-sharing from the old location and re-sharing at the new location.  One other item of note was that I had to be logged on as the serivces account to run the utility. Regular run of the mill admin didn't do it. 

• Proposed as answer by NoufalQA Wednesday, June 11, 2014 8:17 AM
• Unproposed as answer by NoufalQA Wednesday, June 11, 2014 8:18 AM

Since this thread helped me, I'd like to take the liberty of updating it a little ...

We have System Center Essentials 2010, and had a need to move the updates folder.  As this thread indicated, the wsusutil.exe movecontent command seemed to help.  But I spent quite some time trying to find documentation on using wsusutil with SCE ... wasn't entirely sure it would work. 

I found wsusutil.exe under c:\program files\update services\tools

wsusutil.exe /? yielded:

Windows Server Update Services administration utility. Try:
 wsusutil.exe help checkhealth
 wsusutil.exe help configuressl
 wsusutil.exe help configuresslproxy
 wsusutil.exe help deletefrontendserver
 wsusutil.exe help listinactiveapprovals
 wsusutil.exe help removeinactiveapprovals
 wsusutil.exe help export
 wsusutil.exe help healthmonitoring
 wsusutil.exe help import
 wsusutil.exe help listfrontendservers
 wsusutil.exe help movecontent
 wsusutil.exe help reset
 wsusutil.exe help usecustomwebsite
 wsusutil.exe help listunreferencedpackagefolders
movecontent command details:

Changes the file-system location where the WSUS server stores content, and
optionally copies any content from the old location to the new location.

and wsusutil.exe help movecontent yielded:

movecontent <content path> <log file> [-skipcopy]
<content path>: The new root for content files. The path must exist.
<log file>    : Path and filename of the log file to create.
-skipcopy     : Indicates that only the server configuration should be changed
                 and that the content files should not be copied.

 

So in our scenario, I wanted to move UPDATES from E:\data\updates to the F: partition (both locally attached hard disks). 

I had to first create f:\data\updates. While I was at it, I created f:\data\logs

Then I ran

wsusutil.exe movecontent F:\data\UPDATES F:\data\logs\movcon.log

Seems to have worked like a charm!

Edited to add:  I also noticed that the e:\data\updates had two subfolders, each of which was shared out.  The wsusutil seems to have taken care of the un-sharing from the old location and re-sharing at the new location.  One other item of note was that I had to be logged on as the serivces account to run the utility. Regular run of the mill admin didn't do it. 

• Proposed as answer by NoufalQA Wednesday, June 11, 2014 8:17 AM
• Unproposed as answer by NoufalQA Wednesday, June 11, 2014 8:18 AM

Since this thread helped me, I'd like to take the liberty of updating it a little ...

We have System Center Essentials 2010, and had a need to move the updates folder.  As this thread indicated, the wsusutil.exe movecontent command seemed to help.  But I spent quite some time trying to find documentation on using wsusutil with SCE ... wasn't entirely sure it would work. 

I found wsusutil.exe under c:\program files\update services\tools

wsusutil.exe /? yielded:

Windows Server Update Services administration utility. Try:
 wsusutil.exe help checkhealth
 wsusutil.exe help configuressl
 wsusutil.exe help configuresslproxy
 wsusutil.exe help deletefrontendserver
 wsusutil.exe help listinactiveapprovals
 wsusutil.exe help removeinactiveapprovals
 wsusutil.exe help export
 wsusutil.exe help healthmonitoring
 wsusutil.exe help import
 wsusutil.exe help listfrontendservers
 wsusutil.exe help movecontent
 wsusutil.exe help reset
 wsusutil.exe help usecustomwebsite
 wsusutil.exe help listunreferencedpackagefolders
movecontent command details:

Changes the file-system location where the WSUS server stores content, and
optionally copies any content from the old location to the new location.

and wsusutil.exe help movecontent yielded:

movecontent <content path> <log file> [-skipcopy]
<content path>: The new root for content files. The path must exist.
<log file>    : Path and filename of the log file to create.
-skipcopy     : Indicates that only the server configuration should be changed
                 and that the content files should not be copied.

 

So in our scenario, I wanted to move UPDATES from E:\data\updates to the F: partition (both locally attached hard disks). 

I had to first create f:\data\updates. While I was at it, I created f:\data\logs

Then I ran

wsusutil.exe movecontent F:\data\UPDATES F:\data\logs\movcon.log

Seems to have worked like a charm!

Edited to add:  I also noticed that the e:\data\updates had two subfolders, each of which was shared out.  The wsusutil seems to have taken care of the un-sharing from the old location and re-sharing at the new location.  One other item of note was that I had to be logged on as the serivces account to run the utility. Regular run of the mill admin didn't do it. 

• Proposed as answer by NoufalQA Wednesday, June 11, 2014 8:17 AM
• Unproposed as answer by NoufalQA Wednesday, June 11, 2014 8:18 AM

Since this thread helped me, I'd like to take the liberty of updating it a little ...

We have System Center Essentials 2010, and had a need to move the updates folder.  As this thread indicated, the wsusutil.exe movecontent command seemed to help.  But I spent quite some time trying to find documentation on using wsusutil with SCE ... wasn't entirely sure it would work. 

I found wsusutil.exe under c:\program files\update services\tools

wsusutil.exe /? yielded:

Windows Server Update Services administration utility. Try:
 wsusutil.exe help checkhealth
 wsusutil.exe help configuressl
 wsusutil.exe help configuresslproxy
 wsusutil.exe help deletefrontendserver
 wsusutil.exe help listinactiveapprovals
 wsusutil.exe help removeinactiveapprovals
 wsusutil.exe help export
 wsusutil.exe help healthmonitoring
 wsusutil.exe help import
 wsusutil.exe help listfrontendservers
 wsusutil.exe help movecontent
 wsusutil.exe help reset
 wsusutil.exe help usecustomwebsite
 wsusutil.exe help listunreferencedpackagefolders
movecontent command details:

Changes the file-system location where the WSUS server stores content, and
optionally copies any content from the old location to the new location.

and wsusutil.exe help movecontent yielded:

movecontent <content path> <log file> [-skipcopy]
<content path>: The new root for content files. The path must exist.
<log file>    : Path and filename of the log file to create.
-skipcopy     : Indicates that only the server configuration should be changed
                 and that the content files should not be copied.

 

So in our scenario, I wanted to move UPDATES from E:\data\updates to the F: partition (both locally attached hard disks). 

I had to first create f:\data\updates. While I was at it, I created f:\data\logs

Then I ran

wsusutil.exe movecontent F:\data\UPDATES F:\data\logs\movcon.log

Seems to have worked like a charm!

Edited to add:  I also noticed that the e:\data\updates had two subfolders, each of which was shared out.  The wsusutil seems to have taken care of the un-sharing from the old location and re-sharing at the new location.  One other item of note was that I had to be logged on as the serivces account to run the utility. Regular run of the mill admin didn't do it. 

• Proposed as answer by NoufalQA Wednesday, June 11, 2014 8:17 AM
• Unproposed as answer by NoufalQA Wednesday, June 11, 2014 8:18 AM

Since this thread helped me, I'd like to take the liberty of updating it a little ...

We have System Center Essentials 2010, and had a need to move the updates folder.  As this thread indicated, the wsusutil.exe movecontent command seemed to help.  But I spent quite some time trying to find documentation on using wsusutil with SCE ... wasn't entirely sure it would work. 

I found wsusutil.exe under c:\program files\update services\tools

wsusutil.exe /? yielded:

Windows Server Update Services administration utility. Try:
 wsusutil.exe help checkhealth
 wsusutil.exe help configuressl
 wsusutil.exe help configuresslproxy
 wsusutil.exe help deletefrontendserver
 wsusutil.exe help listinactiveapprovals
 wsusutil.exe help removeinactiveapprovals
 wsusutil.exe help export
 wsusutil.exe help healthmonitoring
 wsusutil.exe help import
 wsusutil.exe help listfrontendservers
 wsusutil.exe help movecontent
 wsusutil.exe help reset
 wsusutil.exe help usecustomwebsite
 wsusutil.exe help listunreferencedpackagefolders
movecontent command details:

Changes the file-system location where the WSUS server stores content, and
optionally copies any content from the old location to the new location.

and wsusutil.exe help movecontent yielded:

movecontent <content path> <log file> [-skipcopy]
<content path>: The new root for content files. The path must exist.
<log file>    : Path and filename of the log file to create.
-skipcopy     : Indicates that only the server configuration should be changed
                 and that the content files should not be copied.

 

So in our scenario, I wanted to move UPDATES from E:\data\updates to the F: partition (both locally attached hard disks). 

I had to first create f:\data\updates. While I was at it, I created f:\data\logs

Then I ran

wsusutil.exe movecontent F:\data\UPDATES F:\data\logs\movcon.log

Seems to have worked like a charm!

Edited to add:  I also noticed that the e:\data\updates had two subfolders, each of which was shared out.  The wsusutil seems to have taken care of the un-sharing from the old location and re-sharing at the new location.  One other item of note was that I had to be logged on as the serivces account to run the utility. Regular run of the mill admin didn't do it. 

• Proposed as answer by NoufalQA Wednesday, June 11, 2014 8:17 AM
• Unproposed as answer by NoufalQA Wednesday, June 11, 2014 8:18 AM

Since this thread helped me, I'd like to take the liberty of updating it a little ...

We have System Center Essentials 2010, and had a need to move the updates folder.  As this thread indicated, the wsusutil.exe movecontent command seemed to help.  But I spent quite some time trying to find documentation on using wsusutil with SCE ... wasn't entirely sure it would work. 

I found wsusutil.exe under c:\program files\update services\tools

wsusutil.exe /? yielded:

Windows Server Update Services administration utility. Try:
 wsusutil.exe help checkhealth
 wsusutil.exe help configuressl
 wsusutil.exe help configuresslproxy
 wsusutil.exe help deletefrontendserver
 wsusutil.exe help listinactiveapprovals
 wsusutil.exe help removeinactiveapprovals
 wsusutil.exe help export
 wsusutil.exe help healthmonitoring
 wsusutil.exe help import
 wsusutil.exe help listfrontendservers
 wsusutil.exe help movecontent
 wsusutil.exe help reset
 wsusutil.exe help usecustomwebsite
 wsusutil.exe help listunreferencedpackagefolders
movecontent command details:

Changes the file-system location where the WSUS server stores content, and
optionally copies any content from the old location to the new location.

and wsusutil.exe help movecontent yielded:

movecontent <content path> <log file> [-skipcopy]
<content path>: The new root for content files. The path must exist.
<log file>    : Path and filename of the log file to create.
-skipcopy     : Indicates that only the server configuration should be changed
                 and that the content files should not be copied.

 

So in our scenario, I wanted to move UPDATES from E:\data\updates to the F: partition (both locally attached hard disks). 

I had to first create f:\data\updates. While I was at it, I created f:\data\logs

Then I ran

wsusutil.exe movecontent F:\data\UPDATES F:\data\logs\movcon.log

Seems to have worked like a charm!

Edited to add:  I also noticed that the e:\data\updates had two subfolders, each of which was shared out.  The wsusutil seems to have taken care of the un-sharing from the old location and re-sharing at the new location.  One other item of note was that I had to be logged on as the serivces account to run the utility. Regular run of the mill admin didn't do it. 

• Proposed as answer by NoufalQA Wednesday, June 11, 2014 8:17 AM
• Unproposed as answer by NoufalQA Wednesday, June 11, 2014 8:18 AM

Since this thread helped me, I'd like to take the liberty of updating it a little ...

We have System Center Essentials 2010, and had a need to move the updates folder.  As this thread indicated, the wsusutil.exe movecontent command seemed to help.  But I spent quite some time trying to find documentation on using wsusutil with SCE ... wasn't entirely sure it would work. 

I found wsusutil.exe under c:\program files\update services\tools

wsusutil.exe /? yielded:

Windows Server Update Services administration utility. Try:
 wsusutil.exe help checkhealth
 wsusutil.exe help configuressl
 wsusutil.exe help configuresslproxy
 wsusutil.exe help deletefrontendserver
 wsusutil.exe help listinactiveapprovals
 wsusutil.exe help removeinactiveapprovals
 wsusutil.exe help export
 wsusutil.exe help healthmonitoring
 wsusutil.exe help import
 wsusutil.exe help listfrontendservers
 wsusutil.exe help movecontent
 wsusutil.exe help reset
 wsusutil.exe help usecustomwebsite
 wsusutil.exe help listunreferencedpackagefolders
movecontent command details:

Changes the file-system location where the WSUS server stores content, and
optionally copies any content from the old location to the new location.

and wsusutil.exe help movecontent yielded:

movecontent <content path> <log file> [-skipcopy]
<content path>: The new root for content files. The path must exist.
<log file>    : Path and filename of the log file to create.
-skipcopy     : Indicates that only the server configuration should be changed
                 and that the content files should not be copied.

 

So in our scenario, I wanted to move UPDATES from E:\data\updates to the F: partition (both locally attached hard disks). 

I had to first create f:\data\updates. While I was at it, I created f:\data\logs

Then I ran

wsusutil.exe movecontent F:\data\UPDATES F:\data\logs\movcon.log

Seems to have worked like a charm!

Edited to add:  I also noticed that the e:\data\updates had two subfolders, each of which was shared out.  The wsusutil seems to have taken care of the un-sharing from the old location and re-sharing at the new location.  One other item of note was that I had to be logged on as the serivces account to run the utility. Regular run of the mill admin didn't do it. 

• Proposed as answer by NoufalQA Wednesday, June 11, 2014 8:17 AM
• Unproposed as answer by NoufalQA Wednesday, June 11, 2014 8:18 AM

Since this thread helped me, I'd like to take the liberty of updating it a little ...

We have System Center Essentials 2010, and had a need to move the updates folder.  As this thread indicated, the wsusutil.exe movecontent command seemed to help.  But I spent quite some time trying to find documentation on using wsusutil with SCE ... wasn't entirely sure it would work. 

I found wsusutil.exe under c:\program files\update services\tools

wsusutil.exe /? yielded:

Windows Server Update Services administration utility. Try:
 wsusutil.exe help checkhealth
 wsusutil.exe help configuressl
 wsusutil.exe help configuresslproxy
 wsusutil.exe help deletefrontendserver
 wsusutil.exe help listinactiveapprovals
 wsusutil.exe help removeinactiveapprovals
 wsusutil.exe help export
 wsusutil.exe help healthmonitoring
 wsusutil.exe help import
 wsusutil.exe help listfrontendservers
 wsusutil.exe help movecontent
 wsusutil.exe help reset
 wsusutil.exe help usecustomwebsite
 wsusutil.exe help listunreferencedpackagefolders
movecontent command details:

Changes the file-system location where the WSUS server stores content, and
optionally copies any content from the old location to the new location.

and wsusutil.exe help movecontent yielded:

movecontent <content path> <log file> [-skipcopy]
<content path>: The new root for content files. The path must exist.
<log file>    : Path and filename of the log file to create.
-skipcopy     : Indicates that only the server configuration should be changed
                 and that the content files should not be copied.

 

So in our scenario, I wanted to move UPDATES from E:\data\updates to the F: partition (both locally attached hard disks). 

I had to first create f:\data\updates. While I was at it, I created f:\data\logs

Then I ran

wsusutil.exe movecontent F:\data\UPDATES F:\data\logs\movcon.log

Seems to have worked like a charm!

Edited to add:  I also noticed that the e:\data\updates had two subfolders, each of which was shared out.  The wsusutil seems to have taken care of the un-sharing from the old location and re-sharing at the new location.  One other item of note was that I had to be logged on as the serivces account to run the utility. Regular run of the mill admin didn't do it. 

• Proposed as answer by NoufalQA Wednesday, June 11, 2014 8:17 AM
• Unproposed as answer by NoufalQA Wednesday, June 11, 2014 8:18 AM

Not skincopy , It is skipcopy

It works

wsusutil.exe movecontent C:\Sources\WSUS C:\Sources\WSUS\Logs\wsusmove.log

This post solved my problem.  The new directory MUST exist prior to executing the command

Thanks.