2000bug
asked on
SQL Reporting Services 2000 Revoke Builtin\Administrators
Hi,
Does anyone know a way of revoking the Builtin\Administrators access from SQL Reporting Services 2000. I would like to deploy our Reports Server to a shared webfarm environment and do not want the server SA's to have access to these reports. I have tried deleting the group via the Reports GUI but the users seems to always have access.
Many Thanks
Does anyone know a way of revoking the Builtin\Administrators access from SQL Reporting Services 2000. I would like to deploy our Reports Server to a shared webfarm environment and do not want the server SA's to have access to these reports. I have tried deleting the group via the Reports GUI but the users seems to always have access.
Many Thanks
ASKER
Hi,
I did remove the BUILTIN\Administrators group from Site Settings -> Configure Site Wide Security and also from the Home Folder Security but members of the group were still able to access the front end with full access rights. My worry is that this group has is setup internally to reporting services and cannot be removed.
I'm not to concerened with blocking access on the db as we have other controls in place to prevent changes here.
Any help would be much appreciated.
I did remove the BUILTIN\Administrators group from Site Settings -> Configure Site Wide Security and also from the Home Folder Security but members of the group were still able to access the front end with full access rights. My worry is that this group has is setup internally to reporting services and cannot be removed.
I'm not to concerened with blocking access on the db as we have other controls in place to prevent changes here.
Any help would be much appreciated.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Did you remove the BUILTIN\Administrator account under:
Site Settings -> Configure Site Wide Security -> and then delete Admin account?
SQL:RS has 2 levels of security.. one for accessing the front end (Report Manager) and security at the datasource level. Your going the right way, as it's easiest trying to block the front end because SA accounts are too integrated in the dB.