Endpoint Protection

 View Only
  • 1.  Cannot upgrade to latest build of SEPM-not enough disk space

    Posted Mar 31, 2009 02:12 PM
    I'm trying to upgrade the Symantec Endpoint Protection Manager Console on one of my Windows Server 2003 boxes to the latest build (version 11.0.4014.26). It says there is not enough disk space. I cannot remove anything else to free up space. I have 1GB available. I'm currently running version 11.0.3001.2224 (embedded database).


  • 2.  RE: Cannot upgrade to latest build of SEPM-not enough disk space



  • 3.  RE: Cannot upgrade to latest build of SEPM-not enough disk space

    Posted Mar 31, 2009 05:58 PM
    These are just some more or less random thoughts that may also help (ignore them if they don't).  Use or don't use, at your own risk and with careful preparation and investigation beforehand; don't forget to make backups:

    - Add a partition/HDD to the system and run SEP from there.
    - If SEP runs on a RAID array (presumably RAID 5 or higher?), you may be able to add a drive to the array and then expand the partition that currently runs SEP.
    - Check PageFile settings, and if the partition that is running SEP has a large PageFile allocated on it, then look for a better place/partition to run your PageFile.
    - Defragment the partition that runs SEP; a defragmented drive often makes more efficient use of space.
    - Run the Disk Cleanup tool to help find temp files than can be deleted, and set to "Compress Old Files" if that is a suitable option for you (read up on the effects first).
    - Sometimes even on a server, Internet Explorer (or other browsers) have huge caches of Temporary Internet Files (can be a Gigabyte or more) - reduce them to something in the realm of 60 Megabytes (generally, this will have no noticeable impact if you have a broadband connection).
    - Check with Symantec Tech Support about deleting abandonded/useless files left over from the SEP Client and/or SEPM installation.  Most machines will have at least close to 200 Megabytes of "junk" left on them that is no longer needed by SEP clients or the SEPM (very sloppy IMHO...).

    These are all fairly basic and common things to do.  I fight this battle on a regular basis too, especially when a software developer suddenly descides that it's okay to ramp up the footprint exponentially, to the tune of something like 100x compared to previous versions/releases (not to mention doing about the same thing in terms of memory and CPU utilization at the same time...)  :0(

    Good luck.