It was a folder permissions issue. After ensuring that the current user was in the proper local groups and also in the proper domain groups, all went well. I had to work with someone in our tech support department to fix this for a customer in the West Indies, so I am not quite sure of the specific fix, as we were extremely frustrated and on tight time restraints. So after a few attempts at other fixes, we made multiple permissions changes to minimize remote reboots.
I am sorry that I can't narrow it down to the very specifics, but I can say for sure that if you double, triple, quadruple check that all related users and groups have necessary permissions to all folders involved in the installation, the issue will be solved.