WinConnect Server VS is a software solution that turns a Windows Host computer into an RDP 6.0 Server. This allows multiple Remote Desktop Protocol (RDP) 4.0, 5.0, 5.1, 5.2-and 6.0-enabled devices (such as Terminals, Internet/Information Appliances, Tablet PCs and PDAs) to connect to it to run Windows applications simultaneously and independently. These devices can connect to the server over a wired or wireless TCP/IP connection, such as local area network (LAN), wide area network (WAN), dial-up (Internet), digital subscriber line (DSL, ADSL), Integrated Services Digital Network (ISDN), or virtual private network (VPN) connection.

You can remotely connect to your computer from another office, from home, or while traveling. This allows you to use the data, applications, and network resources that are on your office computer, without physically being in your office.

WinConnect Benefits:

•	Reduces enterprise TCO by providing an alternative to MS Windows® 2000 Server or Windows Server 2003
•	Remote connection means that you have access to your data and Windows applications wherever you need it
•	Centralized processing means that your data is safer, stored on a central computer
•	Centralized processing means that your Thin Client devices (such as Terminals, Internet/Information Appliances, Tablet PCs and PDAs) are less expensive to purchase and less expensive to maintain back

•	You must purchase or register WinConnect Server VS from the computer on which it was installed. Hence, please ensure that you have installed the WinConnect Server VS software on the computer and make sure it is working correctly in demo mode and meeting your requirements before purchasing and registering WinConnect Server VS online.
•	Open Microsoft Internet Explorer and run as an Administrator.
•	Under Microsoft Internet Explorer, click on Tools/Internet/Options/Security/Custom Level. Set the "Reset To:" option to "Medium" and click on the Reset button. Next, click on the "OK" button to apply the changes
•	When prompted to install and run "ThinSoft WinConnect Server Registration Control", you must click on the "Yes" button to accept and trust content from ThinSoft Inc

•	Color Depth - Supports for up to 32-bit color
•	Support Font Smoothing
•	Support Desktop Composition

• Windows® Server 2008 (32-bit), Windows® Vista Business or Windows® Vista Ultimate (32-bit) computer
• Network/Internet connection
• A Pentium IV 2.8GHz or faster processor is the minimum recommendation for 1 Host and 1 Remote Desktop users. Increase the processor speed by 100MHz or more per additional Remote Desktop user, depending on the applications the user will be running. For best performance, a single or dual Pentium IV processor is suggested. Equivalent AMD processors are also supported.
• For Windows® Server 2008 (32-bit), Windows® Vista Business or Windows® Vista Ultimate (32-bit), the minimum memory requirement for 3 Remote Desktop users is (3 x 256 Megabytes) + 512 Megabytes of RAM. With Windows Vista Aero enabled, the minimum memory requirement for 3 Remote Desktop users is (3 x 256 Megabytes) + 1 Gigabytes of RAM.
• 256 MB of additional RAM or more is recommended for each additional Remote Desktop user, depending on the applications the user will be running.

Installation is simple. By following a few steps, it normally takes less than 10 minutes to set up. See the WinConnect Server VS User Manual for instructions.

You can purchase/register the WinConnect Server VS software online via the WinConnect Server VS Control Center or visit our web site at http://www.thinsoftinc.com.

Important Notes for Internet Registration:

1.	Ensure that you are using the Microsoft’s Internet Explorer as the default browser.
2.	Make sure you have logged into Windows as an Administrator with full access rights.
3.	If you are running Windows Vista (32-bit), locate the Internet Explorer (IE) icon in the Windows Quick Launch (next to the Windows Start) or the IE shortcut via Windows Start => All Programs => Internet Explorer. Right-click on the IE shortcut, and then click “Run as administrator”. If Windows is in Classic View, click on Windows Start/Programs/Internet Explorer. Right-click on the IE shortcut, and then click “Run as administrator”. Note: Presume that the Windows User Account Control (UAC) is turned on by default.
4.	Within Microsoft Internet Explorer, click on Tools => Internet => Options => Security => Custom Level. Set the "Reset To:" option to "Medium" and click on the Reset button. Next, click on the "OK" button to apply the changes. This is the required Internet Explorer setting and is what the WinConnect Server VS Registration page requires in order to successfully work the purchase/registration process. Notes: When prompted to install and run the "ThinSoft ..." and/or the "SheriffNet Module" ActiveX controls, you must click on the "Yes" button to install and run the ActiveX controls. Please wait for each page to load completely before proceeding to the next page.

