Bilou_Gateux
Content Type
Profiles
Forums
Events
Posts posted by Bilou_Gateux
-
-
Adobe Support Knowledgebase
Document 322064
Using a Setup.iss File for a Silent Installation of Acrobat Reader in WindowsThis record provides instructions on how to record a Setup.iss script, which you can use for a silent installation of Adobe Acrobat Reader. (A silent installation means the installer displays no interface, and all options are preselected.) Once you've recorded the Setup.iss script, you can use it in conjunction with the Acrobat Reader installer to install in 32-bit Windows operating systems (for example, Windows 98, Windows NT 4.0).
For large-scale enterprise deployment of Acrobat Reader, use the Acrobat Enterprise Installation Tool, available from Adobe's Web site at www.adobe.com/support/downloads/main.html.
Note: The Abcpy.ini file (Adobe blind copy initialization file), which enables you to customize the Acrobat Reader installer, isn't needed for these instructions. This record doesn't include instructions on how to use the Abcpy.ini file, display dialog boxes during a silent install, or access other installer applications. For information on using the Abcpy.ini file, see Related Records.
Disclaimer: Adobe Systems Incorporated provides these instructions as a courtesy, because this information is not readily available elsewhere. These instructions were not tested by Adobe Engineering, and Adobe Technical Support cannot assist with the creation of a Setup.iss script or troubleshoot issues that arise from an improperly created Setup.iss script.
Recording the Installation Process
The first step in creating the script for a silent installation is recording, or copying, the installation process you'll want to use for the silent installation:
1. Choose Start > Run, then click Browse.
2. Navigate to the Acroread folder on the Acrobat CD-ROM, select the Setup.exe file, and click Open. The pathname appears in the Run dialog box.
3. Type a space after the path in the Run line, and then type -r. For example, the pathname could appear as "C:\Acroread\Setup.exe -r". Click OK.
4. Follow the on-screen instructions, selecting the options you want to use for any silent installations, such as the location of the Acrobat Reader program files. The installer creates a Setup.iss file in the Windows folder.
Using the Script
Once you've got the Setup.iss script file that contains the recorded installation options, you can run the Acrobat installer with the script from any other computer:
1. Copy the Setup.iss file into the same folder as the Acrobat Reader installer. (If your installer is on a CD, you will have to copy the folder with the installer to your hard drive.)
2. Choose Start > Run, then click Browse.
3. Select the Setup.exe file for Acrobat Reader, and click Open. The pathname appears in the Run dialog box.
4. Type a space after the path in the Run line, and then type -s. For example, the pathname could appear as "C:\Windows\Desktop\Setup.exe -s". Click OK.
The installer installs Acrobat Reader using the options you selected while creating the Setup.iss file. You won't have to select any installation options and the installer won't display any dialog boxes indicating its progress.
0 -
Many thanks for the easy way.
Is fsutil only available in Windows XP Professional or freely downloadable on MS ?
0 -
Very interesting to avoid errors and a lot of works by doing it with this script.
One typo error to mention but doesn't matter, it's in echo command
MTUTIL.EXE should be MDUTIL.EXE ?:MDUTILERROR@ECHO Cannot find the MTUTIL.EXE file, this script requires this utility to function.
and one question ?
what's the purpose of this section
@ECHO.@ECHO Registering ASP.NET...
REM ASP.NET mappings must be registered, the easy way to do this using aspnet_regiis.exe
%WinDir%\Microsoft.NET\Framework\v1.1.4322\aspnet_regiis.exe -i
@ECHO.
@ECHO.
@ECHO IIS Should now be installed and configured correctly on this system
GOTO End
Should we install The .NET Framework version 1.1 on the W2K Server
This stuff is a component of the Microsoft Windows® operating system used to build and run Windows-based applications.
I would like not to install that stuff because it's huge and i suppose not really needed for a small IIS Server on my LAN.
0 -
After extraction of the exe with the command
rmusetup.exe /c /t:c:\temp\rmusetup
you've got an rmu.msi setup.exe and setup.ini file and MSI Installer v2 for Win9x and Win2K (Instmsia.exe and instmsiw.exe)
You should add some settings in your setup.ini(*) or another way is to launch the commands with msiexec /i rmu.msi /qb
(*)Maybe looking setup.ini file in an Office 2000 or XP CD may help you
0 -
@shotgun
Can you reply and make available your modifications to install.ins and branding.cab to disable OE install to others MSFN members.
I'm very interested to make this at installation.
The same way, i would like to disable NetMeeting installation.
The Folder for these applications are created somewhere by registry value in HKEY_LOCAL_MACHINE or HKEY_USER key.
When i change the default location of PFiles folder in the registry
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion]
"ProgramFilesDir"="C:\\Program Files"
to
"ProgramFilesDir"="D:\\Program Files"
and reboot, folders that don't exist are created in my new Path D:\Program Files
and are empty.
@AirMaleDFW
Great works, i will have a try tomorrow at works.
0 -
Another great tool to collect informations about OEM Drivers with branded computers.
source : http://www.mail-archive.com/unattended-inf...t/msg01073.html
From: Alex MagnaySubject: [unattended]Plug n play driver management
New PCs arrive at the office with XP preinstalled with all the pnp drivers we need. We have a tool to rip the drivers from the vendor's build and put them into our corporate build. We then wipe the PC and rebuild.
We make zip files, per model, containing the pnp drivers.
We can then pick the model from a DOS menu during our build. The drivers are unzipped to c: and the unattend.txt file is updated with the correct OEMPnPDriver path.
We made a tool called PnPRipper which we use to make our zip files. We run it on each new type of PC we get in the office before we wipe it to install the corporate standard build. We then copy the zip file to our build share and that's it. The build now supports the new make and model of PC. Point, click, drag drop. Easy. So the desktop engineers don't need to know how the build works. They just need to run pnpripper. No need to visit the vendor's website to download drivers one by one for intergration into your build.
Currently we have 19 zip files for 19 different makes and models of IBM Thinkpad, Compaq and HP.
Link to the tool below. Freely distributable. Do what you like with it. Includes example batch file showing how you can extract make and model info from the zip files to parse for your menu.
http://www.geocities.com/pnpripper
Regards
0 -
To obtain informations about the computer via WMI, i have found some informations on the web at the URL
http://www.microsoft.com/technet/community...s/wmimatic.mspx
and scripts at
http://www.microsoft.com/technet/community...mt/default.mpsx
witch can help to enumerates devices to build the $oem$ drivers folder.
or we can use GetSysInfo - console application providing system information
0 -
It's just what i'm looking for because many tutorials and tools already exists but they are for Windows XP.
As for my compagny, i install Windows 2000 Professional, for the moment my installations are half-automatised and not full unattended.
The W2K installation process is done by loading a base ghost image with the i386 and $oem$ folders already built and the winnt.exe /s:c:\i386 /u:c:\unattended.txt command is launched at first boot in autoexec.bat
All the others tasks are launched after installation by [guirunonce] or with keyboard input after reboot
Your program should be "open" and let the admin choose what to install.
For example, i install DirectX 8.1b on the computer and not the last version 9.0b.
see details in my applaunch.ini
I must apply the fixes depending on the version of directX installed.
see details in my applaunch.ini
at the moment, i use a freeware call applaunch.exe http://abernard.net:81/software with a ini file that contains all the install commands
Drivers,Intel® Extreme graphics driver,C:\IBMTOOLS\DRIVERS\VIDEO\INTEL\WXPW2K\setup -16x800x600x75 -s -SMSDrivers,Intel® INF installation utility,C:\IBMTOOLS\DRIVERS\CHIPSET\INTEL\setup -s -SMS
Drivers,IBM ScrollPoint II Mouse and Wheel Mouse driver,C:\ibmtools\drivers\mouse\SP2wheel\setup.exe /s /nr
Drivers,Analog Devices Inc. SoundMAX audio driver,C:\IBMTools\Drivers\audio\SoundMAX\setup -s -SMS
Drivers,Intel® PROSet,CALL C:\IBMTOOLS\DRIVERS\LAN\INTEL\PROinstall.cmd
MSFT,Microsoft DirectX 8.1,C:\IBMTOOLS\MSFT\DIRECTX8\DX81NTOP.EXE
MSFT,Microsoft Internet Explorer 6 SP1,C:\IBMTOOLS\MSFT\ie6sp1\ie6setup.exe /C:"ie6wzd /S:""#e"" /Q:A /R:N"
MSFT,Microsoft VM pour Java 5.0.3810,C:\IBMTOOLS\MSFT\JAVAVM\MSJavWU_8073687b82d41db93f4c2a04af2b34d.exe /c:"javatrig.exe /exe_install /l /qq /nowin2kcheck" /q:a /r:n
MSO9STD, Microsoft Office 2000 standard,msiexec /qb /i E:\data1.msi ADDLOCAL=ALL REBOOT=ReallySuppress NOUSERNAME=1 ALLUSERS=1 DISABLEADVTSHORTCUTS=1 PIDKEY=xxxxxxxxxxxxxxxxxxxxxxxxx
MSO9STD, Microsoft Office 2000 Service Pack 3,C:\IBMTOOLS\APPS\MSO2K\o2ksp3.exe /r:n /q /c:"msiexec /qb /p MAINSP3.msp REBOOT=ReallySuppress"
REGTWEAK,Registry Tweaks,REGEDIT /S C:\IBMWORK\SPSRCPTH.REG
SOFTWARE,Adobe Reader 6.01,C:\IBMTOOLS\APPS\AdbeRdr6\AdbeRdr60_fra_full.exe -p"-s /v\"/qn\""
SOFTWARE,Symantec pcAnywhere 10.5 Elève seulement,msiexec /i C:\IBMTOOLS\APPS\HOSTONLY\package.msi /qn
SOFTWARE,Symantec Norton AntiVirus Corporate Edition,msiexec /i C:\IBMTOOLS\APPS\NAVCECLT\navce.msi /qn
PCAUPD,Kill reboot after update process,C:\IBMWORK\pskill.exe runpcalu.exe
PCAUPD,Symantec pcAnywhere 10.5.1 update,C:\IBMTOOLS\APPS\HOSTONLY\fr_up_10.5.1.exe /s
PCAUPD,Kill reboot after update process,C:\IBMWORK\pskill.exe runpcalu.exe
WU,April 2003 Cumulative Patch for Outlook Express,C:\IBMTOOLS\MSFT\WU\q330994.exe /q /r:n
WU,February 2004 Cumulative Patch for Internet Explorer,C:\IBMTOOLS\MSFT\WU\q832894.exe /q /r:n
W2KFIXES,Critical update 329115 (MS02-050),C:\IBMTOOLS\MSFT\W2KFIXES\Windows2000-KB329115-x86-FRA.exe /u /n /z
W2KFIXES,Critical update 823182 (MS03-041),C:\IBMTOOLS\MSFT\W2KFIXES\Windows2000-KB823182-x86-FRA.EXE /u /n /z
W2KFIXES,Critical update 823559 (MS03-023),C:\IBMTOOLS\MSFT\W2KFIXES\Windows2000-KB823559-x86-FRA.EXE /u /n /z
W2KFIXES,Critical update 824105 (MS03-034),C:\IBMTOOLS\MSFT\W2KFIXES\Windows2000-KB824105-x86-FRA.EXE /u /n /z
W2KFIXES,Critical update 824141 (MS03-045),C:\IBMTOOLS\MSFT\W2KFIXES\Windows2000-KB824141-x86-FRA.EXE /u /n /z
W2KFIXES,Critical update 824146 (MS03-039),C:\IBMTOOLS\MSFT\W2KFIXES\Windows2000-KB824146-x86-FRA.EXE /u /n /z
W2KFIXES,Critical update 825119 (MS03-044),C:\IBMTOOLS\MSFT\W2KFIXES\Windows2000-KB825119-x86-FRA.EXE /u /n /z
W2KFIXES,Critical update 826232 (MS03-042),C:\IBMTOOLS\MSFT\W2KFIXES\Windows2000-KB826232-x86-FRA.EXE /u /n /z
W2KFIXES,Critical update 828035 (MS03-043),C:\IBMTOOLS\MSFT\W2KFIXES\Windows2000-KB828035-x86-FRA.EXE /passive /n /norestart
W2KFIXES,Critical update 828749 (MS03-049),C:\IBMTOOLS\MSFT\W2KFIXES\Windows2000-KB828749-x86-FRA.EXE /passive /n /norestart
W2KFIXES,Critical update 828028 (MS04-007),C:\IBMTOOLS\MSFT\W2KFIXES\Windows2000-KB828028-x86-FRA.EXE /passive /n /norestart
W2KFIXES,Critical update 814078 (MS03-008),C:\IBMTOOLS\MSFT\W2KFIXES\js56nfr.exe /q /r:n
W2KFIXES,Extra update 832483 (MS04-003),C:\IBMTOOLS\MSFT\W2KFIXES\FRN_Q832483_MDAC_x86.EXE /c:"dahotfix.exe /q /n" /q
W2KFIXES,Extra update 828026 (WMP),C:\IBMTOOLS\MSFT\W2KFIXES\WindowsMedia-Q828026-x86-FRA.EXE /passive /n /norestart
W2KFIXES,Extra update 819696 (MS03-030) (DIRECTX8),C:\IBMTOOLS\MSFT\W2KFIXES\DirectX8-KB819696-x86-FRA.exe /q:a /r:n
I have some problems with WU that requires reboot after MSFT IE6SP1 installation in order to be installed
And an other problem with InstallShield installer in Drivers.
I would like to have a great program to build the $oem$ folder and unattended.txt depending on the hardware !
0 -
Google search : outlook pst compact
OL2000: (CW) Compacting Outlook PST and OST Files
http://support.microsoft.com/default.aspx?...B;en-us;196990&
Compact and Fix Outlook's Information Files
http://www.techtv.com/callforhelp/howto/ju...3409489,00.html
Managing the Outlook PST File
http://www.zdnetindia.com/help/specials/of...ries/17533.html
I believe the third solution is the more accurate for your problem :
if you can't launch Outlook 2000 (hangs up), start at point 2. make 3. and 1. then continue 4. til 12.
0
remplacer %systemdrive%
in Application Installs
Posted
Jeff answer translated to english :
it's easy replace %systemdrive% with %cdrom%. For Office 2003, there is no SP3, only for Office XP