I ran into the same problem and was told it was because AAMEE packages files for distribution using SCCM and ARD. To get around this issue, we created a self-extracting zip file containing a batch file to start the installation. I am sure there was probably a better way to accomplish the task, but this is what worked for us based on system restrictions and server permissions.
Batch file contains the following text: (Modify echo text as you see fit and include your msi filename in the msiexec line)
echo "Press ENTER to begin installation."
pause
msiexec /i Build\YOUR_MSI_FILENAME_HERE.msi
Exceptions\ExceptionDeployer.exe --workflow=install --mode=post
echo "Press ENTER to exit installation."
pause