AccessData Group LLC

425 Market Street, 7th Floor

San Francisco, CA, 94105

415.442.0404 tel
415.442.0403 fax
www.accessdata.com

Migrating Summation iBlaze to a New Server

This document is not intended to be all inclusive. It is intended to provide a general overview of what is involved
in a server migration.
If you are going to be moving Summation from one server to another (or change its location on the server), with
a different name or path we recommend you do the following:
1. It is advisable that you run the maintenance utilities on each caseBackup, Check, Pack, and Blaze on
each case. You should also check with the attorneys, paralegals, and IT staff involved to determine the
location of any files and/or folders that are referenced by Summation case that DO NOT fall under the
Summation directory structure.
2. If the old server is not going to continue to be available on the network you should uninstall the network
clients.
3. Install Summation (Install a new system) to the NEW server from a workstation.
4. Update each of the clients so they are pointing to the NEW server. To do this, uninstall the old client
(Add/Remove Programs) and the install the new client from the workstation by browsing to the Client Setup
folder at the root of the Summation application folder on the server. Open the Client Setup folder, and
double click on the file there.
NOTE: IF the migration has already occurred, and there is an error launching the client in that it looks for
the old location, use the VOMUS command to fix this. To accomplish this on the client machine that is
having the problem, go to the Start button and open the run command. Type the following, replacing the
square bracket text with the appropriate path, AND make sure you use the quotation marks where noted,
AND uppercase/lowercase is important:
msiexec.exe /i "\\msbfs\summ\Summation Blaze.MSI" REINSTALL="ALL" REINSTALLMODE="vomus"
Here is a sample command line:
msiexec.exe
/i
"\\Servername\Sharename\AppDir\Summation
REINSTALLMODE="vomus"

Blaze.MSI"

REINSTALL="ALL"

5. Open Windows Explorer, browse to your OLD server's Summation folder. Go into the CASEDATA folder
and manually copy all of the case folders and paste them into the NEW server's CASEDATA folder.
6. Next, open the OLD server's CASES folder and copy all of the .CI files (NO NOT copy the Caseinfo.ini) and
paste them into the NEW server's CASES folder.
If you have the Admin Console set up with users, and are not just using the default settings, you will also
want to copy the ADMIN folder from the old installation to the new installation, overwriting what was installed
on the new server.
You may also want to copy the individual profile folders, in the PROFILES folder (the one in the root of the
application folder). If you are upgrading to a newer version of Summation you will NOT want to copy the
ALL USERS profile folder, from the old installation to the new one. If you do, you risk overwriting newer
script files with older ones. You may want to compare the script folders and copy scripts files (*.vs) from the

AccessData Group LLC

425 Market Street, 7th Floor
San Francisco, CA, 94105

415.442.0404 tel
415.442.0403 fax
www.accessdata.com

old installation to the new, were those files do not exist in the new script folder (summation
application\Profiles\All Users\Script).
7. Next, right click on each of the .CI files in the new directory, open with Notepad, and change the Case
Directory path to point to the NEW server location.
8. When all of the .CI files are updated, go into the Summation ADMIN folder on the new server. Double click
on swadmin.exe. The default password is: Admin
9. Go into the Groups tab, click on the Case Paths button, and verify that it is correctly pointing to your new
server's Cases folder.
10. Click on the Case Options button, and then select "Verify case info files".
11. Repeat steps 8 and 9 for all user groups in the drop down list. By default, if you did not create any user
groups, there are 2 groups: Unassigned Users and Admin.
12. Next, launch the new Summation client. Go to Case > Customize, verify they are correctly pointing to the
new server location. Also verify that you can see all of the data, images, etc.
The UDL links for Briefcases and companion links may need to be updated on the new server. If you have
any Briefcases you will have to update the case directory path in the UDL file manually, changing the case
directory path to point to the new server location. For companion links (i.e. People table, Chronology of
Events) under the Case Explorer tree, you can easily update the UDL files by right clicking on each and
removing them. Then right click on the case name within the Case Explorer and select Create New >
Folder and re-add them to the Case Explorer tree.
Any transcript link files will need to be examined and updated where a path to the old server exists. These
files can be found in the Casedata\[case]\Profiles\All Users\SWLinks folder. Right click on the XML files
for the transcripts, open with notepad and do a find/replace there as necessary.