Getting ready to demo this solution. As a current Secret Server customer we use Secret Server with multiple servers behind a load balancer due to the business requirements of availability.

From what I understand with PRS, there isnt a reason to cluster servers, rather just load balance with sticky state (using a central DB). Is this the case? Anything else you can share on HA implementations on PRS would be helpful.

Most customers are not usually too concerned about HA for PRS - my understanding is that it is not typically deemed a critical system since the help desk can take over if needed or some downtime during recovery is acceptable.

However, PRS does support MS SQL database mirroring - see this KB article: <a href="http://support.thycotic.com/KB/a62/setting-up-password-reset-server-for-disaster-recovery.aspx">http://support.thycotic.com/KB/a62/setting-up-password-reset-server-for-disaster-recovery.aspx</a>

PRS does not support front end clustering today. This is a feature request on roadmap but is behind many other higher priority requests.

Our enterprise DB infrastructure handles all DR nicely already. I'm more concerned about HA for global use. To us, this solution would be used globally in 14 offices, spanning 5 times zones. Offering a solution like this and having something silly happen to IIS causing an outage would be a shame.

Is there and system state that would prevent just building 2 of these servers, using the same database, and operating the IIS servers behind a LB with sticky sessions?

Unfortunately that is an unsupported configuration at this time. The background processes would not be handled separately e.g. you could get sync problems with AD or duplicate password expiration emails. The background processes will be handled correctly when clustering is implemented in PRS.