I have been working in IT since 2001 for companies such as Computacenter and Getronics. I started out as a first line support analyst supporting heterogeneous networks but rapidly worked my way up the ranks expanding my knowledge as I went to include areas such as system builds, deployments, networking, and security to name a few.In 2008 I decided to concentrate on the monitoring and management of large enterprise networks using Microsoft's System Center Operations Manager (OpsMgr) 2007 of which I have extensive knowledge. As testament to this the Windows Management User Group (WMUG), invited me to join their ranks as a Community Leader where I have been invaluable in helping to bolster the OpsMgr skills to the benefit of the group and it's members.I have now moved into an OpsMgr 2007 consultancy role to do what I like most - working with OpsMgr and sharing my knowledge and experiences with the community.
I have been using Opalis constantly since it became available from Microsoft and I think it is an absolutely great application. The ability to integrate, automate and orchestrate virtually anything is awesome and I am now always finding myself saying "Opalis could do that".
When using Opalis this week though, I noticed that Integration Server console kept hanging for 2-3 minutes every time I tried to access certain policies. After trying the usual reboot step to no avail, I went digging a bit deeper and found this MS article, http://support.microsoft.com/kb/2104676.
Basically, Opalis keeps historical data of policies in Policy logs and over time these logs can grow and grow and grow until eventually you start experiencing performance issues in the console. The solution is to simply purge the policy logs and all is good again. And, to prevent the same thing happening in the future, you can schedule the purge of these logs.
To manually purge the policy logs:
To automatically purge the logs, simply follow the steps above, enable and configure a log purge schedule, and hit Finish.
As easy as that!!!