To install without calling setupx.exe create a folder with
and call for a quiet install (without the Nero Scout):
msiexec.exe /i "NeroSuite.msi" TRANSFORMS=1031.mst /qr ARPSYSTEMCOMPONENT=1 ALLUSERS=2 USERNAME="Username" COMPANYNAME="Company" USERSEL="6" STARTMODE="-1" FAMILYNAME="Nero 7" STARTPARAM="CallFromExe" DONOTRUNSETUPX="1" PIDKEY=xxxxxxx NERO_SCOUT="FALSE"
1."REBOOT=REALLYSUPRESS" or "/norestart" doesn't work!
To avoid reboot you should use an autoit3 script at the end of the installation.
2.On W2K I had an error with registering the Soundbox.ocx - with autoit3 I created a script which registered the ocx by calling "%System%\regsvr32.exe /i "%ProgramFilesDir%\nero\nero 7\Nero soundTrax\Soundbox.ocx"" and cancelled the error message after that; this worked fine.
Nero 7.8.5 brings some stuff along, you most probably don't want to deploy. Here is my way step by step:
1) Start Setup Package and retrieve the folder namend RarSFX0 from temp. This contains the uncompressed install files.
2) From those files simply delete the following to skip ask.com toolbar installation:
3) You <u>need</u> to create a transform to remove the Nero Scout desktop search feature. NERO_SCOUT=FALSE will NOT work! (thanks to nheim for posting this!):
- Load nero.msi in orca
- create new transform
- in SelfRegEx table, drop row MediaLibraryNSE32FE850B.dll
4) While you already have the MST open you may add your Serialnumber (serialnum_userval) to the MST, also if you set the following, you will not have the nagging eula screen upon first start:
- EULA_AGREEMENT to 1
- AgreeToLicense to Yes
5) Once you have created the mst you will need the following msi call, as those variables will not work inside an mst (note: 1031.mst only for german localization):
Use this to uninstall Nero silently and without a reboot:
msiexec /qb /x nero.msi /norestart
Note: The reg key above ("allocatecdroms"="1") will overwrite whatever is set in Nero Burning Rights. Even if NBR is set to administrator, with "allocatecdroms"="1" - all users will have access to the CD drive.
Here's how I deployed Nero 184.108.40.206 via an MSI object in ZENworks 7.0 SP1:
1.) Run the SetupX.exe file and let it get right up to the point of actually installing. This will extract all the CAB files and duplicate the ones as needed - if you don't let the setup get here some CABs will be missing.
2.) Create a transform to specify the serial key, username, and company name as indicated above.
3.) You can modify the features in the property table that you don't want installed by setting their properties to "0" as listed above. This will still leave you with Nero Scout, though. If you want to remove that, do the following:
--Drop the following components from the component table: NeroSearchHelp_ENG5122ABE3, NeroSearch_Vista09F80378, NeroSearchfiles3A144A73, and NeroSearchDllE239C0AB.
--Drop the following entries from the SelfRegEx table: MediaLibraryNSEABC8A37D.dll and NMBgMonitorB7C6977C.exe.
Running with the /qr switch (as I usually do; something interesting to look at usually) will bring up a dialog at the end of the install that (depending on what features you chose to install) asks you to configure the program options. Since I was only installing the tools and burning components, it would only ask about putting Nero apps in the autoplay menu for blank media. I don't so much care about that, so I just set the /qb! switch instead - no dialog box at the end of the install. Optionally you could remove the NeroAg_RunFileAssociationsDialog custom action from the InstallExecuteSequence table - that's the action that pops that dialog up.
Word to the wise: the installer will fail on the NeroAg_RegisterComEx custom action if DirectX 9.0c isn't installed, and it won't install in a silent install of the MSI. From a batch script you can run X:\<PathToNeroInstall>\Redist\DirectX\dxsetup.exe /silent; since I'm going through Zen I created a simple object to run this program from the server and used that object as a dependency of the main Nero object. The Nero object is an MSI object using 1033.mst and Nero.mst (or whatever you called it). You can specify properties in MSI -> Properties so that it will actually run: DONOTRUNSETUPX=1, STARTPARAM=CallFromExe, and MSISOURCEFILE=nero.msi. Finally, in the Run Options -> Application tab, set the Path to File as "C:\Program Files\Nero\Nero 7\Nero Toolkit\NeroBurnRights.exe" and the Parameters to "/all." I've had problems running this zen object as a power user; in Run Options -> Environment, you can try running as a secure user to get around those problems.
We've seen that some people have trouble with deploying Nero 220.127.116.11 using group policy. While this is a bit convoluted it is not by any means impossible.
The reason it does not work to set all the properties in the property-table is because the Nero msi contains some custom actions that run even before the property-table is evaluated. Open Nero.msi up in Orca and have a look at the InstallExecuteSequence, sort it by the "Sequence"-column. You'll see them as the four first actions starting with "NeroAg_".
To be able to deploy the msi using group policy you need to set the required properties using type 51 custom actions earlier in the sequence. The properties you need to set are already on this page, DONOTRUNSETUPX, STARTPARAM, MSISOURCEFILE and SERIALNUM_USERVAL.
Also remember to that the april 2006 update of DirectX is required before trying to deploy Nero (the latest update right now is february 2007). If not the msi will fail when trying to register some of the dlls right at the end of the installation process.
The latest version of Neros Burning ROM package have proved problomatical to silent install, they seem to have made a bit of a mess of the installation process, however the following pretty much works.
1) Run the downloaded executable to decompress the package, then go and copy it from a folder in C:\Documents and Settings\%USERNAME%\Local Settings\Temp to another location. If installing from a network or CD\DVD-ROM you will need to perform the copying part of the below batch file, however if you run it off your hard drive you shouldn't need the copying part at all.
REM Installing Nero Burning ROM
XCOPY \Nero\*.* c:\nero /E /I /Q /Y
C:\NERO\SETUPX.EXE /qn /norestart
REGEDIT /S \Nero\nero.reg
DEL /F /Q /S C:\NERO\*.*
RD /S /Q C:\NERO
The contents of the REG file are as follows...
Windows Registry Editor Version 5.00
"Serial7_1149677731"="<YOUR SERIAL NUMBER HERE>"
"User"="<YOUR USERNAME HERE>"
"Company"="<YOUR COMPANY NAME HERE>"
Personally I've had a bit of a tussle with the REG file for some reason. it is valid since if you run it by double clicking on it it works fine, however for some reason, it has not always applied correctly when running from the batch file. Maybe it needs a restart before application?
* 1033.mst is the "English - United States" LCID - use the appropriate LCID for your location and the files you downloaded.
* The ADDLOCAL entry above severly restricts which components are installed - you can make changes to the list by using InstallShield (or another similar product) to inspect the MSI and looking at the features list.
* ARPSYSTEMCOMPONENT, USERSEL, STARTMODE, STARTPARAM, and DONOTRUNSETUPX all came from previous posters
* USERNAME and COMPANYNAME should be set as appropriate
* SERIALNUM_USERVAL is a new name for the serial number (evidently used to be PIDKEY) - I figured it out by using InstallShield to inspect the dialog box where it usually gets entered
* AGREETOLICENSE was deduced by using InstallShield to inspect the licensing dialog box
* /all turns out to be the Command Line parameter for granting burn rights. The NeroBurnRights.exe parameters are (supposedly):
/group=<group_name> - enclose entire parameter in quotes if there are spaces
/sec_class - apply to future devices as well
/sec_device - apply only to existing devices
* It didn't force a reboot, but I obviously do one after everything completes
I just downloaded Nero 7 and had to get it to install and deploy it with LANDesk.
At first I had difficulty trying to use the MSI with the notes above. It turned out much easier than I expected.
I did the following:
1. Downloaded the executable.
2. Extracted it (I used winrar to extract it)
3. I went into the "Nero Install\Redist\Config" and found a conf.txt.
- I read this conf.txt and figured out how to use it.
- Put EXCLUDE instead of INCLUDE for the items not desired.
- At the bottom of the file, add MSIPROPERTY property "value" for each value you want changed. (I used ORCA to see what values were available)
4. Put the files on a package server (web share).
5. Created an Executable Distribution Package in LANDesk that runs SETUPX.EXE, has /q as the only switch, and includes everything in the Nero Install and all subfolders as additional files.
6. The install worked fine.
I struggled with Nero 18.104.22.168, you can't decompress the 100MB .EXE file and silent install from a script it screamed for a CAB file that appeared to be missing. However if you run the 100MB .EXE file then once it's decompressed itself make a copy the files from the Nero Temp Directory in <your porfile>\Local Settings\Temp. This'll sort you out. After this I use the following script in conjunction with a .REG file to register the software...