The community will be in read-only from Tuesday 11:59pm (PST) to Wednesday 7:30am (PST)
The community will be in read-only from Tuesday 11:59pm (PST) to Wednesday 7:30am (PST)
cancel
Showing results for 
Search instead for 
Did you mean: 

HPRM8.1 thick client in a mix mode environment

Highlighted
c-y-s
Super Collector

HPRM8.1 thick client in a mix mode environment

My customer will be doing a TRIM upgrade from V7.1 to V8.1. Some of the users are using WIn XP, some using WIn 7.

 

The customer has installed the V8.1 client program into a several Win XP and Win 7 PC. The server side is still TRM7.1 and some client has v7.1 and some has v8.1 . It is a tempoary mix mode environment during the upgrade period.

 

We noticed that after we install HPRM 8.1 client program ... it will expired in 30 days and the program is still able to connect to the HPRM 8.1 server but not to the TRIM7.1 anymore after the 30days license expired. The customer's TRIM7.1 server has a licensed product key entered and have no clue why it cannot be assessed after 30 days.

 

Please assist to check how to use HP Records Manager in a mixture environment, there is installed HP RM client 8.1 to connect to our existing TRIM version 7.1 after the 30days license expired.

6 REPLIES
EWillsey
Honored Contributor

Re: HPRM8.1 thick client in a mix mode environment

Step 1 in your upgrade project plan should be to request an 8.1 license key from HP.  Without that you're SOL in the long run.  In the short term go into the 8.1 Enterprise Studio, expand general, open license key, and click Evaluation Copy.  It'll give you another 90 days, click ok and then deploy.  

c-y-s
Super Collector

Re: HPRM8.1 thick client in a mix mode environment

The v8.1 client that the customer installed expires after 30days. After the expiry, there is no way for the customer to access the TRIM7.1 server as the v8.1 is expired.  We noticed that the v8.1 client can connect to v8.1 server but not the TRIM7.1 server after 30 days.

 

How can we extend evaluation period of the v8.1 client to access TRIM 7 after 30 days? (This is because after 30 days the v8.1 can still access v8.1 server but not the TRIM7 server). We need the know how mix mode can be achieved for TRIM 7 to RM8 upgrade to ensure that all users can still accessing TRIM7 while upgrading to RM8 slowly.

EWillsey
Honored Contributor

Re: HPRM8.1 thick client in a mix mode environment

Clients do not expire. Contact support.
Greg Fraser_1
HPE Expert

Re: HPRM8.1 thick client in a mix mode environment

I chucked a post up about it a while ago, check out this tech note

http://h30499.www3.hp.com/t5/HP-Records-Manager-HP-TRIM-Forum/Error-accessing-the-RM8-production-dataset/td-p/6742290#.VZMhjfmqpBc

**Any opinions expressed in this forum are my own personal opinion and should not be interpreted as an official statement on behalf of Hewlett Packard Enterprise**
c-y-s
Super Collector

Re: HPRM8.1 thick client in a mix mode environment

Thanks for the documentation. However, we don't find it working.

 

The customer is having Win7 and Win8. Both installed with RM8.1 client. In the registry, we cannot find the 'License' key that stated in the given document. We tried to create the key by ourself and again, the v8.1 client still showing expired in the mix mode environment (as customer is doing upgrade fom TRIM7 to RM8.1).

 

Any recommendation ?

 

 

Below is the information in the gievn documentation:

 

Upgrade the workgroup server to 8.1.x and the message will disappear. However, if the rollout out is still in progress, a completion date must be decided and each affected client machine needs to have a registry key updated to that date.

 

To do this, the following key needs to be modified: Under HKEY_CURRENT_USER\License

Value Name – Expiry Type – REG_SZ Data – [Date Value – in YYYYMMDD format]

 

Set the date value to the date of upgrade completion. 

Greg Fraser_1
HPE Expert

Re: HPRM8.1 thick client in a mix mode environment

Might be easier to log a support case 

**Any opinions expressed in this forum are my own personal opinion and should not be interpreted as an official statement on behalf of Hewlett Packard Enterprise**
//Add this to "OnDomLoad" event