thanks for the replay.
This is one of the solutions that I tried. the task can't be done manually.
I when client connecting to relevant network it's trigger a script that checking all the relevant services and registry KEYs. if everythig is fine its updating the meraki dashboard.
But I have few issues with that solution.
1. The defualt policy cannot block everthing beacuse the client needs to reach the meraki API. that meens that i need to create policy that Layer4 firewall allow port 443 and block all the rest.
layer 7 firewall will allow only access to meraki domain.
2. but the real issue in this solution is that all clients will hold the API key
3. also the api requests are limited for 5 requests per second that means that I need to create connection control.
The other solution I thought about is to create custom captive portal so clients will be redircted when they are connectig to the meraki. the client will provide that server the relevant information and this server will make the decision.
But the customer will like to avoid such solution.
Maybe there is easier way ?