Hi All,At the moment I'm trying to figure out to no avail of how to enable remote desktop into a single Windows Server 2003 Std. Which is stand alone (not join to the domain)?currently i can do 2x Administrator Remote Desktop + 1x Administrator Logon locally (in front of the Server). What I want is that to enable multiple local user to have access using Remote desktop into it.I don't have and not planning to have a terminal server in place so I wonder if there is any solution for this?Any idea would be greatly appreciated.Thanks. Does the application have any sort of user registration/login? If the user has to be set up in the application I could see the problem occurring.
How To Crack Windows Server 2003 Terminal Services Install
If that's the case, the issue should occur with any new user that you create. I think at this point you've pretty much eliminated any possibility of an issue with the user account itself in Windows.I would look at file ownership to make double-sure that permissions aren't set for individual users, and I would look at any sort of validation or user setup for the application. Akp982 wrote:Is win connect legal?My feet tell me no because it breaks the Microsoft licensing? I maybe wrong?1.4 Remote Desktop/Remote Assistance/NetMeeting. TheSoftware contains Remote Desktop, Remote Assistance,and NetMeeting technologies that enable the Software orapplications installed on the Workstation Computer(sometimes referred to as a host device) to be accessedremotely from other Devices. You may use the Software'sRemote Desktop feature (or other software which providessimilar functionality for a similar purpose) to access aWorkstation Computer Session from any Device providedyou acquire a separate Software license for that Device.As an exception to this rule, the person who is thesingle primary user of the Workstation Computer mayaccess a Workstation Computer Session from any Devicewithout acquiring an additional Software license forthat Device.
When you are using Remote Assistance orNetMeeting (or other software which provides similarfunctionality for a similar purpose) you may share aSession with other users without any limit on the numberof Device connections and without acquiring additionallicenses for the Software. For Microsoft andnon-Microsoft applications, you should consult thelicense agreement accompanying the applicable softwareor contact the applicable licensor to determine whetheruse of the software with Remote Desktop, RemoteAssistance, or NetMeeting is permitted without anadditional license. Check out xpunlimited atI've been using thir solution for over 3 yrs at to locations. The original XP Pro eula states that no more than 16 simultaneous logins or conections to an XP pro pc. Microsoft changed a few dll's to limit this when they decided - uh oh, we could lose a lot of $$$ if people use XP Pro instead of our server product.It's scalable to multiple pc's, they have good support, the admin utlity makes it a snap to setup the desktops for the remote sessions. Users can have full desktops, or just be presented the apps. You wish them to access.
John7360 wrote:Check out xpunlimited atI've been using thir solution for over 3 yrs at to locations. The original XP Pro eula states that no more than 16 simultaneous logins or conections to an XP pro pc.
Microsoft changed a few dll's to limit this when they decided - uh oh, we could lose a lot of $$$ if people use XP Pro instead of our server product.It's scalable to multiple pc's, they have good support, the admin utlity makes it a snap to setup the desktops for the remote sessions. Users can have full desktops, or just be presented the apps. You wish them to access.$716 for unlimited users, not to bad. Winconnect is $300 per 3 users.
To install Terminal Services on a Windows Server 2003 on all clients within a network, follow the steps below:. Click Start button.
Terminal Service Configuration Windows 10
Go to Control Panel. Double click Add/Remove Programs. Click the Add/Remove Windows Components option on left side of the window. The components wizard will start automatically, scroll down the list to the Terminal Services option. Click the checkbox next to this option. Click Next to proceed. The appropriate files will be copied from the Windows Server 2003 distribution CD and click Finish to end the wizard.