Using windows xp as a terminal server




















For more information about Remote Desktop and how to install Remote Desktop on versions of Windows other than Windows XP, click the following article number to view the article in the Microsoft Knowledge Base:. Are you able to remote in via IP address? If yes, look at bad DNS records.

If no, check the keys:. Do you have any other XP machines you could try remoting into? I don't believe there was an RDS patch that would break it, but I could be wrong. Type your user name and password, and then click OK. Paging Zefram Cochrane: Humans have figured out how to make a warp bubble. Show Comments. Hide Comments. My Profile Log out. Join Discussion. Add your Comment. Skip to main content. This browser is no longer supported. Download Microsoft Edge More info.

Contents Exit focus mode. Please rate your experience Yes No. Any additional feedback? DBeer, NComputing is not virtualization but is actually just hardware that facilitate a license violation. In another thread Microsoft stepped in and clarified that NComputing is absolutely illegal and can never be used with Windows XP. It can only legally be sold because 1 It passes the legal violation on to the end user as NComputing carefully says that it does not take responsility for the licensing aspects and 2 There is a way, with Windows Server and terminal server CALs to make it legal - but then you have everything already and it makes no sense.

Scott Windows XP is licensed for one user at a time, period. No technology overrides the Windows license which is the only real limitation that you have with XP.

It is easy to make it do what you want but it cannot be done legally. There are several products that claim to provide what you want but all that we have seen mentioned in SpiceWorks thus far very clearly violate the XP EULA and put you in the same position legally as if you had just pirated many copies of XP. No actually virtualization involved. It's all just manager buzz words meant to confuse.

But obviously they are not related to virtualization at all. If NComputing was actually virtualizing Windows XP on top of Windows XP they would be in for even heavier license violations than with just remote desktops thin clients.

For multiuser applications, customers should run NComputing vSpace software on a server operating system Server for an XP-like end-user experience or Server for a Vista-like end-user experience. Notice that Windows XP and Vista do not support more than a single user.

So whatever NComputing is doing is literally getting you nothing that you didn't already have with the base operating sytem with Remote Desktop enabled.

You will have to own one physical box for each user and all they are doing is accessing them remotely. Except NComputing has gotten you to buy expensive hardware from them and you get nothing for it. So this is a crazy expensive solution and no one seems to know any benefits of using NComputing over just using the OS provided by Microsoft.

In fact, it is almost certainly far worse, but that is just a guess. They list VDI here but that cannot be the case or else even using NComputing on a single box would not be legal without extremely expensive Windows virtual licenses as virtualizing XP or Vista without them is not allowed. The VDI is a mistake in the Wikipedia entry or else Microsoft has missed this additional licensing issue in their diligence on NComputing's product. What NComputing does that is "special" is that they do not require traditional thin clients but make what are basically "Windows terminals.



0コメント

  • 1000 / 1000