Thanks there were no disacards when i looked but in the end ive got the chrome update working, but then there was a knock on effect with normal web sites being blocked because of the url filtering profile i had applied. My original aim was to have our normal web access policies to 3 different AD groups (so 2 rules per group) which would block exe, msi, pe etc but above these rules i would have one rule that has the 3 different AD groups in that would allow exe, msi and pe files to a select group of sites in a another url filtering profile to update the like of adobe reader/creative cloud, chrome, visual studio etc. After doing some more tests and a call with PA support, it seems this is not possible, so now im back to square one. What i am now thinking is adding an extra rule for each web access group. At the moment our setup is something like the below. Web access full AD group - zone outside - web access full allowed apps - application -default service - Web access full URL filtering & file blocking profile Web access full AD group - zone outside - allowed apps decrypt to other ports - custom ports service - Web access full URL filtering & file blocking profile What i propose to do is the following Web access full AD group - zone outside - any application - any service - web access full URL filtering with approved category & file blocking profile allowing EXE & PE file types Web access full AD group - zone outside - web access full allowed apps - application -default service - Web access full URL filtering & file blocking profile Web access full AD group - zone outside - allowed apps decrypt to other ports - custom ports service - Web access full URL filtering & file blocking profile but now i have just typed that out i dont think that will work as the first rule would allow all applications so the other rules wouldnt really come into place I think i need a break from this and come back to it with a fresh head lol
... View more