Also bear in mind you will be doubling your IP addresses too when effectively using 2 NIC's to log 1 user on!
@pcstru I agree regarding the cost savings. Do these costings include:
The extra labour/cost required to 'nurse' and replace older 'thick' clients that have long fallen out of warranty? Sooner or later, those PC's are going to start failing.
The extra hours put in by ICT support staff to support VDI, which back end wise does seem pretty labour intensive. Some applications which work perfectly fine in a physical environment need lots of tweaking to get working in VDI.
You only have to follow the posts on here to see many unsatisfied VDI users...
By contrast you hear about very few unhappy terminal services/Citrix users...
Make of that what you will....!
VDI is very fashionable right now - and the "industry" loves selling it as it means big bucks and high consultancy fees. (No one is scared of managing a terminal server - but a new VDI installation....?)
I've been in the thin-client industry for 15 years - not much happened in the first 12 years (W2000, Citrix, W2003, W2008 etc) thin clients were seen as low cost, low maintenance devices for industries such as call centres and point of sale, data-entry and in many cases replacing dumb ascii VT type terminals.
They were never billed as PC replacement devices - rather they filled a sizeable niche under "power" PC level requirements.
Now it seems people are buying into all the benefits (easily done), jumping in with both feet, but not fully understanding the limitations, so end up disappointed.
To make the disappointment more acute, some thin clients now cost as much as PCs, use same chipset & O/S, so essentially are PCs, so contain all the problems thin clients were initially supposed to address - so its gone full circle, but now the PCs have a server in the middle...
Ultimately its all about setting and matching expectations, running a pilot and not believing everything you read/hear.
I hope this doesn't sound like a rant - it's not meant to be - I just find it annoying when resellers exaggerate thin-client's abilities and cause unnecessary negative feeling
towards what in the correct environment are very effective devices on many levels....
andyturpie (1st March 2013)
We are looking at VDI as being a solution to BYOD.
Students bring whatever device they like - ipad, macbook, wintel, etc, and are all able to use the same desktop experience.
Got a demo of citrix in and it seems to work pretty well with the connector and ios/android etc.
What other providers are there?
There is a VMware version and HyperV can do it, basically the 3 usual suspects.
Part of the problem with RDS or VDI in a Microsoft solution is always going to be office.
Using office via VDI/RDS on your ipad? Then that's a CAL, RDS/VDI license and an Office license you'll need to get somehow.
Use the same on your android phone, well you may be covered with user CALs for RDS/VDI with your ipad above, still need another office license though...
how does the CALs thing work with EES when you only license per full time employee?
RabbieBurns (1st March 2013)
so the idea that a student owned device will 'save' money, will actually cost the school more in licensing costs?
Yes, pretty much. But your student could use Office 365 as an alternative.
All our VDI devices etc are owned by the school.
Where are we with VDI?
Make that four.There is a VMware version and HyperV can do it, basically the 3 usual suspects.
We are using RHEV.
Basically we setup a machine to our liking then replicate it into a 'pool' of virtual machines. Give the students access and they log in as administrators. Reboot the machine and it goes back to its original config.
The SPICE protocol offloads some of the work onto the local machine, so server load isn't too bad (about 40 VM's per server) and it costs around £600 per server per year plus about £200 per year for 25 licenses.
No IoS or Android connector though.
There are currently 1 users browsing this thread. (0 members and 1 guests)