The License Statistics application can use different machines, which might be in different timezones, including:
A. License server being monitored
B. License Statistics server
C. License Statistics external database
D. License Statistics client machine (device used for accessing the UI in a browser)
The following table defines the rules for differing timezones between the above components.
| Machine combination | Different timezone between machines allowed? | How timezone affects usage and monitoring data | |
|---|---|---|---|
A and B/C | Yes | Your license server may be located anywhere in the world and monitored by License Statistics users in different locations. License Statistics uses the timezone of the license server for all statistics it gathers. | |
| D and A/B/C | Yes | You can use the License Statistics UI in any timezone; however, the timezone of the license server will be used for all data shown in the UI. When License Statistics detects that your client timezone is different than your license server timezone, a message informing you of the discrepancy will display at the top of the application window. This message will persist until you either:
Note that a difference between the timezone of the client machine and the License Statistics server can lead to minor inconsistencies in the data displayed in the License Statistics UI. For example, you may see warnings that the last update time of a feature is no longer up to date, because License Statistics is constantly comparing the server/database timezone to the timezone of the client machine. | |
| B and C | No | License Statistics checks that both the License Statistics server and database have the same timezone. If they do not match, License Statistics will not run. |