I was wondering is there a "how-to" for moving one license server to another. We are migrating our test environment to another machine. I have SLM running on the new machine. But when I attempt to start the license server (using Baan NT manager) it fails to start. The SLM does perform correctly. I cannot locate documentation on the files that need to be moved, etc...

Thanks for everyones input.

Stacy,

Without actually seeing your server configuration is it difficult to suggest what steps need to be taken other then the generic ones.

Refer to the SLM Documentation (you can get them from the Support Site or the installation CD) to start with and post any specific Qs.

Document code: U9200B US
Release: Infor Solution License Manager 7.1
Publication date: February 08


Document code: U9261B US
Release: Infor Solution License Manager 7.1
Publication date: February 08

The server is Windows 2003/SQL Server 2005
We have an existing License server (not SLM) and that is what I am trying to move. The SLM is on the new machine and would that cause an issue with the regular license manager (on the new machine) from starting.

Infor supplied me with the answer thanks for everyones help. I am posting it here.

Revalidating Baan IV on Windows

First, all of the validation sessions are in the Tools >> Software Installation >> Validation menu.


If you need to make changes to the dates of the current license:
1. Open the Maintain Requested System Configuration (ttiex3100m000) session.
2. Go to the appropriate field and key in the change.
3. Save and Exit.

If you need to make changes to the number of users or commercial functions:
1. Open the Maintain Requested System Configuration (Tools) (ttiex3101m000) session.
2. If you changed the dates on ttiex3100m000, above, click the Group Insert (bowtie) button and tab to the date fields and enter the new dates.
3. Make the changes needed to the number of users and/or commercial functions marked runable.
4. Save and Exit.

From this point, revalidation takes place in two parts. The first is generating the new Requested System Configuration (RSC) with changes made in the steps above and the second is applying the new validation keys to the server.

Part 1 – Generating the RSC
1. Open the Print Requested System Configuration (ttiex3400m000) session.
2. Click OK when the warning about overwriting the security code appears.
3. Make sure the information shown, including the License Code and Sequence Number is correct.
4. Click Continue.
5. Select a rewrite device to save the Requested System Configuration (RSC) to a file.
6. E-mail the RSC file to keys@ssaglobal.com.

The validation group will process the RSC through the validation server and new keys will be e-mailed back to you. This process usually takes 24 to 48 hours.

*************************************************************************************
Part 2 – Applying the new validation keys
1. Log into Baan.
2. Open the Maintain Security Code/Validation Key (ttiex3102m000) session.
3. Enter the new keys for Validation Key (Tools) and the Validation Key Software (Standard) if the latter was changed.
4. Save and Exit.
5. Run the Validate Tools Set (ttiex3220m000) session.
6. Log out of Baan.
7. Restart the Baan license service.
8. Log into Baan.
9. Run the Configure Application (ttiex3225m000) session. Validation is complete when the message Patch Process Ready appears.