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

Recording Tab Missing on DVD CD RW Properties

Issue: 
When attempting to burn a CD or DVD with Windows built-in burning features, the option is not available.
Environment:
Windows 7 Non-Domain System. Although solution could be applied to a domain environment. This occurred on a Dell laptop.
Symptoms:
The tell-tale sign that Windows will not be able to record to disk is a missing recording tab of the DVD RW properties.
Solution:
For many people, this issue issue is caused by a local security policy found here:
User Configuration\Administrative Templates\Windows Components\Windows Explorer
"Remove CD Burning Features" set to Enabled will remove CD Burning.
However, this was not the case for my system;
In my policy editor:
Computer Configuration\Administrative Templates\System\Removable Storage Access\
"CD and DVD: Deny write Access" set to Enabled will remove CD Burning.
Change the setting from Enabled to Disabled. This setting can be editied by double-clicking on the item.
Click the "OK" button at the bottom of the window.
Close the window titled "Local Group Policy Editor"

Check if CD burning is working. If yes, great! Mine was not. No, I had to also uninstall and reinstall the driver for this to work!

Click on "Start" button
Type in "Device Manager"
Click on Device Manager in search results.
If prompted to allow "Microsoft Management Console" to make changes to your computer, Click "Yes".
Expand DVD/CD-ROM drives
Double-Click on drive (ex: Matshita DVD+RW)
Click on "Driver" tab
Click "Uninstall" button
Accept the warning that the device is about to be uninstalled by Clicking "OK"
While still in device manager, Click on the "Action" menu from the top bar.
Select "Scan for Hardware Changes"
The DVD+RW will automatically reinstall.

Check if CD burning is working. If not, Reboot.

Note: To open policy editor:

Click on "Start\Windows" button
Enter gpedit.msc and Press Enter
If prompted to allow "Microsoft Management Console" to make changes to your computer, Click "Yes".

Your account is configured to prevent you from using this computer. Please try another computer.

Issue:
When attempting to log on to a Windows system, the error message: "Your account is configured to prevent you from using this computer. Please try another computer." is received. The system then returns to a logon screen.
Environment:
Windows workstation. Non-Administrator account login.
Symptoms:
An administrator account appears to be able to log into a target system, but "standard" users cannot. The standard account is not locked.
Solution:
There was a corrupt entry in the registry for the item: "HKLM\System\CurrentControlSet\Control\LSA\CrashOnAuditFail" This should be a DWORD of 0 or 1 only. I recommend 0. Unsure as to the root cause of the corruption. Review the system's event logs. This issue is likely to take effect if the logs are full, thus impacting the ability to perform "audits".
It is worth reviewing all of the system logs and clearing them off.
Even after doing all this, the issue may still remain. It may take a reboot or a little bit of time before the system will allow for a login, especially if the computer is "slow".
Note:
If the solution provided does not resolve the issue, the following may help:
In ADUC on a domain environment, the account may be limited as to which systems it is allowed to "Log On To..."
The login hours of the account may be impacting the abillity to login.

Detecting MSXML4, MSXML6 Versions

Issue:
Service Pack of MSXML is not apparent. For example, the Add\Remove Programs applet may list MSXML6 Parser as an installed program, without mention that it is Service Pack 2.
Environment:
Windows All Versions
Solution:
Look at the version of the %systemfiles%\msxml*.dll
The number which follows the major version is the "Service Pack"
For example, if on the properties of msxml6.dll, the version is 6.2, then the Service Pack is 2.

Project: Detect MSXML Service Pack from Command Line
Obtain the latest version of "filever.exe", available for free from Microsoft as part of the Windows Support Tools. For example, from http://www.microsoft.com/en-us/download/details.aspx?id=18546
Then, run the following:

filever.exe C:\Windows\System32\msxml* > xmlversions.txt
findstr /C:"  4.0" xmlversions.txt > nul
IF %ERRORLEVEL% EQU 0 (ECHO MSXML4)
findstr /C:"  4.1" xmlversions.txt > nul
IF %ERRORLEVEL% EQU 0 (ECHO MSXML4SP1)
findstr /C:"  4.2" xmlversions.txt > nul
IF %ERRORLEVEL% EQU 0 (ECHO MSXML4SP2)
findstr /C:"  4.3" xmlversions.txt > nul
IF %ERRORLEVEL% EQU 0 (ECHO MSXML4SP3)
findstr /C:"  6.0" C:\Temp\xmlversions.txt > nul
IF %ERRORLEVEL% EQU 0 (ECHO MSXML6)
findstr /C:"  6.1" C:\Temp\xmlversions.txt > nul
IF %ERRORLEVEL% EQU 0 (ECHO MSXML6SP1)
findstr /C:"  6.2" C:\Temp\xmlversions.txt > nul
IF %ERRORLEVEL% EQU 0 (ECHO MSXML6SP2)
findstr /C:"  6.3" C:\Temp\xmlversions.txt > nul
IF %ERRORLEVEL% EQU 0 (ECHO MSXML6SP3)

Symantec Endpoint Protection Client Rolls Back During Installation

Issue:
Symantec Endpoint Protection Client Rolls Back During Installation
Environment:
Windows client (XP) in need of an Endpoint Protection Client in a domain with Symantec Endpoint Protection Server and other working Symantec Clients
Symptoms:
Product initially appears to be installing fine. Near the end of installation, the progress bar rolls back and the installation fails.
Solution:
I've encountered this issue a few times... Try the following in order of most to least likely:
1. Verify you are logged in as Administrator
2. If user permissions are misconfigured, try using a different Administrator account to perform the installation. For example, use the local system administrator account, or a newly created administrator account, or your backup administrator account. If this fixes your issue, you should track down why your administrator account is limited where your other accounts are not.
3. Perform a cleanup of Symantec Applications on the client:
A. Run Cleanwipe (Symantec's Installation Cleanup tool), Reboot, then try reinstalling. Select "yes" to each Cleanwipe option (Skip if cleanwipe not available)
B. Verify in Add\Remove Programs that both Liveupdate and the Client are removed.
C. Use a registry analyzer to clean Symantec References (ccleaner, for example)
D. Reboot, then reinstall the client
4. Verify that the latest root certs are on the system (obtaining from Microsoft is OK)
5. Use the Symantec Support Tool (available from the Server installation media) and run on target machine. Address any issues which this tool finds.
The following steps have not worked for me, but have come up in my research:
6. Install the latest version of Windows Installer
7. Install Liveupdate (LUSETUP.exe) before installing the client on target machine.
8. In the registry (Obligatory Warning: Backup registry before modifying it!),
Find:
HKEY_USERS\.DEFAULT\Software\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders\AppData
value=%APPDATA%
and change it to value=%USERPROFILE%\AppData\Roaming
9. Update Internet Explorer 6 to Internet Explorer 7
10. Perform a thorough registry check for Symantec, and be sure to remove:
HKEY_USERS\.DEFAULT\Software\Symantec [remove]
HKEY_CURRENT_USER \Software\Symantec
11. On the server, rebuild the client package and redeploy or re-run on target system
12. Verify that the correct version of the client is being installed (32bit, 64bit, etc.)
13. Click on Start, Select Run, Type: "dcomcnfg", Expand the Component Services, Expand Computers, Expand My Computer, Expand DCOM Config, Right-click LuComServer and select Properties, Click on Identity tab, Select the "This user" option and choose a Local Administrator account., Click OK, Restart the computer