Step 1:	On the Windows desktop, right-click on the WinConnect Server VS Control Center icon and then click "Run as administrator". Click on the WinConnect Server VS Control Center icon located on your desktop. This will launch the WinConnect Server VS Control Center. First, select Help from Control Center menu, and then select Register on the Web from the Help sub-menu.
Step 2:	Microsoft Internet Explorer will be launched and directed to the WinConnect Server VS Registration site. Select the language you wish to use to register WinConnect Server VS.
Step 3:	If you have purchased WinConnect Server VS prepaid serial number(s), enter the prepaid serial number(s), and click the “Register New Serial Numbers” button. If you do not have the WinConnect Server VS prepaid serial number(s) and want to purchase/ register WinConnect Server VS license online, select the option “Check this box if you would like to purchase additional user licenses” and click “Create New License and Purchase WinConnect Server VS” button.
Step 4:	Enter the information requested and click “Continue with Registration”.
Step 5:	Once WinConnect Server VS is successfully registered, you will need to restart Windows.

WinConnect Server VS can be purchased online via http://www.thinsoftinc.com at a price of US$ 299.95 per pack of 3 users. Each WinConnect Server VS license allows an additional 3 users. As user needs increase, additional licenses can be purchased online.

Yes, up to a maximum of twenty-one (21) Remote Desktop Clients can be connected to the WinConnect Server VS Host.

It depends on the type of software products you are using. Most software products will allow all users to open and edit different documents at the same time, using the same program. Each user can also use different software products, concurrently.

If you have any questions regarding compatibility of a particular application program, you can download the trial version of WinConnect Server VS to test your application before you purchase. Alternately, you can ask the software vendor if the application supports Windows Terminal Services. If Windows Terminal Services is supported, the software will most likely work on the WinConnect Server VS environment.

Users who intend to run the software products concurrently are advised to do the following:

(a) Review the Software Products' End User License Agreement if they are authorized to run multiple instances/sessions, using a single copy of the Software Products, concurrently

and/or

(b) Check with the respective companies of the Software Products for such usage and/or similar usage.

It depends on the types of applications you are running. Some applications will provide full read and write privileges to the user who opened or accessed the file first; the other users may then have read only privilege.

All of your preferences are stored in individual "profiles". Your profile stores all of your preferences, and individual information.

In order to take advantage of this feature, each user must log in to the system with a unique user name.

The Remote Desktop Client supports windowed DOS box where you can run DOS applications and access the DOS command prompt.

Files can be stored on the central WinConnect Server VS Host or on the local storage of the Remote Desktop Client.

Yes, if the Remote Desktop Client is a RDP 5.1, 5.2 or 6.0-enabled device and local drive redirection is enabled when connecting to the WinConnect Server VS Host.

Data can be stored in the central WinConnect Server VS Host instead of the local PC hard drive. Normally, the server is located in a secured place and is only accessible by an IT personnel who has the rights to do so. The data transmitted from your Remote Desktop Client, normally, takes a path along a secured communication/network, to the WinConnect Server VS Host. Consider this security against data stored on a PC, in an open office environment, vulnerable to be stolen along with your data (in the Thin Client environment, they would have stolen a "nearly" worthless box with no data in it).

The performance of the WinConnect Server VS Host will depend on the system set-up and configuration, the number of users supported and the applications the users will be running.

For more information, refer to "What is the recommended WinConnect Server VS Host requirement?" above.

A broadband Internet connection over digital subscriber line (DSL, ADSL), cable or Integrated Services Digital Network (ISDN) connection improves performance. However, RDP transfers only minimal data (such as display data and keyboard data) between the WinConnect Server VS Host and the Remote Desktop Client, therefore, it works even with a low-bandwidth Internet connection over a wired or wireless connection (Dial-up, GPRS, etc.).

