no increasing their profile size is the only option. The way (i think) caching works is per view, so if you get to a size of 80mb, the users might use less views and get a smaller profile... than again if they create custom views it can become a lot bigger (to the extreme of 1-2 GB :)). Cleaning up the profiles on logout helps when you are on a TS configuration... Rob Korving http://jama00.wordpress.com/

no increasing their profile size is the only option. The way (i think) caching works is per view, so if you get to a size of 80mb, the users might use less views and get a smaller profile... than again if they create custom views it can become a lot bigger (to the extreme of 1-2 GB :)). Cleaning up the profiles on logout helps when you are on a TS configuration... Rob Korving http://jama00.wordpress.com/

Hi, I've been authoring MP's containing groups, webapps, views and rules using the full SCOM console (not the Authoring Console). The trouble is that since the authoring, my profile immediately went through the roof - going from 7MB to 76MB. After a bit of research, I found that by deleting the reg key Computer\HKCU\Software\Microsoft\Microsoft Operations Manager\3.0\Console and the running NTREGOPT I could get my 7MB profile back again. The real problem though is that the registry file immediately grows when you use the full Console to access the MP views again. To make matters worse, user profiles are limited to 25MB, after which people are prevented from logging out. These views are needed to be used by other users, user who I can't expect people to hack and compact their registry every day.. Is there any way that I can disable this behaviour? I already start the scom console with the /nocache option... Many Thanks, Rob.

Agree with ROb. If you are using the full console for your users you probably have to increase their allowed profile to above 25 MB. I think 75 MB is still small. We have seen much larger for the cache, as Rob Korving says as well. You could try to also create a scom operator role with a very limited amount of available views for those users and see if that makes a difference. Otherwise investigate seriously if they can not work with the web console, which will have a smaller footprint. I see no other ways.Bob Cornelissen - BICTT (My Blog about SCOM) - MVP 2012 and Microsoft Community Contributor 2011 Recipient

Agree with ROb. If you are using the full console for your users you probably have to increase their allowed profile to above 25 MB. I think 75 MB is still small. We have seen much larger for the cache, as Rob Korving says as well. You could try to also create a scom operator role with a very limited amount of available views for those users and see if that makes a difference. Otherwise investigate seriously if they can not work with the web console, which will have a smaller footprint. I see no other ways.Bob Cornelissen - BICTT (My Blog about SCOM) - MVP 2012 and Microsoft Community Contributor 2011 Recipient

Thanks for the advice people, much appreciated. Normal users will use the webapp, but unfortunately the operators will need full console access to create and edit overrides as well as full access to all views. I'll need to up their profile quotas so that it does not become a problem. Many Thanks, Rob.