mjgardne
asked on
Thin Clients + SBS2008
Hello,
We have a SBS2008 Standard server and would like to start replacing desktop computers with thin clients. We would like our 10 employees to be able to access some Internet based web services using Internet Explorer and they need to run three applications that exist on the SBS server. I am confused about our options and required licenses.... Here is our list, I think...
1) We could get thin clients that have a lite version of WinXP embedded in them and they use RDP to connect to the SBS2008 server. How do I give the users access to the three applications that are on the server for them to use? Terminal Services has changed on SBS2008 and I am unsure how to proceed with this option. Microsoft has been talking about releasing a VDI technology soon as a replacement for Terminal Services that uses Hyper-V. Is that what we need on SBS2008?
2) We could get thin clients that connect to a VMware virtual machine that exists on the server. This idea is very easy for me to understand and manage. It also is very well established technology. The point I am wondering about is best practices. If there will be 8 to 10 virtual machines, should I have an SBS2008 server and a separate VMware ESXi server for the virtual machines/desktops? Although there would be two physical servers, this permits full access to SBS' features (i.e. faxing, etc) while permitting migrating to virtual desktops over time. The alternative would be to run VMware ESXi on the physical server, create an SBS2008 virtual machine and the desktop machines. This would work, but I think there is less flexibility for SBS and there is no access to USB and eSata devices, which affects our backup technology.
These are the choices that I know about. There are good thin clients for both... Right now, I am seriously considering the VMware solution since it is scalable, very easy to implement, reasonably priced, and easy to accomplish. What do you think?
Thanks for your ideas and suggestions...
Mike
We have a SBS2008 Standard server and would like to start replacing desktop computers with thin clients. We would like our 10 employees to be able to access some Internet based web services using Internet Explorer and they need to run three applications that exist on the SBS server. I am confused about our options and required licenses.... Here is our list, I think...
1) We could get thin clients that have a lite version of WinXP embedded in them and they use RDP to connect to the SBS2008 server. How do I give the users access to the three applications that are on the server for them to use? Terminal Services has changed on SBS2008 and I am unsure how to proceed with this option. Microsoft has been talking about releasing a VDI technology soon as a replacement for Terminal Services that uses Hyper-V. Is that what we need on SBS2008?
2) We could get thin clients that connect to a VMware virtual machine that exists on the server. This idea is very easy for me to understand and manage. It also is very well established technology. The point I am wondering about is best practices. If there will be 8 to 10 virtual machines, should I have an SBS2008 server and a separate VMware ESXi server for the virtual machines/desktops? Although there would be two physical servers, this permits full access to SBS' features (i.e. faxing, etc) while permitting migrating to virtual desktops over time. The alternative would be to run VMware ESXi on the physical server, create an SBS2008 virtual machine and the desktop machines. This would work, but I think there is less flexibility for SBS and there is no access to USB and eSata devices, which affects our backup technology.
These are the choices that I know about. There are good thin clients for both... Right now, I am seriously considering the VMware solution since it is scalable, very easy to implement, reasonably priced, and easy to accomplish. What do you think?
Thanks for your ideas and suggestions...
Mike
I believe that Terminal Services on the SBS Server itself is no longer supported or can be enabled. You must use a separate server.
Whatever solution you use, you will have to purchase Terminal Server CALs. Therefore I would be looking at a separate Windows 2008 server (or Windows 2003 if you prefer) with the TS licensing server on the SBS Server.
You will find that most SBS deployments are now going in to virtual machines. I know that is what I am doing. Gives a lot more flexibility with the system. I am using ESXi with compatible hardware.
-M
Whatever solution you use, you will have to purchase Terminal Server CALs. Therefore I would be looking at a separate Windows 2008 server (or Windows 2003 if you prefer) with the TS licensing server on the SBS Server.
You will find that most SBS deployments are now going in to virtual machines. I know that is what I am doing. Gives a lot more flexibility with the system. I am using ESXi with compatible hardware.
-M
Terminal services should not be installed on a SBS server. You will need a second machine for this with Server 2008 Standard or Enterprise (2003 would also work). You would setup this server as a member server and have the thin clients log into this machine.
I hope this information helps. Good luck.
I hope this information helps. Good luck.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Hello,
Do you still need help?
Was this issue resolved?
if so, please close this question:
https://www.experts-exchange.com/help.jsp?hi=403
regards,
suppsaws
Do you still need help?
Was this issue resolved?
if so, please close this question:
https://www.experts-exchange.com/help.jsp?hi=403
regards,
suppsaws
ASKER
Thanks for the help! I virtualized our SBS server, created virtual machine workstations, and are connecting via RDP clients. Absolutely a great solution and very, very stable. The only thing that I still need to work on is getting the time to sync properly in the virtual machines... Another question elswhere! :)
Wow,I'm not sure about all aspects of Your question but it seems pretty reasonable to choose the option of creation a SBS2008 virtual machine as this will definetly slash the costs and improve overal project ROI .
As for device access,I know for sure that Vmware can provide access to any device including most SCSI / RAID devices.
for clients You will mostly need the Vmware Infrastructure Client, to connect to the ESXi server .
Additional plus of going with this option that network access will be facilitated for You with the Vmware as it will create the privet subnet You'll need to connect to in case You install separate SBS2008 server.