It depends on the server settings. If the 'Max session idle time' option is enabled, connections will be disconnected after the specified amount of idle time. This means that the session will disappear from your screen and it will become 'disconnected'. It doesn't mean the applications you had opened will be closed. If you reconnect to the WinConnect Server VS Host again, they will still be active. You may configure the server settings so that 'Disconnected' sessions stay in that state for certain amount of time, during which you can reconnect. If you do not reconnect within the specified amount of time, the disconnected session will be log off and all applications will be closed, at which point, the next time you reconnect, you will have to re-run the applications, as you will be starting a new session.

Yes, Windows and Novell Netware networks are supported. You only require one network node (one network card and one IP address) for all the users. Users can login to the network by using different user names and passwords.

The Console user cannot monitor and control the activities on the Remote Desktop Clients.

The Security Policy Settings in Windows Server 2008 (32-bit) and Windows Vista (32-bit) allows the Administrator to control certain user's privileges, as well as control certain actions allowed for the users.

Administrator can modify the security-relevant settings, including users' rights to shut down Windows, by configuring the Local Security Policy.

The WinConnect Server VS allows multiple users to simultaneously and independently share the same hardware and software installed on the Host computer. Some software is licensed for use on a single computer while other software may be licensed for single or multiple users. It is the responsibility of the WinConnect Server VS purchaser/user to read and comply with the licensing agreements of any software that may be used.

Additionally, it is the responsibility of the WinConnect Server VS purchaser/ user to read and comply with the Windows licensing agreement with regards to Remote Desktop access, or contact Microsoft for clarification.

You may download or purchase the WinConnect Remote Desktop Client software from our web site at http://www.thinsoftinc.com

The Remote Desktop Client software is available for download at the Microsoft web site here. The client software is installed by default on computers running Windows Vista (32-bit) and Windows Server 2008 (32-bit).

The instructions on how to create a Remote Desktop connection and start a Remote Desktop session are available for download at the Microsoft web site here.

The Remote Desktop Client software is available for download at the Microsoft web site here.

On the MS Remote Desktop Connection (RDC) software, click on Options --> Local Resources --> More and check the "Drives" option, then connect to the WinConnect Server VS Host.

Within the remote desktop session, open "My Computer" and you should be able to see the local drives.

Note: You may not see the remote client’s local drives appear in the Windows Explorer of the remote desktop session immediately. There may be a short delay for all the local drivers to be redirected.

For local printer re-direction on the remote client:

1.	On the remote client, before connecting to the WinConnect Server VS Host, you will need to install the printer as per normal and make sure that the printer is working correctly, please refer to the printer user manual for installation instructions.
2.	On the remote client, open the MS Remote Desktop Connection (RDC) software, click on Options --> Local Resources, and check "Printers". Then connect to the WinConnect Server VS Host. On the remote desktop session, click on Start --> Settings --> Printers and Faxes; you should then see your printer (please see note below).

NOTES:

Printing at the remote client location is a function of the MS RDC software being used. The MS RDC software send the information about the local printer to WinConnect Server VS/Windows Server 2008 (32-bit)/Windows Vista (32-bit) Host and if that printer is listed among the Windows native printer list, then all will go fine. If the printer model is not one contained within the list of Windows native printers, then it will be necessary to install the printer driver on the WinConnect Server VS/Windows Server 2008 (32-bit)/Windows Vista (32-bit) Host first. In some cases, to install the printer correctly on the WinConnect Server VS/Windows Server 2008 (32-bit)/Windows Vista (32-bit) Host will require actually connecting the printer to the WinConnect Server VS/Windows Server 2008 (32-bit)/Windows Vista (32-bit) Host or the printer driver will not install properly. When this installation is done, the printer should be detected as a local printer when the remote client is connected to the WinConnect Server VS Host.

If local printing still does not work after following the above procedure, you will need to check with the printer manufacturer to verify if the printer driver is designed to support Windows Terminal Services, or the procedure to install the printer and it's printer driver to work under Windows Terminal Services

Printers that use ports that do not begin with COM, LPT, or USB are not redirected in a remote desktop connection. Please check with your printer manufacturer's Technical Support on how to configure your printer to use a COM/LPT/USB port.

