I'm not sure if this is a Serv Man problem or a Config Man problem, it's really something between the two. But I decided to start with Serv Man on this mailing list before moving to the config man list and then eventually Tech Net if needed.
About two weeks ago the WindowsWorkflowTaskJobStatus table in our Service Manager database grew exponentially. For initial damage control I tweaked the grooming settings down to 1 day so the size has stopped increasing but has remained constant as there are still a great many workflow task status jobs each day. The majority of these seem to be coming from Config Manager's Desired Configuration Management. In order to stem the tide and decrease the database size I have turned off all DCMs and removed any assignments, as FEP were really the only DCMs we were using. That was 5 days ago and I'm still seeing DCM noncompliance task status appear in the Service Manager database? Does anyone have any ideas how I can begin to troubleshoot why Service Manager is getting DCM statuses when there aren't even any DCMs enabled or assigned? Tom Aguero Technical Support Shared Services | Information Technology 900 N Garver Rd, Monroe, OH 45050 Phone: 800.834.8001 [email protected]<mailto:[email protected]>
