Title: Message
1) No silent is not equal unattended.
Silent means I'm logged my session, is active with my rights, access etc.  AND I see anything.
Unattended  means that never the system ask to me an aswer by a click or a prompt or like situation.
It's a boolean serie
unattended but visible
unattended and visible
visible and attended
2) What admion rights ?
Admin domain rights? workstation rights ? RunAs Admin rights ?
The logon process not automatically give the right combination immediately and the task where live the logon scripts when will can become 'administrating' ?
3) look at at yor 4th line. Probably the error is there
c:\temp\v5r2\setup -s -f1z:\iseriesv5r2.iss -f2c:\v5r2.log -SMS
 
----- Original Message -----
Sent: Thursday, November 20, 2003 2:03 PM
Subject: RE: [ActiveDir] OT: Using InstallShield in a Startup Script

not really an expert on this, but here are two suggestions:
- Is it really a silent install (silent isn't equal to unattended) ?
- Some setups do require Admin rights/does the setup create reg keys/shortscuts in part of the profile
- Would it be a problem to run the script at logon time instead ?
 
Erik
-----Original Message-----
From: Celone, Mike [mailto:[EMAIL PROTECTED]
Sent: Wednesday, November 19, 2003 11:41 PM
To: '[EMAIL PROTECTED]'
Subject: RE: [ActiveDir] Using InstallShield in a Startup Script

I tried this and it does the same thing.  I have a script that lists all processes running on the machine and I can see setup.exe in there but it never does anything.  I'm starting to think you can't use an InstallShield installer until you are logged in.  I can see it copy the files down and the install starts but that's it.  Also InstallShield never creates the log file either.  Here's an example of the batch file:

md c:\temp
md c:\temp\V5R2
copy \\server\iseries\*.* c:\temp\v5r2
c:\temp\v5r2\setup -s -f1z:\iseriesv5r2.iss -f2c:\v5r2.log -SMS
 
Mike


From: Douglas M. Long [mailto:[EMAIL PROTECTED]
Sent: Wednesday, November 19, 2003 4:41 PM
To: [EMAIL PROTECTED]
Subject: RE: [ActiveDir] Using InstallShield in a Startup Script

If you are able to get to the share, but the script is not executing the .exe, try copying the file from the share to the local machine (in your script) and then running setup.exe. Just make sure to use full paths in all instances
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]On Behalf Of Celone, Mike
Sent: Wednesday, November 19, 2003 4:12 PM
To: '[EMAIL PROTECTED]'
Subject: [ActiveDir] Using InstallShield in a Startup Script

Has anyone ever called an InstallShield setup from a startup script before?  I have a simple batch file that calls an InstallShield setup.exe file from a startup script but it never seems to run.  The setup.exe file is on a server with a Null Share.  I've verified that the script is able to reach the file but the setup does not seem to run.  The machine I'm testing it on says "Running startup scripts" when it boots up for about 15 minutes but the setup program is never run.  If I login to the machine and run the file it works without any problems. 
 
Mike Celone
Systems Specialist
Radio Frequency Systems
v 203-630-3311 x1031
f 203-634-2027
m 203-537-2406
 

Reply via email to