Video Screencast Help

HOWTO: Move the SEPM content folder to another drive

Created: 28 Jan 2008 • Updated: 21 May 2010 | 18 comments
Paul Murgatroyd's picture
A number of people have asked if there is a way to move the content folder from the install folder of SEPM to another drive or folder with more space.  Yes there is.  Please take a look at this KB:
Please note that this will not stop the folder from growing very large, there are other fixes for that.  However if you DO want to keep a large amount of historic content or DO want to move the content folder to another drive, then this will work.
Please post your feedback to this post.

Comments 18 CommentsJump to latest comment

Aaron Blosser's picture
That's an interesting method, however if you do not have a dedicated physical drive to use for this content, but you do have another existing partition with plenty of space, you can use a similar method, but using a junction.
Over at the sysinternals website, there's a utility called "junction.exe" that lets you easily create a junction on an NTFS file system.
Follow the steps given in the original article, but then instead of creating a mount point, you'd copy the existing "content" directory (let's say you copy it over to D:\SEP_Content) and then create a new empty content directory in the old spot.
Then just run the command:
junction "c:\program files\Symantec\Symantec Endpoint Protection Manager\Inetpub\content" d:\sep_content
(line probably wrapped... that's all one line).
Since there are other subdirs in the "inetpub" area that can get big, personally I just created a junction point for the entire inetpub structure, pointed it to d:\SEP_Inetpub on my management servers.  Worked out pretty well.
Softsource's picture

Using junctions is a wonderful Idea, especially so you dont have find a new drive/partition

Gregg Hill's picture

The link above does not work. Can you sort it please? Richard

Paul Murgatroyd's picture
Hi, sorry for the inconvenience - that KB is currently awaiting technical review after being updated.  In the meantime, google has the old version cached if you want to read it (just search for the KB number)

Paul Murgatroyd
Principal Product Manager, Symantec Endpoint Protection
Endpoint twitter feed:

Paul Murgatroyd's picture
KB is back up

Paul Murgatroyd
Principal Product Manager, Symantec Endpoint Protection
Endpoint twitter feed:

cwitt's picture

You said..

"Please note that this will not stop the folder from growing very large, there are other fixes for that. "

How do I find those "other" fixes?  My search attempts are coming up empty.

pbogu's picture


shut down SEPM service

modify this file
Symantec\Symantec Endpoint Protection Manager\tomcat\etc\

Xs default value is 10, we can adjust it as we want but preferably 1-5 this line must be the last line in the file

delete all GUIDs folders in \Program Files\Symantec\Symantec Endpoint Protection Manager\Inetpub\content GUIDs are looking like that:

start SEPM service

Dwayne Gibson's picture

I used the Junction method outlined above by Aaron. Thanks! It's working great.

I also had a few servers that were running out of space on the C:\ and this solutions is a life saver. (cherry)

Maggots's picture
Is there's a way to stop the Content from growing very big. Inetpub content is now 22go and I can't imagine what it will looks like when we'll reach 1 year with the product.
I don't want to move it.. I just need to stop it from growing more everyday.
Thank you
SKlassen's picture
There are several things you can do to pare down the space usage of SEPM Maggots:
1)  Make certain that you have MR1 installed and are not running the original release version of SEPM.
2)  From the SEPM console, tune your installation to reduce the retention of logs and the number of log entries kept.  There are also configurable items for retention of definitions within the database.  You can find all of this stuff in the Admin>Server section by digging around.
3)  From the IIS manager MMC, turn off logging for the SECARS virtual directory.  Then manually delete any prior IIS logs you no longer need.
4)  This one deals with the Inetpub bloat you mentioned.
a)  Turn off the SEPM service
b)  Delete all of the GUID named directories in Inetpub\Content\
c)  Find the file in the tomcat\etc\ directory.  Edit this file and add as THE LAST ENTRY scm.lucontentcleanup.threshold=  .  After the = sign you want to put a number which is the number of prior definitions you want to keep.  Mine is scm.lucontentcleanup.threshold=3.
d)  Restart the SEPM service.  Within a few minutes, you should start to see the GUID named directories in Inetpub\Content\ recreated and repopulated, within the limit you set in 
e)  You may also want to run a manual live update from the SEPM console admin area.
5)  If your making regular backups of the SEPM DB, manually delete any you decide are too old to be of value anymore.
6)  From within the SEPM console, delete any install packages that are no longer needed.  For example, after you install MR1, the "MR0" packages will still be in the DB, but you won't want these anymore.  Will probably be the same when MR2 comes out and is installed.
Maggots's picture
Ok but i'll be honest with you, i've tried it because i've seen it on the first page and I had some problems with my virus definition on the clients computers after that.  I needed to put an ghost iamge back on the server. The problem was that my SEPM was up to date from the 20th of march but ALL my clients computer were stopped updating at 18th march.. So I took panic because I though I might have deleted some ({1CD85198-26C6-4bac-8C72-5D34B025DE35}) that were important for the server so I did put the image back on the machine. Now i'm where I was, that mean, my C:\Program Files\Symantec\Symantec Endpoint Protection Manager\Inetpub\content have a lot of random named folders and it' approximatly 22.5go.
I though there were an easy setting on the programs to fix this but If you're telling me that I need to Stop a service manually, delete all the folders, then update a file ... ehhh I'm a little scared to do it another time because I don't want to crash the setup another time. Will the MR2 fix this of maybe just make it a little easier ?
SKlassen's picture
It can be a bit scary, but it does work.  If your really unsure of yourself going through this process, file a support case specifying that you want a call-back and not just an email.  The support engineer should be willing and able to stay with you on the phone and walk you through the entire process step by step while you actually do it.
If you run into any snags along the way, you've got help right there.

Message Edited by Scott Klassen on 03-24-2008 06:22 PM

Maggots's picture
Thanks Scott,
I just realized that I had the original release and not the MR1. Would it help If I update my SEPM ? I didn't know that the MR1 was release in fact I was unpatiently waiting the MR2 without knowing that there already was another release out. Is there's a list of fix or update for this release ? I'm know i'm out of topic but I would help me to know If I wait or move for this version before the MR2.
And if I update to MR1, will the client update too ? It seems that MR1 has a lot of bug too and I wouldn't want to make my problem bigger than now.
Thanks a lot
SKlassen's picture
MR1 Fixes a ton of issues in the original release.  MR1 does not automatically update clients, it will create new install packages in you SEPM which will need to be pushed out to the clients.  Alternately, there's a small MR1 updater .msp file at for updating clients only.
After MR1 came out, MP1 was released which fixes a few issues with MR1.  This is for updating SEPM only, the clients don't need this one.
Both MR1 and MP1 install media are available at FileConnect.
Cyb0rG's picture
Hi Paul,

            Found an alternative [not complete] for junction.exe.
            How about mountvol.exe [windows command line].
            This MS KB would be helpful
            Have a look at subst.exe [windows command line], Probably not related but found interesting .
Pradeep Jhala's picture
The MR-2 release is available for download, upgrade to this version and the content folder growing issue will be fixed.
Best luck
Pradeep Jhala