May 05 2023 07:46 AM
Looking to get our print Spooler and DHCP redundant/Failover. The Spooler currently Spools to about 25 Printers DHCP and the Spooler are installed on a Primary AD DC. We have About 120 users. Servers are Windows Datacenter 2022.
The AD DC is one of 2 at this Location. Looking at Windows Server Failover Clustering, it looks like I can install WSFC on a AD DCs and then Add the Print Spooler to the cluster. (Yes, loosing the original \\host\share)
My 2 Questions are:
1) WSFC on DCs is Supported, though Wanted real World experience. Is this fine? I dont want to have to spin up 2 more VMs to just maintain printing. Is this a good way to do redundant Print Spooling?
2) DHCP has its own built in Failover as you can tie it to another DHCP server and make them function as one. Is the built in failover Better than adding DHCP as a WSFC Resource?
Thank you,
Scott<-
May 09 2023 08:16 AM