If you experience an error using the Typical setup path of the 3.2 Installer regarding the MSP_SERVICE_ACCOUNT creation, use one of the following choices as a workaround. This should only occur on some installs using Windows Auth with PCs on a domain. Options:
1. Have the customer create that user ‘MSP_SERVICE_ACCOUNT’ on the box and assign it the default password 11MspServiceUser! BEFORE re-trying the MSP install. (Even the manual creation of this account and password may not be allowed by domain policy restrictions).

2. Have them manually create a different runtime user that will be used instead of the above and select that specific user during the ‘MSP User Selection’ section of the CUSTOM Install type of the MSP Installer.
The problem is essentially that the domain security policy is rejecting the automatic creation of that user due to password strength requirements not being met. I have already submitted a bug ticket to change the default password for the next release, but for now use the choices for a workaround. We have found a couple cases of this issue so far but it may not be very common. See an example of the error message given in the screen capture attached.