cset
cset copied to clipboard
Enterprise setup script sets app pool user invalid if machine is domain joined
The enterprise setup script creates local user CSETUser to run the app pools, then it sets to app pools to run under "${env:userdomain}\CSETUser". If the machine is not domain joined that is fine since it will return the machine name, but if it is domain joined this will not be a valid account. Maybe this ought to use env:computername.
edit: same goes for sqlcmd creating the login and role etc.
I found this to be an issue as well and I concur with the proposed change which will work for both domain and non-domain joined computers.
If this is not going to get fixed, the documentation should indicate that a local administrator account should be used to perform the install.
I ran into this as well, had to edit the enterprise setup script. replaced "${env:userdomain}\CSETUser" with "computername\CSETUser" but "${env:computername}\CSETUser" would work for all installs. Great suggestion. I'm going to edit the script saved locally with that.