VMware Horizon Community
jonesvmware
Contributor
Contributor
Jump to solution

Server 2003 As A Desktop Client In View

The problem: We have OEM copies of XP Pro on our desktops (no SA). Because of MS licensing, to run View on a desktop we would need to purchase:

  • Vista Business with SA - a lot

  • VECD - $330

  • VMware View - $250

Because of the MS licensing setup, I have 0% chance of running view.

Two questions:

  1. What is the reason that VMware didn't/couldn't make Server 2003 available as a desktop OS in View?

  2. Any process/possibility of getting this changed?

Virtuozzo is doing something similar to what I want to do, that is:

  1. Buy copies of Server 2003 Datacenter for each proc

  2. Push out Server 2003 as a desktop to avoid re-buying a desktop OS.

    • source:

The one catch with Virtuozzo seems to be that you have to connect via a TS session, which obviously would be undesirable.

So I am resigned to the fact that this won't work, but just wanted to make sure and see if it was something that could possibly be changed.

Thanks!

0 Kudos
1 Solution

Accepted Solutions
TomHowarth
Leadership
Leadership
Jump to solution

It will most likely be a version check in installation routine of the Agent, you could open the MSI in ORCA to have a look but remember any modifcation will render your Support invalid. you the resulting deployment will be unsupported. View is a VDI deployment mechanism. therefore it deploys Desktop OSes, XP or Vista. Win2K3 and Win2K8 are server based operating systems.

I can understand your frustration however it is MS that need to change their licensing policy. you will find the same issue with all VDI brokers, Leostream, VizionCore, VMware View, etc.

If you found this or any other answer useful please consider the use of the Helpful or correct buttons to award points

Tom Howarth VCP / vExpert

VMware Communities User Moderator

Blog: www.planetvm.net

Contributing author for the upcoming book "VMware Virtual Infrastructure Security: Securing ESX and the Virtual Environment”.

Tom Howarth VCP / VCAP / vExpert
VMware Communities User Moderator
Blog: http://www.planetvm.net
Contributing author on VMware vSphere and Virtual Infrastructure Security: Securing ESX and the Virtual Environment
Contributing author on VCP VMware Certified Professional on VSphere 4 Study Guide: Exam VCP-410

View solution in original post

0 Kudos
3 Replies
TomHowarth
Leadership
Leadership
Jump to solution

You can do the same with View but it is a TS session too.

If you found this or any other answer useful please consider the use of the Helpful or correct buttons to award points

Tom Howarth VCP / vExpert

VMware Communities User Moderator

Blog: www.planetvm.net

Contributing author for the upcoming book "VMware Virtual Infrastructure Security: Securing ESX and the Virtual Environment”.

Tom Howarth VCP / VCAP / vExpert
VMware Communities User Moderator
Blog: http://www.planetvm.net
Contributing author on VMware vSphere and Virtual Infrastructure Security: Securing ESX and the Virtual Environment
Contributing author on VCP VMware Certified Professional on VSphere 4 Study Guide: Exam VCP-410
0 Kudos
jonesvmware
Contributor
Contributor
Jump to solution

Hi Tom,

Do you know, is this a licensing issue that prevents VMware from letting 03 work like a normal desktop OS (like XP would, for instance), or is this just the way VMware implemented it?

If just implementation, any ideas on how to escalate to get a change?

Thanks!

0 Kudos
TomHowarth
Leadership
Leadership
Jump to solution

It will most likely be a version check in installation routine of the Agent, you could open the MSI in ORCA to have a look but remember any modifcation will render your Support invalid. you the resulting deployment will be unsupported. View is a VDI deployment mechanism. therefore it deploys Desktop OSes, XP or Vista. Win2K3 and Win2K8 are server based operating systems.

I can understand your frustration however it is MS that need to change their licensing policy. you will find the same issue with all VDI brokers, Leostream, VizionCore, VMware View, etc.

If you found this or any other answer useful please consider the use of the Helpful or correct buttons to award points

Tom Howarth VCP / vExpert

VMware Communities User Moderator

Blog: www.planetvm.net

Contributing author for the upcoming book "VMware Virtual Infrastructure Security: Securing ESX and the Virtual Environment”.

Tom Howarth VCP / VCAP / vExpert
VMware Communities User Moderator
Blog: http://www.planetvm.net
Contributing author on VMware vSphere and Virtual Infrastructure Security: Securing ESX and the Virtual Environment
Contributing author on VCP VMware Certified Professional on VSphere 4 Study Guide: Exam VCP-410
0 Kudos