Thanks, will have a try.

FYI: There is no magic answer for your question so you're unlikely to find one here.  Unity is a Windows-based application that, in most ways, is simply an application running on Windows - unlike the pre-Linux CCM application where there wasn't much freedom to do anything on the underlying OS and still have support.  For the most part, you don't mess with the /CommServer folder - on your server should be installed on D.  This is the heart and soul of the Unity application.  Otherwise, you just need to be smart and move or delete files with caution.  Apparently my first round of feedback wasn't of much use to you so good luck with it.

Hi -

Here are my recommendations for helping your Unity disk full condition:

- Remove files that begin with $ - these are Windows service updates and uninstall files.  I typically keep the existing month's security updates on disk but delete all others.

- Run DbWalker first without any checks, and then run it a second time checking the optional - Remove old stream files.  These files are the "abandoned" recorded names and greetings that stay around after subscribers are deleted.  Over time, these can bog down your C drive - typically stored on c:\commserver\stream files directory.

- Check your c:\commserver\UnityMta\Failed folder for messages sent to deleted subscribers or that can occur for other errors.

- SQL log files - you can compress your UnityDb log and ReportDb log files.  If you are comfortable using SQL, change each of these databases from Full to Simple, then compress ONLY the log files, not the database files.  Then change the databases back to Full.

Hope this helps!  Ginger

Following the install guide, the only thing that should generally be on C (see above).