The use of a firewall will improve the security of your WinConnect Server VS Host. However, both the built-in Windows Server 2008 or Windows Vista firewall and third party firewalls will block the network traffic necessary for Remote Desktop Protocol (RDP). This traffic must be enabled for WinConnect Server VS Host to work.

There are three ports necessary for WinConnect Server VS. The first two TCP ports required for WinConnect Server VS software and RDP are 3389 & 36157. The third is a UDP port required if you want the computer to be visible as a terminal server to a client browsing the network. This is port 137.

If you are using a third party firewall, please see the documentation that comes with your firewall.

To configure the built-in Windows firewall, go to Start>Control Panel>Security>Windows Firewall. Click on the Change Settings option. On the Exceptions tab, check Remote Desktop. This will enable the TCP port of 3389. Click on the Change Settings option. On the Exceptions tab, check Remote Desktop. This will enable the TCP port of 3389. Click on the Add Port button. Type a short name for the port to help you remember what it is used for. Enter "137" for External Port number. Click on UDP, and then click on OK. Click on OK in the Windows Firewall dialog box.

For additional security it is possible to change the port number used by RDP. Instructions can be found in FAQ on “Using port other than the standard Microsoft RDP port 3389”. If you do change this port number, you must also adjust your firewall to enable TCP traffic through whatever port you have chosen.

Background:

1.

Without WinConnect Server VS software installed, Windows Server 2008 native terminal services or Windows Vista's native remote desktop listens to port 3389 (0d3d Hex).

2.

With WinConnect Server VS software installed, WinConnect Server VS software listens to port 3389 (0d3d Hex) and Windows Server 2008 native terminal services or Windows Vista's native remote desktop listens to port 36157 (8d3d Hex). Note: The difference between ports 0d3d Hex and 8d3d Hex is: a. the most significant bit of 8d3d Hex is set and the most significant bit of 0d3d Hex is cleared; or b. 8d3d Hex is the equivalent of (0d3d Hex OR 8000 Hex); or c. 0d3d Hex is the equivalent of (8d3d Hex AND 0FFF Hex).

Follow the steps described below to connect to the WinConnect Server VS system's Console session from the remote client via the Remote Desktop Connection software:

Step 1:	Open Remote Desktop Connection (Click Start, point to Programs or All Programs, point to Accessories, and then click Remote Desktop Connection)
Step 2:	Click on the Options button to configure the Windows Logon and connection settings
Step 3:	In Computer, type in the IP address of WinConnect Server VS system and port number used by WinConnect Server VS software (e.g. 218.10.0.30:36157; port number must be in decimal). Click Connect.
Step 4:	In the Log On to Windows dialog box, type in the same user name and password that user has logged on the WinConnect Server VS system, and then press the Enter key. The Remote Desktop window will open.

Note: If you are still not able to establish the connection, please check to make sure that the TCP port 36157 is not blocked by any firewall on the WinConnect Server VS system, remote client(s) and/or network. Additionally, if you are using a router, please ensure the router is configured to forward port 36157 to the WinConnect Server VS Host. Please see FAQ on “router configuration”.

Background:

1.

Without WinConnect Server VS software installed, Windows Server 2008 native terminal services or Windows Vista's native remote desktop listens to port 3389 (0d3d Hex).

2.

With WinConnect Server VS software installed, WinConnect Server VS software listens to port 3389 (0d3d Hex) and Windows Server 2008 native terminal services or Windows Vista's native remote desktop listens to port 36157 (8d3d Hex). Note: The difference between ports 0d3d Hex and 8d3d Hex is: a. the most significant bit of 8d3d Hex is set and the most significant bit of 0d3d Hex is cleared; or b. 8d3d Hex is the equivalent of (0d3d Hex OR 8000 Hex); or c. 0d3d Hex is the equivalent of (8d3d Hex AND 0FFF Hex). d. In conclusion, changing the port number used by WinConnect Server VS software will affect the port number used by Windows Server 2008 native terminal services or Windows Vista's native remote desktop; and vice versa.

A.

