The tool does query the database directly as far as I know, so no reporting services involved at all. You just need read permissions on the database.Torsten Meringer | http://www.mssccmfaq.de

We have a setup where the SCCM installation and the SQL database are on seperate boxes. I have permissions required on the SCCM server but nothing on the SQL box, so I cannot do reports or reporting services and also which is a bit of a pain I cannot use import policy feature in the Roger Zander SCCM Client Center tool which I guess requires SQL permissions to archieve. I know that that tool is not supported on this forum but thought it would be related to the reporting services. Any help on this would be great, I have read some similar questions but they did differ slightly to my requirements which I think maybe a little more basic. You'll need to work on the SQL admins and get yourself some permissions.

We have a setup where the SCCM installation and the SQL database are on seperate boxes. I have permissions required on the SCCM server but nothing on the SQL box, so I cannot do reports or reporting services and also which is a bit of a pain I cannot use import policy feature in the Roger Zander SCCM Client Center tool which I guess requires SQL permissions to archieve. I know that that tool is not supported on this forum but thought it would be related to the reporting services. Any help on this would be great, I have read some similar questions but they did differ slightly to my requirements which I think maybe a little more basic.

The tool does query the database directly as far as I know, so no reporting services involved at all. You just need read permissions on the database.Torsten Meringer | http://www.mssccmfaq.de