Windows Server 2012 R2 Setup Guide

Post a reply

Smilies
:D :) :( :o :shock: :? 8) :lol: :x :P :oops: :cry: :evil: :twisted: :roll: :wink: :!: :?: :idea: :arrow: :| :mrgreen:

BBCode is OFF
Smilies are ON

Topic review
   

Expand view Topic review: Windows Server 2012 R2 Setup Guide

Re: Windows Server 2012 R2 Setup Guide

Post by pls_it » Thu Sep 15, 2016 5:08 pm

As a first step can you make a remote desktop connection to your Windows 2012 R2 server from a PC and run the required executables?

Windows Server 2012 R2 Setup Guide

Post by backXslash » Mon Sep 12, 2016 9:17 pm

Heya!

I'm not really sure where to go, or how to ask, but WTware appears to be the perfect solution to what I need. I just don't know how to go about setting it up. I've got an ANCIENT piece of software that REQUIRES an Windows environment to run, because the dev wrote it in VisualFox Pro. It doesn't require a lot of overhead though, and the usage scheme is fairly easy as well.

The program is a store manager for my business, and its use is mandated by county ordinance, so I can't replace it. During normal use, one computer "hosts" the program (really just its the directory it uses to keep all the .dbf and .cdx files that make up its "database"). That computer can run the executable or not, as needed. In order for other users to operate the program simultaneously, they simply need to connect to a network share where that central folder is located, and run the executable as well.

I'd like to replace all my "terminal" computers with RPis, and simply allow a central server to provide the overhead. I think Windows RDS SHOULD allow me to do this, but I have NO IDEA how to go about setting it up. I've got a copy of Server 2012 R2, and I've got three RPis. As far as where to go from there, I'm 100% lost.

Does anyone know enough about it to give me a rough guide? Or to point me in the right direction? Any help would be amazing!


------------ Edit For Clarity --------------

Basically, I need any solution that allows a terminal to access a server and run that executable as if it was a local user. I'm thinking that as long as the program directory is accessible to all logged in users, it should work without a hitch. Basically store the program at the root directory of C:\ on the server, and allow each user to log into a remote desktop session and run the executable.

Top