Follow

Worldox Server Install\Move Process GX3

Pre-Staging: Things to know

Windows 2008(R2) and 2012(R2) Server and 8.3 File Name Support

Windows 2008(R2) Server & 2012(R2) is shipped with 8.3 file name support turned off. That doesn't

mean that you can’t save files on a with 8.3 names. What it does mean is for files and folders with longer

names is Windows it will not create their corresponding 8.3 alias names.

The problem with that is when Worldox indexes a sites Legacy documents, it is indexing the 8.3 alias-

naming format for the longer named files and folders. If the Windows aliases that the OS creates are not

there because 8.3 is turned off, your legacy files will not be indexed properly and user’s will not be able

Here is a link to a Microsoft page explaining the 8.3 naming convention:

http://msdn.microsoft.com/en-us/library/aa365247(VS.85).aspx

One of the commands to turn 8.3 support back on for the server is:

To enable the 8.3 name creation on all NTFS partitions, type fsutil.exe behavior set NTFSdisable8dot3 0

at a command prompt, and then press ENTER. Then reboot the server.

Note: 8.3 file support MUST BE SET BEFORE YOU START TO COPY DATA TO THE NEW SERVER.

Install\Move Implementation

This article assumes that all the path and drive-letter mappings will remain the same from the current

server to the new server. To ensure a successful upgrade, we recommend:

 When you perform a server upgrade, you should COPY and not move the information from the

old server to the new one. This way, you preserve the original information.

 Be certain that you have rights to copy ALL System and Hidden files.

 During the server upgrade, users must be off the network, and the indexer must be shut down.

 Proof your work and confirm that all data has been transferred.

 FOR GX3 SERVER MOVES: YOU MUST CONTACT TECH SUPPORT TO HAVE YOUR LICENSE RESET

SO IT CAN BE ACTIVATED ON THE NEW SERVER.

The following items will be copied from your old server to your new server:

Be sure to save all path information you uncover in these 4 steps. You will need that information when

1. Locate the Worldox program folder on the network. At a workstation where Worldox is

running, select Help > About

This is a sample path: f:\apps\worldox\ (Mirrored From or Network Home)

2. Load WDADMIN and select AuditTrail > Configure. If an audit trail database is defined on the

old server, obtain the database path.

These are sample paths: W:\worldox\audit & W:\audit_trail

3. Still in WDADMIN, select Profiles > Add/Edit. Highlight each active profile group in turn and

click Edit. Note the base path and UNC mapping for each. The base path is where data is stored.

4. At the Worldox Indexer, click Close Server, then highlight each indexed drive in turn:

a. Select Profiles > Properties to determine where the profile database is stored. The

first field is the location of the profile database on the network.

b. Select Text > Properties to determine where the text database is stored. The first field

is the location of the text database on the network.

Before copying files, make sure that:

 All users are off the network.

 You have the rights to copy System and Hidden files.

a. Copy the entire program structure from the old server to the new one. This includes

the Worldox program folder and all its subfolders. Use the path information from Step 1

in the above section, Finding Locations.

b. Copy all the data from the old server to the new one. Use the path information from

Step 3 in the above section, Finding Locations.

Copy the profile and text databases. Use the path information obtained in Step 4 of

If an audit trail was defined, copy the Audit trail databases. Use the path information

obtained in Step 2 of Finding Locations.

1. After all files are copied, load WDADMIN on the new server.

2. Select Profiles > Add/Edit. Highlight each active profile group in turn and click Edit.

a) Edit the Base Path field with the new root folder location for that Profile Group

b) Edit the mapping field to match (i.e., the UNC mapping.) This mapping should extend

only to the root of the base path, and NOT into any named folder in the base path.

3. To maintain user favorite files, you will need to add the following section to the worldox.ini

file in the network program folder:

\\oldserver\oldshare\=\\newserver\newshare\

(with their old UNC info =new UNC info)

Note: Worldox stores each user’s favorite files by UNC path and will only perform the above translation

if the old server/shares are not available. Please ensure that either the old server is either no longer on

the network, or has its shares offline.

Failure to do so will create a condition where documents on the old server will be modified.

4. Change all user login scripts and mappings so that users can connect to the new server\share.

5. Give users full rights to the Worldox directory and data on the server.

6. On the Indexer, you will need to do a few things to complete the server move process.

a) It is best practice to - if possible - do a full INIT of your databases after the move.

However, this may not always be required, depending on changes made. If your

databases are small and don’t take long to re-init, then it is best practice to do so. If they

are large and/or you may want keep them after the move, then consult your reseller or

tech support in advance, to confirm that your databases will still work after the move

b) No matter whether you re-init your databases or not, YOU MUST adjust for the

change in UNC location of the databases. Each database has an INI that contains the

UNC location of the database files; the INI will be wrong as a result of the server move.

This must be corrected by editing some INI files in the database folder to adjust that

UNC pointer. Failure to do so will result in your databases not being found when you

restart the Indexer(s).

6.1 To adjust for UNC location changes on the Indexer:

a) Go to the database location for each active drive (use the path information obtained

in Step 4 of this document in Finding Locations).

b) In the profile database location(s), edit the wdindex.ini file and replace the old UNC

path with the new UNC path.

c) In the text database location(s), edit the wdindex.ini file and replace the old UNC path

with the new UNC path. (Please note: if there are text splits, you will need to replace

each reference to the old UNC with the new UNC).

d) Then load the Indexer, and check each active drive to make sure that you can

properly see the databases:

 Start up the Indexer in maintenance mode.

 Check off the drive(s) being indexed.

 If you are going to re-init your databases, then go to the Update tab and

click on Profiles and Text > Initialize and Create Databases.

 Once this step is done, you will need to put the Indexer back into Server

Mode by going to Server and clicking Start.

7. Restart one of the workstations. It should behave as if there was no server change.

1. For everything that was copied, compare the file and byte count between the source and the

target. They must agree exactly. If you find any discrepancies, recheck the tasks in the section

Copying until everything checks out.

2. If all the clients’ drive mappings are the same and are mapped identically, clients will see the

Worldox home folder exactly as before, and will not notice any difference.

3. If the clients are using mirrored files, the UNC will be different. This won’t affect desktop

users who do not work in offline mode. Users who work on their laptops in offline mode during

the server upgrade will need to manually synchronize their files to the network when they go

4. Configure your antivirus software. Exclude all Worldox xname files from scanning. If your anti-

virus software allows exclusion by extension, then exclude *.lib, *.crs,*.wat, and *.pds. Some

antivirus packages, such as Norton Corporate, let you identify exclusions on the server and

propagate them to the desktops.

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.
Powered by Zendesk