IBM License Metric Tool (ILMT)

ILMT 9.2.33 on Windows

Good day folks,  we have a plan to migrate up to 500 Windows servers from UAT ILMT environment to PROD ILMT environment.  Since the software bundling has been done on these 500 UAT servers and migrating them over to PROD ILMT environment will have a new BigFIx Client ID as well.    They will end up a complete set of new servers in PROD environment.   So that is an issue.  How do I also maintain/reserve all the software bundling done on these 500 servers after migrated to PROD?   We don't want to re-do each one of them. 

Any simple working solution to accomplish this task?    Please advise.

Thanks. 

Hello York,

The crucial question is if there is a connection between UAT ILMT & PROD ILMT environments (PROD ILMT -> UAT Bigfix) ?
If it is you can back up the database of the UAT ILMT server and restore it under the PROD ILMT server and enable the computer reconciliation mode.
In such case Software classification is preserved during the migration..
If there is no connection the partial migration be means of REST API would be the only solution...

ILMT 9.2.33 on Windows

Good day folks,  we have a plan to migrate up to 500 Windows servers from UAT ILMT environment to PROD ILMT environment.  Since the software bundling has been done on these 500 UAT servers and migrating them over to PROD ILMT environment will have a new BigFIx Client ID as well.    They will end up a complete set of new servers in PROD environment.   So that is an issue.  How do I also maintain/reserve all the software bundling done on these 500 servers after migrated to PROD?   We don't want to re-do each one of them. 

Any simple working solution to accomplish this task?    Please advise.

Thanks. 

Hi Oktawian, to clarify your feedback.  How I could backup the UAT ILMT database (TEMADB) and restore it under PROD ILMT server with the same database name (TEMADB)?    

Even with the REST API method,  how does it know to reference back to the same server as the computer ID or besclient ID would be different after UAT servers registered to PROD ILMT environment?

Hello York,

The crucial question is if there is a connection between UAT ILMT & PROD ILMT environments (PROD ILMT -> UAT Bigfix) ?
If it is you can back up the database of the UAT ILMT server and restore it under the PROD ILMT server and enable the computer reconciliation mode.
In such case Software classification is preserved during the migration..
If there is no connection the partial migration be means of REST API would be the only solution...

ILMT 9.2.33 on Windows

Good day folks,  we have a plan to migrate up to 500 Windows servers from UAT ILMT environment to PROD ILMT environment.  Since the software bundling has been done on these 500 UAT servers and migrating them over to PROD ILMT environment will have a new BigFIx Client ID as well.    They will end up a complete set of new servers in PROD environment.   So that is an issue.  How do I also maintain/reserve all the software bundling done on these 500 servers after migrated to PROD?   We don't want to re-do each one of them. 

Any simple working solution to accomplish this task?    Please advise.

Thanks. 

Hello York,

How I could backup the UAT ILMT database (TEMADB) and restore it under PROD ILMT server with the same database name (TEMADB)? 
Backup/restore of the ILMT database (TEMADB) can be done using SQL Server Management Studio (SSMS).

Please remember that ILMT database is not linked to ILMT instance itself...so, it's perfectly safe to move TEMADB from one ILMT instance to another as long as it's the same OS & ILMT version:
https://www.ibm.com/docs/en/license-metric-tool?topic=mbc-migrating-license-metric-tool-server-between-computers-same-operating-systems

As to different besclient IDs...
It's a job of computer reconciliation mode processing...to match the agents using Host name/IP address rather than besclient ID.
As long as BigFIx Client has the same Host name/IP address it should be perfectly mapped between UAT & PROD ILMT. 

Hi Oktawian, to clarify your feedback.  How I could backup the UAT ILMT database (TEMADB) and restore it under PROD ILMT server with the same database name (TEMADB)?    

Even with the REST API method,  how does it know to reference back to the same server as the computer ID or besclient ID would be different after UAT servers registered to PROD ILMT environment?

Hello York,

The crucial question is if there is a connection between UAT ILMT & PROD ILMT environments (PROD ILMT -> UAT Bigfix) ?
If it is you can back up the database of the UAT ILMT server and restore it under the PROD ILMT server and enable the computer reconciliation mode.
In such case Software classification is preserved during the migration..
If there is no connection the partial migration be means of REST API would be the only solution...

ILMT 9.2.33 on Windows

