This is a known issue, defect 439468 was opened for it, and this has been fixed in 2017.3 SU1, which is currently in focused release.
This fix currently isn't being ported back to 2016.3. As a workaround, under "Computer.OS.NT Info" there will be a Release ID value. For LTSB 2016 the release ID is 1607, as opposed to 1511 for LTSB 2015. You can key off of that for querying purposes.
If you have data analytics, you could also create a rule that modifies the name to change 2015 to 2016.
Thanks for the quick reply.
That makes sense as I know we are a bit behind on the updates.
I did expect as much so I will see if I can push forward with getting our installation updated.