Joe User 99

You are calling the wrong setup.exe. You need to point to the Office setup.exe. Try using the full path. Since unattended installs default to the system32 directory, it is attempting to run whichever setup.exe it finds in there.

With older versions of Office (XP, 2000) I think the only way to patch a local install that was installed via an admin install point, was was to patch the admin install point, and then call MSIEXEC to reinstall office. On 2003 though, you should be able to patch a local install that was installed via admin install point as long as you use the "Full File" patch. I have never tried it though. For more info on patching Office 2003, check this document: Strategies for Updating Office 2003 Installations It has info on how to patch the admin install point as well as the local installation.

I've never tried changing it through registry settings, but yes the tool to create the customized installations does allow you to set everything. We use it here at work, and basically, everything is locked down on it. You make your changes, and it builds it all into the single file .exe.

Just create a MST with your changes and post it instead. (It'll be smaller too.)

Wise Package Studio Professional 5.6

I opened it up in a MSI editor and poked around the dialogs and tables.

Ok, before I pass along this info, let me state, I have not tried any form of unattended install of this, and don't really have plans to. But I am interested in seeing if it can be done. So, here is what I have found in relation to serial numbers. According to the MSI: The "Full" version serial number property is: SERIALNUMBERTEMP The "Trial" version serial number property is: SERIALNUMBERTRYOUT The properties to set which version ("Full" or "Trial") is: UNITYSELECTION="RETAIL" or UNITYSELECTION="TRYOUT" So it sounds like you would call: Adobe Photoshop CS2.msi /qb UNITYSELECTION="TRYOUT" SERIALNUMBERTRYOUT="xxxx-xxxx-xxxx-xxxx-xxxx-xxxx" Now, I realize this doesn't help on the abcpy.ini way of setup, but for those setting up straight from the MSI (and maybe those passing the MSI properties through setup.exe without using abcpy.ini), hopefully this will help.

Try adding "-!" like this: AdbeRdr70_enu_full.EXE /v"/qb-! EULA_ACCEPT=YES"

Not sure, but I think it is this one:

Trying to create a Sysprep image for 2003 SP1. I've got everything set up the way I want, and then I run Sysprep. The system reboots, runs the mini setup, reboots again, and comes up to login. I login and find that the second partition is no longer on the drive letter I assigned it (E:), but has moved to D:. (This is the pagefile partition btw.) Is there any way to set the drive letters for individual partitions in sysprep?

That worked, but I want it without MSN as homepage, without MSN toolbar, without MSN Search Assistant,... Any ideas? <{POST_SNAPBACK}> To NOT INSTALL these items, use the following property values. ADDEXPLORERTOOLBAR = "" SETSEARCHENGINE = "" SETHOMEPAGE = "" To INSTALL these items, use the following property values. ADDEXPLORERTOOLBAR = AddExplorerToolbar SETSEARCHENGINE = SetSearchEngine SETHOMEPAGE = SetMyHomePage For example: MsnMsgs.msi ADDEXPLORERTOOLBAR = "" SETSEARCHENGINE = "" SETHOMEPAGE = "" /QB"

Here at my office, we are using Novell Zenworks 6.5 for imaging. This allows us either a imaging CD (using scriptable linux), or PXE. The server side allows rules based imaging, so when the system boots, it will check against certain hardware rules (including chipset, processor, video, nic, ram, hd size, etc), which will determine the particular image it is supposed to use. Using PXE we can also force a reimage remotely. The image and all the apps are seperate, but also fall into the script. The Apps are created as Zenworks NAL objects, when can be deployed (similar to group policy), or in this case, a seperate image file for each app is created. The script then tells which apps go with which system and they are pulled down together with the OS image. In our office we are using sysprep'd images, but it will work for standard load as well. For reimaging, Zenworks allows personality migration (which will save user data, settings, profiles, etc), before reimaging and restore them afterwards. Nice features, for a Netware environment.

You should be able to create the dialup connection only, by selecting single disk branding as the option, then uncheck everything except the connections section. This will just create a setup.exe that does nothing but apply your settings and reboot. As for shrinking the flat? I don't know everything that can be removed, but if you are only installing on Windows 2000, the all the IENT_Sx.CABs, IEMIL_x.CABs, can be removed, as they are for other OS's, and I'm sure there is more. If anyone has a specific list of the bare cab requirements for each OS, that would be useful.

Actually, The Installshield Tuner for Acrobat v7 is available now. Check here: http://www.adobe.com/support/downloads/detail.jsp?ftpID=2709 And it does give the option to remove the shortcuts in the Transform. The MSI Editors I use are Wise Package Studio 5.51, and Installshield AdminStudio 6.0 Value Pack1 As for free MSI Editors, you might try WinInstall LE 2003 I've never used it, but I've heard lots of people here give good reviews ot it. http://www.ondemandsoftware.com/freele.asp

I think the problem you are having is part of the MSI self healing process. If you look in the Application Event log, it should mention what was missing. Just a guess, but most likely it will be the HKEY_CURRENT_USER keys in the registry. I figure when you install it at the T-12 spot, that is not the same HKEY_CURRENT_USER hive as your account. So when the check is run, it finds those missing and repairs itself. If this is the problem, what you would need to do, would be to remove the KeyPath check for all the current user keys in the MSI. Now, this is just a guess, as I am not installing mine during windows setup. But have a look. Hope it helps.

Did you try the Installshield Tuner for Acrobat? I have not used it since I own a full blown MSI editor, but I know it creates transforms. And transforms can be used to supress the shortcuts without modifying the original MSI. That is how I deployed it here at the office. Used a transform to set everything I needed.

Using Orca, Go to the Shortcut Table, all 3 are listed there. Just right click on each one and select Drop Row. Then resave your msi.

On mine, it defaults to English. It is the first language listed.

I think this is it: [HKEY_CURRENT_USER\Software\Microsoft\Office\11.0\Common\Internet] "UseOnlineContent"=dword:00000002 [HKEY_CURRENT_USER\Software\Microsoft\Office\Common] "QMEnable"=dword:00000000

Got a little bonus for all you concerning the Stupid Yahoo Button: Previously registry keys were given to "hide" it. But I think I have got a way to remove it completly. It does require editing either a transform or the MSI itself using Orca or similar MSI editor though. Here is what I did: First, I am not installing the Updater Feature at all. Since I am preping to distribute this to our entire enterprise, rather than just disable the Updates, I just don't install it. This will matter in the modification below. You either need a Feature you are not installing, or you need to create a new Feature. Go to the FeatureComponents Table. The Component you are looking for is "Reader_WebSearch_WebSearchENU.pdf". Change this Component's Feature to one you are not installing, for example, I changed it to Updater, since I am not installing the Updater feature. Then either save the MSI or create a Transform from it. That's it! I then tested by installing on a clean machine. Opened a PDF in both the standalone application, and in IE. And No stupid Yahoo bar! Not only that, but right clicking on the toolbar, shows no option to enable it either! B) NOTE: When testing this, you need to uninstall any previously installed copies. The changes won't take effect if 7.0 is already installed, it will just use a cached copy of the MSI instead. Hope this works for you all as well as it did for me!

The reason it prompts you for the MSI, is because every time it is launched, it is checking the KeyPath for each Component in the Component table. This is part of the self-healing/repair functionality of the Windows Installer. If you don't want it to do this, simply remove all the values in the KeyPath colum in the Component Table of the MSI. (This must be done before the MSI is installed. Otherwise, you will have to uninstall and reinstall the MSI for the changes to take effect.)

I mean, open the MSI using a MSI editor, such as Orca, WinInstallLE, etc. there is a table called "EnterpriseRegistry". It lists a bunch of registry keys you can set to disable or pre-set certain options, such as the ones I listed.

Here are some helpful registry keys I pulled out of the 7.0 MSI: [HKEY_LOCAL_MACHINE\SOFTWARE\Adobe\Acrobat Reader\7.0\FeatureLockdown] "bEFIPrintMe"=dword:00000000 "bPurchaseAcro"=dword:00000000 "bShowEbookMenu"=dword:00000000 "bUpdater"=dword:00000000 "bShowAdsAllow"=dword:00000000 Meanings: "bEFIPrintMe"= Remove the "PrintMe Internet Printing" menu item on File menu. "bPurchaseAcro"= DISABLE (NOT remove) the "Purchase Adobe Acrobat" menu item under Help menu. "bShowEbookMenu"= Remove the "Digital Editions" menu item on File menu. (This can also be done by disabling the entire eBookEBXPlugin Feature). "bUpdater"= Remove the "Check for updates now..." menu item under Help menu. "bShowAdsAllow"= Remove the Ad box. And there are a ton more. Check under the "EnterpriseRegistry" table of the MSI.

Try adding ALLUSERS=1 to the flsw.msi

Uh....Easy CD 6 is a native MSI. There isn't any conversion needed. It's been a native MSI since version 5.