Good day folks,  we have a plan to migrate up to 500 Windows servers from UAT ILMT environment to PROD ILMT environment.  Since the software bundling has been done on these 500 UAT servers and migrating them over to PROD ILMT environment will have a new BigFIx Client ID as well.    They will end up a complete set of new servers in PROD environment.   So that is an issue.  How do I also maintain/reserve all the software bundling done on these 500 servers after migrated to PROD?   We don't want to re-do each one of them. 

Any simple working solution to accomplish this task?    Please advise.

Thanks. 

Hi Oktawian,   I believe there is a confusion with my question.    Let me try my best to re-word my question again.

Basically,  we have

UAT ILMT/BigFix server with 500 eps.

PRO ILMT/BigFix server with its own eps

We are shutting down the UAT ILMT/BigFix server.   Need to re-direct all the 500 eps to a PROD ILMT/BigFix server.    These 500 servers will have their own Computer ID, other IDs created in the PROD ILMT/BigFix database as expected.  Remember that these 500 UAT eps are never existed in PROD ILMT before.  This part is very straight forward.

As usual, HW and SW scan jobs are done on these 500 servers and reporting to PROD ILMT database.  

Now the real question is that how to transfer or maintain the software bundling data for these 500 eps from UAT ILMT database into PROD ILMT database?

Enabling the computer reconciliation mode won't work as these 500 eps are never existed before in PROD ILMT database.  They are now a completely new server instance just like any new ep registered to BigFix.   

How would you carry over the software bundling done from UAT to PROD for these 500 eps?

Hello York,

How I could backup the UAT ILMT database (TEMADB) and restore it under PROD ILMT server with the same database name (TEMADB)? 
Backup/restore of the ILMT database (TEMADB) can be done using SQL Server Management Studio (SSMS).

Please remember that ILMT database is not linked to ILMT instance itself...so, it's perfectly safe to move TEMADB from one ILMT instance to another as long as it's the same OS & ILMT version:
https://www.ibm.com/docs/en/license-metric-tool?topic=mbc-migrating-license-metric-tool-server-between-computers-same-operating-systems

As to different besclient IDs...
It's a job of computer reconciliation mode processing...to match the agents using Host name/IP address rather than besclient ID.
As long as BigFIx Client has the same Host name/IP address it should be perfectly mapped between UAT & PROD ILMT. 

Hi Oktawian, to clarify your feedback.  How I could backup the UAT ILMT database (TEMADB) and restore it under PROD ILMT server with the same database name (TEMADB)?    

Even with the REST API method,  how does it know to reference back to the same server as the computer ID or besclient ID would be different after UAT servers registered to PROD ILMT environment?

Hello York,

The crucial question is if there is a connection between UAT ILMT & PROD ILMT environments (PROD ILMT -> UAT Bigfix) ?
If it is you can back up the database of the UAT ILMT server and restore it under the PROD ILMT server and enable the computer reconciliation mode.
In such case Software classification is preserved during the migration..
If there is no connection the partial migration be means of REST API would be the only solution...

ILMT 9.2.33 on Windows

Good day folks,  we have a plan to migrate up to 500 Windows servers from UAT ILMT environment to PROD ILMT environment.  Since the software bundling has been done on these 500 UAT servers and migrating them over to PROD ILMT environment will have a new BigFIx Client ID as well.    They will end up a complete set of new servers in PROD environment.   So that is an issue.  How do I also maintain/reserve all the software bundling done on these 500 servers after migrated to PROD?   We don't want to re-do each one of them. 

Any simple working solution to accomplish this task?    Please advise.

Thanks. 

Indeed, there is no way to use computer reconciliation mode if you don't want to reuse the existing TEMADB database (Backup existing UAT ILMT & restore under PROD ILMT).
Just please make sure that there is good reason behind such decision...
As I've stated before, ILMT database is not linked to ILMT instance itself...it's perfectly safe to move TEMADB from one ILMT instance to another as long as it's the same OS & ILMT version.

Anyhow, without computer reconciliation mode the only other way would be through a customized REST API.

Even with the REST API method,  how does it know to reference back to the same server as the computer ID
Good point,
Basically in the 'Request body' you'd have to use computer_dns_name instead of computer_bigfix_id
To be honest I've never tried such a 'switch' but I don't see any particular reason why this would not work...

Hi Oktawian,   I believe there is a confusion with my question.    Let me try my best to re-word my question again.

