Joe User 99

I don't have the retail app, but if it is similar to the PhotoShop Album 2.0 "Starter Edition", it extracts to a MSI. That uses the standard MSI switches. Launch the install to the point it reaches the first dialog box, then check your temp folder for any newly created folders, see if there is a MSI there. Then you can use that with the /qn switches, etc.

I ran the setup to the point where the first dialog appears. Then I opened up windows explorer and browsed to my temp folder and there located the extracted temp files, including the iTunes.msi. I then used my copy of Wise Package Studio to open the msi and have a look around. Found those in the Property table. But I also checked for custom actions, etc. I noticed there were no settings related registry settings, so I guessed there must be a config file, and just looked in the user profile\Application Data folder, as it is a default for such things.

I don't think you can customize settings from the install. The settings appear to be stored in a file called iTunes.pref in the <userprofile>\Application Data\Apple Computer\iTunes folder. But I imagine you could set up iTunes on a system, copy that file off and push it after install, and it would probably work. As far as settings from the install. The only ones I noticed off hand were ASSUME_MEDIA_DEFAULTS, which I think corresponds to the dialog option to set iTunes as the default audio player. ASSUME_QT_DEFAULTS, which I think corresponds to the dialog option to set QuickTime as the default media player. and INSTALL_DESKTOP_SHORTCUTS, which I think corresponds to the dialog option to create desktop shortcuts. These should all be useable in the commandline, after the /v to be passed to msiexec. There may be others, but that is all I noticed on a quick look.

It's a setup.exe that is calling a MSI file. /L Language ID is what language to use. /S Hide initialization doalog. For silent mode: /S /v /qn The /S hides the Setup.exe dialogs the /v passes subsequent switches to msiexec /qn tells msiexec to be silent. /UA<url to InstMsiA.exe> this is the path to the win9x Windows installer update /UW<urll to InstMsiW.exe> this is the path to the Win2k XP windows installer update these are only for updating systems that need a newer Windows installer. It is not needed if they are up to date. The language identifiers allow you to quickly tell which language file you need for the setup to be a particular language. For example, For Setup.exe to run in Chinese (Traditional) 1028 0404 you would use the 0x0404.ini (switch is like MCT demonstrated above.) There are usually coresponding .mst files for MSIs. So if iTunes is passing it's switchs to msiexec, it means it should be extracting a MSI based install to a temp folder, which means you could just grab that fileset and use the standard MSI switches, rather than go through the bother of these.

