Forum Discussion
Make Print Spooler and DHCP services Redundant?
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. Server...
Hello,
1) Don't mix WSFC with DC, Active Directory has its own resiliency mechanism. It doesn't mix well at all with WSFC (not even sure it is supported). Don't mix Print Server with DC too - too much of a security risk.
For resiliency, you could rely on VM failover if it's a virtual machine. WSFC could work but it's kinda overkill for 120 users.
2) DHCP failover is easy to configure and reliable, and much easier to implement/manage than WSFC. Like 1), don't mix DHCP server roles with DC - put it on its own server. VM failover is also a solution (rebuilding a DHCP server take barely more time than reinstalling the OS).
You should avoid WFSC unless you have a very specific need tbh, it's overkill for most use cases wherever built(in resiliency is available.
1) Don't mix WSFC with DC, Active Directory has its own resiliency mechanism. It doesn't mix well at all with WSFC (not even sure it is supported). Don't mix Print Server with DC too - too much of a security risk.
For resiliency, you could rely on VM failover if it's a virtual machine. WSFC could work but it's kinda overkill for 120 users.
2) DHCP failover is easy to configure and reliable, and much easier to implement/manage than WSFC. Like 1), don't mix DHCP server roles with DC - put it on its own server. VM failover is also a solution (rebuilding a DHCP server take barely more time than reinstalling the OS).
You should avoid WFSC unless you have a very specific need tbh, it's overkill for most use cases wherever built(in resiliency is available.