Basically,  we have

UAT ILMT/BigFix server with 500 eps.

PRO ILMT/BigFix server with its own eps

We are shutting down the UAT ILMT/BigFix server.   Need to re-direct all the 500 eps to a PROD ILMT/BigFix server.    These 500 servers will have their own Computer ID, other IDs created in the PROD ILMT/BigFix database as expected.  Remember that these 500 UAT eps are never existed in PROD ILMT before.  This part is very straight forward.

As usual, HW and SW scan jobs are done on these 500 servers and reporting to PROD ILMT database.  

Now the real question is that how to transfer or maintain the software bundling data for these 500 eps from UAT ILMT database into PROD ILMT database?

Enabling the computer reconciliation mode won't work as these 500 eps are never existed before in PROD ILMT database.  They are now a completely new server instance just like any new ep registered to BigFix.   

How would you carry over the software bundling done from UAT to PROD for these 500 eps?

Hello York,

How I could backup the UAT ILMT database (TEMADB) and restore it under PROD ILMT server with the same database name (TEMADB)? 
Backup/restore of the ILMT database (TEMADB) can be done using SQL Server Management Studio (SSMS).

Please remember that ILMT database is not linked to ILMT instance itself...so, it's perfectly safe to move TEMADB from one ILMT instance to another as long as it's the same OS & ILMT version:
https://www.ibm.com/docs/en/license-metric-tool?topic=mbc-migrating-license-metric-tool-server-between-computers-same-operating-systems

As to different besclient IDs...
It's a job of computer reconciliation mode processing...to match the agents using Host name/IP address rather than besclient ID.
As long as BigFIx Client has the same Host name/IP address it should be perfectly mapped between UAT & PROD ILMT. 

Hi Oktawian, to clarify your feedback.  How I could backup the UAT ILMT database (TEMADB) and restore it under PROD ILMT server with the same database name (TEMADB)?    

Even with the REST API method,  how does it know to reference back to the same server as the computer ID or besclient ID would be different after UAT servers registered to PROD ILMT environment?

Hello York,

The crucial question is if there is a connection between UAT ILMT & PROD ILMT environments (PROD ILMT -> UAT Bigfix) ?
If it is you can back up the database of the UAT ILMT server and restore it under the PROD ILMT server and enable the computer reconciliation mode.
In such case Software classification is preserved during the migration..
If there is no connection the partial migration be means of REST API would be the only solution...

ILMT 9.2.33 on Windows

Good day folks,  we have a plan to migrate up to 500 Windows servers from UAT ILMT environment to PROD ILMT environment.  Since the software bundling has been done on these 500 UAT servers and migrating them over to PROD ILMT environment will have a new BigFIx Client ID as well.    They will end up a complete set of new servers in PROD environment.   So that is an issue.  How do I also maintain/reserve all the software bundling done on these 500 servers after migrated to PROD?   We don't want to re-do each one of them. 

Any simple working solution to accomplish this task?    Please advise.

Thanks. 

IF PROD ILMT server has its own TEMADB database on the SQL instance, how I could even restore the TEMADB database from UAT into PROD SQL instance.   Don't you end up two database names with the same TEMADB if it even allows to do so.   If you could have multiple TEMADB databases from in the same SQL instance in PROD,  how does PROD ILMT application know to use both same TEMADB database names.   That is impossible. 

Can 1 ILMT application links or works on multiple TEMADB database names?    I know it can links to multiple BigFix datasources and NOT database name.

Can you give me a complete sample of the REST API call with usage of the two switches as described below.   Thanks.

Basically in the 'Request body' you'd have to use computer_dns_name instead of computer_bigfix_id
To be honest I've never tried such a 'switch' but I don't see any particular reason why this would not work...

Indeed, there is no way to use computer reconciliation mode if you don't want to reuse the existing TEMADB database (Backup existing UAT ILMT & restore under PROD ILMT).
Just please make sure that there is good reason behind such decision...
As I've stated before, ILMT database is not linked to ILMT instance itself...it's perfectly safe to move TEMADB from one ILMT instance to another as long as it's the same OS & ILMT version.

Anyhow, without computer reconciliation mode the only other way would be through a customized REST API.

Even with the REST API method,  how does it know to reference back to the same server as the computer ID
Good point,
Basically in the 'Request body' you'd have to use computer_dns_name instead of computer_bigfix_id
To be honest I've never tried such a 'switch' but I don't see any particular reason why this would not work...

