Difference between revisions of "MS Office 2010"

From WPKG | Open Source Software Deployment and Distribution
Jump to: navigation, search
(→‎Installation: found way for automatically generation of config.xml :-))
(→‎Configuration)
Line 178: Line 178:
 
==Configuration==
 
==Configuration==
  
−
If you have an Windows Server with an AD, it is possible to use Group Policy to enforce some Office 2010 settings. You need the [http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=18968 Office 2010 Administrative Template files] and find a comprehensive guide in this [http://www.microsoft.com/downloads/de-de/details.aspx?FamilyID=66a6848c-6c28-4b61-9c12-a8cad4b380a4 document] (change language before download if needed). --[[User:Konus|Konus]] 15:10, 1 February 2012 (CET)
+
If you have an Windows Server with an AD, it is possible to use Group Policy to enforce some Office 2010 settings. You need the [http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=18968 Office 2010 Administrative Template files] and find a comprehensive guide in this [http://www.microsoft.com/downloads/de-de/details.aspx?FamilyID=66a6848c-6c28-4b61-9c12-a8cad4b380a4 document] (change language before download if needed).
 +
 
 +
A good start is the [http://www.cloudtec.ch/blog/tech/office-2010-update.html table on the botton of this site] --[[User:Konus|Konus]] 15:10, 1 February 2012 (CET)
  
 
[[category:Silent Installers]]
 
[[category:Silent Installers]]
 
[[Category:Microsoft Office]]
 
[[Category:Microsoft Office]]

Revision as of 12:23, 2 February 2012

MS Office 2010 (volume license)

For this install, create a custom MSP file by running the Office setup.exe with /admin. Customise the installation you require (don't install Outlook etc. One tip, if installing Access, also install 'Visual Basics'). The MSP file can be saved outside the documents \upgrades directory if you wish to.

Customization

Disable the Opt-in Welcome Wizard

In the Customization Tool, go to Features \ Modify user settings \ Microsoft Office 2010 \ Privacy \ Trust center and set "Disable opt-in wizard on first run" to Enabled.

Installation

<?xml version="1.0" encoding="UTF-8"?>
<packages>

<package id="msoffice2010" name="Microsoft Office 2010" revision="1" reboot="false" priority="72">

	<check type="uninstall" condition="exists" path="Microsoft Office Professional Plus 2010" />

	<install cmd='%comspec% /C start "" /WAIT "%SOFTWARE%\office\msoffice10\source_files\setup.exe" /adminfile "%SOFTWARE%\office\msoffice10\maths_config\maths_base_install.MSP"' >
		<exit code="1641" />
		<exit code="3010" />
	</install>
    
	<upgrade cmd='%comspec% /C start "" /WAIT "%SOFTWARE%\office\msoffice10\source_files\setup.exe" /adminfile "%SOFTWARE%\office\msoffice10\maths_config\maths_base_install.MSP"' >
		<exit code="1641" />
		<exit code="3010" />
	</upgrade>
    
	<remove cmd='%comspec% /C start "" /WAIT "%SOFTWARE%\office\msoffice10\source_files\setup.exe" /uninstall ProPlus /config  "%SOFTWARE%\office\msoffice10\maths_config\silentuninstall.xml"' >
		<exit code="3010" />
	</remove>
	
	
</package>

</packages>

To remove Office 2010, as per Office 2007, create a file (silentuninstall.xml) containing: 

<Configuration Product="ProPlus">
	<Display Level="none" CompletionNotice="no" SuppressModal="yes" AcceptEula="yes" />
	<Setting Id="SETUP_REBOOT" Value="NEVER" />
</Configuration>

The line '<Setting Id="SETUP_REBOOT" Value="NEVER" />' sops the pc rebooting when Office is removed, omitting this line will reboot your pc without you being asked!

KMS Activation

To activate Office via KMS, a 'dependant' WPKG XML file is created. 

<?xml version="1.0" encoding="UTF-8"?>
<packages>

<package id="msoffice2010-activation" name="Activation MS Office 2010" revision="1" reboot="false" priority="71">

	<depends package-id="msoffice2010" />	
	<variable name="update" value="01" />	
	<check type="execute" path="%software%\office\msoffice10\maths_config\activation.bat" condition="exitcodeequalto" value="0" />
	<check type="file" condition="exists" path="%PROGRAMFILES%\Microsoft Office\Office14\WORDIRM.XML.%update%" />
	
	<!-- First make a backup of the a random file, WORDIRM.XML file.  This is used for the <remove /> part of this file as there isn't
	an uninstaller for the update therefore we need to uninstall something to make the <check /> work so that we can then uninstall
	the main Maple program-->
	<install cmd='%COMSPEC% /c copy /y "%PROGRAMFILES%\Microsoft Office\Office14\WORDIRM.XML" "%PROGRAMFILES%\Microsoft Office\Office14\WORDIRM.XML.%update%"' >
		<exit code="any" />
	</install>
	<!-- Now do the KMS... -->
	<install cmd='"%SYSTEMROOT%\system32\cscript" "%PROGRAMFILES%\Microsoft Office\Office14\OSPP.vbs" /sethst:kms.somewhere.over.the.rainbow' />
	<install cmd='"%SYSTEMROOT%\system32\cscript" "%PROGRAMFILES%\Microsoft Office\Office14\OSPP.vbs" /act' />
	
	<remove cmd='%COMSPEC% /c del /q "%PROGRAMFILES%\Microsoft Office\Office14\WORDIRM.XML.%update%"' />

<!-- 
To check Office is activated, run
cscript "c:\program files\Microsoft Office\Office14\OSPP.vbs" /dstatus
-->

</package>

</packages>

So that this package can be uninstalled, a random file in c:\program files\Microsoft Office\office14\ is copied, a 'check' added and the <remove> line removes this copied file.

activation.bat = 

@echo off

%Systemroot%\system32\cscript "%ProgramFiles%\Microsoft Office\Office14\OSPP.vbs" /dstatus | find "---LICENSED---"
exit %errorlevel%

MS Office 2010 single license

The Office Customization Tool (OCT) is available only with volume licensed versions of Office 2010 (and the 2007 Office). Unfortunately the prices of volume licenses are significantly higher, than for single licenses. So the above solution can't be used if you bought several single licenses for budget reasons.

config.xml

To configure a silent installation (unattended installation) of an Office 2010 product that requires no user interaction, create a config.xml. You find an example in the subfolder of the installation called product_folder_name.WW 

<Configuration Product="SingleImage">
	<Display Level="none" CompletionNotice="no" SuppressModal="yes" AcceptEula="yes" />
	<!-- <Logging Type="standard" Path="c:\temp" Template="MS_Office_Install_Log.txt" /> -->
	<PIDKEY Value="AAAAABBBBBCCCCCDDDDDEEEEE" /> <!-- you have to enter a valid key here! -->
	<!-- <USERNAME Value="Customer" /> -->
	<!-- <COMPANYNAME Value="Organisation" />  -->
	<!-- <INSTALLLOCATION Value="%programfiles%\Microsoft Office" /> -->
	<!-- <LIS CACHEACTION="CacheOnly" /> -->
	<!-- <LIS SOURCELIST="\\server1\share\Office;\\server2\share\Office" /> -->
	<!-- <DistributionPoint Location="\\server\share\Office" /> -->
	<!-- choose what to install -->
	<OptionState Id="ACCESSFiles"  State="Absent" Children="force" /><!-- Access -->
	<OptionState Id="EXCELFiles"   State="Local"  Children="force" /><!-- Excel -->
	<OptionState Id="OneNoteFiles" State="Absent" Children="force" /><!-- OneNote -->
	<OptionState Id="OUTLOOKFiles" State="Absent" Children="force" /><!-- Outlook -->
	<OptionState Id="PPTFiles"     State="Local"  Children="force" /><!-- Powerpoint -->
	<OptionState Id="PubPrimary"   State="Absent" Children="force" /><!-- Publisher -->
	<OptionState Id="WORDFiles"    State="Local"  Children="force" /><!-- Word -->
	<!-- <Setting Id="Reboot" Value="IfNeeded" /> -->
</Configuration>

Installation

It is necessary to give a real product key in config.xml during installation. Remember, no volume license. So for single license products, every client has his own license number. You can deal in two ways with this problem:

A: change product key after installation

If you delete all subkeys from [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Office\14.0\Registration] (for 32bit Office in a 64bit windows) or HKEY_LOCAL_MACHINE\Software\Microsoft\Office\14.0\Registration\ (for a 64bit Office) after installation (and before first usage), Office ask the user for the product key after startup.

B: use a different config.xml for every client

You can create a copy of config.xml for every client and use the the Value %COMPUTERNAME% to direct the client to his config.xml

For automatically generation of the config file, you can use a little tool called FilesFromCSV use the above config.xml, replace the pid with %computername% save it as template.xml

Then generate a csv file like this and call it license.csv: 

computername;pid
w01;010101
w02;020202
...

Finally run the tool with 

FilesFromCSV.exe -HDR=YES -D=; -csv=C:\temp\license.csv -template=C:\temp\template.xml -filenamefield=computername -outpath=C:\temp\output\


after that you can install the packet with 

<package id="office2010"
	name="Microsoft Office 2010"  
	revision="1"
	reboot="false"
	priority="10">
	<check type="uninstall" condition="exists" path="Microsoft Office Home and Business 2010" />
	<commands>
		<command type="install" cmd='%comspec% /C start "Installer" /WAIT "%SOFTWARE%\O2010\x86\setup.exe" /config "%SOFTWARE%\O2010\x86\%COMPUTERNAME%.xml"' >
			<exit code="1641" />
			<exit code="3010" />
		</command>
	</commands>
</package>

Configuration

If you have an Windows Server with an AD, it is possible to use Group Policy to enforce some Office 2010 settings. You need the Office 2010 Administrative Template files and find a comprehensive guide in this document (change language before download if needed).

A good start is the table on the botton of this site --Konus 15:10, 1 February 2012 (CET)

Retrieved from "https://wpkg.org/index.php?title=MS_Office_2010&oldid=10456"