Imaging and the Marimba client

Is it possible to deploy images with the Marimba client installed to some degree or do you have to install the client as a post installation procedure?

0 Comments   [ + ] Show comments

Answers (1)

Posted by: kkaminsk 13 years ago
9th Degree Black Belt
An old colleage came through for me. Here's the solution in case anyone is interested:

The important thing is that the tuner should not be running when the image is taken and the following actions have been taken.
1. Remove the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Marimba\Inventory if present
2. Remove the properties.txt file in the tuner workspace (usually in .marimba folder). Make sure that you do not delete the properties.txt in the Installation Directory but in the Tuner workspace.
3. If the tuner has ever performed a kernel upgrade, then remove the folder .updatesprev or .updates (if it is present) from \lib
4. If the tuner has ever run a Tuner Update Manager (TUM), then delete the tuner id field in the installation directory lib\properties.txt. Open this file and delete the line that says id=3103105784360235419 or something similar. Also delete .update folder in the Tuner directory.
5. Make sure that the tuner is NOT started.
6. Take Ghost image of the machine.
To sum it up...
To ghost a machine with a Tuner for imaging, install the Tuner and delete the properties.txt located in the Tuner workspace. Then, delete the HKEY_LOCAL_MACHINE\SOFTWARE\Marimba\Inventory registry key. The first is a file used for the Tuner ID, the second is an Inventory unique ID.
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