You need to ensure that the Windows Server Update Services (WSUS) update files are stored on the new volume

You have a server named WSUS1 that runs Windows Server 2012 R2. WSUS1 has the Windows
Server Update Services server role installed and has one volume.

You add a new hard disk to WSUS1 and then create a volume on the hard disk.
You need to ensure that the Windows Server Update Services (WSUS) update files are stored on the
new volume.
What should you do?

A.
From the Update Services console, configure the Update Files and Languages option.

B.
From the Update Services console, run the Windows Server Update Services Configuration
Wizard.

C.
From a command prompt, run wsusutil.exe and specify the export parameter.

D.
From a command prompt, run wsusutil.exe and specify the movecontent parameter.

Explanation:
Local Storage Considerations
If you decide to store update files on your server, the recommended minimum disk size is 30 GB.
However, depending on the synchronization options you specify, you might need to use a larger disk.
For example, when specifying advanced synchronization options, as in the following procedure, if
you select options to download multiple languages and/or the option to download express
installation files, your server disk can easily reach 30 GB. Therefore if you choose any of these
options, install a larger disk (for example, 100 GB).
If your disk gets full, you can install a new, larger disk and then move the update files to the new
location. To do this, after you create the new disk drive, you will need to run the WSUSutil.exetool
(with the movecontent command) to move the update files to the new disk. For this procedure, see
Managing WSUS from the Command Line.
For example, if D:\WSUS1 is the new path for local WSUS update storage, D:\move. log is the path to
the log file, and you wanted to copy the old files to the new location, you would type: wsusutil.exe
movecontent D:\WSUS1\ D:\move. Log.
Note: If you do not want to use WSUSutil.exe to change the location of local WSUS update storage,
you can also use NTFS functionality to add a partition to the current location of local WSUS update
storage. For more information about NTFS, go to Help and Support Center in Windows Server 2003.
Syntax
At the command line %drive%\Program Files\Update Services\Tools>, type:
wsusutilmovecontentcontentpathlogfile -skipcopy [/?]
The parameters are defined in the following table.
contentpath – the new root for content files. The path must exist.
logfile – the path and file name 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.
/help or /? – displays command-line help for movecontent command.
References:
httHYPERLINK “http://blogs.technet.com/b/sus/archive/2008/05/19/wsus-how-to-change-thelocation-where-wsus-stores-updates-locally.aspx#_blank”pHYPERLINK
“http://blogs.technet.com/b/sus/archive/2008/05/19/wsus-how-to-change-the-location-wherewsus-stores-updates-locally.aspx#_blank”: //blogsHYPERLINK
“http://blogs.technet.com/b/sus/archive/2008/05/19/wsus-how-to-change-the-location-wherewsus-stores-updates-locally.aspx#_blank”.HYPERLINK
“http://blogs.technet.com/b/sus/archive/2008/05/19/wsus-how-to-change-the-location-wherewsus-stores-updates-locally.aspx#_blank”technetHYPERLINK
“http://blogs.technet.com/b/sus/archive/2008/05/19/wsus-how-to-change-the-location-where-

