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:. Give the network name resource an appropriate title such as PCAppSrv. The need for a new cluster group is not required. It is, however, recommended as it gives the most flexibility in terms of load balancing Printer load balancing automatically distributes print jobs between two or more printers. Load balancing is generally used to equally distribute print jobs across a pool of printers saving valuable time in document output for the user and at the same time balancing the wear and tear among printer devices.
Click Next at Possible Owners page. Right-click the cluster group; then select Bring online. Interface the PaperCut Print Provider layer with the clustered spooler service by following the same setup notes as described for Mode 1. The client and Release Station Print Release Stations place a print job on hold and allow users to release it when required. Often a Release Station is a dedicated PC terminal located next to the printers, however, Release Stations can take other forms such as a web browser based interface.
Some common examples where Release Stations can be used include secure printing, approved printing, and authentication. In a secure printing environment jobs are only printed when the user arrives at the print area and confirms his or her identity. This ensures the user is there to collect the job and other users can't "accidentally" collect the document.
In some organizations it may be appropriate to hold jobs until they are approved by selected individuals. A good example would be a teacher approving printing on an expensive color printer. Users must authenticate prior to releasing their jobs allowing PaperCut NG to confirm their identity. Mode 2 setup is about as complex as it gets! These services are dependent and must be hosted in the same group. Set the Preferred owners of each group to different physical nodes.
Restart or bring on line each group, and independently test operation and operation after fail-over. Take some time to simulate node failure. Monitoring can stop for a few seconds while the passive server takes over the role. It is important that the version of PaperCut running on each node is identical.
Ensure that any version updates are applied to all nodes so versions are kept in sync. The PaperCut installation sets up a read-only share exposing client software to network users. If your organization is using the zero-install deployment method, the files in this share are accessed each time a user logs onto the network.
If this occurs, printers that share a common name won't be available. Again, it's recommended to adhere to the 8. After you add all the desired print queues, use Cluster Administrator to move the group that contains the Print Spooler resource to all other nodes. Printing is available immediately to clients when the queue has been created even though the drivers have not been copied to all other available nodes.
It is not necessary to move the spooler group over to all other nodes immediately after creating the queues for the cluster to function. You can do this later when you can schedule a brief outage during which time you can take the Spooler resource offline. When you set up a print cluster, you have to set the Quorum log size to a size that is large enough to comply with the number of printers that will be installed. You should increase the size of the reset quorum log when you increase the size of the Quorum log size.
To help determine whether you have to increase the reset quorum log size value, verify the size of the Clusdb file. The size of the reset quorum log for the transactional log should be larger than the size of the Clusdb file for the cluster registry. For example, if you have installed printers and the size of the Clusdb file is 6 megabytes MB , you should increase the size of the reset quorum log to bytes 8 MB.
By default, the size of the reset quorum log on Windows Server is 4 MB. You should increase the size of the reset quorum log in KB increments. A good rule is to double the current size of the reset quorum log. Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Feedback will be sent to Microsoft: By pressing the submit button, your feedback will be used to improve Microsoft products and services. Privacy policy.
Thank you. Creates a clustered print server, a resource group that includes a printer and a disk for storing print job information and printer drivers. The Add-ClusterPrintServerRole cmdlet creates a clustered print server a resource group that includes a printer and a disk for storing print job information and printer drivers. When adding a clustered print server, specify a name for the print server, any IP address information that is not automatically supplied by your DHCP settings, and the storage volume or volumes that the clustered print server should use for print job information and printer drivers.
0コメント