- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
08-13-2026 06:52 PM
Hi everyone,
I recently set up GP user-id mapping in our network. It's showing domain.local\username in the logs. I was also told to set up User-ID mapping using the windows agent as well since our users would need to disconnect from GP occasionally. The logs that we get from the windows agent is domain\username.
Issue now is that when we set a policy, if the firewall sees that it came from domain\username it gets denied, I think it's because our group mapping uses domain.local. I checked the Group Mapping settings and saw that we have domain.local in the user domain setting. Will changing this to just the domain fix this? Will it cause downtime when this is applied? I assume once this is done, we'll only see domain\username in our logs?
Thank you
08-14-2026 12:56 AM
Hi @R.Perez481389 ,
The User Domain field tells the firewall how to format the user string when querying AD groups. Changing this to the NetBIOS name ensures that traffic identified as domain\username matches your group-based Security Policies.
When you commit and refresh, the firewall re-fetches the group details from Active Directory. This takes a few seconds. To avoid any brief policy matching blips while the group table repopulates, it is best practice to run this during a low-traffic time or minor maintenance window.
Best,
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!

