WMS - Configure Default Policy

The WMS policies work using inheritance.

The top-level group is the Default Policy Group. This will be configured with options that will apply to all stores.

Table of Contents

Open your browser and navigate to the WMS and click on the Groups & Configs tab:

You will want to change the group key (right side of the screen). The default for older versions of WMS is ‘defa-defadefa’.

Scroll down, and you will see the available settings.

NOTE: this document will contain only changes from the defaults.

General Settings (8.5+)

Configure the options as listed above. Setting the Terminal Name to $DNS means that the terminal name will be set to it’s name within the DNS server. If there is no PTR record, then the name will need to be set in the Devices tab. (See other guide).

General Settings

  • Update the User Name and password. This is for logging into the device itself, but is not used in our environment, so change it from the default.

  • Set the timezone as appropriate

Security

In the top half of these settings, set up an administrator username and password that are different than the defaults. This account will be used to open up the ‘admin mode’ of the device for troubleshooting and viewing the logs, configured IP address, etc.

  1. Set the Security Policy to warning. This allows remote connections when the SSL certs are self-signed.

  2. Enable VNC and set a password. This allows the IT group to do remote troubleshooting on the devices.

  3. Disable the WDM service, as we use only the WMS service.

Display

  1. Make sure to force the number of monitors to a ‘Single monitor’. Some devices incorrectly discover a second monitor on a second VGA interface, which causes the login screen to be out of range. If you have a store or device with multiple monitors, you can change this at the Store or Device level.

Visual Experience

  1. Set the background color to something that matches your company logo or other plain color.

  2. Use the Zero Launchpad

  3. Allow the Wyse toolbar to be used. This toolbar has buttons to restart the RDP session or go into admin mode.

  4. Require the mouse to be in the left margin for 2 (or more) seconds before popping up.

Firmware Upgrade

This will vary per client. In this example, the site has 5010 and 3040 units. The firmware in use is 8.6_024. Older units will upgrade to this firmware when booted.

Direct RDP Connections

We will set up a direct RDP connection to the AMI Terminal Server:

  • The HostName or IP Address is the address of the AMI Terminal server

  • UserName for logging into the AMI Terminal Server is $TN, which is this terminal name. Typically, these names will be something like 001Pricing2, which maps to Store=001, Pricing Station=2. These logins are set up by the AMI Administrators beforehand.

  • The Doman Name is AMI for hosted services. For on-prem servers, ask the AMI Administrators.

  • AutoStart 5 - start up the RDP session 5 seconds after boot.

  • Make sure Map Serials is on to map the scanner and keyboard.

Save

After making changes, make sure to click the ‘Save & Publish’.

NOTE: certain changes may cause the remote units to reboot with the new information.