|
-
Jul 8th, 2005, 11:19 AM
#1
Thread Starter
Fanatic Member
Terminal Server or not
I'm the new programmer here at work, the other guy has been here for awhile and is set in his ways. His way of deploying an app is to set it out on a terminal server and have everyone log into it to use the various apps out there. From a programmer's stand point this seems to be the easy way to do things (You only have one place to put your app when you update it, you can remote a user's session to see the problem without getting up from your desk, plus you don't have to worry about compatibility, etc.).
Lately, I've been getting the feeling that the IT dept would like to phase out this way of doing things, and i see their point (Having practically everyone logging into to a server reaks havoc on the network, plus it adds a step to the users who want to use the app.). Plus the IT guys have gotten a new app that will automatically disperse my app to all the people who need it, eliminating the need to go to each workstation and install it.
Being the new guy here I'm kinda in a interesting position, I could stick with the old way of doing things or create my own. So i guess my question to all of you is "how would/should this be done?"
Thanks
Andy
Using VB6 or VB.net 2008 with .net 3.5
"Life... death... either way I'll be confined to a small cubicle!" - Hermes Conrad
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|