Outlook 2003
Hi,
I have tried the below batch file to install Outlook 2003 silently, could not succeed.
##############################################################
@Echo off
set ooo_install=%Z%\packages\outlook2003\setup.exe
todo.pl ".reboot-on 194 %ooo_install% /q"
goto exit
:exit
##############################################################
Please suggest/guide.
Thanks and Regards
Kaushal
I have tried the below batch file to install Outlook 2003 silently, could not succeed.
##############################################################
@Echo off
set ooo_install=%Z%\packages\outlook2003\setup.exe
todo.pl ".reboot-on 194 %ooo_install% /q"
goto exit
:exit
##############################################################
Please suggest/guide.
Thanks and Regards
Kaushal
0 Comments
[ + ] Show comments
Answers (10)
Please log in to answer
Posted by:
airwolf
14 years ago
Similar to my post in your other thread:
1. Are you sure your tag is correct for silent install?
2. We really can't help much without the source for todo.pl.
3. If you're installing this on Windows and using a Perl script, I assume you've got something installed in Windows to run Perl scripts...
1. Are you sure your tag is correct for silent install?
2. We really can't help much without the source for todo.pl.
3. If you're installing this on Windows and using a Perl script, I assume you've got something installed in Windows to run Perl scripts...
Posted by:
kaushalshriyan
14 years ago
Hi,
I am using http://unattended.sourceforge.net/ for automated windows deployment.
Do you want me to pastebin the todo.pl perl script ?
Thanks,
Kaushal
I am using http://unattended.sourceforge.net/ for automated windows deployment.
Do you want me to pastebin the todo.pl perl script ?
Thanks,
Kaushal
Posted by:
anonymous_9363
14 years ago
Hmmmm...two (now three!) posts detailing the same problem, a Perl script failing...I wonder if it's the command line or the script?
There is a dedicated 'Scripting' forum here on AppDeploy. I expect a moderator will move this thread there.
There is a dedicated 'Scripting' forum here on AppDeploy. I expect a moderator will move this thread there.
Posted by:
kaushalshriyan
14 years ago
Hi VBScab,
The command line options failing and not the perl script as it works fine for other applications.
Please suggest/guide
Thanks,
Kaushal
The command line options failing and not the perl script as it works fine for other applications.
Please suggest/guide
Thanks,
Kaushal
Posted by:
anonymous_9363
14 years ago
It would be wise, then, to ask simply about the command line arguments, rather than confusing the issue with Perl getting in the way.
Where does your Outlook 2003's set-up executable come from? Any incarnation of OL I've seen installs from an MSI.
Where does your Outlook 2003's set-up executable come from? Any incarnation of OL I've seen installs from an MSI.
Posted by:
Bobo
14 years ago
ORIGINAL: VBScab
It would be wise, then, to ask simply about the command line arguments, rather than confusing the issue with Perl getting in the way.
Where does your Outlook 2003's set-up executable come from? Any incarnation of OL I've seen installs from an MSI.
Actually, atleast on the Office 2003 CD there's EXE files, that Microsoft for some reason suggest you use, perhaps they like to use setup.ini.
But why someone would prefer to use the EXE file instead of the MSI I don't understand.
ORIGINAL: kaushalshriyan
The command line options failing and not the perl script as it works fine for other applications.
Please suggest/guide
Thanks,
Kaushal
Have you tried to run the command directly from command line without involving the perl script?
Have you tried to log the installation?
setup.exe /q /lv* "%temp%\Outlook(*).log"
Posted by:
pjgeutjens
14 years ago
But why someone would prefer to use the EXE file instead of the MSI I don't understand
The reason why, in the case of Office Applications, you want to use those exe's is that they are pretty much the only manageable tools to perform mass deployment. Installing Office Components based on their specific installation files (msi's) is an absolute pain in the ass and should only be done if you have severe masochistic tendencies.
PJ
Posted by:
anonymous_9363
14 years ago
For 2003, I disagree. Wave the ORK at the MSI, change your settings, save the transform, deploy. Easy.
Now, 2007...N O W you're talking PITA!
Now, 2007...N O W you're talking PITA!
Posted by:
Bobo
14 years ago
I've deployed Office 2000, XP and 2003 with ORK (CIW & CMW) and then used the MSI's, and MST's, no problemos.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.