Hello,
i'm having an issue in one customer(it actually relates to very common problems) and i can't seem to find a solution(even when the 9.1 release notes noted some of the stuff said):
1) MAC address definition is essentially useless: It doesn't let you define a name-MAC address pair, you need to assign it to a HOST with a CERTAIN IP address, that's useless, the whole point of defining something by MAC is because i don't care/know/want to know what ip or hostname it has, it has to be L3 agnostic!, it also can't be used on app control nor web control, making it even more useless.
2) Application control granularity: on opening app control you have that nice infographic showing each group being controlled and etc, but you can only select NETWORKS not AD USERS and even less MAC DEFINITIONS, thus making app control a gimmick more than anything(as conrol should not be set by network, but by user).
So i have a group of stations(that have dynamic IP and will stay as such) in which the customer wants to restrict applications AND browsing REGARDLESS of which user is logged in.
So i thought about using the much-vaunted mac address definition to define the stations then use those definitions in app and web control, bzzz no dice, that useless host/ip definition makes it unusable.
It also can't read the station IP from active directory(i see the machine$ user network but it doesn't resolve to a usable IP).
so i'm stuck, and the functionality that should resolve these issues is broken.
ideas?
This thread was automatically locked due to age.
