Thin client on windows

I have updated my post to indicate the target PC is running Win10 Pro. I have a variety of applications I run - the point is to run them seemlessly, as per the RDP method I have mentioned. I am seeking solutions to the requirement I have listed. The one link that looks relevant is the "thinos launch RDP remoteapp" - it seems familiar - I may have read it.. Hi, Thank you for your feedback. Sincerely sorry for the delay of replying. This may be somewhat a complex issue. Via many researches, here are some hints may help you.

Windows 10 Dual Monitor remote session only showing one monitor on connection. How many Windows sessions are in use when connecting to a user session via RDP. Microsoft Remote Desktop Mac Mouse problem. Ok, download this directly to the server, dont put it on a flash drive because I tried it and it didnt work right, so just to be safe.

Now go ahead and install it, then determine the number of terminals you want to use, then take and set up that number of user accounts WITH Passwords Personally I have three thin clients that I want to set up, so I have three accounts. Your almost done! Ok, this is really quite simple, just connect the terminals to your network, then connect your server. Make sure that there is one account per thin client terminal, these accounts MUST have a password, otherwise they will not work!

Configuring- Well go ahead and start up your thin client and it should come up to some kind of connection window, with windows CE If you have a Compaq Evo you may have to reset it, all you have to do to reset it is, hold down G while turning on the thin client Now,go to the connection editor, the default should be named something like RDP test or RDP If everything works right you should see something like the picture below.

Insert your information. Continue to next step. Well, Sorry about the lack of creative writing but, hey, its supposed to be an informative instructable. Woah dude! I'm no white knight but patching a Microsoft - non server OS with terminal services. Will it work sure, will you get caught, probably not, but man this is straight up piracy. Each session except for the administrative RDP would require a license this holds true for a virtualized environment as well Hyper-v etc.

Be careful mang. Reply 5 years ago. Reply 4 years ago. How would I do this? What software do I need on the laptop? Think of it as a hardware gateway to a remote desktop session. They are typically smaller and less expensive. Reply 10 years ago on Introduction. No, once they are set up, you can use them on the same network as the host PC without needing an internet connection. Reply 11 years ago on Introduction.

Either will work, depending on what you're trying to do. VDI can get expensive quickly, so keep that in mind, but you'll need it if you want the end user to be connecting to a Windows 10 desktop. Chris Microsoft has a good how-to on the licensing aspect:. That might also work for your needs, but you haven't really given us much info as to your requirements other than you say you want them to connect to Windows 10, which would rule out RDS. Make sure you check the licensing agreements for all of the software that the users will need to access, as licensing will vary by product.

I have the feeling your managers thing this would be less costly than a wired desktop environment. Thin client as stated isn't cheap. You need a lot of licensing and server hardware to pull it off and thin client devices cost as much as a full desktop often.

Also I would push back strongly on the wifi requirement. If you are creating a kiosk-like environment, Kiosk system software is going to offer the best security and can be used in a thin client environment.

KioWare is one such solution. It really depends on how much access the user needs to the desktop, and how locked down you want it to be. To continue this discussion, please ask a new question.

Lenovo 53, Followers - Follow Mentions Products. Kyle for Lenovo.