Jump to content


Photo

How can I deploy Office 2007 with SCCM


  • Please log in to reply
24 replies to this topic

#1 murda

murda

    Advanced Member

  • Members
  • PipPipPip
  • 67 posts
  • Location:Antwerpen

Posted 12 June 2009 - 11:33 AM

How can I deploy Office 2007 with SCCM

In this guide I will deploy Office 2007 Enterprise & Office Language Pack towards a client in a OSD Task Sequence.

Important notice:

You use the Office Customization Tool (OCT) to customize an installation of the 2007 Microsoft Office system. The OCT is part of the Setup program and is the recommended tool for most customizations. You run the OCT by typing setup.exe /admin at the command line. The OCT is available only with volume licensed versions of the 2007 Office system. Office Standard 2007, Office Small Business 2007, Office Professional Plus 2007, and Office Enterprise 2007 are available for purchase through volume licensing. For more information, see How to buy the 2007 Microsoft Office suites (http://go.microsoft..../?LinkID=121942).

To determine if your 2007 Office suite installation is a volume licensed version, check the 2007 Office suite installation disk to see if it contains a folder named Admin. If the Admin folder exists, this disk is a volume license edition. If the Admin folder does not exist, this disk is a retail edition. For more information, see Microsoft Knowledge Base article 93141: How to determine whether you have a retail edition or a volume license edition of a 2007 Microsoft Office suite (http://go.microsoft..../?LinkId=149830).


See Technet

If you don't have a Volume license edition then you need to make your customizations with the config.xml.
How you can customize your office with a config.xml is explained here & here.





I have an Enterprise volume license edition so I will proceed with customizing Office 2007 with OCT (.msp file) and the Language Pack with a config.xml file.

First thing I did was download Microsoft Office 2007 Enterprise & Language Pack NL edition.
I unpacked the folder to my client pc so I can test the silent installs before making a package in SCCM.

The unpacked folders look like this:

Office 2007 Enterprise:
unpacked_folders_office.jpg

Office 2007 language pack:
unpacked_folders_language_pack.jpg

Side note info from technet to understand where the setup.exe is going to check for the customization files (.msp or config.xml)

If you have problems with customizing office
Setup looks for a copy of Config.xml in the same folder as Setup.exe. If a copy is not found there, Setup uses the Config.xml file that resides in the core product folder for the product that you are installing. If there are multiple products available in the installation source, Setup waits until you specify which product to install before it looks for the copy of Config.xml. Because of this design, the Logging element is only used by Setup when the Config.xml file resides in the same folder as Setup.exe, or if you specify the Config.xml file by using the Setup /config command-line option. If Setup uses the Config.xml file in the product folder, the default standard logging options are used.


Next step is open CMD and customize your Office 2007 EE install
Run the following switch from CMD: "setup.exe" /admin
cmd_admin.jpg

This will open a window and select "Create a new setup customization file for the following product"
admin_config.jpg

For testing I just filled in my Office Enterprise License and the following options:

Display Level="none" CompletionNotice="No" SuppressModal="Yes" AcceptEula="Yes"


I will not go in depth of customizing Office 2007 but you always can check technet for further details on how to customize Office 2007.

When you're done customizing the office 2007 then you can save your customization file in the Office 2007 root folder.
I saved two customizations: Full_silent.msp & Standard_silent.msp
msp_files.jpg

Now lets try out our saved .MSP file and see if it works correctly before proceeding for a Office Language Pack.

Now let's open CMD.
browse to your install and enter the following switch: "setup.exe" /adminfile file.msp
install_with_admin_command_root.jpg

Sidenote: If you only have one .MSP file then you can place it in the Updates folder under the root folder and just run the "setup.exe" without switches. "Setup.exe" will automatic apply the saved .msp file from the updates folder.
If you have more .MSP files like me then place them all in your Office 2007 EE root folder.


Now check the process of the installation.
When you configured the customization as a silent install then you can follow the process in the TaskManager (CTRL+SHIFT+ESC)setup_installing_in_pcocess_explorer.jpg

You've to wait till the following files are dissapeared in your taskmanager
- setup.exe
- msiexec.exe
- ose00000.exe


After that you can check if you're office is correctly installed:
office_installed.jpg


Oké, lets install a Language Pack. In my example I am going to install a NL language pack.
Now lets browse to your Language Pack Folder.

Now copy the config.xml file that is in the OMUI.NL-NL to the Office Language pack root folder.
place_config_root.jpg

Now you can customize the config.xml with a Text editor (notepad or notepad++).
For more information on how to customize the config.xml for language packs I refer you to this site: technet

This is how my config.xml looks like
xml_config_language_pack.jpg

The code so you can copy past and test it:
<Configuration Product="OMUI.nl-nl">
<Display Level="none" CompletionNotice="No" SuppressModal="Yes" AcceptEula="Yes" />
<AddLanguage Id="nl-nl" ShellTransform="Yes" />
<OptionState Id="OfficeMUI" State="Local" Children="force" />
</Configuration>


Lets test this config.xml just by running the "setup.exe" from the "Language Pack"

Sidenote: If your config.xml is in another directory then (besides the root folder and the OMUI.NL-NL folder then you have to give the full path in the command line).
Example: "setup.exe" /config \\server\share\Office12\OMUI.NL-NL\Config.xml



Check the process in TaskManager like explained above.
When the process is finished, you can select your desired language by selecting "Microsoft Office 2007 Languages"
browse_language.jpg

Checking if the language are installed:
see_if_its_installed.jpg
Looks like it is correctly installed.


What about the updates?

Go to Microsoft Office Online and update you office but DO NOT INSTALL them.
Write down the available or needed updates for your office and download them manually to your Updates folder that is located at your Office 2007 EE folder
These updates will be automaticly applied.
addiitional_updates.jpg
  • Vladimir Jakovljevic likes this

#2 murda

murda

    Advanced Member

  • Members
  • PipPipPip
  • 67 posts
  • Location:Antwerpen

Posted 15 June 2009 - 10:36 AM

Office 2007 in SCCM2007

First off all let us put the two folders on your SCCM2007 server.
My server is used for a test environment so I just copied them in my software directory.
office_on_server_in_seperate_maps.jpg


Make a folder under your "software distribution" and name the folder "Microsoft Office".
make_a_folder_under_software_packages.jpg


Then we need to make a package for Office 2007 Enterprise and a package for the additional Language Pack that you want to install.
make_a_package.jpg


Now fill in the name of the package and click next.
office_2007_full_1.jpg


Locate your Office 2007 directory with an UNC path.
eg: \\SCCM07SERVER\\SOFTWARE\OFFICE 2007
office_2007_full_2.jpg
Click next till you can click finish.


Then do the same for the language pack



In the next steps we are going to assign the program towards the package.
Expand you "Office 2007" folder under "software distribution" and right click on "programs" and then slect "new - programs".
new_program_office.jpg



Fill in the wizard like in the screenshot below.
Command line: "fill in your tested command line like I described above"
office_2007_program_command_line.jpg
Click Next



Select your estimated disk space. (Leave it on unknown if you're running in a test environment)
estimated_disk_space_office.jpg
Click Next



Select "program can run: whether or not a user is logged in".
whether_or_not_.jpg
click Next


Select the following option: "Allow this program to be installed from the Install Software Task Sequence without being advertised."
allow_this_program_to_be_installed_from_the_install_software_task_sequence.jpg
click Next


Note: The following step can be skipped in a test environment if you don't need a repair option for this program.
In the "windows Installer" screen you can select your .msi file.
The Office 2007 .msi file is located in the Enterprise.WW folder and for the Language Pack it would be OMUI.NL-NL (or FR-FR depends what language pack you want to install)
import_windows_installer.jpg
Click Next & Finish


Try and do the same steps for the Office 2007 Language pack.
The only difference is the command line.
In my case it is just : "setup.exe"

See my screenshot from the program properties.
language_office_2007_properties_1.jpg
  • Vladimir Jakovljevic likes this

#3 murda

murda

    Advanced Member

  • Members
  • PipPipPip
  • 67 posts
  • Location:Antwerpen

Posted 16 June 2009 - 07:31 AM

Adding the software in the Task Sequence and advertise towards a collection

I assume everyone can make a Task Sequence for OS deployment.
If not then check Anyweb's guide on how to deploy Windows Vista in SCCM.

- Part 1 - Deploy Vista
- Part 2 - Deploy Vista
- Part 3 - Deploy Vista
- Part 4 - Deploy Vista
- Part 5 - Deploy Vista
- Part 6 - Deploy Vista



I used an existing OSD Task Sequence to try out the office 2007 deployment.
Modify an existing Task Sequence and add the Microsoft Office 2007 package into the Task Sequence under "Install Software"

Click on "Add" - "General" - "Install Software"
install_software.jpg

Then Click on "browse" to select your Office 2007 software package.
browse_software.jpg
You can edit the name off the "Install Software" towards the name of your software package. In my case it was "Office 2007 FULL"

Click "Apply"


Now follow the same steps for the additional Language Pack


I also assume you have advertised the existing OSD Task Sequence towards a collection.
If not, check Anyweb's how to's I posted above.

Lets check the "Advertisement" properties.
Under "Software Distribution" go to "Advertisements" - "right click on your advertisement" - choose "properties"


Now on the "General" tab select:
- include members of the subcollection
- Make this Task Sequence available to boot media and PXE


sidenote: Your advertisement name and collection can be different from mine so don't mind that. Its important that these settings are the same.
advertisement_properties_1.jpg


Then go to "Distributions Point" tab:
Then select "Download content locally when needed by running Task Sequence"
distribution_point_setting.jpg
Click "Ok"

Test this advertisement on a pc that is in the advertisement collection and PXE boot this client.
  • Vladimir Jakovljevic likes this

#4 infotech

infotech

    Newbie

  • Members
  • Pip
  • 9 posts

Posted 16 June 2009 - 09:16 AM

hi murda,

it is nice tutorial. thanks for giving me this link.
I tried the first section of this tutorial before creating a package on SCCM. I did exactly as you describe it. I have waited for few hours and yet i can't see those processes you mentioned.
Then i updated existing setup customized file (.msp) file in a way to completionNotice=yes to let me know the status of the application installation process for testing purpose. but it displays this error message "set up was aborted. setup customization files are not supported on this microsoft office product type. Run setup again without usig a setup customization file. This customization file may be located in the updates folder of the installation image"

Fyi, i saved the (.msp) file in E:\software\office 2007\enterprise directory.


thanks a lot!

#5 anyweb

anyweb

    Administrator

  • Root Admin
  • PipPipPip
  • 5,747 posts
  • Gender:Male
  • Location:Sweden
  • Interests:Deploying Operating systems and more with System Center Configuration Manager

Posted 16 June 2009 - 10:56 AM

thanks Murda for an excellent post, I am pinning this one

cheers
anyweb
Microsoft MVP > Enterprise Client Management
My linkedin profile at > linkedin.com
Follow me on Twitter > ncbrady
Follow windowsnoob.com on Twitter > windowsnoob
My blog

#6 murda

murda

    Advanced Member

  • Members
  • PipPipPip
  • 67 posts
  • Location:Antwerpen

Posted 16 June 2009 - 12:22 PM

hi murda,

it is nice tutorial. thanks for giving me this link.
I tried the first section of this tutorial before creating a package on SCCM. I did exactly as you describe it. I have waited for few hours and yet i can't see those processes you mentioned.
Then i updated existing setup customized file (.msp) file in a way to completionNotice=yes to let me know the status of the application installation process for testing purpose. but it displays this error message "set up was aborted. setup customization files are not supported on this microsoft office product type. Run setup again without usig a setup customization file. This customization file may be located in the updates folder of the installation image"

Fyi, i saved the (.msp) file in E:\software\office 2007\enterprise directory.


thanks a lot!


Edit: I updated my first post a bit regarding OCT and config.xml

Which office are you using?
Because If you can't customize your Office 2007 with OCT (.msp file), you have to do it with your config.xml like the I explained in the language pack.

You use the Office Customization Tool (OCT) to customize an installation of the 2007 Microsoft Office system. The OCT is part of the Setup program and is the recommended tool for most customizations. You run the OCT by typing setup.exe /admin at the command line. The OCT is available only with volume licensed versions of the 2007 Office system. Office Standard 2007, Office Small Business 2007, Office Professional Plus 2007, and Office Enterprise 2007 are available for purchase through volume licensing. For more information, see How to buy the 2007 Microsoft Office suites (http://go.microsoft..../?LinkID=121942).

To determine if your 2007 Office suite installation is a volume licensed version, check the 2007 Office suite installation disk to see if it contains a folder named Admin. If the Admin folder exists, this disk is a volume license edition. If the Admin folder does not exist, this disk is a retail edition. For more information, see Microsoft Knowledge Base article 93141: How to determine whether you have a retail edition or a volume license edition of a 2007 Microsoft Office suite (http://go.microsoft..../?LinkId=149830).


http://technet.micro...y/cc179097.aspx


Try the following:

- copy your config.xml that is located in the Enterprise.WW folder into the OFFICE 2007 root folder
- modify the config.xml towards your needs
- run the "setup.exe"

Try it with this config.xml (replace the generated key with your key)
sidenote: remove the !-- --> if you want this option to be applied.
<Configuration Product="Enterprise">

	<Display Level="Basic" CompletionNotice="Yes" SuppressModal="Yes" AcceptEula="Yes" />
	
	<!-- <Logging Type="none" Path="%temp%" Template="Microsoft Office Enterprise Setup(*).txt" /> -->
	
	<PIDKEY Value="C33MX33GY311TTF3D2FV8GQFG" />

	<!-- <USERNAME Value="Customer" /> -->
	
	<!--COMPANYNAME Value="yourcompany" /> -->
	
	<!-- <INSTALLLOCATION Value="%programfiles%\Microsoft Office" /> -->
	
	<!-- <LIS CACHEACTION="CacheOnly" /> -->
	
	<!-- <SOURCELIST Value="\\server1\share\Office12;\\server2\share\Office12" /> -->
	
	<!-- <DistributionPoint Location="\\server\share\Office12" /> -->
	
	<!-- <OptionState Id="OptionID" State="absent" Children="force" /> -->
	
	<!--Setting Id="Reboot" Value="Never" /> -->
	
	<!-- <Command Path="msiexec.exe" Args="/i \\server\share\my.msi" QuietArg="/q" ChainPosition="after" Execute="install" /> -->

</Configuration>


#7 Rajiv

Rajiv

    Advanced Member

  • Members
  • PipPipPip
  • 36 posts
  • Gender:Male

Posted 06 November 2009 - 07:30 PM

good guide!



When I deploy Office 2007 to a machine where Office 2003 is already there.....the Office 2007 setup upgrades 2003 but the links to Office 2003 apps is still there in Start > Programs.

I hear in other forums that the only way to handle this is to uninstall 2003 first and then run 2007 setup.

How are others here solving this problem?

- Rajeev

rajdude.com


#8 Srinivas

Srinivas

    Member

  • Members
  • PipPip
  • 12 posts
  • Location:singapore

Posted 10 December 2009 - 03:21 PM

Hi Murda,


I hope your doing well,

I have problem advertising office 2007 via sccm ,

I created ms office 2007 package adding with some additional languages.I configured config.xml file as following below.

I created program with setup.exe /config "Proplus.WW\Config.xml" with this i can execute successfully from command prompt .when i try to distribute using sccm not installing .

Could you please advise on this .



- <Configuration Product="ProPlus">
<Display Level="Basic" CompletionNotice="yes" SuppressModal="No" AcceptEula="yes" />
<Logging Type="standard" Path="%ProgramFiles%\office\Logs" Template="Microsoft Office Professional Plus Setup(*).txt" />
<PIDKEY Value="B6PKR-XYQWK-XK6MH-BJKD6-RV2V3" />
<AddLanguage Id="match" ShellTransform="yes" />
<AddLanguage Id="en-us" />
<AddLanguage Id="ja-jp" />
<AddLanguage Id="ko-kr" />
<AddLanguage Id="NB-No" />
<AddLanguage Id="DE-DE" />
<AddLanguage Id="zh-cn" />
- <!-- <USERNAME Value="Aptina" />
-->
<COMPANYNAME Value="Aptina Imaging Corporation" />
<INSTALLLOCATION Value="%programfiles%\Microsoft Office" />
- <!-- <LIS CACHEACTION="CacheOnly" />
-->
<SOURCELIST Value="\\softwareunc\software\Enterprise\Applications\Win32\Microsoft\Office\2007\ProfessionalPlus;http://software/Ente...ofessionalPlus" />
<OptionState Id="ACCESSFiles" State="Local" Children="force" />
<OptionState Id="EXCELFiles" State="Local" Children="force" />
<OptionState Id="OUTLOOKFiles" State="Local" Children="force" />
<OptionState Id="PPTFiles" State="Local" Children="force" />
<OptionState Id="PubPrimary" State="Local" Children="force" />
<OptionState Id="WORDFiles" State="Local" Children="force" />
<OptionState Id="XDOCFiles" State="Local" Children="force" />
<OptionState Id="SHAREDFiles" State="Local" Children="force" />
<OptionState Id="TOOLSFiles" State="Local" Children="force" />
<Setting Id="SETUP_REBOOT" Value="NEVER" />
- <!-- <Command Path="msiexec.exe" Args="/i \\server\share\my.msi" QuietArg="/q" ChainPosition="after" Execute="install" />
-->
</Configuration>

#9 Jimm

Jimm

    Member

  • Members
  • PipPip
  • 22 posts
  • Gender:Male

Posted 15 December 2009 - 09:24 PM

Good day,

I've tried deploying Office 07 Enterprise a few times now and I keep getting the same result. The program begins to install but the initial dialog appears asking which product I wish to install. I used OCT to create my MSP package and it is placed in the Updates folder. I still see this dialog. I tried using the config.xml file as well to cache the install then a TS to execute the install from the local media. This also produced the same dialog. Any ideas as to what I am doign wrong? If I simply select Enterprise from this first dialog, the install continues and works fine.

Jimm
Jimm Panik

#10 mrbadgolf

mrbadgolf

    Newbie

  • Members
  • Pip
  • 5 posts

Posted 06 January 2010 - 02:57 PM

Can anyone tell me what happens if a users is working in office 03 and sccm tries to install office 07. Will the user get a notification, or will it just close out the application they are working in and install 07? I have tested that my package work, but it has never completed the install while I was actually in the office. I am ready to push this out to about 100 users but my boss would like to know this before we start so we can let the users know what will take place.

#11 ajamali

ajamali

    Newbie

  • Members
  • Pip
  • 1 posts

Posted 01 March 2010 - 12:41 PM

Good day,

I've tried deploying Office 07 Enterprise a few times now and I keep getting the same result. The program begins to install but the initial dialog appears asking which product I wish to install. I used OCT to create my MSP package and it is placed in the Updates folder. I still see this dialog. I tried using the config.xml file as well to cache the install then a TS to execute the install from the local media. This also produced the same dialog. Any ideas as to what I am doign wrong? If I simply select Enterprise from this first dialog, the install continues and works fine.

Jimm


Hi,

You can specify the product to be installed by using the /config switch:

setup.exe /adminfile file.msp /config Enterprise.WW\config.xml

You don't have to modify the config.xml but there are some options that you can uncomment
  • Vladimir Jakovljevic likes this

#12 Harvey

Harvey

    Member

  • Members
  • PipPip
  • 25 posts

Posted 19 August 2010 - 10:58 AM

For our Office 2007 package, the MSP file is in the same directory as the setup.exe.

Our command line is just setup.exe which I assume by default references the MSP file there, the xml is not configured and when it was configured would interfere with it.

The only problem I have with Office 2007 upgrade from 2003 is that the reporting never fully updates when it's finished installing, setting it to reboot itself or not.

#13 SabHaZi

SabHaZi

    Newbie

  • Members
  • Pip
  • 7 posts

Posted 01 February 2011 - 09:05 AM

How do i run the setup for office 2007 EE for the current user? When i run the setup.exe (with .msp)then the setup install office for all users. I only want the current user.

#14 scumi

scumi

    Member

  • Members
  • PipPip
  • 16 posts

Posted 12 May 2011 - 10:03 AM

this my be a little old but for historic reasons we still roll out winxp with sccm... now there is also a office 2007 on it. It is already in the image it self and works fine.

i have 18 different languages to support ,so i only install them according on country code which is based on the computer name - this works. BUT in TS of operating system the log keeps stopping @ "Waiting for job status notification... InstallSoftware 12.05.2011 22:47:15 876 (0x036C)"

I have the following:

<Configuration Product="OMUI.de-de">

<Display Level="None" CompletionNotice="No" SuppressModal="Yes" AcceptEula="Yes" />

<AddLanguage Id="de-de" />

<OptionState Id="OfficeMUI" State="Local" Children="force" />

<Setting Id="Reboot" Value="never" />

</Configuration>

Do i need to turn on completion notification? For single installation it works but not in the TS.

Any help would be appreciated, especially because it will be the same with office2010 i guess... :(

#15 ajbar

ajbar

    Newbie

  • Members
  • Pip
  • 7 posts
  • Gender:Male
  • Location:Woerden

Posted 15 June 2011 - 09:20 AM

I have the following problem with the instalation of the Language packs.

I am using SCCM 2007 R3

Following Scenario.

Installing Office 2010 x86 EN
Instralling project 2010 x86 EN
Installing Visio 2010 x86 EN

With OCT i created a MSP file which i placed in the Update folder.

Created Task Sequence with the following setting.

Install OS (windows 7 x64)
normal OS deployment Sequence.

Install Software:
install Office 2010
Install project 2010
Install Visio 2010

All works well and all 3 packages are fully unattended installed.

Next i want to install the language pack.
It is the dutch language pack.

in the OMUI.nl-nl I edited the config.xml.
The only thing in the XML is:

<Configuration Product="OMUI.nl-nl">
<Display Level="none" CompletionNotice="no" SuppressModal="yes" AcceptEula="yes" />
<!-- <Logging Type="standard" Path="%temp%" Template="Microsoft Office Dutch Language Pack Setup(*).txt" /> -->
<!-- <USERNAME Value="Customer" /> -->
<!-- <COMPANYNAME Value="MyCompany" /> -->
<!-- <INSTALLLOCATION Value="%programfiles%\Microsoft Office" /> -->
<!-- <LIS CACHEACTION="CacheOnly" /> -->
<!-- <LIS SOURCELIST="\\server1\share\Office;\\server2\share\Office" /> -->
<!-- <DistributionPoint Location="\\server\share\Office" /> -->
<!-- <OptionState Id="OptionID" State="absent" Children="force" /> -->
<!-- <Setting Id="SETUP_REBOOT" Value="IfNeeded" /> -->
<!-- <Command Path="%windir%\system32\msiexec.exe" Args="/i \\server\share\my.msi" QuietArg="/q" ChainPosition="after" Execute="install" /> -->
</Configuration>

in the same way i Edited the config files in the PMUI.nl-nl and VisMUI.nl-nl folder.

On a server i created a share called OSD_TS_Source.
The language pack files are in that folder in a subfolder Office2010_LP_Dutch_X86
in the same OSD_TS_Source Folder is a folder Office2010_English_x86, Project2010_English_X86 and Visio2010_English_x86 which contains the files for those products.

In SCCM I created a package called Microsoft Offcie Language pack 2010 x86 Dutch
details as follows:

Data Source:
This package contains source files: \\S114\OSD_TS_Source\Office2010_LP_Duch_X86
Always obtain files from Source Directory

Data Access:
Default values

Distribution Settings
Default Values

Reporting
Default Settings

Security
Default Settings

Distribution Points:
\\S114 (the DP is also the server where the source files are)

created a program:
Office 2010 LP Dutch x86
Command line: setup.exe /config \\s114\OSD_TS_Source\Office2010_LP_Dutch_X86\OMUI.nl-nl\config.xml
Run: Normal (alreaddy tried hidden)
After running: No action required

Requirements:
Default values

Environment:
only when no user is logged on
Drive Mode:
Runs with UNC Name (default)

Advanced:
Suppress programm notifications
Allow this program to be installed from the Software Task Sequence

Windows Installer:
Default values

MOM Maintenance mode
Default values

The same thing i did for the Visio LP and the Project LP

In the Task Sequence i added the 3 packages.

Type: Install Software
Name: Install Software "Office 2010 LP"
Install a single Application
package: Microsoft Offcie Language pack 2010 x86 Dutch
Program: Office 2010 LP Dutch x86

Advertised the task Sequence:
Name: Deploy Windows 7 Standard Workplace
task Sequence :Deploy Windows 7 Standard Workplace
Collection : OSD Bare Metal Deployment
Incluce menbers of subcollection
make this task sequence available to boot media and PXE

Distribution Points:
Access content directly from a distribution point when needed by the running task sequence.

rest of advertisement all default values.

When I PXE boot a machine a select the TS I install the OS.
Joint the machine to the domain
drivers are installed
ConfigMgr is installed and configured
Office is installed
Project is installed
Visio is installed

and then NOTHING !!!!!

when it tries to install the LP it is saying Running Action Install Software "Offcie 2010 LP" and after 2 hours (the maximum run time) it exit with an error code 259
program ran past its maximum runtime. It will be orphaned.

When I logon to the machine and I open a command prompt and type \\s114\OSD_TS_Source\Office2010_LP_Dutch_X86\setup.exe /config \\s114\OSD_TS_Source\Office2010_LP_Dutch_X86\OMUI.nl-nl\config.xml the program start immidiatly and finishes within 3 minnutes and the LP is installed. As far as I can think. The command line is correct in the packages otherwise it would NOT install from a command line.

Am I missing something ??? this is driving me nuts.

#16 ajbar

ajbar

    Newbie

  • Members
  • Pip
  • 7 posts
  • Gender:Male
  • Location:Woerden

Posted 15 June 2011 - 10:57 AM

Little bit more information for the above.
here are some extracts from the logs and the reports.


Report information for report: Advertisement status messages for a particular computer and advertisement

Program started for advertisement "WRD2002E" ("WRD0004A" - "Office 2010 LP Dutch x86").
Command line: "\\s114.ccs.nl\SMSPKGE$\WRD0004A\setup.exe" /config \\s114\OSD_TS_Source\Office2010_LP_Dutch_X86\OMUI.nl-nl\config.xml
Working directory: \\s114.ccs.nl\SMSPKGE$\WRD0004A\ User context: NT AUTHORITY\SYSTEM

The program for advertisement "WRD2002E" ("WRD0004A" - "Office 2010 LP Dutch x86") exceeded the maximum allowed run time of 120 minute(s).
Systems Management Server (SMS) has stopped monitoring the program, and is unable to determine the status of the program.
SMS will not automatically attempt to run this program again. Possible causes: The program might have taken longer to run than expected, or the program might have experienced problems while running.
Possible solution: Make sure the maximum allowed run time specified for the program allows enough time for the program to finish running.
If the program requires user input, ensure the program properties allow the user to interact with the program.

The task sequence execution engine failed executing the action (Install Software "Office 2010 LP") in the group (Install Software) with the error code 2147942659
Action output: ng for job status notification... Waiting for job status notification...
Waiting for job status notification... Waiting for job status notification...
CompleteExecution received CompleteExecution processed Received job completion notification from Execution Manager Installation completed with exit code 0x80070103
Setting TSEnv variable 'SMSTSInstallSoftwareJobID_WRD0004A_WRD2002E_Office 2010 LP Dutch x86'='' GetExecRequestMgrInterface successful Releasing job request,
jobID='{298BA35F-E2F6-480B-8490-44E8D4D1C6D3}' Releasing of Job Request successful CompleteJob successful
Entering ReleaseSource() for \\s114.ccs.nl\SMSPKGE$\WRD0004Areference count 1 for the source \\s114.ccs.nl\SMSPKGE$\WRD0004A\
before releasing Installation failed with error (0x80070103)
Released the resolved source \\s114.ccs.nl\SMSPKGE$\WRD0004ApInstall->Install(sPackageID, sProgramName),
HRESULT=80070103 (e:\nts_sms_fre\sms\client\osdeployment\installsoftware\main.cpp,374) Install Software failed, hr=0x80070103. The operating system reported error -2147024637: No more data is available.

The task sequence execution engine ignored execution failure of the action (Install Software "Office 2010 LP") in the group (Install Software).

Folllowing is taken from the clients ExecMgr log.

Policy arrived for child program Office 2010 LP Dutch x86 execmgr 6/15/2011 12:42:27 PM 1668 (0x0684)
Creating mandatory request for advert WRD2002E, program Office 2010 LP Dutch x86, package WRD0004A execmgr 6/15/2011 12:42:27 PM 1668 (0x0684)
CExecutionRequest::Overriding Service Windows as per policy. execmgr 6/15/2011 12:42:27 PM 1668 (0x0684)
Executing program setup.exe /config \\s114\OSD_TS_Source\Office2010_LP_Dutch_X86\OMUI.nl-nl\config.xml in Admin context execmgr 6/15/2011 12:42:27 PM 1668 (0x0684)
Execution Request for package WRD0004A program Office 2010 LP Dutch x86 state change from NotExist to NotifyExecution execmgr 6/15/2011 12:42:27 PM 1668 (0x0684)
Execution Manager timer has been fired. execmgr 6/15/2011 12:42:27 PM 2300 (0x08FC)
Checking content location \\s114.ccs.nl\SMSPKGE$\WRD0004A\ for use execmgr 6/15/2011 12:42:27 PM 1668 (0x0684)
Successfully selected content location \\s114.ccs.nl\SMSPKGE$\WRD0004A execmgr 6/15/2011 12:42:27 PM 1668 (0x0684)
Executing program as a script execmgr 6/15/2011 12:42:27 PM 1668 (0x0684)
Successfully prepared command line "\\s114.ccs.nl\SMSPKGE$\WRD0004A\setup.exe" /config \\s114\OSD_TS_Source\Office2010_LP_Dutch_X86\OMUI.nl-nl\config.xml execmgr 6/15/2011 12:42:27 PM 1668 (0x0684)
Command line = "\\s114.ccs.nl\SMSPKGE$\WRD0004A\setup.exe" /config \\s114\OSD_TS_Source\Office2010_LP_Dutch_X86\OMUI.nl-nl\config.xml, Working Directory = \\s114.ccs.nl\SMSPKGE$\WRD0004A\ execmgr 6/15/2011 12:42:27 PM 1668 (0x0684)
Created Process for the passed command line execmgr 6/15/2011 12:42:28 PM 1668 (0x0684)
Raising event:
[SMS_CodePage(437), SMS_LocaleID(1033)]
instance of SoftDistProgramStartedEvent
{
AdvertisementId = "WRD2002E";
ClientID = "GUID:E1D09EFE-6000-4F6E-85A5-F4EFD5C8874A";
CommandLine = "\"\\\\s114.ccs.nl\\SMSPKGE$\\WRD0004A\\setup.exe\" /config \\\\s114\\OSD_TS_Source\\Office2010_LP_Dutch_X86\\OMUI.nl-nl\\config.xml";
DateTime = "20110615104228.485000+000";
MachineName = "TESTLAPTOP";
PackageName = "WRD0004A";
ProcessID = 1512;
ProgramName = "Office 2010 LP Dutch x86";
SiteCode = "WRD";
ThreadID = 1668;
UserContext = "NT AUTHORITY\\SYSTEM";
WorkingDirectory = "\\\\s114.ccs.nl\\SMSPKGE$\\WRD0004A\\";
};
execmgr 6/15/2011 12:42:28 PM 1668 (0x0684)
Raised Program Started Event for Ad:WRD2002E, Package:WRD0004A, Program: Office 2010 LP Dutch x86 execmgr 6/15/2011 12:42:28 PM 1668 (0x0684)
Program exit code 259 execmgr 6/15/2011 2:42:28 PM 3008 (0x0BC0)
Looking for MIF file to get program status execmgr 6/15/2011 2:42:28 PM 3008 (0x0BC0)
Program ran past its maximum runtime. It will be orphaned execmgr 6/15/2011 2:42:28 PM 3008 (0x0BC0)
Raising event:
[SMS_CodePage(437), SMS_LocaleID(1033)]
instance of SoftDistProgramExceededTime
{
AdvertisementId = "WRD2002E";
ClientID = "GUID:E1D09EFE-6000-4F6E-85A5-F4EFD5C8874A";
DateTime = "20110615124228.769000+000";
MachineName = "TESTLAPTOP";
MaximumTime = "120";
PackageName = "WRD0004A";
ProcessID = 1512;
ProgramName = "Office 2010 LP Dutch x86";
SiteCode = "WRD";
ThreadID = 3008;
};
execmgr 6/15/2011 2:42:28 PM 3008 (0x0BC0)
Raised Program Exceeded Time Event for Ad:WRD2002E, Package:WRD0004A, Program: Office 2010 LP Dutch x86 execmgr 6/15/2011 2:42:28 PM 3008 (0x0BC0)
Execution is complete for program Office 2010 LP Dutch x86. The exit code is 259, the execution status is Unknown Status execmgr 6/15/2011 2:42:28 PM 2020 (0x07E4)
Execution Request for package WRD0004A program Office 2010 LP Dutch x86 state change from Running to Completed execmgr 6/15/2011 2:42:28 PM 2020 (0x07E4)

#17 Peter van der Woude

Peter van der Woude

    Advanced Member

  • Moderators
  • PipPipPip
  • 2,272 posts
  • Gender:Male
  • Location:The Netherlands

Posted 15 June 2011 - 04:15 PM

Did you try the command by hand (so without SCCM)?

My Blog: http://www.petervanderwoude.nl/
Follow me on twitter: pvanderwoude


#18 ajbar

ajbar

    Newbie

  • Members
  • Pip
  • 7 posts
  • Gender:Male
  • Location:Woerden

Posted 16 June 2011 - 04:54 AM

Did you try the command by hand (so without SCCM)?


When I logon to the machine and I open a command prompt and type \\s114\OSD_TS_Source\Office2010_LP_Dutch_X86\setup.exe /config \\s114\OSD_TS_Source\Office2010_LP_Dutch_X86\OMUI.nl-nl\config.xml the program start immidiatly and finishes within 3 minnutes and the LP is installed. As far as I can think. The command line is correct in the packages otherwise it would NOT install from a command line.

Yep...i dit try to run it manually :) and that works like a charm. With machine in the above i mean the client :)

#19 Peter van der Woude

Peter van der Woude

    Advanced Member

  • Moderators
  • PipPipPip
  • 2,272 posts
  • Gender:Male
  • Location:The Netherlands

Posted 16 June 2011 - 06:20 AM

I think it has something to do with the location of your config.xml...

Command line: "\\s114.ccs.nl\SMSPKGE$\WRD0004A\setup.exe" /config \\s114\OSD_TS_Source\Office2010_LP_Dutch_X86\OMUI.nl-nl\config.xml
Working directory: \\s114.ccs.nl\SMSPKGE$\WRD0004A\ User context: NT AUTHORITY\SYSTEM

Why are you not calling it from the package?

My Blog: http://www.petervanderwoude.nl/
Follow me on twitter: pvanderwoude


#20 ajbar

ajbar

    Newbie

  • Members
  • Pip
  • 7 posts
  • Gender:Male
  • Location:Woerden

Posted 16 June 2011 - 07:14 AM

I think it has something to do with the location of your config.xml...

Why are you not calling it from the package?



Am I not calling it from a package ?

In SCCM I created a package called Microsoft Offcie Language pack 2010 x86 Dutch
details as follows:

Data Source:
This package contains source files: \\S114\OSD_TS_Source\Office2010_LP_Duch_X86
Always obtain files from Source Directory

Data Access:
Default values

Distribution Settings
Default Values

Reporting
Default Settings

Security
Default Settings

Distribution Points:
\\S114 (the DP is also the server where the source files are)

created a program:
Office 2010 LP Dutch x86
Command line: setup.exe /config \\s114\OSD_TS_Source\Office2010_LP_Dutch_X86\OMUI.nl-nl\config.xml
Run: Normal (alreaddy tried hidden)
After running: No action required

Requirements:
Default values

Environment:
only when no user is logged on
Drive Mode:
Runs with UNC Name (default)

Advanced:
Suppress programm notifications
Allow this program to be installed from the Software Task Sequence

Windows Installer:
Default values

MOM Maintenance mode
Default values






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

Locations of visitors to this page