We're running SEPM 12.1.5 on Windows Server 2008 R2 Datacenter.  The server is virtualized.  When our Operations group created the server, they set up multiple virtual drives / volumes.

C:\ is for the operating system only and currently has around 700 MB free.

D:\ is where SEPM is installed and has around 40 GB free.

E:\ is the SQL database for SEPM and has around 32 GB free.

It's my understanding that even though SEPM is installed on D:\, the LiveUpdate software is installed on C:\.  As this drive is almost filled, I believe we are no longer getting virus updates.

When I look at the LiveUpdate Downloads in SEPM, our Virus and Spyware definitions are 10/06/2014 r1, and they should be either 10/08/2014 or 10/09/2014.  Also, the "Show LiveUpdate Status" shows "Symantec Endpoint Protection Manager could not update Virus and Spyware definitions Win64 12.1 RU5.".

I did see a knowledgebase article suggesting we could use the Sysinternals program "Junction" to point the LiveUpdate content to a different drive (like D:\), but it referred to another Symantec knowledgebase article which is no longer available (I think it was supposed to show how to turn off LiveUpdate prior to moving it).

Any suggestions / ideas?

Thanks!

You can re-direct the content to a new drive, see here:

How to use a new Drive or Partition to host the Symantec Endpoint Protection content directory without reinstalling

Very easy, works well!

Soooo, if you were to do so, then you could move, then use the Junction tool to redirect, the folders described in the below article to another drive:

What files from Symantec Endpoint Protection installation are installed to the C:\ Drive, when the application is installed to a different drive

The thing you need to bear in mind is that doing so places you in an unsupported configuration.  Meaning you may be preventing yourself from receiving future Symantec support should you encounter issues further down the line.

I'd personally start by checking out the log.liveupdate and sesmlu.log files decribed in the below article first (to verify if this is a C: space issue) before deciding on a plan of action:

LiveUpdate and Content Troubleshooting for the Symantec Endpoint Protection Manager