Our organization is experiencing lengthy startup times after improper shutdowns that seem to be tied to the size of the WMI repository. For example, a repository folder size of 50 megs might result in 10 minutes added to startup time, while 500 megs might take a whole hour.
There's a hotfix for this sort of problem, but I'd like to track down what's causing the repository to grow. Certain pieces of software? Multiple user profiles? In some cases, a couple hundred different users might have profiles on a given machine. We do not use roaming profiles, and we use delprof2 to clear these profiles out periodically, but it doesn't have any effect on this repository size.