Is there a way to force an IIS application pool to continue to retry to start even if its pool identity login failed the first time? Here is the sequence I am seeing:
- IIS app pool is set to run as valid domain credentials
- Machine is rebooted
- IIS app pool attempts to start, but domain controllers cannot be contacted yet
- IIS app pool identity logon fails
- Event viewer shows 'WAS' event IDs 5021, 5057, 5059 in quick succession (basically errors that the app pool identity logon failed)
- app pool is disabled and needs manual intervention to restart.
- After short amount of time passes, app pool manual start is successful after network path to domain controllers becomes available