G
Guest
I need a group of Mac clients to be able to run a Windows program. To this
end, I'm setting up a Terminal Server (2003).
I know that using TSCC I can configure Terminal Server to run a certain
program whenever a user connects. What I'd like, however, is for the user to
be limited to this one program and nothing else -- not even the desktop.
I don't want them to see the desktop or interact with anything except this
single VB.Net application. It'd be nice if they couldn't minimize the
program window in the Terminal Services client and theTaskbar could be
hidden, so they never even become aware of the desktop. In fact, it would be
great if the Terminal Services client could be configured to disappear as
much as possible, so the users barely even know they're using Terminal
Services, and just think they're running a native app over the network.
(Note that this is not because I don't trust my users. It's because I want
the Mac users to feel as much a part of this application deployment as the
Windows users. User adoption being as key as it is to any software
deployment project, I don't want the Mac users to feel like they have one
extra obstacle to surmount.)
How possible is this?
Deane
end, I'm setting up a Terminal Server (2003).
I know that using TSCC I can configure Terminal Server to run a certain
program whenever a user connects. What I'd like, however, is for the user to
be limited to this one program and nothing else -- not even the desktop.
I don't want them to see the desktop or interact with anything except this
single VB.Net application. It'd be nice if they couldn't minimize the
program window in the Terminal Services client and theTaskbar could be
hidden, so they never even become aware of the desktop. In fact, it would be
great if the Terminal Services client could be configured to disappear as
much as possible, so the users barely even know they're using Terminal
Services, and just think they're running a native app over the network.
(Note that this is not because I don't trust my users. It's because I want
the Mac users to feel as much a part of this application deployment as the
Windows users. User adoption being as key as it is to any software
deployment project, I don't want the Mac users to feel like they have one
extra obstacle to surmount.)
How possible is this?
Deane