Can I publish my windows application on web

Forums / NoMachine for Windows / Can I publish my windows application on web

Viewing 8 posts - 1 through 8 (of 8 total)
  • Author
    Posts
  • #2953
    Avatarhamel
    Participant

    Hi every body

    I have a few windows applications and I wish to publish them on the web and my customers be able to works with them remotely. Citrix Xenapp upon windows server and windows terminal server provides this functionality but the license costs for them are very high. Please tell me, does NoMachine provide such functionality? and if so which product? I appreciate your guidance.

    #3037
    AvatarBritgirl
    Keymaster

    NoMachine can’t replace a Windows Terminal Server computer or make any Windows computer become a Windows Terminal Server. Even if it was possible to overcome the technical limitations, this would still be in violation of the Windows licensing terms. In fact both XenApp and Citrix WinFrame/ MetaFrame, as they were formerly called, require a Windows Terminal Server to operate.

    Because of the high cost of licensing of Windows Terminal Server and the need to have a Windows Client Access License for every client accessing the server, this is not the way we suggest our clients to deliver Windows applications to multiple users. What we suggest is creating multiple Windows instances virtualized on top of popular hypervisors like Xen, KVM or VMware, install the applications to be delivered in the virtualized Windows environment, install the Enterprise Desktop on each instance and add each instance to a NoMachine Cloud Server. You can then create the required user profiles on the Cloud Server to let the user access only the application to which he/she subscribed. NoMachine lets you control exactly to which virtual machine or application the user will have access, plus scripting tools to tell the server what it must run when the user connects or disconnects.

    All NoMachine Enterprise servers can deliver as many Windows instances as you like, federated in a high-availability cluster. This includes the NoMachine Cloud Server, letting users access whatever application using a Web browser.

    #3417
    Avatardsreynol
    Participant

    Where are the doc details on how to actually execute this?

    and add each instance to a NoMachine Cloud Server. You can then create the required user profiles on the Cloud Server to let the user access only the application to which he/she subscribed. NoMachine lets you control exactly to which virtual machine or application the user will have access, plus scripting tools to tell the server what it must run when the user connects or disconnects.”

    #3487
    AvatarBritgirl
    Keymaster

    There is currently a bug in profiles which won’t let you correctly disable access to the node:

    User can connect to a remote node even if access to that host is disabled by profile rules
    http://www.nomachine.com/TR05L04399

    Once this bug is fixed the correct procedure will be to create user profile rules to forbid connections to specific Enterprise Desktops:
    /usr/NX/bin/nxserver –ruleadd –class node –type <node:port> –value no  –user <username>

    where <node:port> is the name of the node as displayed by the nxserver –nodelist
    Because of TR05L04399, a solution is to use the redirect capabilities instead of profile rules. You can use the following command to redirect connections from the cloud server to the enterprise desktop based on the users:

    /usr/NX/bin/nxserver –useredit <username> –redirect <node:port>

    where <node:port> is the name of the node as displayed by the ‘nxserver –nodelist ‘ command.

    Redirection can be set also on-per client IP basis:

    /usr/NX/bin/nxserver –hostadd <clientIP> –redirect <node:port>

    Pre-requisite is that the user has a system account on the Cloud server host and on the Enterprise Desktop host. The username has to be the same. First of all add each Enterprise Desktop as a node of the Cloud server by running the following command from a console on the server host:

    /usr/NX/bin/nxserver –nodeadd <IP of the Enterprise Desktop>

    You can gather information on the node by running:

    /usr/NX/bin/nxserver –nodelist

    All the Enterprise Desktop you added will be seen by all users connected to the Cloud Server. Users will be able to choose which Windows desktop to join.

    #3500
    Avatarsnejok
    Participant

    Britgirl, as I know, “–redirect” option is only one way to force “user or ip” to choose certain node.

    I think it will be nice if you could make fully “redirect and forget” mechanism and sessions will continue to work when Enterprise Server shuts down 😉

    Because Enterprise Server “stays in the middle” of NX session in the current realisation and is a point of failure. Maybe clusterisation helps with it, but, as I understand, anyway all nx sessions will be disconnected when the cluster switch (or not?).

    I speak about “fully redirect” mechanism, that redirects session on another NXSERVER and forgets about this session (will not stay in the middle): works as dispetcher-redirector only.

    #3499
    Avatardrichard
    Participant

    @hamel:  I can’t speak to your exact license situation, but from a technical standpoint there is a way to publish a Windows app on the web.  Linux support multi-user connections and has no CALs.  What you could do is create user accounts on Linux, and in the Xsession file instead of running a desktop, just run a rdesktop connection back to Multi-user Windows and their software applications.  Using rdesktop on Linux, you can publish a whole desktop with Start bar or just run one particular application.  Rdesktop also can kick into fullscreen mode with no window manager, so it will consume the whole pane of NX.

    We have many Windows applications deployed using NX on Linux in a similar manner.  We purchased User CALs instead of workstation CALs, which allows users to connect from any end device and gives you more freedom.

    #3687
    AvatarBritgirl
    Keymaster

    @snejok

    Because Enterprise Server “stays in the middle” of NX session in the current realisation and is a point of failure. Maybe clusterisation helps with it, but, as I understand, anyway all nx sessions will be disconnected when the cluster switch (or not?).

    The high-availability feature of NoMachine monitors the servers in an active-passive set up. Check this document for more details:

    https://www.nomachine.com/DT03L00066

    Sessions on the NoMachine nodes are preserved in case of failover and can be reconnected.

    #3695
    Avatarhaiderghny
    Participant

    thanks so much

Viewing 8 posts - 1 through 8 (of 8 total)

This topic was marked as solved, you can't post.