The New LabStats - Hot Tips
Posted by ShaNeil Harada on 01 December 2015 10:12 AM
The New LabStats:
- The New LabStats is a new product built from the ground up. While it may share some features and options with previous versions of LabStats, there may be features or options that are not included in this new product. If there is a specific feature you are concerned about, please contact us to confirm if it is available.
- We are continuously working to improve the New LabStats and welcome your feedback and feature requests.
How to check if your clients are up to date:
- You can see how many of your stations are running older versions by navigating to Admin >> Settings >> Client Update Settings. The "Stations Running Old Versions" item will show a count of stations running older versions. If you click on the count it will bring up a list of those stations and show what version they are currently on.
- If you don’t want your clients to update except during certain maintenance windows, you can disable the automatic client updates on this same page.
- The AD tool available is used to create groups and assign stations to those groups according to how they are organized within AD.
- The AD tool is not used for LDAP authentication. LDAP authentication is not available at this time.
- The Viewer role can view all dashboards, stations, applications, logins, reports and alerts but cannot access any administrative functions, maps or change settings.
- The Admin role has full administrative privileges.
Deploying LabStats as part of an image:
- If you are deploying the LabStats client as part of an image, you will need to make sure the "Hostnames are unique" option is not selected by navigating to Admin >> Settings >> Client Settings >> Machine Identifications section. Make sure "Hostnames are unique" is not selected.
- Selecting "Hostnames are unique" will cause multiple machines to clump together under a single station.
- If you have done so by mistake, you will need to contact support to help you separate the machines.
- If your images contain VM software (i.e. Virtual Box or VMWare) it is possible that the virtual MAC address for these VMs will be shared across all of the clients with the same image. This could cause the machines to all be tied together into the same station.
- To avoid this, you will need to make sure the virtual MAC addresses on the master image are all listed in the ignoredMacAddresses table in the database. Please contact support for more information.
Mac Install Path Change:
- If you use file location criteria to determine if software needs to be installed, you may have previously checked for /usr/bin/LabStats*. To accommodate the changes in El Capitan, this path has changed in the latest Mac client to /usr/local/bin/.
- If you have a logout script that forces a reboot with each logout, then you may want to redirect the C:\ProgramData\LabStats folder to a thawspace using Data Igloo or mklink.
- If a reboot doesn't happen with each logout, you may still want to create the redirect, but it won't be necessary as the new LabStats infers an end of record so full records won't be lost.
- For more information see the following article.