nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Teamsite Upgrade from 6.7.2 to 7.x

parsan99

We are looking to upgrade Teamsite 6.7.2 to 7.x on Linux. 6.7.2 is currently 32-bit only. With the upgrade will the application be 64-bit by default or is there something we have to configure?. Any input on this is appreciated.

Find more posts tagged with

Comments

Crsb

the application is still 32bit, but you can and you should install it on 64bit machine to get good performance. but of course you can install it on 32bit machine too.

the installation is the same on 32bit and 64bit.

rrose

Hi,

We are also planning to upgrade from TeamSite 6.7.2 to 7.2. Is this supported upgrade path. Did you face any upgrade issues. In one of the documentation it was specified that the TeamSite Upgrade path is from 6.7.2 to 6.7.2 sp2 and from 6.7.2 sp2 to 7.2

Please let me know.

Thanks!

nipper

If that is what the docs say, then do it.

There are often a couple tweaks needed for a major upgrade, hence the need to apply a SP first.

Have a really good backup. If you use a VM, then take a snapshot and keep it for a while. The rate of infant mortality on 7.X upgrades is high and I have seen many people have to start from scratch.

brizrobbo

Hi,

We are also planning to upgrade from TeamSite 6.7.2 to 7.2. Is this supported upgrade path. Did you face any upgrade issues. In one of the documentation it was specified that the TeamSite Upgrade path is from 6.7.2 to 6.7.2 sp2 and from 6.7.2 sp2 to 7.2

Please let me know.

Thanks!

I have had it actually confirmed from IWOV support that TS 6.7.1 SP2 to TS 7.2 is an appropriate upgrade path. Anything less than TS 6.7.1 SP2 to TS 7.2 is not.

Bowker

We are migrating from 6.5 to 7.2.1. There are quite a few changes including some to CSSDK that tripped us up. The Backing store can be copied over in one shot.

We are currently running an extended test to verify everything, but so far...all is good.

One major issue we had was permissions on folders under the Interwoven folder to allow for workflows, custom commands and external tasks to execute properly.