Windows User-ID agent not collecting mapping

[LucasCroce]

I'm working on getting a Windows User-ID agent set up for a customer and it's not collecting logs.  Checked all permisssions and service account user is in Event Log Readers and has permissions to both the install folder and registry entries.  Just as a test, I had the customer add the service account to the domain admins group and the user mapping started populating immediately.  Any permissions that I'm missing?  If not, what could be wrong on the AD side preventing Event Log Readers from viewing the logs? 

[OtakarKlier]

Hello,

Check out this article. My guess is something might have been missed/overlooked?

https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000Cm5bCAC

Once thing we found that worked better for us were using the Exchange logs instead. Outlook is always hitting Exchange and authenticating, so if a user moves their laptop or goes wireless, its a faster transition on the firewall side of things.

Regards,

[LucasCroce]

Went over that document already.  Nothing missed as far as I can tell.

[OtakarKlier]

Hello,

Is the service that is running the user-id agent set to run as the user/service account you setup to allow it grab logs from a DC?

Just grasping at straws, but it seems as an authentication/authorization issue.

Regards,

[LucasCroce]

You mean is the user configured in the user-id agent the same one in the "event log readers" group? Yes.  The user configured in the agent has been added to the group, is permitted to log on as a service, has rights to the PAN folder under Program Files (x86), and has rights to the PAN registry entries listed.  Like I said originally, all permissions and groups and things associated with the service account user were double and triple checked.    

EDIT: You are absolutely right though that this is an authorization issue because like I said adding the same user to Domain Admins makes it work.  I've done dozens of user-id installs before and this is the first time I've had it not work when all documented permissions where in place.

[OtakarKlier]

Hello,

Sorry for not making myself clear, I meant the windows service:

If that doesnt work, I'd say open a support case since you already went through everything.

Regards,

[LucasCroce]

Oh, I'll double check that but I'm pretty sure that is the case as the agent stops and starts correctly.  

[Mick_Ball]

doesn't this account require access to the security logs and not the event logs?  or did i misread here...?

[LucasCroce]

Misread I think.  I was talking about adding the user to the "event log readers" group as mentioned in documentation.

[Mick_Ball]

on the AD side have you matched this criteria..?

Must be a member of Event Log Readers, Server Operators, and Distributed COM.

[LucasCroce]

Yes, the user is in those groups.  

[Mick_Ball]

Hmm odd,,, i will double check mine in the morning as we have 4 agents hammering away nicely on both windoze servers and local.

are your agents on servers or local....????

[LucasCroce]

Agents installed on Windows Servers.  They connect to the firewall fine.  Services start and stop fine.  DCs are populated in the interface.  Just no user mappings.  I think I'll recommend this customer contact TAC.  

[Mick_Ball]

OK just FYI,,,  we had to add add user rights "Manage auditing and security log" to the service account for this to work but cant remember exactly why as it was a while ago...

[LucasCroce]

You mean under "User Rights Assignment" in group policy?  I already thought of that and tried it.  It didn't appear to work.  Customer opened a case yesterday.  We'll see what support says.