Just send an email with as much detail about the issue, including screenshots if
applicable, to support [at] noxigen [dot] com.
Click here to see the latest features and fixes.
Active Directory (optional) - Having the System Frontier
server(s) and users in Active Directory is the ideal configuration, but
workgroup and multiple domain scenarios are also supported.
Web Server - Windows Server 2008 R2 or newer with .NET Framework 4.6.1 or newer. Supports single server or load balancing.
Database Server - MS SQL 2008 R2 or newer (any version, including the free Express
edition). Any OS supported by the version of SQL Server. Single server or
clustering is supported. SQL authentication (mixed mode) must be enabled.
Management Server - Windows Server 2008 R2 or newer with NET
Framework 4.6.1 or newer. It's recommended that the management server's OS match
the highlest level OS you plan to manage.
Managed systems - Target system support includes Windows
10/8.1/8/7/Vista/XP as well as Windows Server 2012 R2/2012/2008 R2/2008/2003 R2/2003/2000. PowerShell Remoting is not required out of the box.
Limited support for Linux, other
operating systems and even network devices (switches, routers, printers, etc..)
is available via the Custom Tools integration. "Limited" refers only to the
built-in functionality. Any function that can be performed remotely via
command-line can be used as a delegated tool in System Frontier. Note: You do not have to install any
agents on managed Windows systems or other devices as System Frontier is
Client Web Browser - (latest recommended) IE 8+, Chrome 22+,
Firefox 21+. iPad, iPhone, Android and Surface RT browsers work, but are not officially supported
yet. Feedback from customers using other devices is greatly appreciated.
FAQ (Frequently Asked Questions)
Q: Does System Frontier require a separate username or password?
A: No. System Frontier utilizes Active Directory and Integrated Windows Authentication
so that NO additional logins or passwords are needed to access the application. Workgroup installations are possible, but
not officially supported at this time.
Q: Do you offer any discounts for educational institutions or non-profit organizations?
A: Definitely. Educational and non-profit institutions receive a 30% minimum discount,
with no minimum license requirement.
Q: How is System Frontier licensed?
A: The software is licensed per physical or virtual node. A "node" being anything that you manage either directly or indirectly with System Frontier. There are no "per user"
For example, if you have
100 servers or workstations to manage, 50 users and have the software installed on 2 web
servers, a 2-node SQL cluster and 1 management server - you only pay for 100
managed device licenses. You can add or remove users and scale out the server
architecture as your needs change without the hassle of a confusing license
scheme. You also save money by
delegating admin rights.
Q: I have dozens or hundreds of machines being added and removed every
month. Will I have to manually configure delegated permissions every time my
A: If you can define dynamic memberships for Containers based on criteria like
hostname patterns, environment, keywords in the description or a number of other
data elements - the answer is no. The Container object in System Frontier let's
you create dynamic groups of servers that will include or exclude computers
based on criteria you provide, making it easy to apply permissions to a large
number of systems as they are added or removed. You can also manually add
or remove systems as needed.
Q: I get a "Caller is not authorized" error when attempting to perform
any management action or pull information up on a server.
A: During the installation of the management service, you must specify the name
of the IIS application pool identity and the IP address of your web server(s).
This is an additional security measure to prevent unauthorized users from
directly accessing the management service. Please check the Authorization.xml
file in the management service installation folder and verify that you have the
correct IPv4 and/or IPv6 address(es) and that the domain\username of the app
pool is correct.
UPDATE: This issue has been resolved for installations where the web console and
management service are installed on the same machine.
Q: I just finished installing System Frontier and get an "access denied"
error when I add a computer.
A: After installation, one of the first things you should do after adding your
license key is update the administrative credentials used for managing your
systems. Go to Settings > Server credentials and put in the the credentials
that have admin rights on servers you plan to manage with System Frontier.
Q: I need to remove admin rights on most or all servers at my
organization. How will System Frontier help me give them the right access?
A: With System Frontier, you can grant very specific rights to manage servers
remotely. No changes will be made to the actual servers you managed because all
roles and permissions are managed internally. Users authenticate to Active
Directory and then are authorized to perform actions remotely on servers based
on permissions assigned to their role(s).
Q: If I open the System Frontier web console from a server, everything
looks out of place.
A: Internet Explorer Enhanced Security Configuration is turned on by default on
Windows Server 2008 and is most likely causing the issue. You should normally
connect from a workstation, but if you need to view the site on the server, try
disabling IE ESC first.
Q: Can't I just use various freeware or open source tools, edit registry permissions,
modify SDDL permission strings or use Group Policy to delegate rights?.
A: If you come up with the right combination of tools, knowledge base articles
and advanced scripting skills or Windows internals - yes... sort of. Most
articles about how to natively delegate admin rights to various objects start of
with "This is really complicated, but...."
With System Frontier, you can centrally delegate very broad or very granular
rights to manage servers or workstations using role based access control. That's something you
definitely don't get with native Windows tools, including Group Policy, although
those tools are great for their intended purposes.