ITAM Geolocation

Summary

Geolocation in ITAM can use OS features to pull coordinates.

Body

Geolocation in ITAM allows administrators to enable the client to pull Latitude and Longitude coordinates from the Location Services of the native Windows or MacOS system.  This feature is not available on Linux.  This article covers the basic data collection functionality.  Future development will look to add platform features that leverage this data.

This article covers the following topics:

Prior to 8.2.0.3

Some customers may have noticed foundation items for this feature and been confused by it so we offer some clarification here.  If you just want to use it as of this release skip to the next section.

  • On MacOS - The client did not have the ability to ask for location permissions.  Geolocation would only be enabled if the end user enabled it in MacOS Settings manually.
  • On Windows - The client could ask for permission but did not yet actually retrieve location data from the OS.
  • ITAM Server - As of 8.2.0.0 there was a global Audit setting to enable the feature.  However, clients could try to send the data even when this was disabled.  Additionally, the data would be stored as there was not yet a rejection check in place.

Enabling in 8.2.0.3 and later

There are 3 layers of setting for geolocation data to be collected.  All 3 MUST be enabled for the data to be collected for a given computer.  This is to ensure there are no privacy concerns from accidental collection of this information.

  • Global - In Settings -> Audits -> "Gather Geo-location from clients".  This is disabled by default.
  • Division - Right click a division on the Computers page and Edit.  "Gather location information from computers in this division".  This is enabled by default.  This allows an admin to override the global default and turn off the location collection for computers in a given division.
  • Computer - Categorization tab -> Map Availability line "Geolocation".  This is disabled by default.  This allows individual computer override of the above two options.

The server will not prompt the client to supply geolocation unless all 3 of these are enabled for a given computer.  You can bulk enable the computer option using the Quick Edit feature on the Computers page (field name is Geolocation).

Compatibility

If there are mixed client and server versions it's important to understand the impact.  We always state that any client can be used with any server, and that is true.  The shared features of the lowest version will be used in the communication.  To that end:

  • If the client is 8.2.0.3 or later but the server is older than that, the client will not send location data.
  • If the server is 8.2.0.3 or later but the client is older than that, the clients will behave with the above noted historic limitations.  The server will only save the data when the global option is enabled.  That is, the older clients will not honor the division and computer settings and send the data despite the server not asking for it, but the server will not accept it.

Development

While 8.2.0.3 is the first version fo the platform to reliably use this feature, there are no practical uses for it in ITAM as of that release.  The goal is to add tools that leverage this data in interesting ways.  Some ideas we have include:

  • Plot the location of all selected computers on a street Map set.
  • Pull up the current location of a given computer.

If you have ideas or "votes" about features related to the use of geolocation data, please submit a feature request in this portal.  Customer feedback drives our development.

Pre-approving Location Access with Group Policy Preferences

Please note the following information is generated by Claude AI and has not been fully tested by TeamDynamix for total accuracy, it has only been reviewed for technical soundness. 

Why this is needed

TeamDynamix Client 8.2 collects device geolocation as part of the hardware audit. The request is made by the per-user helper process kass.exe, which runs in the logged-in user's session and calls the Windows Location API. If Location is turned off for the device, for the user, or for desktop apps, Windows shows its location consent UI to the end user.

Pre-setting the Windows location consent state with Group Policy Preferences removes the prompt. The client itself has no preference to suppress the request; the controls are entirely on the Windows side.

Nothing else in the 8.2 Windows client produces an end-user prompt. DEX telemetry, ETW sessions, the file-system filter driver, Wi-Fi sampling and self-update all run inside the KeyAccess service (session 0) and cannot show UI. The client opens no inbound ports, so Windows Firewall never prompts. The MSI is signed, so SmartScreen is not a factor for managed deployment.

Step 0: confirm no policy is turning location off

In this GPO, or any higher-precedence GPO, confirm each of these is Not Configured or Disabled:

  • Computer Configuration > Policies > Administrative Templates > Windows Components > Location and Sensors > Turn off location
  • Same folder > Turn off location scripting
  • Same folder > Windows Location Provider > Turn off Windows Location Provider

"Turn off location" writes DisableLocation = 1 under HKLM\SOFTWARE\Policies\Microsoft\Windows\LocationAndSensors. That policy overrides every consent key below, so the preferences will have no effect while it is Enabled.

Step 1: device-wide switch (Computer side)

Computer Configuration > Preferences > Windows Settings > Registry > New > Registry Item

Field Value
Action Update
Hive HKEY_LOCAL_MACHINE
Key path SOFTWARE\Microsoft\Windows\CurrentVersion\CapabilityAccessManager\ConsentStore\location
Value name Value
Value type REG_SZ
Value data Allow

