Making a Group Assignment Rule with AD Groups doesn't work for me.
I have added client PC's to a group in AD, then in EMS I've matched that AD Group with a Group created for endpoints, which is then used in Endpoint policy, which again uses the Endpoint Profile, than is handling the deployment of the install package. Sorry if this sounds a little weird, but I'm still trying to wrap my head around the terminology to explain things. The point is - the client PC's that are in that AD group do not show up in the Endpoint group defined in EMS - thus, the client PC does not get deployed with the install package. What can be the cause of this? I don't want to manually add new PC's that are introduced to the AD - as long as it's in the right AD Group it should get the FortiClient deployed...
Nominating a forum post submits a request to create a new Knowledge Article based on the forum post topic. Please ensure your nomination includes a solution within the reply.
Select Forum Responses to become Knowledge Articles!
Select the “Nominate to Knowledge Base” button to recommend a forum post to become a knowledge article.
User | Count |
---|---|
1645 | |
1070 | |
751 | |
443 | |
210 |
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2024 Fortinet, Inc. All Rights Reserved.