If you have to communicate with the server's own physical serial port from within a remote desktop session you should change the numbers of the server's physical com ports to a higher value in the server's device manager (e.g. from com1 to com11 and com2 to com12).
Thinstuff Xp Vs Terminal Server For Windows Serial
A terminal server, also sometimes called a communication server, is a hardware device or server that provides terminals, such as PCs, printers, and other devices, with a common connection point to a local or wide area network (WAN). The terminals connect to the terminal server from their RS-232C or RS-423 serial port. The other side of the terminal server connects through network interface cards (NIC) to a local area network (LAN), usually an Ethernet or token ring LAN, through modems to the dial-in/out WAN, or to an X.25 network or a 3270 gateway. (Different makes of terminal server offer different kinds of interconnection. Some can be ordered in different configurations based on customer need.) The use of a terminal server means that each terminal doesn't need its own network interface card or modem. The connection resources inside the terminal server are usually shared dynamically by all attached terminals.
Some terminal servers can be shared by hundreds of terminals. The terminals can be PCs, terminals that emulate 3270s, printers, or other devices with the RS-232/423 interface. Terminals can use TCP/IP for a Telnet connection to a host, LAT to a Digital Equipment Corporation host, or TN3270 for a Telnet connection to an IBM host with 3270 applications. With some terminal servers, a given terminal user can have multiple host connections to different kinds of host operating systems, such as UNIX, IBM and DEC.
The way that a terminal server works tends to vary from one vendor to the next. In the case of a Windows terminal server, the Windows operating system is configured to support multiple user sessions. This is different from other multi-session environments such as a Windows file server because the operating system renders a user interface (UI) for each of the sessions.
When a user needs to interact with a session through keyboard, mouse, or touch inputs, those inputs are made within the RDP client. The RDP client then transmits the inputs to the terminal server for processing. The terminal server is also responsible for performing all graphical rendering, although it is the RDP client that actually makes the session visible to the user.
A terminal Server and a remote desktop both serve a similar purpose. They allow a user to interact with a remote session through an RDP client. The main difference is that terminal servers run on a Windows Server, and the user is therefore provided with a Windows Server desktop. Conversely, remote desktop environments typically have desktop operating systems such as Windows 10 running within virtual machines (VM). As such, the user is provided with a true desktop operating system, rather than a session running on a server.
The point is, that regardless of the OTHER software used, if you access the virtualized Windows session (as in terminal server solution) or a virtualized desktop (a in VDI) you must comply with MS licensing terms. So, whatever VDI suite or "terminal server alternative" you are using you still have to buy appropriate MS licenses - Server CALs, RDS CALs, VDA or SA etc.
The point is, that regardless of the OTHER software used, if you access the virtualized Windows session (as in terminal server solution) or a virtualized desktop (a in VDI) you must comply with MS licensing terms. So, whatever VDI suite or "terminal server alternative" you are using you still have to buy appropriate MS licenses - Server CALs, RDS CALs, VDA or SA etc. At the end, the full licensing cost of those alternative solutions is at least as high as cost of "pure MS" solution - cause you have to buy BOTH Microsoft AND the other party (GraphOn, Citrix, ) - unless you of course go for a Linux desktop VDI ;) 2ff7e9595c
Comments