Teamsite 6.7 upgrade

Thiags

Hi,

We are running teamsite 6.5 on win2k3 server. I m planning to upgrade it to temaiste 6.7. Here is my question. The teamsite 6.5 currently was installed on the C:/Program files/Interwoven/Teamsite path. During the upgrade can I install Teamsite 6.7 in a custom folder like c:/iwhome instead of above path. Is it advisable to do so? Will any of the teamsite services and functionalities be affected?

Thanks,
Thiags

Adam Stoller

Hi, We are running teamsite 6.5 on win2k3 server. I m planning to upgrade it to temaiste 6.7. Here is my question. The teamsite 6.5 currently was installed on the C:/Program files/Interwoven/Teamsite path. During the upgrade can I install Teamsite 6.7 in a custom folder like c:/iwhome instead of above path. Is it advisable to do so? Will any of the teamsite services and functionalities be affected? Thanks, Thiags

What you are suggesting is (a) not an upgrade and (b) highly recommended ;-)

It's not an upgrade because if you're installing into a different path - you're not upgrading the existing software - plus it will probably cause all sorts of headaches since TeamSite is likely to get confused somewhere along the line about where it's home directory is.

It's highly recommended because paths with spaces in them are "evil" and break lots of scripts in ways that often take hours, days, and sometimes longer to figure out.

I'm not sure what the best approach is here - you ***might*** be able to (a) stop TeamSite, (b) find all references to the current iwhome path (in files and in the registry) switch them to the desired path, (c) move the iwhome directory to the desired path, (d) start TeamSite back up. If that works --- then you can do an upgrade using the desired path.

You probably should talk to Support first though.

The other options are to install fresh on a new server and migrate customizations and backing store - or backup your customizations and backing store - wipe the current server and install fresh on it and then work on migrating your customizations into place. Given that 6.7 upgrade does some automated stuff for upgrades - it would probably be nice if the stop-edit-move-start approach worked - but it's purely theoretical at this point.