trying to rollout Java with active directory

used Orca to change "Iexplorer=1", but still got a problem with Rollout.
the installating takes only 12 sec. and then the installation stops, and every time the comp. reboots he is trying to install the package again, bud Java doint make a Installation log file.

somebody nows how to get a log file so i can check whats going wrong
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
Hi omnifred,

Try to use msiexec.exe /i <Path to MSI> /L*V <Path to where the log file be created (EX: C:\Log\java.log)>

Hope this helps,
knight
Answered 09/27/2006 by: knight
Orange Senior Belt

Please log in to comment
0
Thanks Knight,

bud i found that also, i only have the problem with deploing with Active Directory.
if i install the MSI by hand then it installs perfectly.
Answered 09/27/2006 by: omnifred
Yellow Belt

Please log in to comment
0
Try to see the application event viewer why java is installing itself again.
Answered 09/27/2006 by: knight
Orange Senior Belt

Please log in to comment
0
The event viewer doint show the problem.

found something

activate the logging policy for windows installer on MSI files in "Computer Configuration / administrative templates / windows components / windows installer /


gona try this
Answered 09/27/2006 by: omnifred
Yellow Belt

Please log in to comment
0
Hi Fred,
be aware that the logs for a machine GPO install go to 'systemroot\temp'.
Regards, Nick
Answered 09/27/2006 by: nheim
Tenth Degree Black Belt

Please log in to comment
0
I think you meant "%windir%\temp" as the installation is run under the system context using machine GPO.
Answered 09/27/2006 by: AngelD
Red Belt

Please log in to comment
0
Hi AngelD,
%systemroot% and %windir% resolve to the same path on every machine i know. But i forgot te percent symbols.
Regards, Nick
Answered 09/28/2006 by: nheim
Tenth Degree Black Belt

Please log in to comment
0
Found the prob. in the log file, little bit silly.

the person (college) whoem deployd the package, didnt use a UNC Path :-(

beginners error !!!!

sorry had to bother you people with this (bud nice to find out about the policy setting for logging MSI installations)


Thanks
Answered 09/28/2006 by: omnifred
Yellow Belt

Please log in to comment
Answer this question or Comment on this question for clarity