PENDING AppEnforce and AppDiscovery Not Created with Client Re-Install

[Garren10]

Hello all,

We recently have had an issue with our site where it seems like 1/3 of our PC show in deployments as gray "Client check passed/Active" and will not receive any deployments. Powershell scripts that are sent out still seem to work correctly. If I go to re-install the client, everything seems to get re-built correctly but the AppEnforce and AppDiscovery logs do not re-appear. Since this started, we actually stood up a new environment and started testing with machines, only for the issue to re-appear and cause issues. Any ideas what could cause this issue?

 

[Garth]

Hello all,

We recently have had an issue with our site where it seems like 1/3 of our PC show in deployments as gray "Client check passed/Active" and will not receive any deployments. Powershell scripts that are sent out still seem to work correctly. If I go to re-install the client, everything seems to get re-built correctly but the AppEnforce and AppDiscovery logs do not re-appear. Since this started, we actually stood up a new environment and started testing with machines, only for the issue to re-appear and cause issues. Any ideas what could cause this issue?

Are you only using IP ranges for boundaries? Is hardware inventory and heartbeat discovery working?

 

[Garren10]

Both of those are working with no issues, and we're using AD sites for the boundaries.

 

[Garth]

Ip ranges is the only boundary type that is 100% correct all the time. What exact do you mean by they are working? Why do you think they are working?