Ok, feedback confirms this as the solution (in my case at least). There were some inconsistencies with some users not been able to use Java, but in ALL those cases it was shown that multiple Java versions were present. By removing all versions except for the latest (7u7) and having the correct rule in the PM, Java works as its supposed to. Hope this helps
... View more
I'm afraid this is an age old known problem with F-Secure and I've always preferred to leave the F-Secure client off images so that I can always deploy the latest client via Group Policy on Windows AD based networks for newly created Ghost-ed machines. We created a GPO that checks a machine when it boots for the presence of F-Secure and if it doesn't have it installed, the client gets automatically deployed and then we update the MSI centrally every time a new version of the client is released. That way, we can ensure that the latest version of the client is always installed on to newly Ghost-ed machines. Also, I've found you have to be careful what you install on to a "cloned image" as any other software that uses a kind of "SID" to identify itself to a centralised management server will also exhibit a similar problem and WSUS servers are also known to exhibit this behavior. Therefore we reset the machines WSUS ID as part of the shutdown script we use when we run Sysprep on the final image, just before we Ghost the image. Hope this helps.
... View more