RE: [ActiveDir] OT: Using InstallShield in a Startup Script

[Celone, Mike]

Title: Message

I did that exact thing to simulate LocalSystem context.  I created a batch file that would just create a text file on the remote null share and it works.  Also the batch file was able to copy the files from the null share to the machine in the startup script.  Thanks for the help though.   Mike From: marcus [mailto:[EMAIL PROTECTED] Sent: Friday, November 21, 2003 9:53 AM To: [EMAIL PROTECTED] Subject: RE: [ActiveDir] OT: Using InstallShield in a Startup Script Maybe I'm missing something here... but how did you simulate the LocalSystem context accessing the Null Share path to ensure that part was working?  If you decide to look at this again, I would suggest looking into that part of it... just drop a few lines to create a text file, with what process it's at:   Echo creating temp >> <path>\text.txt md c:\temp Echo creating v5r2 >> <path>\text.txt md c:\temp\V5R2 echo copying files >> blah blah blah... copy \\server\iseries\*.* c:\temp\v5r2 c:\temp\v5r2\setup -s -f1z:\iseriesv5r2.iss -f2c:\v5r2.log -SMS     From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Celone, Mike Sent: Thursday, November 20, 2003 4:02 PM To: '[EMAIL PROTECTED]' Subject: RE: [ActiveDir] OT: Using InstallShield in a Startup Script   I realized I goofed on that when I typed it earlier.  I responded back right after that with the corrected line.  My batch file does use complete paths.  I've given up already and am using psexec to do it instead.   Thanks for all the help Mike   From: Steve Rochford [mailto:[EMAIL PROTECTED] Sent: Thursday, November 20, 2003 2:17 PM To: [EMAIL PROTECTED] Subject: RE: [ActiveDir] OT: Using InstallShield in a Startup Script I'd agree with your 3) below - the reference to z:\ will fail because you've done nothing to map that drive. As douglas said, you need to use full paths -   c:\temp\v5r2\setup -s -f1\\server\iseries\v5r2.iss -f2c:\v5r2.log -SMS or c:\temp\v5r2\setup -s -f1c:\temp\v5r2.iss -f2c:\v5r2.log -SMS   should work.   I think the admin rights is irrelevant here - the startup script is running as local system - but the other thing to look out for is that "domain computers" must have read access to the folder \\server\iseries.   Steve -----Original Message----- From: Stefano Tufillaro [mailto:[EMAIL PROTECTED] Sent: 20 November 2003 13:21 To: [EMAIL PROTECTED] Subject: Re: [ActiveDir] OT: Using InstallShield in a Startup Script 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----- 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