Not sure if this is the place for this, but I'll start here. I have two MSI's that I am deploying in a mixed env of AD and Novell. The AD is simple and done through GPO. The Novell is acting up. I have a vbs that calls the shell to exec the install strings. The script executes perfectly when I test as GPO startup script in AD. In Novell, the script hangs. Has anyone seen this before? Since there are two MSI's I have two scripts. One removes the old and installs the new version. The second does the same for a different app. Because the first script hangs, the second is never called. I'm puzzled as to why this is happening.

Jimm
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
As ever, use logging to find out what's happening. Either set logging by policy or, since you're using a script, add the following to the command line: /L*V [path_to_and_name_of_log_file]

Kill the MSIExec.EXE process at the point of hanging then examine the log.
Answered 10/08/2007 by: VBScab
Red Belt

Please log in to comment
0
I'm not saying the MSI was locked. The logon script from Netware locked.

Jimm
Answered 10/09/2007 by: JimmPanik
Orange Belt

Please log in to comment
0
How would you know WHAT is locked?

The hack here would be to add logging to your script. Use the FileSystemObject to open a text file in %TEMP% (or wherever) and log each line as it executes.
Answered 10/10/2007 by: VBScab
Red Belt

Please log in to comment
0
Do you not have Zenworks on this site ?
Answered 10/11/2007 by: jmcfadyen
Fifth Degree Black Belt

Please log in to comment
0
We have ZEN installed.

I discovered that the culprit iwas the objShell.Run command. For some reason, the Netware side of things does not close the shell even though the errorlevel returned from the command I issued was sucessful. I replaced the line with objShell.Exec and it is now working. The odd thing is that this issue only occurs on the Netware attached devices. there's really no reason I can see for this but at least it is resolved.

Jimm
Answered 10/11/2007 by: JimmPanik
Orange Belt

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