/build/static/layout/Breadcrumb_cap_w.png

Issue with sequencing Java 7.51

I have sequenced Java 7.51 together with some IE shortcuts using Appv 4.6 sp2.

Some users are now getting the following error:

hnz5vY.png

I always untick the Enforce Security Descriptors and I'm guessing it has something to do with UAC. Is it possible to get this to work by installing Java to the Q drive or do I have to fall back to VFS? The IE shortcuts are not desktop ones but I have created a folder under All Programs. Any help is welcome please.


0 Comments   [ + ] Show comments

Answers (3)

Posted by: apptopack 4 years ago
Red Belt
0

I don't think so. If you want to give a shot, try sequencing it with VFS with default install location.

The below link should help you.

http://packageology.com/2014/02/sequencing-java-the-definitive-guide-part-1/


Posted by: rileyz 4 years ago
Red Belt
0

Procom, I don't think this is a security issue. I think its a path issue, ie, something is referencing the exe but it can be found.

Your stating some users have this issue, so its not a problem across the board. You need to check on the problem machines for the common factor. I know java can get a bit upset if you have other version on java on the machine at the same time, so that is worth checking.

Posted by: msagredou 4 years ago
White Belt
0
All the PCs have Java 6.45 as a local install. We have an application that needs Java 7.51 to run and hence why that one is sequenced. Am I right to think that installing it to the Q drive is what is causing the issue? Should 7.51 be installed in VFS location?

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