VMware Horizon Community
vmsf
Contributor
Contributor

View 3.0.1 to View 3.1 official upgrade guide

Hi,

Where can I find the official upgrade guide to View 3.1?

Thx,

-vmsf

Tags (1)
Reply
0 Kudos
16 Replies
vmsf
Contributor
Contributor

I have checked at this site - didn't find an upgrade guide.

Is it embedded in some other document?

Reply
0 Kudos
Troy_Clavell
Immortal
Immortal

I don't think there is an "upgrade guide" per say, the VMware View Manager Administration Guide is as close as you will get.

Here's a great site as well, that may have some helpful information

http://www.thatsmyview.net/

Reply
0 Kudos
AndreTheGiant
Immortal
Immortal

http://www.vmware.com/support/viewmanager3/doc/releasenotes_viewmanager31.html#upgrade

Andre

**if you found this or any other answer useful please consider allocating points for helpful or correct answers

Andre | http://about.me/amauro | http://vinfrastructure.it/ | @Andrea_Mauro
Reply
0 Kudos
Troy_Clavell
Immortal
Immortal

Smiley Wink

Reply
0 Kudos
vmsf
Contributor
Contributor

Thanks for the responses.

I was hoping that Vmware would at least release an upgrade guide.

So from what I found so far I just need to run the view 3.1 exes on the connection server and virtual center (composer), upgrade the agents and the client. I don't have to uninstall before the installation?

-vmsf

Reply
0 Kudos
AndreTheGiant
Immortal
Immortal

So from what I found so far I just need to run the view 3.1 exes on the connection server and virtual center (composer), upgrade the agents and the client. I don't have to uninstall before the installation?

Seems no.

Like from 3.0.0 to 3.0.1.

Andre

**if you found this or any other answer useful please consider allocating points for helpful or correct answers

Andre | http://about.me/amauro | http://vinfrastructure.it/ | @Andrea_Mauro
Reply
0 Kudos
lbourque
VMware Employee
VMware Employee

One thing I would add (I can't remember if it's in the RN or not) is backup the Composer database and the ADAM schema before doing the upgrade.

Want make a difference in the future of VMware Products? Feature request your ideas ( )!

Reply
0 Kudos
arjanhs
Enthusiast
Enthusiast

I have done the upgrade last weekend and with the brokers all went well, but when upgrading the composer software i got error messages about corruption in to the database, so i decided to go back to the previous version. An upgrade guide good be helpfull for the next try.

Arjan

Reply
0 Kudos
-TAZZ-
Enthusiast
Enthusiast

I upgraded our View 3 to 3.1 as soon as it was released. It was certainly worth it!

A full report can be found here: http://www.vmguru.nl/wordpress/2009/05/upgrade-vmware-view-30-to-31/

www.vmguru.com | twitter.com/scholtene
Reply
0 Kudos
arjanhs
Enthusiast
Enthusiast

Did you used the composer in your installatio, this part was broken for me?

Reply
0 Kudos
-TAZZ-
Enthusiast
Enthusiast

No, sorry. We don't use composer/linked clones. We use the fat virtual machines.

www.vmguru.com | twitter.com/scholtene
Reply
0 Kudos
vmsf
Contributor
Contributor

I upgraded my lab environment without any issues but in the production I am getting the following error:

The VM: /Urbana/vm/VD-POC/VD-POC-001 - encountered an error: 6/10/09 11:14:16 AM EDT: View Composer agent initialization state error (6): Unknown failure (waited 0 seconds)

I have followed the exact same process for the upgrade. The composer installation completed without any errors. The new desktops have the Composer service running.

Has anyone encountered this error.

Reply
0 Kudos
arjanhs
Enthusiast
Enthusiast

When i did the upgrade i got the following message:

"The View Composer database has been re-initialized or is corrupt. Please restore from your last backup or see the View Composer Administration guide for help on re-enabling View Composer for View Manager"

So i tried an clean install, but this provides me with the following messages:

(Request883) Request failed: com.vmware.vdi.ob.tunnelservice.cx: Failed whilst returning body: java.io.IOException: Broken pipe

(Request872) Request failed: com.vmware.vdi.ob.tunnelservice.cx: Failed whilst returning body: java.io.IOException: Broken pipe

(Request750) Request failed: com.vmware.vdi.ob.tunnelservice.cx: Failed whilst returning body: java.io.IOException: Broken pipe

(Request437) Request failed: com.vmware.vdi.ob.tunnelservice.cx: Failed whilst returning body: java.net.SocketException: Connection reset by peer: socket write error

(Request416) Request failed: com.vmware.vdi.ob.tunnelservice.cx: Failed whilst returning body: java.io.IOException: Broken pipe

(Request400) Request failed: com.vmware.vdi.ob.tunnelservice.cx: Failed whilst returning body: java.io.IOException: Broken pipe

(Request241) Request failed: com.vmware.vdi.ob.tunnelservice.cx: Failed whilst returning body: java.io.IOException: Broken pipe

So when doing an upgrade or an fresh install, with both I end up with error messages.

Arjan

Reply
0 Kudos
Louch
Contributor
Contributor

has anyone got the upgrade working with vmware view composer?

We are currently running version 3.01 and would like to upgrade to 3.1 but we do not want mess up our production users!

we have 50 desktops currently running and about 45 of them are linked clones...

VMware should release a step-by-step guide and I can't believe they never did........ not good...

Reply
0 Kudos
jrVMguy
Contributor
Contributor

I upgraded our environment from 3.0.1 to 3.1 in about an hour, granted our environment was fairly new and we hadn't really gotten too far into the demo we had. We did have the composer software installed and it upgraded with no issues.

All I did was install the 3.1 software right over the 3.0.1 software and upgrade the agents. Like I said though, we hadn't done anything really with our environment. We had just started trying to use linked clones and ran into an AD issue and upgraded to "fix" that issue.

Reply
0 Kudos