hunter_alexander

Thanks everyone. David, sorry, I hope I didnt come off as rude. Just wanted to stay focused on the main reason I am here. I probably could have worded my original post better. I will create a different thread on the virtues or lack thereof on if I should switch to thin client networking. Domino - I will read up on thinstation. Thanks. I know that RDP is a form of thin client. I guess that I am just used to the standard way of using it, being on a workstation running some flavor of windows, and using RDP onto a server. I wasnt aware that you could use it right from boot. Seamless is what I am after, since, to a user, anytime you make any change, they scream and holler until they are educated on the uses and functionality. (and even then they will keep screaming). Axle - Yeah, I think the thin client aspect is what I am after. How or what do I need to set up on the terminal server to allow the thin client to connect? How does the terminal server supply the desktop image for the thin client? I am probably getting all the different technology confused (read a ton on different tech that can be used) but I guess I was thinking of the citrix form where you create an master image that everything else is based from, and then for each user you add the different things they need to use. Basically how does it work with Terminal server and thin clients? Any links to some good, concise reading on it? Thanks again

Thanks for the fast replies. I am very familiar with RDP. We use it quite a bit to remote onto our clients servers to perform some work. That being said, Remote desktop is not quite what I am after. I am looking to test a thin client or zero client to see how well it works with what we do. The idea for the user to sit at their desk, power up the thin client, put in their logon, have a desktop that is just like them sitting at their computer they have now, and perform all the functions that they do now, but with the ease of centralized administration, lower costs, etc. I wasnt sure if I could use a thin client to just connect to a MS server running terminal server. I thought I would need citrix or some other software to suppy the desktop and apps from the server side. Trying to learn. Thanks all.

Ok, sorry, but rather than go into my daily workload, I would like to just figure out how to set up a testbed of sorts for thin client or zero client computing. I have a spare server, Win2003 R2 on it. I was looking at Citrix. Any advice on what all components are needed to set up for testing? Can this be done with their trial software?

Well the thing is that we are growing. It is only me doing everything, ( including phone support which isnt all that bad). All in all I stay pretty busy trying to do the all the stuff I do, as well as trying to do development work. What I am looking at this is to cut down the deskside support aspect, so I can concentrate on more development work/network administration. Its manageable now, but if we keep growing the way we are, I am going to be swamped. From all that I have read, thin client or zero client setups cuts down or eliminates the deskside support aspect, as pretty much everything is managed on the server side of things (ie. less of me running to each persons desk to fix things). We are also looking at running out of space in our current location and the idea of a remote location has been tossed around. There is no way I am going to be able to support 2 locations software and hardware physically by myself. Its a great job here, great atmosphere great people. They will not hire nor do I want them to hire another person to help me. Just looking to streamline some things. Am I thinking about this wrong? Any insight is appreciated.

Greetings, New here. I am a network administrator for a smaller company. We have 35 people, 3 servers, network printers etc. I am the only NA that this company has. I spend a lot of time doing deskside support. We also have a small to midsize budget for IT. With that said, I am looking into moving over to thin client computing for our network, with the idea of me doing less deskside support, purchasing and upgrading desktops and laptops, and doing more on the network side of things. I have tried to dig up as much info as possible, but I am still sort of at a loss on where to start. I have gotten the approval to look into doing a test bed of sorts to test the functionality. Things we do are: 1. We are a vendor company, with the majority of our work coming from a large software company. 2. We Ras into our main clients network using smart cards to utilize their internal tools and apps. 3. We do a lot of data crunching in excel spreadsheets, as well as using web based tools on thier internal network. We utilize Window software (windows servers, exchange server, Vista enterprise desktops etc.) That being said, can someone help me figure out what I need to set up a test bed? I was thinking of picking up 1-3 different types of thin or zero clients, and setting up a server to work with them. The key here is for the users to keep doing thier work as they always have, utilizing the smartcards/ras that they need to connect to our clients network (required), the ability of testing software on CD's/DVD's and keeping the users existing dual flat screen monitor setup. So what all do I need to get testing? Is there any trial software for a easy server setup? I have a spare server that I can load up with whatever to test with. I am also just finishing up getting everyone on GB ethernet. Thanks everyone for your help. Craig