Office 2007, Unattended Setup & Fine-tuning its very easy & simple!
#152
Posted 21 May 2007 - 02:22 PM
#153
Posted 21 May 2007 - 02:27 PM
Just go to start > run > type in the location of the hotfix with the switch on the end and click OK. It will then run, accept the agreement and then select where to save the output. The output will be an *.msp file, place this in your updates folder.
Example - c:\KB123456.exe /extract
laze.
#154
Posted 22 May 2007 - 04:56 AM
prathapml, on Apr 14 2006, 10:22 AM, said:
Unattending or silently installing MS Office System, has now become easier than ever. There are two ways to unattend your setup:
--> Option A (use it only if you got Office2007 thru SoftwareAssurance, which comes with activation stripped out).
--> Option B is for all the others (retail/OEM/academic/trial/etc). Both are colored differently below.
Option A:
1. Ensure you have an actual enterprise/corporate disc & product-key.
2. Notably, o2k7 uses setup patches (*.MSP) rather than transforms which previous versions used (*.MST). The below instructions will give you an MSP file, which is not accepted by non-corporate versions of o2k7. If you ignored point1 above, then you will end up wasting 15 minutes of your life which I'm not responsible for.
3. Now at the command prompt, type: setup.exe /admin
4. Choose the product for which you want to make a customization-patch.
5. Then go through all steps in the customization wizard (to install the reqd apps & remove junk & change default settings).
6. Be sure to have "completion notice" turned on & "suppress modals" turned off (this is to get to see errors, if any exist). Once you're done with testing, go thru the customization again to modify the MSP to disable completion notice & enable suppress modals.
7. Save the resulting patch file in the same folder as o2k7 setup files.
8. Now just execute this command (thru any method) for silent install: setup.exe /adminfile CUSTOM.MSP
Or if you have the Office 2007 Enterprise VLK, you could even drop the CUSTOM.MSP file in the "Updates" folder & setup will pick it up automatically (without any switches being used). For this, ensure you have WindowsInstaller 3.1 already installed.
*** For completely silent install, you MUST set the DisplayLevel to "none", either by MSP (accessible from step 6 above) or by xml, otherwise you'll get a confirmation dialog similar to the image shown in attachment below. (do this only AFTER testing, when you're sure it works)
................................
This post has been edited by CaNgO: 29 July 2007 - 03:25 AM
#155
Posted 22 May 2007 - 05:12 AM
laze.
#156
Posted 25 May 2007 - 05:14 AM
But I have some questions:
- Can I specify the path where the users save all the documents made with Office 2007 by default, like the ork 2003 do.
- I need to make a visual basic script to run the silent installation, introducing each product key by computer.
Thanks a lot. Shald
#157
Posted 25 May 2007 - 06:46 AM
#158
Posted 06 June 2007 - 12:22 PM
Sgt_Strider, on Apr 22 2007, 08:02 AM, said:
Sanjay, on May 21 2007, 09:14 PM, said:
shald, on May 25 2007, 04:44 PM, said:
But I have some questions:
- Can I specify the path where the users save all the documents made with Office 2007 by default, like the ork 2003 do.
- I need to make a visual basic script to run the silent installation, introducing each product key by computer.
Yes you can specify the default-save-path for documents, it can be done when you're preparing your MSP file.
As for the VBscript, you might need to make it yourself, as per your customized needs.
eangulus, on Apr 24 2007, 10:18 AM, said:
1. First use a key to install.
2. After install, delete this registry key:
Quote
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Office\12.0\Registration (on XP & vista 64-bit)
4. Thats all.
This post has been edited by prathapml: 06 June 2007 - 12:27 PM
#159
Posted 09 June 2007 - 07:14 PM
#160
Posted 09 June 2007 - 07:40 PM
#161
Posted 10 June 2007 - 03:53 PM
In 2003 there was a tool in the Office Resource Kit called LISTool.exe which allowed changing the location of the the LIS or it's removal. More specifically, it dealt with the approriate registry entries. I'm willin gto bet it will work on 2007, though it doesn't appear to be included in the the Resource Kit.
http://office.microsoft.com/en-us/ork2003/...1402361033.aspx
#162
Posted 12 June 2007 - 01:45 PM
But I dont want it to be created at all.
(in office 2003, you could specify that you dont want a local cache at all, and that saved half the install-time)
#163
Posted 12 June 2007 - 01:54 PM
At the moment, I delete MSOCache after the installation completes, but this isn't ideal.
If as prathapml suggests, installation time's drastically cut by not creating MSOCache, then I'm for working that much harder to find a solution.
laze.
#164
Posted 13 June 2007 - 09:37 AM
If it can't be done using the OCT or directly editing a config file, is there another tool I can use by linking it to the SMS package?
- Everett
#165
Posted 14 June 2007 - 01:59 AM
1. I made .msp and everything works fine except one thing - it always asks me what I want to install (look at attachment). Because I have two MUI.
So is there a way to select appropriate product automatically (first one) ?
Quote
Original setup.exe from the worked fine (separately) but now I deleted it
This was a beta of Russian MUI. Now works fine.
Attached File(s)
-
office2007.png (47.99K)
Number of downloads: 65
This post has been edited by Marsianin: 01 July 2007 - 06:25 PM
#166
Posted 21 June 2007 - 02:58 AM
I've tried the following:
msiexec.exe /X{90120000-0030-0000-0000-0000000FF1CE} /quiet /passive /norestart /qb-!
and:
setup.exe /uninstall enterprise /config config.xml
where config.xml includes:
<Configuration Product="Enterprise">
<Display Level="none" CompletionNotice="no" SuppressModal="yes" AcceptEula="yes" />
<Setting Id="Reboot" Value="ReallySuppress" />
</Configuration>
Any ideas on how to prevent that from happening?
This post has been edited by newuzer: 21 June 2007 - 03:01 AM
#167
Posted 21 June 2007 - 03:11 AM
wallacee, on Jun 13 2007, 04:37 PM, said:
If it can't be done using the OCT or directly editing a config file, is there another tool I can use by linking it to the SMS package?
- Everett
Hi,
You can use PSKILL.EXE to kill any application.
laze.
#168
Posted 22 June 2007 - 08:02 AM
newuzer, on Jun 21 2007, 02:58 AM, said:
I've tried the following:
msiexec.exe /X{90120000-0030-0000-0000-0000000FF1CE} /quiet /passive /norestart /qb-!
and:
setup.exe /uninstall enterprise /config config.xml
where config.xml includes:
<Configuration Product="Enterprise">
<Display Level="none" CompletionNotice="no" SuppressModal="yes" AcceptEula="yes" />
<Setting Id="Reboot" Value="ReallySuppress" />
</Configuration>
Any ideas on how to prevent that from happening?
Already found the answer.
config.xml should include:
<Configuration Product="Enterprise">
<Display Level="none" CompletionNotice="no" SuppressModal="yes" AcceptEula="yes" />
<Setting Id="SETUP_REBOOT" Value="Never" />
</Configuration>
#169
Posted 29 June 2007 - 10:44 PM
Quote
1. I made .msp and everything works fine except one thing - it always asks me what I want to install (look at attachment). Because I have two MUI.
So is there a way to select appropriate product automatically (first one) ?
I have the same issue. I tried to specified the Product Code in the config.xml file, still not working.
For the problem #2 make sure you added the proper entries in the config.xml filelocated in the Enteprise.WW folder.
Here's my config.xml file:
<Configuration Product="Enterprise">
<!-- Install Office 2007 Enteprise as default product -->
<Setup Id="Enterprise" Type="Product" ProductCode="{90120000-0030-0000-0000-0000000FF1CE}">
<!-- Match GUI language with system language -->
<AddLanguage Id="match" ShellTransform="yes"/>
<!-- Add english language pack -->
<AddLanguage Id="en-us" />
<!-- Add french language pack -->
<AddLanguage Id="fr-fr" />
Any suggestions ?
This post has been edited by JakeLD: 29 June 2007 - 10:49 PM
#170
Posted 10 July 2007 - 03:50 AM
prathapml, on Apr 14 2006, 09:22 AM, said:
Unattending or silently installing MS Office System, has now become easier than ever. There are two ways to unattend your setup:
--> Option A (use it only if you got Office2007 thru SoftwareAssurance, which comes with activation stripped out).
--> Option B is for all the others (retail/OEM/academic/trial/etc). Both are colored differently below.
Option A:
1. Ensure you have an actual enterprise/corporate disc & product-key.
2. Notably, o2k7 uses setup patches (*.MSP) rather than transforms which previous versions used (*.MST). The below instructions will give you an MSP file, which is not accepted by non-corporate versions of o2k7. If you ignored point1 above, then you will end up wasting 15 minutes of your life which I'm not responsible for.
3. Now at the command prompt, type: setup.exe /admin
4. Choose the product for which you want to make a customization-patch.
5. Then go through all steps in the customization wizard (to install the reqd apps & remove junk & change default settings).
6. Be sure to have "completion notice" turned on & "suppress modals" turned off (this is to get to see errors, if any exist). Once you're done with testing, go thru the customization again to modify the MSP to disable completion notice & enable suppress modals.
7. Save the resulting patch file in the same folder as o2k7 setup files.
8. Now just execute this command (thru any method) for silent install: setup.exe /adminfile CUSTOM.MSP
Or if you have the Office 2007 Enterprise VLK, you could even drop the CUSTOM.MSP file in the "Updates" folder & setup will pick it up automatically (without any switches being used). For this, ensure you have WindowsInstaller 3.1 already installed.
*** For completely silent install, you MUST set the DisplayLevel to "none", either by MSP (accessible from step 6 above) or by xml, otherwise you'll get a confirmation dialog similar to the image shown in attachment below. (do this only AFTER testing, when you're sure it works)
So once I have created the custom msp file, and put it in the main office2007 install source folder, packed it with nlite addon maker using the command switch /adminfile custom.msp to a huge cab file, put it in nLite patches it should install with windows???



Help


Back to top