You can change WinConnect Server VS software to listen to a port other than 3389 (0d3d Hex). To do so, run Regedt32. When using Regedt32, please be careful as it is possible to damage your system. Using Regedt32, locate the KEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp key. Within this key, locate the PortNumber subkey. By default, PortNumber is set to 00008d3d Hex, or 36157 (ie PortNumber is the port number Windows Server 2008 native terminal services or Windows Vista's native remote desktop listens to). Modify the Hex value above 00008400 Hex, or 33792. Save the changes and reboot the computer for it to take effect. Addtionally, please check to make sure that the new TCP ports (both the TCP ports used by Windows Server 2008 native terminal services or Windows Vista's native remote desktop and WinConnect Server VS software) are not blocked by any firewall on the WinConnect Server VS system, remote client(s) and/or network. Example: 1. To change WinConnect Server VS software to listen to port 3390 (0d3e Hex), you will need to change the PortNumber subkey (of KEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp key) to 8d3e Hex (Note: 8d3e Hex is equivalent to the most significant bit of 0d3e Hex being set; or 8d3e Hex is equivelent to 0d3e Hex OR 8000 Hex). 2. With this change, WinConnect Server VS software will listen to port 0d3e Hex, or 3390 and Windows Server 2008 native terminal services or Windows Vista's native remote desktop will listen to port 8d3e Hex, or 36158. 3. On the WinConnect Server VS system and/or network, set the Firewall not to block TCP ports 3390 (0d3e Hex) and 36158 (8d3e Hex).

B.

Follow the steps described below to connect to the WinConnect Server VS system from the remote client via the Remote Desktop Connection software: Step 1: Open Remote Desktop Connection (Click Start, point to Programs or All Programs, point to Accessories, and then click Remote Desktop Connection)     Step 2: Click on the Options button to configure the Windows Logon and connection settings     Step 3: In Computer, type the IP address of WinConnect Server VS system and port number used by WinConnect Server VS software (e.g. 218.10.0.30:3390; port number must be in decimal). Click Connect.     Step 4: In the Log On to Windows dialog box, type in your user name and password (if required), and then press the Enter key. The Remote Desktop window will open.

The Remote Desktop Client software allows Windows platforms to remotely connect to a WinConnect Server VS Host to run Windows applications.

First, get the IP address of the host computer (the computer with WinConnect Server VS installed on it).

Right click on an empty area of the desktop and select Command Prompt.

In the DOS box that appears, enter the command: ipconfig. Then hit the Enter key.

The computer’s IP address will be displayed in the information shown. Make note of it.

Next, open a browser and enter the URL http://www.portforward.com in the address bar.

At the bottom of PortForward’s opening page, make a note of the IP address shown after the text: Your external IP address is

This IP address is what your remote users will need to enter into the “Computer” field in the Microsoft Remote Desktop Connection program on their computers. Remote Desktop Connection is part of Windows Server 2008/Windows Vista and can be found on the Accessories menu (Start/Programs/Accessories).

In the second paragraph on the PortForward opening page, locate the word Routers and click on it. This will take you to a page displaying most brands and models of routers. Locate the specific brand and model of router used in your location and click on it (if your router is not listed, please contact your router's vendor for details on how to configure your router's port forwarding for Remote Desktop access. The remote desktop communication makes use of TCP port 3389).

This action takes you to the Application page. Scroll down until you locate Remote Desktop and click on it.

You will now see a step-by-step set of instructions for configuring your router to allow Remote Desktop access. You will be asked to enter an IP address at the beginning of the configuration routine; this is the IP address you obtained in the first part of these instructions.

Note:

Static IP address:

1.	There are two IP addresses involved regarding Remote Desktop access. One is the external IP address owned by the router and the other is the internal IP address of the host computer. Ideally, both of these should be “static” (meaning they never change). Unfortunately, this is not always the case. The external IP address is controlled by your Internet provider. You may check with them if you are not sure whether your account has a static IP address. The host computer’s IP address is entirely in your control. For detailed information on how to set your host computer to employ a static IP address, please see this web page, http://www.portforward.com/networking/static-xp.htm
2.	If you want to allow remote desktop connection to the WinConnect Server VS Host’s Console, please ensure the router is configured to forward port 36157 to the WinConnect Server VS Host.

Windows Server 2008 x64 (64-bit) and Windows Vista x64 (64-bit) are currently not supported.