Microsoft print server failover cluster

For example, in Windows Server there are a couple Print Spooler failure scenarios that you may want to monitor with Virtual Machine Monitoring:. To configure a service to be monitored for failures on the virtual machine, you can use Failover Cluster Manager.

Any node in the cluster can be used to configure the monitoring, but this feature cannot be configured using Hyper-V Manager. Open Failover Cluster Manager on one of the nodes of the cluster, and connect to the cluster that you wish to manage.

Click the Roles node under the cluster name that you wish to configure. Each virtual machine that is clustered will display in the middle pane.

Right click the virtual machine that will be monitored and select More Actions , and then Configure Monitoring. Select the Print Spooler from the list of services by checking the box next to it. Windows PowerShell equivalent commands.

To configure the Virtual Machine Monitoring feature to monitor the Print Server virtual machine Print Spooler service, open an administrative Windows PowerShell command prompt on the Hyper-V host that currently owns the highly available print server virtual machine and type the following command:. Windows PowerShell command. Although service monitoring can also be configured using the Failover Cluster Manager interface, event monitoring can only be configured using Windows PowerShell.

To configure the Virtual Machine Monitoring feature to monitor the Print Server virtual machine event log for a particular event ID for example , open an administrative Windows PowerShell command prompt on the Hyper-V host that currently owns the highly available print server virtual machine and type the following command:.

Type the following command to display the Virtual Machine Monitoring configuration for a specific virtual machine:. The output of this command for a correctly configured highly available print server should show that both spooler monitoring and event ID monitoring are enabled:. To verify the configuration of Virtual Machine Monitoring it is necessary to simulate a failure of the Print Spooler service or manually generate an event ID using an event generating tool.

The Service Control Manager will restart the Print Spooler process the first two times and Virtual Machine Monitoring will not take action until the third simulated spooler failure. Stopping the Print Spooler service is not considered a failure and will not trigger a recovery action by the Virtual Machine Monitoring feature. After the virtual machine reboots, terminate the Print Spooler process a second time within 15 minutes using Task Manager.

Contents Exit focus mode. Please rate your experience Yes No. Any additional feedback? Module: FailoverClusters. Specifies the cluster on which to create the highly available print server.

Specifies the name of the highly available print server to create. Specifies the cluster disk resource to be added to the created highly available print server. Submit and view feedback for This product This page. View all page feedback. The clustered servers called nodes are connected by physical cables and by software. If one or more of the cluster nodes fail, other nodes begin to provide service a process known as failover. In addition, the clustered roles are proactively monitored to verify that they are working properly.

If they are not working, they are restarted or moved to another node. Failover clusters also provide Cluster Shared Volume CSV functionality that provides a consistent, distributed namespace that clustered roles can use to access shared storage from all nodes.

With the Failover Clustering feature, users experience a minimum of disruptions in service. Skip to main content. This browser is no longer supported. Download Microsoft Edge More info. Contents Exit focus mode. Is this page helpful? Please rate your experience Yes No.