For what it's worth, Server Core installs don't have Print Spooler installed, and that's what Microsoft currently recommends as a domain controller. But since i

For what it's worth, Server Core installs don't have Print Spooler installed, and that's what Microsoft currently recommends as a domain controller. But since it doesn't have a desktop UI, it's a bit less liked by smaller entities. And of course, not all Windows Server roles support being run that way. It's safe to disable Print Spooler on servers that aren't print servers, so I expect that to be a standing recommendation in the future. The other thing though is this vulnerability works against desktop PCs, which need the Print Spooler to print... However, you can set a group policy to disable remote printing to a desktop PC, which should block the flaw. Desktop PCs probably shouldn't be acting as print servers, so this is mostly a good idea to implement too. So the available mitigations/attack surface reductions available here are plentiful... and honestly probably should just be best practice now.