Client Management Suite

 View Only
  • 1.  Permissions Issue with Reports

    Posted Apr 10, 2012 02:47 PM

    Hi all,

    We have recently implemented Altiris 7.1 SP2. We have 20 different locations and each have thier own SIte Server We set up permissions so that each locations Admins could only have access to thier locations PC's. We set up one main Global Security Role and called it Global Symantec Worker 2 and gave global permissions that would apply to all locations admins and then we made a role for each location for example Branch Admin- Louisville, Branch Admin- Baltimore, etc.. We gave each of these roles permissions to thier locations OU in AD view and to thier locations created folders like Louisville Filters, Louisville Jobs & Tasks, Louisville Patch managment etc..

    Each locations Admins are able to only see thier computers and are able to deploy policies on thier computers and everything works fine but when they go to Reports there are alot of reports that don' t show information for espcecially Patch Management reports for example if i go to Reports\Software\Patch Managment\ Compliance and try to run Compliance by Bulletin, Computer or Update they always get "No Results Returned". I can run it as my admin account and of course it returns results for all computers but we need for each locations admins to be able to run this report and have it report the information on thier computers. Some reports work fine like if I go to Notifcation Server Managment\Agent\Computers with Agent Installed it will return results with computers that have the agent installed just at my location which is what we want instead of showing no results or results from all locations.

    Any ideas? Any help is greatly apprecited. I have worked with Symantec support for the past two weeks and they don't have a clue. I request a different technician to try and get out of India or wherever they are and I get someone else that has no idea and I have to go through the whole senario again and I have to do the same troubleshooting over and over. It is driving me crazy.

     



  • 2.  RE: Permissions Issue with Reports

    Posted Jun 15, 2012 05:38 PM

    I have this problem as well. I dug into it a little bit and found that the store procedure that is used by the compliance reports does it's scoping based on the Default OrgView. So the user has to have read access to the Default computers orgview to be able to see anything in this report. 

    Has anyone come up with a replacment report that doesn't use Default?