Issue
How can Build Console be safely moved to a new machine?
Solution
Install a new copy of Imaging Toolkit onto the destination administrative machine, and then copy the appropriate files.
Procedures
Install Imaging Toolkit
- Install your current version of Imaging Toolkit onto the new administrative machine.
NOTE: | Ensure you install the same version that you are running otherwise library modifications between versions may cause corruption. |
|
- If you wish to check the installation copy your existing license file to the installation directory and run Build Console.
Copy files to the new administrative machine
- Ensure that Build Console is not running on the source machine and also on the destination machine
- Copy the contents of the
File Library
, Images
, Integration
and Projects
folders from the old administrative machine to the new one.
If the default folders have been used these will be as follows:
Folder | Default Directory |
---|
File Library | C:\ProgramData\ENGL\ImagingToolkit\<version> \FileLibrary |
Integration | C:\ProgramData\ENGL\ImagingToolkit\<version> \Integration |
Projects | C:\ProgramData\ENGL\ImagingToolkit\<version> \Projects |
Images | <Projects> \images |
The actual paths should be be determined by clicking the Tools | Options menu item within Build Console and selecting the Folders tab.
- Copy the
buildconsole.xml
file to the new machine.
If the default folders have been used the file will be located as follows;
Default Directory |
---|
C:\ProgramData\ENGL\ImagingToolkit\<version> \BuildConsole.xml |
- If you wish to check the copy was successful run Build Console again at this point and check that all the media appears.
Support
If you encounter any issues at any point of the migration please log a support incident with ENGL referencing this TID and the stage which is causing the problem before continuing any further.