NOTE: Users are
authorized in the following
order:
|
- Total sessions for this server
- IP address restrictions (Citrix and
Terminal Services only)
- User restrictions (counts user sessions
on all managed servers)
- Group restrictions (counts group
sessions on all managed servers)
|
|
Citrix MetaFrame / WinFrame Authorization
The MetaFrame/WinFrame authorization feature set
provides the ability to use ServerBoss tools on
Citrix MetaFrame and Citrix WinFrame Servers.
This feature set uses the Citrix API in addition
to NT APIs to provide the best level of
ServerBoss performance and stability on Citrix
server platforms. No client-side configuration
or software installation is required for Citrix
authorization.
|
|
NFuse and Program Neighborhood
Logging into NFuse or Program Neighborhood does not create a persistent session. There is no way for ServerBoss to determine when these API type logons are executed and Winlogon is not invoked on a server. Therefore, you cannot directly restrict by NFuse or Program Neighborhood logons. You can provide the same effect using logon checking and/or application checking as long as you understand how NFuse and Program Neighborhood work in terms of creating new sessions.
|
When you use Program Neighborhood or NFuse
to connect to your application set you will have
one session for every server you connect to. For
example, say you have two Citrix servers,
Citrix1 and Citrix2. Citrix1 is publishing
C1Outlook and C1Project. Citrix2 is publishing
C2Word and C2Excel. When you open Program
Neighborhood or NFuse, you will not have any
sessions. If you then run C1Outlook, you will
have one session on Citrix1. If you then run
C1Project, you will still have only one session
and will be running both apps in the same
session. If you then run C2Word, you will have a
session on Citrix2 as well. If you run C2Excel,
you will have one session on Citrix1 and one on
Citrix2. Even though you have all four published
applications running at the same time you will
only have two sessions, one on Citrix1 and one
on Citrix2.
The exception to this rule is publishing a
desktop. Connecting to a published desktop will
always create a new session that can’t be shared
by another other published apps.
|
|
Integrating with ServerBoss
If you want to authorize your users for a
certain number of launches of any given
application you should use application checking
and publish the renamed SBAppChk.exe (see
application checking installation). Using the
information above you may also be able to use
logon checking to fit your needs. If you have
any questions or would like help configuring
ServerBoss to work in your scenario please
contact ServerBoss support by calling (800)
878-0790 or emailing
support@serverboss.com.
NOTE: Either MetaFrame/WinFrame or Terminal
Server authorization feature set is required in
order to purchase and use the application
authorization feature set.
NOTE: LAN checking is not required for Citrix or
Terminal Server authorization, even when the
remote clients are on the same LAN. No client
configuration or software installation is
required for Citrix or Terminal Server
authorization. |
Browse Additional Features: |
 |
 |
|
|
|
Terms & Conditions |
Privacy Policy |
Return Policy
|
|
|