Final answer:
For server applications not supported by a high availability wizard, administrators should use alternative methods such as clustering, replication, or load balancing, and may need to rely on custom scripting, database mirroring, or other fault tolerance strategies tailored to the application's needs.
Step-by-step explanation:
Server applications not listed within the wizard for high availability should use other methods to ensure their availability. These methods can include clustering, replication, and load balancing techniques that are not necessarily part of a specific high availability wizard. In some cases, this might require manual configuration or the use of third-party software to ensure that the application remains available in the event of a failure.
In situations where the high availability wizard does not support a particular application, administrators must carefully plan and implement a strategy that suits the needs of the application while ensuring minimal downtime and data integrity. This may involve using custom scripts, setting up database mirroring, or employing other fault tolerance measures based on the specific requirements of the service.