Trouble getting Vmware View to work

[jx]

Hello All,

I am new to VDI, but familier with vCenter and VI infrastructure. I am trying to setup a VDI environment and I am running into all sorts of issues. Here is what I do

1) Installed vSphere vCenter on XP SP2

2) Installed VDI connection manager on a Win2003 guest OS, running on a different ESX

3) view composer: The installation goes fine. But When I try to add the vCenter into the VDI connection manager, it says it cannot connect to composer (composer service is running). Once I restart the vCenter machine, vCenter service wouldn't start (the SCM error says the service started and stopped)

Questions I have are:

1) How do I fix this - apparently

2) Do I need SQL server or SQL express which vcenter installs is good? If SQL server is needed, which version?

3) Are there any detailed documents on how to install and configure vmware view?

4) If you guys wants to look at the log files, please let me know which one and the location

5) What is the quick pro domain on the enable composer window? Is it required to add one?

Frankly, I am stuck! Please help

~j

[zilch321]

I'm currently doing a demo of the View environment and was just going over the documentation today. You might want to search in there about using vsphere. I'm 99% sure you cant use any vSphere products with View yet. When I downloaded the installers I took note of this because everything they license you for is ESX 3.5 era, from ESX to vCenter.

[jbruelasdgo]

you are correct. VMware View still does not have support for vSphere

Jose B Ruelas

[Leostream]

Hello!

If you want to continue using vSphere in the near term, but require a Connection Broker, you could try the Leostream Connection Broker. Leostream installs as a virtual appliance within vSphere, and can manage vSphere VMs. One caveat is that Leostream does not support Composer. So, if you are looking to use Linked Clones, Leostream will not work for you, either.

Good luck,

Karen

[jdudakia]

Karen, in my case I have to use linked clones so vSphere wouldn't be an option for me.

All,

Thanks for your responses. I did make some progress lately. I installed VI 3.5 and latest updates and things started working. Well.... not completely, but at least the connection manager and the composer are connecting and I can create a desktop pool using linked clones. Now after creating the pool, the system is stuck on "Customizing" the desktop sources and eventually fails with timeout error. Any idea why??

Another issue: The vCenter I am using to has 10 VMs - running all types of windows OS. I want to pick one VM (a Win2003 ENT) as the desktop pool source parent. But the desktop pool creation wizard in connection manager does not list that VM as one of the available VMs. It lists two windows 2008 VMs and one XP Pro VM. From the document I understand that there must have at least one snapshot taken when the VM was dormant in order for it to be used as a parent VM . I did that but still it doesn't get picked up by the connection manager. Any idea whats going on ??

Thanks

~j

[zilch321]

I had big issues with customization and my AV software, Symantec Endpoint. Even turning off all the endpoint services was not enough to make the customization work. I had to uninstall it completely. At that point customization went through without a hitch. I am told that if I install Endpoint with just the AntiVirus bits the customization will work but I've yet to test that. If your Parent VM has a related protection software package installed do some searching with the brand/product name in regards to customization, there were several vendors I found on this forum that gave the same exact problem.

[jdudakia]

>> I am told that if I install Endpoint with just the AntiVirus bits the customization will work

Can you please point me to the place where you got that information. I would like to know more about it

In my case where the customization fails, the parent VM does NOT have AV software. The reason why I am curious about the point is because I am planning to install AV on it as the next step.