allywilson
Technical User
Hi all,
2003 server acting as a print server. The print spooler service when started and startup set to automatic gets stopped and disabled whenever the group policy is applied to it. I can only assume this as whenever the policy is refreshed I can see the service being stopped in the eventlog and then the security policy successfully applied afterwards (like within a second). RSOP shows that the policy does not have the service disabled (it's not defined) - and I cannot find any group policies on the domain that even has it specified, nor local.
Any ideas how I can track down this rogue policy?
Using workarounds like "sc config spooler start= auto" is fine in the meantime - I would just rather not have to do it longterm i.e. Putting a fix in-place for something that shouldn't be broken is not good in my book.
Cheers,
2003 server acting as a print server. The print spooler service when started and startup set to automatic gets stopped and disabled whenever the group policy is applied to it. I can only assume this as whenever the policy is refreshed I can see the service being stopped in the eventlog and then the security policy successfully applied afterwards (like within a second). RSOP shows that the policy does not have the service disabled (it's not defined) - and I cannot find any group policies on the domain that even has it specified, nor local.
Any ideas how I can track down this rogue policy?
Using workarounds like "sc config spooler start= auto" is fine in the meantime - I would just rather not have to do it longterm i.e. Putting a fix in-place for something that shouldn't be broken is not good in my book.
Cheers,