I have been using the script in unattended mode as part of a startup of a VM and when I ran the script as the farm account (realizing I wasn't supposed to later) I received a database failure later.
When I switched to a dedicated installer account (one that is a DA), now I get this continuous loop trying to create the UPS and waiting for it.
Comments: ** Comment from web user: DDaigle **
When I switched to a dedicated installer account (one that is a DA), now I get this continuous loop trying to create the UPS and waiting for it.
Comments: ** Comment from web user: DDaigle **
No, they are simply using your script. Albeit they used a customized version in their sample, but I started off with yours. It is AutoSPInstaller itself that could benefit with being told whether or not it is running on the same system it is configuring and by direct action of the person doing it.
In that case it works, but either remote unattended or by run task without anyone logging in to the system, it doesn't seem to work without these changes.