wsus-stores-updates-locally.aspx#_blank”.HYPERLINK
“http://blogs.technet.com/b/sus/archive/2008/05/19/wsus-how-to-change-the-location-wherewsus-stores-updates-locally.aspx#_blank”com/b/sus/archive/2008/05/19/wsus-how-to-change-thelocation-whHYPERLINK “http://blogs.technet.com/b/sus/archive/2008/05/19/wsus-how-to-changethe-location-where-wsus-stores-updates-locally.aspx#_blank”ere-wsus-stores-updateslocallyHYPERLINK “http://blogs.technet.com/b/sus/archive/2008/05/19/wsus-how-to-change-thelocation-where-wsus-stores-updates-locally.aspx#_blank”.HYPERLINK
“http://blogs.technet.com/b/sus/archive/2008/05/19/wsus-how-to-change-the-location-wherewsus-stores-updates-locally.aspx#_blank”aspx
httpHYPERLINK “http://technet.microsoft.com/en-us/library/cc720475(v=ws.10).aspx#_blank”:
//technetHYPERLINK “http://technet.microsoft.com/enus/library/cc720475(v=ws.10).aspx#_blank”.HYPERLINK “http://technet.microsoft.com/enus/library/cc720475(v=ws.10).aspx#_blank”microsoftHYPERLINK “http://technet.microsoft.com/enus/library/cc720475(v=ws.10).aspx#_blank”.HYPERLINK “http://technet.microsoft.com/enus/library/cc720475(v=ws.10).aspx#_blank”com/en-us/library/cc720475(v=wsHYPERLINK
“http://technet.microsoft.com/en-us/library/cc720475(v=ws.10).aspx#_blank”.HYPERLINK
“http://technet.microsoft.com/en-us/library/cc720475(v=ws.10).aspx#_blank”10)HYPERLINK
“http://technet.microsoft.com/en-us/library/cc720475(v=ws.10).aspx#_blank”.HYPERLINK
“http://technet.microsoft.com/en-us/library/cc720475(v=ws.10).aspx#_blank”aHYPERLINK
“http://technet.microsoft.com/en-us/library/cc720475(v=ws.10).aspx#_blank”spx
httpHYPERLINK “http://technet.microsoft.com/en-us/library/cc708480(v=ws.10).aspx#_blank”:
//technetHYPERLINK “http://technet.microsoft.com/enus/library/cc708480(v=ws.10).aspx#_blank”.HYPERLINK “http://technet.microsoft.com/enus/library/cc708480(v=ws.10).aspx#_blank”microsoftHYPERLINK “http://technet.microsoft.com/enus/library/cc708480(v=ws.10).aspx#_blank”.HYPERLINK “http://technet.microsoft.com/enus/library/cc708480(v=ws.10).aspx#_blank”com/en-us/library/cc7084HYPERLINK
“http://technet.microsoft.com/enus/library/cc708480(v=ws.10).aspx#_blank”80%28v=wsHYPERLINK
“http://technet.microsoft.com/en-us/library/cc708480(v=ws.10).aspx#_blank”.HYPERLINK
“http://technet.microsoft.com/en-us/library/cc708480(v=ws.10).aspx#_blank”10%29HYPERLINK
“http://technet.microsoft.com/en-us/library/cc708480(v=ws.10).aspx#_blank”.HYPERLINK
“http://technet.microsoft.com/en-us/library/cc708480(v=ws.10).aspx#_blank”aspx
httpHYPERLINK “http://technet.microsoft.com/en-us/library/cc720466(v=ws.10).aspx#_blank”:
//technetHYPERLINK “http://technet.microsoft.com/enus/library/cc720466(v=ws.10).aspx#_blank”.HYPERLINK “http://technet.microsoft.com/enus/library/cc720466(v=ws.10).aspx#_blank”microsoftHYPERLINK “http://technet.microsoft.com/enus/library/cc720466(v=ws.10).aspx#_blank”.HYPERLINK “http://technet.microsoft.com/enus/library/cc720466(v=ws.10).aspx#_blank”com/en-us/library/cc720466(v=wsHYPERLINK
“http://technet.microsoft.com/en-us/library/cc720466(v=ws.10).aspx#_blank”.HYPERLINK
“http://technet.microsoft.com/en-us/library/cc720466(v=ws.10).aspx#_blank”10)HYPERLINK
“http://technet.microsoft.com/en-us/library/cc720466(v=ws.10).aspx#_blank”.HYPERLINK
“http://technet.microsoft.com/en-us/library/cc720466(v=ws.10).aspx#_blank”aspx
httpHYPERLINK “http://technet.microsoft.com/en-us/library/cc708480(v=ws.10).aspx#_blank”:
//technetHYPERLINK “http://technet.microsoft.com/enus/library/cc708480(v=ws.10).aspx#_blank”.HYPERLINK “http://technet.microsoft.com/enus/library/cc708480(v=ws.10).aspx#_blank”microsoftHYPERLINK “http://technet.microsoft.com/enus/library/cc708480(v=ws.10).aspx#_blank”.HYPERLINK “http://technet.microsoft.com/enus/library/cc708480(v=ws.10).aspx#_blank”com/en-us/library/cc708480%28v=wsHYPERLINK
“http://technet.microsoft.com/en-us/library/cc708480(v=ws.10).aspx#_blank”.HYPERLINK
“http://technet.microsoft.com/en-us/library/cc708480(v=ws.10).aspx#_blank”10%29HYPERLINK

“http://technet.microsoft.com/en-us/library/cc708480(v=ws.10).aspx#_blank”.HYPERLINK
“http://technet.microsoft.com/en-us/library/cc708480(v=ws.10).aspx#_blank”aspx