Where it says could not write value Model to key... It is trying to write the mouse model, as selected in the dialog, to the registry. This needs to be set (its a property set via a custom action.) Here at work, most of our systems use the same model mouse, so I just pre set it in a transform. but here are the values I pulled out of the MSI for various models: Wireless IntelliMouse Explorer 2.0 (With Tilt Wheel) = 16 Wireless Optical Mouse 2.0 (With Tilt Wheel) =15 IntelliMouse Explorer 4.0 (With Tilt Wheel) = 14 Basic Optical Mouse = 13 * No 12 listed * Optical Mouse = 11 Wireless Optical Mouse = 10 Wireless Wheel Mouse = 9 Wireless IntelliMouse Explorer = 8 Wheel Mouse Optical = 7 Trackball Optical = 6 Trackball Explorer = 5 IntelliMouse Web = 4 IntelliMouse Optical = 3 IntelliMouse Explorer = 2 Microsoft Mouse = 1 IntelliMouse = 0 This HAS to be set. Now I said I added it into a transform, but you could probably just add a public property for it to the property table of the MSI, that would allow you to set it from the command line. The property MM is being set via a custom action right now, but there shoudn't be any reason you couldn't add MM to the property table, then just add that as a commandline option like so: IP50.msi MM=3 (This probably wouldn't work by default, you would have to modify the property table.) Let me know if you need more help.

To install MSN 6.2 with the MSN Toolbar, but without setting MSN as your default homepage, and without launching Messenger at the completion of setup, use my custom transform file and the following command line: start /wait %systemdrive%\install\Applications\MSN\MsnMsgs.msi TRANSFORMS=CustomMSNMsgr62.mst SEMISILENT="Yes" LAUNCHMSGR="No" /QB Now, the install still launches IE when it completes, so you will have to use something like: process -k iexplore.exe 10 to kill the IE window when it opens. Hope this helps...it's been a while since I messed with this.

I did notice in that document that it mentions that the /P:#e is not needed for WMP10, but that is the only mention of 10 that I see. Oh well....I guess we all will keep looking....

I got that too, if I ran it from a commandline from outside the source directory.If I changed to the source folder, then ran it, it seemed to work better. I think that is for 9.0, cause for 10, I still get the EULA dialog even using these commandlines. If you notice the exe name is different too. For 10, it is MP10Setup.exe, not MPSetup.exe

I don't have switches, but here is what I am playing with so far: Use WinRAR to extract the MP10Setup.exe to a folder. Inside will be all the source files Deleting Eula.txt will bypass the EULA screen and start installing automatically. Problem is that Eulat.txt is required to install (It is copied during install.) So delete the line "eula.txt" from the [V9Copy.Core] section of WMP10.INF and save the file. Then try installing by running "setup_wm.exe" I can't get it to work on a SP2 system, I get a "This program has not passed Windows Logo Certification..." error. But I don't have a SP1 system to try the results on.

Check my post in following thread: http://www.msfn.org/board/index.php?showtopic=18301&st=10

Download and use the Internet Explorer Administration Kit to create a flat install. It will allow you to customize IE, add post reboot patches (which it will stick in RunOnce for you, and select an option that allows the post reboot portion to complete without admin rights.

4.51 SP1, as in the Corporate version? If so, when you license the corporate version, you also get a license for the Installation Designer. If this is the case, go to the Download Upgrades page at NAI and download the Installation Designer (1.1.0 for VirusScan 4.51) https://secure.nai.com/us/forms/downloads/upgrades/login.asp (You will need your Corprorate Grant Number. Usually begins with NAI-) It is a MSI builder for McAfee. It will allow you to set all the options, update the dats, scan engine, add any hotfix files, patches, etc, then it will recompile it all back into a MSI. That way you can preinstall all the updates in 1 MSI.

.NET can be extracted to a MSI, then use the /qn switch

Corporate version of XP Pro? I think this is default. Go into gpedit.msc. It's in there. I don't remember off hand, but I think it's something like Computer configuration/Security Settings/Local Policies/User Rights Assignment/Access the computer from the network. Add guests or everyone and restart. If that's not it, is somewhere in there. Check, Deny logon locally, etc.

I can't say for sure, since I don't own the product....but I've seen similar things from other products. The correct names are held in a transform (MST), did one come with the product? Usually, it would be a different one for each language. Such as 1033.mst, etc. Installing with the proper transform would correct the problem. Such as "productinstall.msi TRANSFORMS=transformname.MST" Hope this helps.

Build a custom IE install using the IEAK ( http://www.microsoft.com/windows/ieak/down...k6/ieak6sp1.asp ) It has an option to allow the install to complete without admin rights after the reboot.

After all this, we still don't know exactly what is not happening. Is it running, but failing? Or not running at all? If it is running and failing, maybe you grabbed the wrong version of the patch. If you notice, most other people who posted their list are installing q837009.exe, where your list shows KB837009.exe There is a seperate one for each version of Outlook Express. One for 5.5 SP2, one for 6.0, one for 6.0 SP1, etc, etc. Since you have it set to silent, you wouldn't see any errors saying it was the wrong version. Try running through without the silent switch for that patch and see if it gives an error.

Ok...this is from my AutoIT 3 script. There is nothing special about it, and I'm sure you could just call the regsrv32 commands from any .cmd file. And import a reg file to delete the keys that MDAC adds during it's install. The autoIT script is pretty easy, and compiles to a .exe, so it's easy to add on to a install. Give it a try and let me know how it turns out. ;;- MDAC 2.8 must register DLL's after reboot. Cannot do this as restricted user, so we are ; doing it prior to reboot, by hand.;;- Here we are deleting the keys added by MDAC 2.8 Install.RegDelete ("HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnceEx\800")RegDelete ("HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnceEx\801")RegDelete ("HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnceEx\802")RegDelete ("HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnceEx\990");;- Here we are running them now, rather than at reboot.;;------ From Key 800RunWait('C:\WINNT\System32\Regsvr32.exe "C:\Program Files\Common Files\System\ADO\msado15.dll" /s',"",@SW_HIDE)RunWait('C:\WINNT\System32\Regsvr32.exe "C:\Program Files\Common Files\System\ADO\msador15.dll" /s',"",@SW_HIDE)RunWait('C:\WINNT\System32\Regsvr32.exe "C:\Program Files\Common Files\System\ADO\msadrh15.dll" /s',"",@SW_HIDE)RunWait('C:\WINNT\System32\Regsvr32.exe "C:\Program Files\Common Files\System\ADO\msadomd.dll" /s',"",@SW_HIDE)RunWait('C:\WINNT\System32\Regsvr32.exe "C:\Program Files\Common Files\System\ADO\msadox.dll" /s',"",@SW_HIDE)RunWait('C:\WINNT\System32\Regsvr32.exe "C:\Program Files\Common Files\System\ADO\msjro.dll" /s',"",@SW_HIDE)RunWait('C:\WINNT\System32\Regsvr32.exe "C:\Program Files\Common Files\System\MSADC\msadce.dll" /s',"",@SW_HIDE)RunWait('C:\WINNT\System32\Regsvr32.exe "C:\Program Files\Common Files\System\MSADC\msadcf.dll" /s',"",@SW_HIDE)RunWait('C:\WINNT\System32\Regsvr32.exe "C:\Program Files\Common Files\System\MSADC\msadco.dll" /s',"",@SW_HIDE)RunWait('C:\WINNT\System32\Regsvr32.exe "C:\Program Files\Common Files\System\MSADC\msadds.dll" /s',"",@SW_HIDE)RunWait('C:\WINNT\System32\Regsvr32.exe "C:\Program Files\Common Files\System\MSADC\msdaprst.dll" /s',"",@SW_HIDE)RunWait('C:\WINNT\System32\Regsvr32.exe "C:\Program Files\Common Files\System\MSADC\msdarem.dll" /s',"",@SW_HIDE)RunWait('C:\WINNT\System32\Regsvr32.exe "C:\Program Files\Common Files\System\MSADC\msdfmap.dll" /s',"",@SW_HIDE)RunWait('C:\WINNT\System32\Regsvr32.exe "C:\Program Files\Common Files\System\OLE DB\oledb32.dll" /s',"",@SW_HIDE)RunWait('C:\WINNT\System32\Regsvr32.exe "C:\Program Files\Common Files\System\OLE DB\msxactps.dll" /s',"",@SW_HIDE)RunWait('C:\WINNT\System32\Regsvr32.exe "C:\Program Files\Common Files\System\OLE DB\msdaenum.dll" /s',"",@SW_HIDE)RunWait('C:\WINNT\System32\Regsvr32.exe "C:\Program Files\Common Files\System\OLE DB\msdaurl.dll" /s',"",@SW_HIDE)RunWait('C:\WINNT\System32\Regsvr32.exe "C:\Program Files\Common Files\System\OLE DB\msdatt.dll" /s',"",@SW_HIDE)RunWait('C:\WINNT\System32\Regsvr32.exe "C:\Program Files\Common Files\System\OLE DB\msdasql.dll" /s',"",@SW_HIDE)RunWait('C:\WINNT\System32\Regsvr32.exe "C:\Program Files\Common Files\System\OLE DB\msdaosp.dll" /s',"",@SW_HIDE)RunWait('C:\WINNT\System32\Regsvr32.exe "C:\Program Files\Common Files\System\OLE DB\msdaora.dll" /s',"",@SW_HIDE)RunWait('C:\WINNT\System32\Regsvr32.exe "C:\Program Files\Common Files\System\OLE DB\msdaps.dll" /s',"",@SW_HIDE);;------ From Key 801RunWait('C:\WINNT\System32\Regsvr32.exe "C:\Program Files\Common Files\System\OLE DB\sqlxmlx.dll" /s',"",@SW_HIDE);;------ From Key 802RunWait('C:\WINNT\System32\Regsvr32.exe "C:\Program Files\Common Files\System\OLE DB\sqloledb.dll" /s',"",@SW_HIDE);;------ From Key 990RunWait("C:\WINNT\System32\rundll32.exe shell32.dll,Control_FillCache_RunDLL","",@SW_HIDE);;- Here we clean up the MDAC 2.8 install. MS's Component Checker shows a few loose ends not fixed by the above entries,; So we will change them here to complete a full clean MDAC 2.8 install.\RegWrite("HKEY_LOCAL_MACHINE\SOFTWARE\Classes\ADODB.Command\CurVer", "", "REG_SZ", "ADODB.Command.2.80")RegWrite("HKEY_LOCAL_MACHINE\SOFTWARE\Classes\ADODB.Connection\CurVer", "", "REG_SZ", "ADODB.Connection.2.80")RegWrite("HKEY_LOCAL_MACHINE\SOFTWARE\Classes\ADODB.Error\CurVer", "", "REG_SZ", "ADODB.Error.2.80")RegWrite("HKEY_LOCAL_MACHINE\SOFTWARE\Classes\ADODB.ErrorLookup\CurVer", "", "REG_SZ", "ADODB.ErrorLookup.2.80")RegWrite("HKEY_LOCAL_MACHINE\SOFTWARE\Classes\ADODB.Parameter\CurVer", "", "REG_SZ", "ADODB.Parameter.2.80")RegWrite("HKEY_LOCAL_MACHINE\SOFTWARE\Classes\ADODB.Recordset\CurVer", "", "REG_SZ", "ADODB.Recordset.2.80")RegWrite("HKEY_LOCAL_MACHINE\SOFTWARE\Classes\ADOR.Recordset\CurVer", "", "REG_SZ", "ADOR.Recordset.2.80")RegWrite("HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Interface\{0000054E-0000-0010-8000-00AA006D2EA4}", "", "REG_SZ", "Command25");;- For some reason, our unattended installs all the files and our regsvr32 lines up above register everyting; correctly, but it doesn't add the version to the registry, so we will add it here.RegWrite("HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\DataAccess", "FullInstallVer", "REG_SZ", "2.80.1022.3")RegWrite("HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\DataAccess", "Version", "REG_SZ", "2.80.1022.3");Sleep(2000);;------------------------------------------------------; Now that MDAC 2.8 is taken care of, we will install the Feb. 2004 MDAC Hotfix.;Install MDAC Security Hotfix (MS04-003)RunWait('C:\WINNT\Temp\w2khotfixes\Q832483.EXE /C:"dahotfix.exe /q /n" /q',"",@SW_HIDE);------------------------------------------------------

How does that affect : [11:29:03]: An error occurred while setup was trying to verify the version of Microsoft Data Access Components current installed on the machine.Either the version currently installed does not match the version of this hotfix package, or setup was unable to determine the version currently installed.?

Hmmmm..... Adobe says they don't support an admin install of 6. I don't have my 6.0 pro cd here. But if I get the chance I will look at the MSI and see what it may be missing. If they did not set it up for admin install, maybe it could be modified to support it. Other than that...I guess you are taking the best approach.

We deployed this here at work, along with some others, and here is what I ran into. The patch will choke if it cannot figure out what version of MDAC is installed, or if it is not the correct version. What we did is install MDAC 2.8, but it requires a reboot before the patch will realize it is there. So I used AutoIT to perform the actions it was doing on reboot during the unattended install, and that works ok, the patch then sees that it is MDAC 2.8 and installs ok. If this sounds like what the problem is, let me know and I will post the AutoIT script I used. (These actions can be taken without AutoIT also if needed.)

Frank, If you are installing from DVD, I figure space is less of an issue for you. So, why not create and Admin install of Acrobat, then apply the patch to the admin install, then move the admin install to your DVD and install from that instead? Saves the step of installing the patch during setup. (Yes, the files would be uncompressed, and probably take up more space this way, but it's just a suggestion.)

Unfortunately, the MSN Toolbar installer's switches are not documented , and I have only found a limted number of them. So there is only so unattended it will get. If you look in the application switches thread to my MSN Toolbar switches, the closest you can get to unattended is the "j" switch. This is included in my transform if you use the SEMISILENT="Yes" switch. (And actually, this is more unattended than offered by either the MSN Messenger installer, or the standalone MSN Toolbar installer.) So it would be MsnMsgs.msi TRANSFORMS=CustomMSNMsgr62.mst SEMISILENT="Yes" /QB That should go completely through unattended and at the end, it will launch IE to the MSN Toolbar's "Get Started" page. Without knowing any other switches for MSN Toolbar to make it completely silent, and NOT launch IE at the end, this is the best we can do.

Ok..... Since it wouldn't be legal to post a modified MSI, I went the other way and created a Transform file to be used in conjunction with the original MSI. Here is what I have changed. (First, you should read my previous posts, as I am not going to go back and explain the reasons for creating the transform; I am only going to explain how to use it.) I have not found any additional command line switches for MSN Toolbar other than the ones I posted previously, so we are still kind of stuck with a semi silent install if you want the toolbar installed. Using the MSN Messenger 6.2 as a baseline, I have created a transform which changes the following: The default MSN Messenger 6.2 MSI installs the MSN Toolbar via a series of custom actions called from the Finish Button of the install dialogs. The particular action is selected via a series of checkboxes during install, and public properties. Since these dialogs are not presented during a unattended install, these actions are not run. Normally, the custom actions would be sequenced along with the other install commands, however these are not. What I have done is add them into the normal install sequence, and added install conditions to match the ones listed in the "Finish" button. In addition to this, I added the UILevel<5 condition to the custom actions so they will only run if at a interface level less than default (Reduced, Basic, None). I also added UILevel>4 to the calls in the "Finish" button just in case. (We don't accidentally want more than one running at a time.) In addition to this, there is a custom action to launch messenger. I have added this to the normal launch sequence, and in order to control it, created a new public property which can be set from the command line. In addition to this, since we are really looking to make this a hands free as possible, I created a entirely new custom action for the MSN Toolbar installation, similar to the existing ones, but instead gave it the command line switch "j", which is the closest to silent I have found. In order to control this action, I created a new public property also. This new action however was not added to the normal dialog sequence. It is only available in the unattended install. Now I did not change any of the properties for these options. I realize they are long names, etc, but that is what they are in the default MSI. So get over it. This is, of course, not supported by Microsoft in any form or fashion. Do not cry to them if it does not work. This was built extremely quickly, with no regard to testing. It had limited testing, and while everything seemed to function, no guarantees are made. Use it at your own risk. ------ Ok, with that out of the way...here is how to use it. <Path>MsnMsgs.msi TRANSFORMS=CustomMSNMsgr62.mst [ADDEXPLORERTOOLBAR=AddExplorerToolbar] [sETSEARCHENGINE=SetSearchEngine] [sETHOMEPAGE=SetMyHomePage] [LAUNCHMSGR=Yes] [sEMISILENT=Yes] These switches are used in combination. Here is a breakdown. TRANSFORMS=CustomMSNMsgr62.mst - This is required if you want to install it this way. Without it, you only have the way MS wrote it, not any changes I made. Copy the MST file to the same folder as the original MSI. As long as they are in the same path, you don't need to specify one. If in a different folder, specify the path along with the transform file name. ADDEXPLORERTOOLBAR="AddExplorerToolbar" - This is the property to install JUST the MSN Toolbar. No Set search engine, non silent, etc. This can be set separately, or together with SETSEARCHENGINE, LAUNCHMSGR, or SETHOMEPAGE. Do not use with SEMISILENT. SETSEARCHENGINE="SetSearchEngine" - This is the property to JUST set MSN as the default Search Engine. It is non silent, No Toolbar etc. This can be set separately, or together with ADDEXPLORERTOOLBAR, LAUNCHMSGR, or SETHOMEPAGE. Do not use with SEMISILENT. SETHOMEPAGE="SetMyHomePage" - This is the property to JUST set the home page to MSN. It is Silent, No Toolbar, etc. This can be set separately, or together with ADDEXPLORERTOOLBAR, LAUNCHMSGR, SEMISILENT or SETSEARCHENGINE. LAUNCHMSGR="Yes" - This is the property to launch the MSN Messenger at the completion of setup. This can be set separately or together with ADDEXPLORERTOOLBAR, SETHOMEPAGE, SEMISILENT or SETSEARCHENGINE. SEMISILENT="Yes" - This is the property to install the MSN Toolbar semi-silently. This cannot be set together with other SETSEARCHENGINE or ADDEXPLORERTOOLBAR. If SEMISILENT is set, it will set SETSEARCHENGINE and ADDEXPLORERTOOLBAR to null values. It can be used with LAUNCHMSGR or SETHOMEPAGE. The default values are as follows: ADDEXPLORERTOOLBAR="AddExplorerToolbar" SETSEARCHENGINE="SetSearchEngine" SETHOMEPAGE="SetMyHomePage" This is the way MS set them. This means all 3 of these options are ON by default. If you do not want these default options, you MUST pass the appropriate switches to change them to your liking. LAUNCHMSGR="No" SEMISILENT="No" These were set by me (Since I added them.) They are OFF by default. Meaning, if you want these options, you must pass these switches, replacing "No" with "Yes". If you find any bugs, let me know.... Its only like 11k or something. CustomMSNMsgr62.mst CustomMSNMsgr62.mst

Added the switches to the Application Switches thread. Also, modifying the MSN Messenger 6.2 MSI and moving the custom actions out of the "Finish" button, etc. But I will be out of town all weekend, so won't have anything till Monday.