Step 2: user switch, desktop-apps switch and per-app entry (User side)

User Configuration > Preferences > Windows Settings > Registry > New > Registry Item

Create three items. All use Action Update, hive HKEY_CURRENT_USER, value name Value, type REG_SZ, data Allow. Only the key path differs.

Purpose Key path
Per-user location switch SOFTWARE\Microsoft\Windows\CurrentVersion\CapabilityAccessManager\ConsentStore\location
"Let desktop apps access your location" SOFTWARE\Microsoft\Windows\CurrentVersion\CapabilityAccessManager\ConsentStore\location\NonPackaged
Per-app entry for the TeamDynamix helper SOFTWARE\Microsoft\Windows\CurrentVersion\CapabilityAccessManager\ConsentStore\location\NonPackaged\C:#Program Files#Sassafras K2#Client#kass.exe

Per-app subkeys use # in place of each backslash in the executable path. If the client is installed somewhere other than C:\Program Files\Sassafras K2\Client\, adjust the last key path to match.

Step 3: the Location service

The Windows Location service (lfsvc) must not be Disabled. The Windows default, Manual, is correct. If a hardening baseline has set it to Disabled, add:

Computer Configuration > Preferences > Control Panel Settings > Services > New > Service

Field Value
Startup Manual
Service name lfsvc
Service action No change

Decisions to make deliberately

Enforce or seed once. With Action Update and default Common-tab settings, Group Policy re-asserts Allow at every refresh (about every 90 minutes). A user who turns location off will find it back on. If the intent is only to seed a default and let users opt out afterward, tick Apply once and do not reapply on the Common tab of each registry item. Most organisations suppressing the prompt want the enforced behaviour.

Deploy before the client. User-side preferences apply at next logon or policy refresh. Link and apply this GPO before pushing TeamDynamix Client 8.2, otherwise the first audit on some machines will prompt once before the keys exist. No restart or logoff is needed once the keys are present; the next location request honours them.

Scope it. If only some OUs run the client, use Item-level targeting on the user-side registry items (for example a security group, or a File Match on C:\Program Files\Sassafras K2\Client\kass.exe) so location is not opened up on machines that do not need it.

Verification on a client

Run these after a gpupdate /force and a fresh logon:

reg query "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\CapabilityAccessManager\ConsentStore\location" /v Value
reg query "HKCU\SOFTWARE\Microsoft\Windows\CurrentVersion\CapabilityAccessManager\ConsentStore\location" /v Value
reg query "HKCU\SOFTWARE\Microsoft\Windows\CurrentVersion\CapabilityAccessManager\ConsentStore\location\NonPackaged" /v Value
reg query "HKCU\SOFTWARE\Microsoft\Windows\CurrentVersion\CapabilityAccessManager\ConsentStore\location\NonPackaged\C:#Program Files#Sassafras K2#Client#kass.exe" /v Value

Each should return Value REG_SZ Allow.

Then trigger or wait for an audit and check the TeamDynamix Client log. A working configuration logs:

geoloc: Status = running
geoloc: Fix acquired after <n> ms.

geoloc: Status = access_denied means one of the keys is missing or a policy from Step 0 is still Enabled. geoloc: Timeout waiting for location fix with status running means consent is fine but no location provider (Wi-Fi positioning or GPS) returned a fix within 10 seconds.

Intune equivalent

  • Settings Catalog > Privacy > Let Apps Access Location = Force allow (covers the HKLM device switch).
  • The HKCU keys have no CSP. Deploy them with a user-context PowerShell script or a Proactive Remediation that writes the three HKCU values above.

Reference: registry file for lab testing

Not for production deployment; use the GPO items above. This is only to confirm behaviour on a test VM.

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\CapabilityAccessManager\ConsentStore\location]
"Value"="Allow"

[HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\CapabilityAccessManager\ConsentStore\location]
"Value"="Allow"

[HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\CapabilityAccessManager\ConsentStore\location\NonPackaged]
"Value"="Allow"

[HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\CapabilityAccessManager\ConsentStore\location\NonPackaged\C:#Program Files#Sassafras K2#Client#kass.exe]
"Value"="Allow"

MacOS Information

Unfortunately MacOS has no global management setting identified at this time, unlike other settings that can be enabled by PPPC file.  As such, each user on a given computer would be prompted by the TeamDynamix "KeyAccess" client to enable location services, and would therefore be able to deny the collection of that data.

Details

Details

Article ID: 173774
Created
Wed 11/11/26 9:33 PM
Modified
Thu 11/12/26 1:45 PM