The remote functionality for users to view the print server security user interface is supported for certain earlier operating systems, including Windows Server , Windows Vista with SP1, and Windows Vista with SP2. However, the delegated print administrator functionality is currently only available on Windows Server R2 and Windows Server Print server permissions control the levels of access for users on a particular print server.
Printer permissions control which printing tasks users can perform on newly added printers that are managed by the print server. Administrators should assign these permissions as needed to users who are not system administrators.
After an administrator customizes the security settings for the print server, all newly added printers to this print server automatically inherit these security settings. The security settings for the existing printers on the server are not altered. The View Server permission assigns the ability to view the print server. Without the View Server permission, users cannot see the printers that are managed by the server. By default, this permission is given to members of the Everyone group.
The Manage Server permission assigns the ability to create and delete print queues with already installed drivers , add or delete ports, and add or delete forms. Only users who have Manage Server access and are members of the Administrators group can add printer drivers.
The Print permission assigns the ability for users to connect to printers and to print, pause, resume, start, and cancel their own documents. By default, this permission is given to members of the Everyone group when a print queue is created. The Manage Documents permission assigns the ability to control job settings for all documents and to pause, restart, and delete all documents. The Manage Printer permission assigns the ability to pause and restart the printer, change spooler settings, share a printer, adjust printer permissions, and change printer properties.
The ability to assign access to a printer on a per-user or a per-group basis makes it possible to manage printers from a central location. For example, an administrator could limit access to a printer in a public area while managing the printer from a more secure, central location. Members of the Administrators group can create a full delegated print administrator by assigning the Manage Server permission to a user.
When the Manage Server permission is assigned, the View Server permission is also automatically assigned. You can also delegate a subset of these permissions to create a partial delegated print administrator. In the left pane, click Print Servers , right-click the applicable print server, and then click Properties. For more information about how to publish report model to report server, please refer to the following article,.
For more information about how to migrate report service , please refer to the following article,. If you have anything unclear, please feel free to let me know.
Thanks, Bill Lu. I tried these steps just now without any luck. The same error appears. I tried changing the servername to localhost since its the same server as BIDS.
I looked at both your links. The migration was completed without a hitch. Everthing seems to be working fine excpt fo this problem. I'm still wondering though if there is something about migrating from SQL to R2 that brings up this problem. I was thinking maybe some field somewhere in the ReportServer database that isn't there for R2 or a switch that wasn't changed when the SSRS Configuration Manager configured the DB for R2 thru the migration process.
Reading thru other people's problems with various issues on SSRS many have said after they made this switch their problems went away. We spent alot of time testing everything under the current setup.
So, changing it for just a possibility it may fix the problem is something I'm not too keen about. But I may have to if there is no alternative. If you migrate your SSRS from to R2 according to MS wizard strictly, once you use reporting services configuration manager connecting to report server database, report server database should be upgraded to report server R2 version completely.
Please pay attention to the below migration steps:. Buck up the files and data including the report database and encryption key which you will later use to regain access to encrypted data. Install report service R2 but not configure it please remember the startup account you setting for it.
Restore the report server database to sql server R2 database engine instance Create the RSExecRole in the system databases if the Database Engine has never hosted a report server database. Configure the report server please remember to restore the encryption key you backup previously.
Create role assignments and add the report server site to Trusted Sites to support local administration role assignments need to add your domain account both in Folder Setting and Site Setting.
Bill Lu. Windows Server Developer Center. Sign in. United States English. Home Learn Downloads Community. Ask a question. Quick access. The administrator tries to run a program on the computer. The program requires elevated user rights. In this scenario, you are prompted to enter the credentials of the administrator.
Additionally, the administrator receives a black screen in the Remote Assistance session. When a standard user account has been granted some additional privileges, the the remote administrator is not presented User Access Control elevation prompts. A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article.
Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix. If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix.
For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:. If you do not see your language, it is because a hotfix is not available for that language. For more information about how to obtain a Windows Vista service pack, click the following article number to view the article in the Microsoft Knowledge Base:.
The English United States version of this hotfix installs files that have the attributes that are listed in the following tables.
0コメント