Hi Oktawian,   I believe there is a confusion with my question.    Let me try my best to re-word my question again.

Basically,  we have

UAT ILMT/BigFix server with 500 eps.

PRO ILMT/BigFix server with its own eps

We are shutting down the UAT ILMT/BigFix server.   Need to re-direct all the 500 eps to a PROD ILMT/BigFix server.    These 500 servers will have their own Computer ID, other IDs created in the PROD ILMT/BigFix database as expected.  Remember that these 500 UAT eps are never existed in PROD ILMT before.  This part is very straight forward.

As usual, HW and SW scan jobs are done on these 500 servers and reporting to PROD ILMT database.  

Now the real question is that how to transfer or maintain the software bundling data for these 500 eps from UAT ILMT database into PROD ILMT database?

Enabling the computer reconciliation mode won't work as these 500 eps are never existed before in PROD ILMT database.  They are now a completely new server instance just like any new ep registered to BigFix.   

How would you carry over the software bundling done from UAT to PROD for these 500 eps?

Hello York,

How I could backup the UAT ILMT database (TEMADB) and restore it under PROD ILMT server with the same database name (TEMADB)? 
Backup/restore of the ILMT database (TEMADB) can be done using SQL Server Management Studio (SSMS).

Please remember that ILMT database is not linked to ILMT instance itself...so, it's perfectly safe to move TEMADB from one ILMT instance to another as long as it's the same OS & ILMT version:
https://www.ibm.com/docs/en/license-metric-tool?topic=mbc-migrating-license-metric-tool-server-between-computers-same-operating-systems

As to different besclient IDs...
It's a job of computer reconciliation mode processing...to match the agents using Host name/IP address rather than besclient ID.
As long as BigFIx Client has the same Host name/IP address it should be perfectly mapped between UAT & PROD ILMT. 

Hi Oktawian, to clarify your feedback.  How I could backup the UAT ILMT database (TEMADB) and restore it under PROD ILMT server with the same database name (TEMADB)?    

Even with the REST API method,  how does it know to reference back to the same server as the computer ID or besclient ID would be different after UAT servers registered to PROD ILMT environment?

Hello York,

The crucial question is if there is a connection between UAT ILMT & PROD ILMT environments (PROD ILMT -> UAT Bigfix) ?
If it is you can back up the database of the UAT ILMT server and restore it under the PROD ILMT server and enable the computer reconciliation mode.
In such case Software classification is preserved during the migration..
If there is no connection the partial migration be means of REST API would be the only solution...

ILMT 9.2.33 on Windows

Good day folks,  we have a plan to migrate up to 500 Windows servers from UAT ILMT environment to PROD ILMT environment.  Since the software bundling has been done on these 500 UAT servers and migrating them over to PROD ILMT environment will have a new BigFIx Client ID as well.    They will end up a complete set of new servers in PROD environment.   So that is an issue.  How do I also maintain/reserve all the software bundling done on these 500 servers after migrated to PROD?   We don't want to re-do each one of them. 

Any simple working solution to accomplish this task?    Please advise.

Thanks. 

Hello York,

To be honest I don't follow this 'multiple TEMADB databases' problem...there is no multiple.
Let me reiterate one more time:
ILMT database is not linked to ILMT server instance.

Anyhow, all the steps of migrating the ILMT database between two different ILMT server instances are thoroughly described here :
https://www.ibm.com/docs/en/license-metric-tool?topic=mbc-migrating-license-metric-tool-server-between-computers-same-operating-systems

IF PROD ILMT server has its own TEMADB database on the SQL instance, how I could even restore the TEMADB database from UAT into PROD SQL instance.   Don't you end up two database names with the same TEMADB if it even allows to do so.   If you could have multiple TEMADB databases from in the same SQL instance in PROD,  how does PROD ILMT application know to use both same TEMADB database names.   That is impossible. 

Can 1 ILMT application links or works on multiple TEMADB database names?    I know it can links to multiple BigFix datasources and NOT database name.

Can you give me a complete sample of the REST API call with usage of the two switches as described below.   Thanks.

Basically in the 'Request body' you'd have to use computer_dns_name instead of computer_bigfix_id
To be honest I've never tried such a 'switch' but I don't see any particular reason why this would not work...

