VMsphere Cloud slaves fail to start up at all since upgrading to 617

I use VMshere to manage my Build servers. I had it working great in 1.505 and now have upgraded to 1.617 to see nothing but disaster. I can't even get the server to start a slave the option to start up the slave is completely gone from the ui so there is no way to trigger a start. I use VIX s

One of my jobs in Jenkins is running but there is no history of the job kept.

I have about 8 jobs that run and only one of my jobs continually runs but doesn't save the job details.. its like it is disabled the ball is always grea and the last Details are always N/A Anyone else seen this? -- You received this message because you are subscribed to the Google Groups "Jen

Windows 2008 R2 Servers set up as a Slave? Errors with JNLP Headless method what do I need todo to get these to connect?

My Jenkins 1.505 server is installed on Windows 2008 R2 using Apache TOMCAT 7.0 I disabled World Wide Web Publisher so I could use port 80. I want to use the headless method to connect my Nodes for builds. if I go to the client and click Launch it connects just fine but I want to control