jkoodari
Contributor
Contributor

Windows 8 with View 5

Is it possible use Windows 8 Consumer Preview desktop with View 5? View Agent installation gives error "Unable to connect to viewserver. TCP connection failure on TCP port 389 Please check he server name entered." Server name is correct and Windows 7 desktops are working fine.

0 Kudos
30 Replies
markbenson
VMware Employee
VMware Employee

Windows 8 is not supported with View 5.0.

Mark

jkoodari
Contributor
Contributor

It is not supported, but is it possible? It would be great to demo View 5 with Windows 8 Consumer Preview.

0 Kudos
amandasmith
Enthusiast
Enthusiast

Currently its not possible, need to wait

Always remember you're unique, just like everyone else
0 Kudos
Datto
Expert
Expert

0 Kudos
vSolid
Enthusiast
Enthusiast

I have installed view 5 on windows 8 32bit, it's working fine

drug the installation, you need to have an View admin account to connect, because it's use Microsoft AD authentication, TCP 389 port is required to authenticat view agent  for connecting  view server (view manager)

BR

0 Kudos
vSolid
Enthusiast
Enthusiast

Also, check if this port is open with network team if you have diffrenet VLANs.

0 Kudos
MattCareyOmaha
Contributor
Contributor

I have also been working a bit with this, attempting to get it to work.

I know it's officially unsupported in every way possible, but I thought I'd throw this out there in case anyone else ran into this snag and found a way around it.

A little background.....

I have View5 running on an ESXi 5.0 host. I have created a virtual machine, and installed Windows8 64 bit. After the installation, I changed the OS in the virtual machine settings to Windows8 Server so that View would think it's a supported OS. I have installed the VMware tools, along with the 64 bit View agent. I have verified that all needed firewall ports are open between the virtual desktop and the connection server.

I am able to add the virtual machine to the inventory in the view Administrator console, but that is where the problem begins. The status constantly says "waiting for agent" and of course if I try to connect using the view client, it does not connect.

I've tried to dig through the logs on the agent side of things, but can't really make heads or tails out of what I've found in there.

If anyone else has ran into this same issue and has a workaround, I'm all ears  :smileygrin:

Otherwise, hopefully the blog in the link above will have the new info posted soon.

0 Kudos
vSolid
Enthusiast
Enthusiast

is your view manager v4.6 ??

if yes, try to download v5.0 as trial and test it

0 Kudos
MattCareyOmaha
Contributor
Contributor

View Manager is 5.0.0 build-481677

0 Kudos
Datto
Expert
Expert

0 Kudos
MindTheGreg
Enthusiast
Enthusiast

I'm waiting on agent also. Tried doing a bunch of  "netsh advfirewall firewall ..." commands because the firewall snap-in crashes on me. Gonna try 32bit.

Set-Annotation -CustomAttribute "The Impossible" -Value "Done and that makes us mighty"
0 Kudos
MattCareyOmaha
Contributor
Contributor

I'm glad to see that the steps have been posted!

I did follow the blog posting step by step, but still in the "waiting for agent" state.

I think I'll just wait until this is fully supported by VMware.......  Smiley Happy

0 Kudos
DavidPatrick
Enthusiast
Enthusiast

Same here. Tried the 32bit & 64bit but still I am getting the message "Waiting for agent"

Also I am unable to get the VM to appear as Registerd Desktop sources even after the OS version =  5 change.

I feel the issues are with the domain account which you supply when installing the View Agent.

"It must have admin privilages on the view server"

Any ideas?

0 Kudos
MattCareyOmaha
Contributor
Contributor

I'm not sure if it does or not, what I *can* say for sure, is that the account I've been using is a domain admin, and also local admin on all servers / desktops in my test domain, so it's probably safe to assume that persmissions are not the limiting factor.

0 Kudos
squevill
Contributor
Contributor

I have the exact same problem "Waiting for Agent" status will not go away.  If anyone knows how to get it working, please post here, it would be much appreciated.

(I have followed the very good detailed instructions from  http://myvirtualcloud.net/?p=2991, tried that three times and still cannot get rid of the issue).

0 Kudos
squevill
Contributor
Contributor

Bump - anyone has found a resolution to the "Waiting for Agent" issue?

0 Kudos
tdubb123
Expert
Expert

looks like view client works on win8 but not local mode. local mode client install fails

0 Kudos
Datto
Expert
Expert

After three times of creating a Manual Pool and inserting my Win8 CP VM into the pool, I finally was able to avoid the "Waiting for Agent" problem the connection finally worked. I now have a View 5.0 pool with Win8 running in it and accessable from the View 5.0 client with PCoIP

I think the trick was to \explicitly follow the instructions on Andre's website (directly below), particularly the ADSIEDIT part on your Connection Broker VM:

http://myvirtualcloud.net/?p=2991&utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+Myvirtu...

but to also after the Connection Broker ADSIEDIT part is complete, pay attention to creating a) Manual Pool and then b) choosing "Other Sources" rather than the default of VCenter Virtual Machines. Then pick out with a checkbox your powered on Win8 CP VM that has the View 5.0 agent on it from the list that should show up on-screen and OK through the remainder.

At this point, I downed and restarted the Win8 CP VM, waited a good long time for the Win8 pretty picture login screen to appear with the time on-screen in big numbers, then waited an additionaol 2 minutes to let the Agent get running inside the Win8 VM so the Connection Broker could dish out the VM to me via the View 5.0 client.

And vi-ola, I chose the pool from the list provided by the Connection Broker, and the Win8 VM showed up in a PCoIP session.

Hope that helps those who have had the Waiting For Agent message like I had received initially.

Datto

0 Kudos
squevill
Contributor
Contributor

Success for me too!  I had to uninstall / re-install the View Agent on the Windows 8 VM, then ensure that the ADSIEDIT was done correctly and it all worked as advertised after that.

Smiley Happy

0 Kudos