This is probably a stupid question to those with experience, but . . .

Due to layoffs, etc., one worker now bounces among 3 different computers in order to complete various duties. A new piece of software has been purchased for her to use, but we don't want to have to make her change machines to use it (she usually spends an entire day on a machine). Can software be installed on a server and then used by that one user on whichever machine she is on? Is there a special way to install it to make it work for her, or would it be installed just like it would on any other desktop?

She can use that software by logging into the work network where the software has been installed on the networks server.

If the pc's are in different locations speed can be an issue unless you have net access covered.

All our apps at work are served from a central server - although I do beleive we run the shells from our box.

I am not an expert in this field so I will shut up now

That's the way I assumed it would work, but it doesn't seem to. The program will open just fine on the server, but the networked PC won't open it. Am I missing something? Does it have to be installed in a particular place on the network? I put it in a folder that is easily accessible over the network rather than the Programs folder - does that matter? I can't get to the Programs folder via the network (even though I am set up as an administrator, it locks me out when I try to access it via my PC!). I can get to the folder I installed it in and I can even get to the .exe, but when I double click on that from the PC, it just sits there (not like it's locked up, more like it just ignores the command).

You're both partly right but missing one vital piece of information: the server must be running Windows Terminal Services, which is a component of Windows 2000 Server. If it's an NT Server, it actually needs to be a specialised version, Windows NT4 Terminal Server.

Once the program is installed and correctly configured on the server, a Terminal Services session needs to be set up. Basically, you need to define on the server that the program is to be made available to PCs on the network and how many licences (sessions) will be made available.

On the PCs on the network, I think you need to install a small Terminal Services Client application so that it understands how to run a program that is actually installed on the server. Then, you need a shortcut on each PC to the program(s) on the server that can be run remotely.

NOTE:
When you run a program remotely, it actually runs it on the server and takes up the server's resources (memory, processing time, etc). All that the client PC does is displays an "image" of what is being run on the server. Lots of clients can run the same program simultaneously because they are managed in separate sessions so one user will not see what another user is doing. However, they each need their own memory resources, processor power, etc, so a Terminal Server is usually a separate high-spec machine that, when under heavy load, will not impact other services like file/print sharing, email, Internet access, etc.

I only have a basic knowledge of Terminal Services, enough to understand the theory rather than to put it into practice myself. However, I'm sure that the Microsoft Technet site (www.microsoft.com/technet) will have articles and 'white papers' to help you decide whether it's what you want or not.

Hope that helps

Oh yeah, and the other thing I meant to say was:

Very basic programs may run remotely just by accessing a shared network location that contains the program files. However, most programs use registry entries, system file registration, configuration files, etc that are only configured on the machine that the software is physically installed on. That's why you need a terminal server to run most programs remotely like this - so that you can get to all that hidden stuff.

Ahhhh . . . I understand. It's the thin client environment. We've talked about moving to that, but we're told that those with considerable image use (Quark, Photoshop, Freehand, etc.) don't do so well in that setting. That means nearly everyone in our office. So it seems like a lot of hassle for just one piece of software to be shared in that manner. Sigh . . . guess we'll stick with just putting it on a PC.

Big, big thanks to both of you for your input and assistance!!!