Migrating This guide will help you navigate migrating EDX software, projects, and all associated data from one computer to another is not necessarily a simple process.
The biggest migration issue is moving projects and data. EDX projects require pointing to a large number of files and folder paths outside of the EDX software installation.
...
Database path locations
...
may cause potential problems.
Before you move the software/projects/data you need to identify:
How many users use the software? Do they share the same login, or do they each have their own?
| Panel | ||
|---|---|---|
| ||
This impacts where projects can be located on the computer. |
Where are the terrain/clutter and other databases located: In the EDX install directory? In the project folder? Another location? These locations need to be the same on both computers.
| Panel | ||
|---|---|---|
| ||
You may need to check the path locations within each project to determine where they’re pointing to for the data. |
In your projects, have you added additional display layers like roads, streets, or other types of GIS data (.shp files, .bna files, KML/KMZ, etc)?
| Panel | ||
|---|---|---|
| ||
You’ll need to know the location of these files, and they’ll need to exist in the same location on the new computer. |
Are you using equipment files, antenna pattern files or channel plan template files? You’ll need to know the project location of each file type.
| Panel | ||
|---|---|---|
| ||
The locations need to be the same on both computers. |
Have you made changes under the File>Preferences menu?
| Panel | ||
|---|---|---|
| ||
If so, you’ll need to move the edx.ini file from the old computer to the new to preserve those values. |
Is there either local or network/remote access to both the old and new computer?
| Panel | ||
|---|---|---|
| ||
If one computer is local and the other is remote, network access to the remote computer is required to implement the migration. |
All of the above data Data paths are stored in each individual project, and as such, depending on who created the project, these paths may not be the same. The end result is if
| Note |
|---|
If these paths don’t match on both computers, a large number of error messages will display when you open the project on the new computer and will require re-pointing/re-adding all of the affected data sources. |
Example 1 – single user/single logon setup
In this example, we’ll assume only one user ever, and that person is the owner/administrator of the computers.
...
Let’s assume the engineer has been placing their data files in either \Program Files\EDX or the \Documents\EDX folder. To migrate the software:
Install EDX software on the new computer and ensure program launches.
Copy the \EDX folder from the \Documents folder on the old computer, to the \Documents folder on the new computer, replacing the new \EDX folder created during the install.
Copy the \ProgramData\EDX folder from the old computer to the new computer, replacing the \EDX folder created during installation.
Copy any data from the old \Program Files\EDX equipment folder or other folders not present in the new installation.
Example 2 – multi-user/multi login setup
...
This is where the migration may get more complicated, and it all depends on where each user is storing their terrain/cluer/other data and projects. To migrate the software and assuming each user is storing everything for the project in their Documents directory:
Create user accounts on the new computer.
Install EDX software on the new computer and ensure program launches.
Copy the \EDX folder from each of the users Documents folder on the old computer, to their Documents folder on the new computer, replacing the new \EDX folder created during the install.
Copy the \ProgramData\EDX folder from the older computer to the new, replacing the \ProgramData\EDX folder created during installation.
Copy any data from the old \Program Files\EDX equipment folder or other folders not present in the new installation.
Other setups
If your scenario doesn’t match either of the above examples, you’ll need to look at each project and their databases/antenna pattern/other project folder settings and determine the paths to these files and folders. Then, you’ll need to recreate the same files/folder locations on the new computer and copy all the relevant files to the same folder location on the new computer.
...