birchanger Posted February 12, 2014 Posted February 12, 2014 I recently rolled out the deployment of Java 7 update 51 having, naturally, tested it and found no problems other than the minor fact that it won't let most apps run any more. I then had reports of many systems being hung with 'installing managed software - Java 7 Update 51' on the screen. I hurriedly removed the policy - so now I have many machines stuck either trying to remove Java, or stuck slightly earlier on in the boot process at 'Applying computer settings'. So, first, how have others fared with this release when deployed by GPO? And any ideas on how to recover the borked machines, other than a rebuild?
FrankJaeger Posted February 12, 2014 Posted February 12, 2014 Can't you start the machine locally in safe mode? Or has the policy been rolled out to users rather than machines?
birchanger Posted February 12, 2014 Author Posted February 12, 2014 Can't you start the machine locally in safe mode? Or has the policy been rolled out to users rather than machines? Yes, I can start in safe mode, but we have an awful lot of machines! In fact some of the machine were OK after a few restarts. We'll rebuild the others - and then try to get Java 7u51 installed.
Bradlys Posted February 12, 2014 Posted February 12, 2014 Have you got OpenGL? GLIntercept? They cause issues for me with the latest Java.
birchanger Posted February 12, 2014 Author Posted February 12, 2014 No, neither. It's annoying as we're using an identical transform as previous versions.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now