Internal documentation only
This page has been marked as draft.
How to set Individual Timezone for Manage Entity
You can add a specific timezone for manage entity by creating an environment along with the active time plugin.
Please refer below:
Environment Plugin (GSE):
Create an environment in the GSE if you have already an active time with a specific timezone you can add that here.
Active Time Plugin:
You can also create an active time if you don’t have any existing, please refer above.
Manage entity Advanced settings: 
After you create the environment go to the manage entities you wish to add the environment/timezone on the advanced setting.
Lastly, if you are referring to this part below this is not changeable.
The last sample times cannot be altered since they are determined by the location of the Netprobe installation.
For instance, if the Netprobe is installed on a server in London, it will report in the London timezone. This configuration is fixed and cannot be modified.
In conclusion, the environment settings establish the sampler run times in UTC for all samplers within the managed entity, according to the active time configuration. You may adjust these settings based on your preferences.
We do have also an FAQ for single samplers please refer below: https://support.itrsgroup.com/hc/en-us/articles/115004030109-Geneos-How-do-I-use-a-single-sampler-with-different-timezones
Furthermore, you can also try setting the timezone on the netprobe directly in the startup script using the TZ environment variable like below:
For example, if using bash: export TZ=America/Mexico_City
This is possible to get this to work on a netprobe server running in EST and with this setting the lastModificationTime in the FKM dataview is reflecting correctly using the TZ defined timezone.