The uploaded content exceeded the maximum size allowed

Issue:
When attempting to upload a software package into the an ePO master repository, an error occurs: "The uploaded content exceeded the maximum size allowed"
Environment:
Web Interface of McAfee ePolicyOrchestrator (ePO)
Symptoms:
Hard disk space is not lacking, and yet, shortly after trying to upload the ZIP file package, the error occurs.
Solution:
Although this could very well be traced to a corrupt zip file, the problem was that the ZIP file I was using contained a tar.gz file inside. I had to extract the zip file, then extract the tar.gz (use a program such as 7zip). Once that was extracted, there was another ZIP file which was the appropriate one to use.

Error untaring Plugins (rc = 2)

Issue:
When attempting to update plugins (such as Active plugins) into Tenable SecurityCenter, an error is received such as: "Error untaring Plugins (rc = 2)"
Environment:
Web Interface of Tenable SecurityCenter hosted on RedHat
Symptoms:
Plugins may or may not appear to be working for a moment, however they quickly fail. An error message indicates: "Error untaring Plugins (rc = 2)".
Solution:
Although this could very well be traced to a corrupt tar.gz file (in which case, re-download and try again), the solution in this case was to free up some hard disk space. Logging into the Redhat SecurityCenter installation, I noted that although the plugins are roughly 150MB, when untarred and gz'ed, they expand to a size requiring up to 900MB. If there is anything less than 1GB free on the root (/) partition, some of it should be moved or removed.

Because of a security error, the client could not connect to the remote computer. Verify that you are logged onto the network and then try connecting again.

Issue: 
Connecting to another system with RDP fails. This system may successfully be able to handle RDP requests from other devices. This occured in a Windows RDP Client connecting to a Redhat XRDP Service.
Environment:
Windows workstation connecting to Redhat via XRDP.
Symptoms:
Connection appears to begin, but error message "Because of a security error, the client could not connect to the remote computer. Verify that you are logged onto the network and then try connecting again." appears.
Solution:
Although the following article may be helpful:
https://support.microsoft.com/en-us/kb/329896
The solution in this case was to disable the enforcement of FIPS. One method is to set the following value to 0:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\FipsAlgorithmPolicy