How many machines do you have on your network?
It seems this is a nasty bug, with a capability of reproducing itself, relatively quickly and infecting networks hard and fast. I followed the thread you mentionned above and other than as stated SecPro there does not seem to be much info on this bug.
Andyb7274 claims to have a .bat that will kill the thing, have you tried that?
* * * * * * *
For a large scale infection like this, you are limited in what you can do to "cure it". Honestly, if no specific anti-virus can get to it, you will have to go about it the old fashionned way, starting with your domain controllers/servers. Everything that has an OS/Service running must be shut down. I mean every machine, mission critical, mail, file server, everything shut down. You have remote sites? Break the connections, shut down the VPNs or routers to the remote sites...
* * * * * * * *
Once this is done, identify and clean the threat. Find the registry values and Exe/DLLs that are running a much on the system and remove them. Once your machine is clean... Shut it down. You don't want it getting re-infected, move on to the next machine. Rinse and Repeat... 1 machine on at a time. 1 will re-infect the others from the behaviour described in the other posts. Once this is done and you are certain the infection has been removed from your network, think about the remote sites. You can try to synchronize doing them all at the same time, if applicable, if not, do not restore the link until you are certain the other side(s) are clean as well.
Once everything is cleaned and working, startup your AV servers. Update them to the latest and scan them again. Next most likely culprit- mail servers. Any chance of compromise, scan and make sure they are still clean. and work your way from there. Once you are sure the machine is clean, remove/detach the network cable from the machine, ensure no interaction with any other machine, except the AV servers to push updates. Once you are certain everything is clean, re-attach network cables and "cross-fingers". The next problem is figuging out where the initial infection came from... this you may never know.
If you don't already, now is a good time to implement a "no personal equipment on the network policy". With the time and effort you (and the staff if applicable) put in, it should not be hard to get approved.
I hope someone, somewhere has a better solution, but until now, I don't see anything either.