I have a Windows 2003 SP2 server that runs some older software that we need to keep for a while longer. 
I have a DCSS 6.0 server and installed the agent on the target machine. With the nul policy in place the performance is within acceptable limits, in terms of the web applications running on it, although the SISIDService is consistently using 50% of the CPU. (So not really acceptable but from the end-user POV its not that big of a hit.) If I try to apply a policy with any restrictions the SISIPService kicks in and uses up the other 50% of CPU. According to the Console the policy never actually loads. I've given it over an hour and it never completes. I can re-apply the null policy and that will take effect after a few minutes.
I have tried the least restrictive out-of-the-box policy that comes with it and get the same result.
Any know fixes or ideas for this?
Thanks!
Jack