An affected computer can be put back into service by rebooting. The resource enumeration request involved in the vulnerability must be made via IPC, so you can protect against remote attacks by blocking NetBios requests at the firewall. Both of these measures are good security practices in any case. This would have a broad impact on other services as well, because the SCM provides the ability for processes to communicate with each other through so-called named pipes. The loss of named pipes would cause many other services on the machine to stop responding to service requests.
Pipes allow processes to communicate with each other.
A pipe is an area of memory that two or more processes share. When Process A wants to communicate with Process B, it puts data into the shared memory and sets a semaphore telling Process B to read it. They can only exist locally. The processes can reside on different machines. Because this vulnerability causes the SCM to fail, and with it named pipes, an attack via this vulnerability would prevent processes from communicating with each other, and thus prevent the affected machine from receiving and servicing requests.