Indeed, there is no way to use computer reconciliation mode if you don't want to reuse the existing TEMADB database (Backup existing UAT ILMT & restore under PROD ILMT).
Just please make sure that there is good reason behind such decision...
As I've stated before, ILMT database is not linked to ILMT instance itself...it's perfectly safe to move TEMADB from one ILMT instance to another as long as it's the same OS & ILMT version.

Anyhow, without computer reconciliation mode the only other way would be through a customized REST API.

Even with the REST API method,  how does it know to reference back to the same server as the computer ID
Good point,
Basically in the 'Request body' you'd have to use computer_dns_name instead of computer_bigfix_id
To be honest I've never tried such a 'switch' but I don't see any particular reason why this would not work...

Hi Oktawian,   I believe there is a confusion with my question.    Let me try my best to re-word my question again.

Basically,  we have

UAT ILMT/BigFix server with 500 eps.

PRO ILMT/BigFix server with its own eps

We are shutting down the UAT ILMT/BigFix server.   Need to re-direct all the 500 eps to a PROD ILMT/BigFix server.    These 500 servers will have their own Computer ID, other IDs created in the PROD ILMT/BigFix database as expected.  Remember that these 500 UAT eps are never existed in PROD ILMT before.  This part is very straight forward.

As usual, HW and SW scan jobs are done on these 500 servers and reporting to PROD ILMT database.  

Now the real question is that how to transfer or maintain the software bundling data for these 500 eps from UAT ILMT database into PROD ILMT database?

Enabling the computer reconciliation mode won't work as these 500 eps are never existed before in PROD ILMT database.  They are now a completely new server instance just like any new ep registered to BigFix.   

How would you carry over the software bundling done from UAT to PROD for these 500 eps?

Hello York,

How I could backup the UAT ILMT database (TEMADB) and restore it under PROD ILMT server with the same database name (TEMADB)? 
Backup/restore of the ILMT database (TEMADB) can be done using SQL Server Management Studio (SSMS).

Please remember that ILMT database is not linked to ILMT instance itself...so, it's perfectly safe to move TEMADB from one ILMT instance to another as long as it's the same OS & ILMT version:
https://www.ibm.com/docs/en/license-metric-tool?topic=mbc-migrating-license-metric-tool-server-between-computers-same-operating-systems

As to different besclient IDs...
It's a job of computer reconciliation mode processing...to match the agents using Host name/IP address rather than besclient ID.
As long as BigFIx Client has the same Host name/IP address it should be perfectly mapped between UAT & PROD ILMT. 

Hi Oktawian, to clarify your feedback.  How I could backup the UAT ILMT database (TEMADB) and restore it under PROD ILMT server with the same database name (TEMADB)?    

Even with the REST API method,  how does it know to reference back to the same server as the computer ID or besclient ID would be different after UAT servers registered to PROD ILMT environment?

Hello York,

The crucial question is if there is a connection between UAT ILMT & PROD ILMT environments (PROD ILMT -> UAT Bigfix) ?
If it is you can back up the database of the UAT ILMT server and restore it under the PROD ILMT server and enable the computer reconciliation mode.
In such case Software classification is preserved during the migration..
If there is no connection the partial migration be means of REST API would be the only solution...

ILMT 9.2.33 on Windows

Good day folks,  we have a plan to migrate up to 500 Windows servers from UAT ILMT environment to PROD ILMT environment.  Since the software bundling has been done on these 500 UAT servers and migrating them over to PROD ILMT environment will have a new BigFIx Client ID as well.    They will end up a complete set of new servers in PROD environment.   So that is an issue.  How do I also maintain/reserve all the software bundling done on these 500 servers after migrated to PROD?   We don't want to re-do each one of them. 

Any simple working solution to accomplish this task?    Please advise.

Thanks. 

Wonderful, let me review that doc link.

Thanks,

Hello York,

To be honest I don't follow this 'multiple TEMADB databases' problem...there is no multiple.
Let me reiterate one more time:
ILMT database is not linked to ILMT server instance.

Anyhow, all the steps of migrating the ILMT database between two different ILMT server instances are thoroughly described here :
https://www.ibm.com/docs/en/license-metric-tool?topic=mbc-migrating-license-metric-tool-server-between-computers-same-operating-systems

