XMS

Performing a Silent Install for ALS

Are you an IT administrator needing to perform a silent install of GMS, SMS, or WMS in a classroom or office? We have gone over the process to do this in the past. However, our licensing methods have changed since those instructions were first written. Because of this, we have felt it would be useful to update our users on the new method of configuration so they will be able to properly set up their silent installs. This post will review registration for the new licensing method and how to perform silent installs with it.

This silent install (or quiet install) workaround requires each user to have the rights to modify the registry. If registry access is restricted, a network administrator can do this by opening the Group Policy Management Editor and creating a startup script that automatically runs the batch file whenever the computer is restarted.

Note: Editing the Registry in Windows is a very advanced administration step. Please always create a backup of the Registry before making changes.

It can be a burden to manually update the local code in HKEY_CURRENT_USER for each user on each computer. The silent install process is simplified by creating a Windows Registry file that contains the license information and a batch file that can be executed to insert the registry information and launch WMS. The batch file automatically updates the registry for the user and then opens the WMS application. This is the safest way to edit the registry key, as well. The batch file can then be placed on each computer that needs to be updated, and the individual users can execute it as needed.

This workaround uses WMS as an example. This information also applies to GMS and SMS. You can see an example of a registry file in step 1 and the batch file in step 2, below.

  1. Create a file, "Netenble.001.reg", as follows:
    Windows Registry Editor Version 5.00M
    "ALS"="1"
    "ALSHost"="127.0.0.1"
    "ALSPort"="56789"

    ALS = 1 specifies the new registration wizard, with new "Local" codes beginning with L, F, or E, instead of 0 for the old network lock. ALSHost = 127.0.0.1 because the code is being located on the local machine. And ALSPort = 56789 should be the default - you can alternatively specify your own port if you would like. You could also specify an ALSCode (license code) as well if you don’t want registration to be required when first launching WMS.
    Note: This information was created using Windows 10. Because different Windows versions can have different REG file formats, we recommend you install WMS on one machine, register it to the correct local code, then export the registry key. Open the registry file in the text editor and remove every line except those similar to those shown in the image above, and save the file as "Netenble.001.reg".
  2. Create a file, "wms11.bat", that will update the registry and start WMS:
    reg import Netenble.001.reg
    wms.exe
  3. Place these two files in the WMS folder in the image that will be distributed to the affected computers. For example, for the 64-bit version of WMS 11.1, the default location for the folder is “C:\Program Files\WMS 11.1 64-bit\”.
  4. Create a desktop shortcut to the batch file for the convenience of the user. If doing this via a startup script in the Group Policy Management Editor, this step can be skipped.

This silent install workaround can save you significant time as a network administrator. If you experience issues while performing a silent install, feel free to contact Aquaveo for assistance.

Troubleshooting Model Executables

GMS, SMS, and WMS (collectively known as XMS) all make use of numerical models for the final simulation run. These numerical models include MODFLOW, ADCIRC, SRH-2D, GSSHA, HEC-RAS, etc. These numerical models are not developed by Aquaveo, but the XMS software does provide an interface for using these models. This article will discuss more about how the XMS software integrates with these numerical models.

XMS will allow you to import all of the starting data and define all the parameters for a numerical model simulation. After the project has been built in XMS, XMS will export all of the files needed for the model run. XMS will then access the numeric model executable and launch the numerical model to run your simulation.

If the numerical model fails to run, there sometimes can be an issue with the numerical model executable. Typically, you will receive a warning message stating the model executable can’t be found. When this happens there are two ways to resolve the conflict.

The first is to click the browse button on the warning dialog and browse to the location of the model executable. Select the model executable and simulation will start running. In most cases, the model executables are located in a folder called models located in the locations where the XMS software has been installed.

The second method is to make certain the path to the model executable location has been correctly in XMS. This is done by going the Preferences dialog (use the Edit | Preferences command). In the Preferences dialog, there is a tab call either Files or File Locations. On the Files tab is a list of the available numerical models and where XMS is accessing that executable for the model. From here, you can change the file path to point to the correct location of the model executable.

File Locations tab in the Preferences dialog

Often when the model executable cannot be found the cause is one of a few common issues. One is that the path location was not correctly set when XMS was installed. Another is that the numerical model was not installed correctly. And another is that you may have been using a custom installation of the numerical model software with the model executable in a location where XMS is not looking.

Also note that some numerical models require multiple executables. Often this is a pre-processor that has its own executable. Make certain that the file path is correct for all executables used by the numerical model.

Making certain the correct model executable can be found by XMS can make running your model simulation a lot easier. Check out all the available numerical models availing in XMS today!

Blog tags: 

Understanding Projections vs. Reproject

Have you ever wondered what the difference between projection and reprojection is? Have you ever needed to convert a projection from one type to another in GMS, SMS, or WMS (collectively known as XMS)? The use of projections in WMS can be confusing, so the following should provide further clarification.

Specifying Projections

Projections can be associated with individual data objects, either in the object data file itself or in an associated *.prj file. If XMS cannot find a projection, the object will be left as "no projection," or, when new objects are created, XMS will assign the display projection to it. You can specify an object's projection by right-clicking on it and selecting Projection. Note that this projection must be the same as the original projection of the data; specifying an incorrect projection will result in data issues.

Reprojecting on the Fly

"Reprojecting on the Fly" occurs when datasets or objects from multiple projections are loaded into a project, where the x and y values would not otherwise overlap (i.e., the data would be displayed in two or more distinct locations). The different projections for these data will be "reprojected on the fly" to match the display projection such that the data objects will line up. Note that this does not change any *.prj files or the projections that are set for each object; it is an automatic function internal to XMS used for display purposes.

Converting a Projection

If you need to convert from one projection to another, this can be done by right-clicking on it and choosing Reproject. To use this command, the data must first have the correct projection specified. After choosing Reproject, the command will prompt the user to select a new projection, the data will be converted to the selected projection. If a *.prj file is associated with the object (such as a TIFF), reprojecting the object will change the *.prj file. Reprojection on the fly is usually sufficient for most applications. Please note that there are some limitations for reprojecting.

Reporject Dialog Example

Once the datasets are referencing their projection correctly, XMS should reproject them on the fly to match your display projection. If you don't have a display projection set, you can do so by selecting the Display menu and choosing Projection. At that point, if you would like to reproject your scatter(s) into the same projection as the display projection, you would be able to do so.

Now that you see the differences between projection vs. reproject try them out in XMS today!

Blog tags: