cancel

HP TRIM Upgrade

Highlighted
user33
Respected Contributor.

HP TRIM Upgrade

we are using HP TRIM 6.2.5 in our infrastructure and intend to upgrade to 7.3.

 

Do you see any issue with this upgrade...as in from 6.2.5 to 7.3,

 

Is it recommended to do this raqther step wise, from 6.2.5 to 7.1.2 and then 7.3 or there is no concerns in this aspect ?

 

 

3 REPLIES
EWillsey
Acclaimed Contributor.

Re: HP TRIM Upgrade

The 7.3 documentation states that you can upgrade directly from 6.2.x to 7.x.  So you don't need to do a step-wise upgrade.

user33
Respected Contributor.

Re: HP TRIM Upgrade

also is this true

 

one cannot use TRIM 7.3 on windows server 2003,

                   HP TRIM 7.3 requires Windows Server 2008 Sp2, Windows server 2008 R2 SP1 or windows server 2012.

 

also, that we cannot use MS office 2003 with TRIM 7.3,

                   Requires MS office 2007 SP3 or MS office 2010 SP1.

 

Pl confirm ?

 

 

Neil Summers
Acclaimed Contributor.

Re: HP TRIM Upgrade

If that's what it states in the documentation (TRIM7.33_Spec.pdf), then that's correct. Server 2003 and Office 2003 are particularly old now and hence the latest TRIM releases aren't tested or supported on those platforms.

 

Also be aware that users will lose their 6.2 global settings, interface customisations, and probably favourites etc. when upgrading from 6.2 to 7.x. Plenty of forum posts on this subject too. Plan to roll out a new set of globals as part of the 7.2 upgrade project.

 

Also 7.x clients aren't officially backward-compatible with 6.2 workgroup servers. Keep this in mind when planning the upgrade, as the usual staged rollout process where you upgrade clients first, then servers later (as you might do for a 6.x or 7.x service pack upgrade) isn't a supported option (it may work but isn't tested, hence isn't supported by HP).


Neil

Note: Any posts I make on this forum are my own personal opinion and (unless explicitly stated) do not constitute a formal commitment on behalf of HPE.

(Please state the version of CM you're using in all posts.

HPE Software Support Online (SSO): https://softwaresupport.hpe.com/