
You need local administrator rights on the WTS to perform any installation.
To prevent possible screen flicker issues on WTS, it is absolutely required to install and apply the Microsoft hotfix 955692. For more information, see http://support.microsoft.com/kb/955692/en-us. The equivalent Citrix hotfix reference is CTX121354.
It is also possible to install NWBC centrally on Windows Terminal Server (WTS) farms which end-users can access.
You have to log on to the WTS as local administrator to perform the installation. The installation is always done in install mode. If you switch the WTS into install mode additional registry entries will be maintained during the installation process, and the environment will be prepared for multi-user environments. For more information, see http://www.msterminalservices.org/articles/Managing-User-Specific-Application-Configuration-Data-Terminal-Service-Environment.html .
For end-users the NWBC works only after a domain user has logged on as administrator via Independent Computing Architecture (ICA) and has started the NWBC in install mode at least once. Usually, the local administrator can do this. It is also possible to install NWBC via Remote Desktop Protocol (RDP) as administrator.
The number of NWBC sessions that can be supported on a WTS server is very dependent on the typical usage pattern, for example whether SAP GUI or Web Dynpro applications are run, and the number of open windows. NWBC is also an application with an extensive use of graphics, which could cause an additional load on the WTS servers.
After having installed the NWBC, the administrator performs configuration settings. For more information, see Administrator Configuration.