Each of the hosts used in the environment theoretically can have different timezone.
| Host | |
|---|---|
| 1 | License Server being monitored |
| 2 | License Statistics server |
| 3 | License Statistics database |
| 4 | Client machine showing License Statistics UI (browser) |
| Different timezone between | Description |
|---|---|
| 2 and 3 | It's not allowed. License Statistics verifies if both database and server has the same timezone and refuses to run the application otherwise. |
| 1 and 2/3 | It's allowed. License Statistics uses the local timezone of the license server for all statistics it gathers. |
| 4 and 2/3 | It's allowed. Customer can watch License Statistics UI in any timezone, still the date visible to him will be displayed in the timezone it was stored. The difference between the timezone of the machine you are using and the timezone of the machine on which License Statistics is installed can lead to minor inconsistencies in the data displayed in the License Statistics UI. For example, you can get information that the last update time of your feature is no longer up-to-date, because it is constantly being compared to the timezone of your browser. When the difference between the two timezones is detected, a message appears at the top of each License Statistics page. The message remains visible until you do one of the following:
|