IF PROD ILMT server has its own TEMADB database on the SQL instance, how I could even restore the TEMADB database from UAT into PROD SQL instance.   Don't you end up two database names with the same TEMADB if it even allows to do so.   If you could have multiple TEMADB databases from in the same SQL instance in PROD,  how does PROD ILMT application know to use both same TEMADB database names.   That is impossible. 

Can 1 ILMT application links or works on multiple TEMADB database names?    I know it can links to multiple BigFix datasources and NOT database name.

Can you give me a complete sample of the REST API call with usage of the two switches as described below.   Thanks.

Basically in the 'Request body' you'd have to use computer_dns_name instead of computer_bigfix_id
To be honest I've never tried such a 'switch' but I don't see any particular reason why this would not work...

Indeed, there is no way to use computer reconciliation mode if you don't want to reuse the existing TEMADB database (Backup existing UAT ILMT & restore under PROD ILMT).
Just please make sure that there is good reason behind such decision...
As I've stated before, ILMT database is not linked to ILMT instance itself...it's perfectly safe to move TEMADB from one ILMT instance to another as long as it's the same OS & ILMT version.

Anyhow, without computer reconciliation mode the only other way would be through a customized REST API.

Even with the REST API method,  how does it know to reference back to the same server as the computer ID
Good point,
Basically in the 'Request body' you'd have to use computer_dns_name instead of computer_bigfix_id
To be honest I've never tried such a 'switch' but I don't see any particular reason why this would not work...

Hi Oktawian,   I believe there is a confusion with my question.    Let me try my best to re-word my question again.

Basically,  we have

UAT ILMT/BigFix server with 500 eps.

PRO ILMT/BigFix server with its own eps

We are shutting down the UAT ILMT/BigFix server.   Need to re-direct all the 500 eps to a PROD ILMT/BigFix server.    These 500 servers will have their own Computer ID, other IDs created in the PROD ILMT/BigFix database as expected.  Remember that these 500 UAT eps are never existed in PROD ILMT before.  This part is very straight forward.

As usual, HW and SW scan jobs are done on these 500 servers and reporting to PROD ILMT database.  

Now the real question is that how to transfer or maintain the software bundling data for these 500 eps from UAT ILMT database into PROD ILMT database?

Enabling the computer reconciliation mode won't work as these 500 eps are never existed before in PROD ILMT database.  They are now a completely new server instance just like any new ep registered to BigFix.   

How would you carry over the software bundling done from UAT to PROD for these 500 eps?

Hello York,

How I could backup the UAT ILMT database (TEMADB) and restore it under PROD ILMT server with the same database name (TEMADB)? 
Backup/restore of the ILMT database (TEMADB) can be done using SQL Server Management Studio (SSMS).

Please remember that ILMT database is not linked to ILMT instance itself...so, it's perfectly safe to move TEMADB from one ILMT instance to another as long as it's the same OS & ILMT version:
https://www.ibm.com/docs/en/license-metric-tool?topic=mbc-migrating-license-metric-tool-server-between-computers-same-operating-systems

As to different besclient IDs...
It's a job of computer reconciliation mode processing...to match the agents using Host name/IP address rather than besclient ID.
As long as BigFIx Client has the same Host name/IP address it should be perfectly mapped between UAT & PROD ILMT. 

Hi Oktawian, to clarify your feedback.  How I could backup the UAT ILMT database (TEMADB) and restore it under PROD ILMT server with the same database name (TEMADB)?    

Even with the REST API method,  how does it know to reference back to the same server as the computer ID or besclient ID would be different after UAT servers registered to PROD ILMT environment?

Hello York,

The crucial question is if there is a connection between UAT ILMT & PROD ILMT environments (PROD ILMT -> UAT Bigfix) ?
If it is you can back up the database of the UAT ILMT server and restore it under the PROD ILMT server and enable the computer reconciliation mode.
In such case Software classification is preserved during the migration..
If there is no connection the partial migration be means of REST API would be the only solution...

ILMT 9.2.33 on Windows

Good day folks,  we have a plan to migrate up to 500 Windows servers from UAT ILMT environment to PROD ILMT environment.  Since the software bundling has been done on these 500 UAT servers and migrating them over to PROD ILMT environment will have a new BigFIx Client ID as well.    They will end up a complete set of new servers in PROD environment.   So that is an issue.  How do I also maintain/reserve all the software bundling done on these 500 servers after migrated to PROD?   We don't want to re-do each one of them. 

Any simple working solution to accomplish this task?    Please advise.

Thanks.