January 8, 2014 at 2:47 pm
We recently moved the Reporting Services system from one domain to another. The production domain is its new home, on a VM that houses both the dbs and SSRS services. Previously, when it was on the other domain, users of said domain could get to the Report Manager and schedule their own reports easily. Now, attempts to get to the schedule show them several fields that are disabled, like the email fields. It auto fills in their name. For example, mine would fill in 'TJay.Belt', but nothing else. It is not a valid email address, and it is rendered disabled, and cannot be changed.
Admins on the machine, can schedule reports, and edit these fields. But users cannot.
Somewhere, in the move from the users domain to the production domain, we lost some security, is what I am guessing.
On the Report Manager, we have granted a group rights in permissions to be Browsers, as we had done in the other system (well, more groups and individuals then. we narrowed it to a single group that all groups and users are amember of, to simplify it).
I was poking around on the actual box and noticed that the old system had 'Domain Users' as a windows user, and granted this same on the new machine. No testing has occurred to see if this magically fixed it.
But it comes down to this, users are all members of Domain X, and SSRS is in Domain Y, with users able to reach Report Manager, but certain options within are not enabled, leaving them unable to use Report Manager fully.
What did we goof up? where should we look to fix? etc?
Viewing 0 posts
You must be logged in to reply to this topic. Login to reply