Forum Discussion
RHendle_110546
Jan 07, 2011Nimbostratus
F5 Actions Task not visible
I'm trying to setup action tasks for users based on their role. I understand that under administration, security, user role there are some example profiles that can be used or customized. I've adde...
Dave_Ruddell_79
Jan 08, 2011Historic F5 Account
Hey Rob,
C:\Documents and Settings\username\Local Settings\Application Data\Microsoft\Microsoft.Mom.UI.Console
We are actually not doing anything special with SCOM with how we create views and User Roles. Everything is done through the same means that any user would go through. That being said, there is a possibility of 2 things going on here. The first (and most likely) is that SCOM is caching the Console states in the local registry. When it does this, you will see inconsistancies between the Console and the database. In your case, you are seeing that the F5 Pack isn't showing up for any of the users. If you want to clear this cache, there are a few different alternatives which you can try. The first is to start the Console from the command line with the /clearcache option:
C:\Program Files\System Center Operations Manager 2007\Microsoft.MOM.UI.Console.exe" /clearcache
The next option is to manually delete the console view settings from the registry. They will be located here for the current user:
HKEY_CURRENT_USER\Software\Microsoft\Microsoft Operations Manager\3.0\Console
Or in the appropriate USERS folder:
HKEY_USERS\S-1-5-21-779940496-1561666661-2965329820-1131\Software\Microsoft\Microsoft Operations Manager\3.0\Console
In either of the above cases, if the view was the issue, it should now be cleared out and the next time the console is closed and launched, the cache will be regenerated and the correct views will be pulled from the database. The other location in this case will be in local files, located for each user here for Windows 2008 / Vista / 7:
C:\Users\username\AppData\Local\Microsoft\Microsoft.Mom.UI.Console
or here for most other versions:
Now on the other hand, it may not be your cache at all, in which case you should carefully review your other security roles. In some cases, new views will not automatically be added to the roles when they are added to Operations Manager. I'm not sure why the Admin accounts are not seeing the F5 Folders or Views, but I believe it might be cache related.
For the other User Roles, make sure that the views for that particular user or group are not disabled in another User Role. I have a feeling Operations Manager will pick the most locked down Role, but I could be wrong. I would just make sure you look through your other Roles and make sure there aren't any oddities and definitely make sure to clear out the cached views so you know you are getting the latest and most updated versions for all users.
Let me know if these work out your issues, or if you are still facing these problems afterward. Sorry for the troubles on this, but good luck!
-Dave
Recent Discussions
Related Content
DevCentral Quicklinks
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com
Discover DevCentral Connects