Install package Office 2007 sp1

kkelley · 07-02-2008, 11:30 AM

When I run the job I get this error "Setup cannot find the required setup controller file. Either are network error, error reading from cd, dvd, other installation media or problem with package you downloaded"

I have run setup /admin and created offcie2007.msp file. I placed that file in updates folder.

I extracted sp1 and placed the files in the updates folder.

Created a job with path to setup and used /adminfile office2007.msp

I do get the error when I try and finish the job that "The specified d:\msoffice2007\setup.exe doesn't appear to be a valid RapidInstall or PC Transplant package" Do you want to contine I say yes.

When I run the job the error I mentioned first comes up asap.

jenifer.arnold · 07-02-2008, 12:20 PM

I would use a Run Script task instead of a Distribute Software task...

kkelley · 07-02-2008, 01:22 PM

Yes I just tried that. On first screen I put setup /adminfile office2007.msp in the run this script box. Scripting OS windows. On the next window I checked off On the client computer. And checked off pre=boot.

It boot to automation, client reboots, goes through PXE and then reboots again, goes throug pxe, and then hangs the 2nd time thru pxe. Not always same spot but this time at Initializing tcp/ip

skedens · 07-02-2008, 01:44 PM

Why are you installing Office in a preboot environment? I would uncheck preboot and give it a shot.

kkelley · 07-02-2008, 02:44 PM

Well I am running out of options to get this to work. I believe the 'run script' is the way to go but how hard is it to execute "setup /adminfile office2007.msp"

Do you think I need to look at the xml file???

The one thing I can tell you is to make sure the .xml file is also part of the files being copied. You may have to pass the .xml file on the command line. That seemed to be one item in common from all the consultants.

jenifer.arnold · 07-02-2008, 03:17 PM

When you create your Run Script task, use the second option called Run this script. In the box, put the command line you would run from a DOS prompt (put all of your switches in this window). The script operating system should be set to Windows. On the next screen, change the security context to an account that has access to the share where the install files are and that is also administrator on the local machine. Then click Finish.

I am attaching a picture of my Office 2007 install task.

kkelley · 07-03-2008, 09:33 AM

Thank you.

So I followed directions and used \\lofs1\msoffice2007\setup.exe /adminfile \\lofs1\msoffice2007\updates\office2007.msp

Assigned local adminsitrator.

When I run the script you can se the job start on the client but then it stops and DS gives "error 30059 during script execution"

kkelley · 07-07-2008, 02:01 PM

Well I am still getting error messages. I edited the config.xml file and the error 30059 now is 30066 error during script execution.

kkelley · 07-07-2008, 02:10 PM

I mean setup starts on target machine and then gives error 30066. Setup only stays up for 4 or 5 seconds.

ztruelove · 07-07-2008, 03:05 PM

A quick Google search of that error code shows that it is a prerequisite check failure. Possibly not enough free drive space? Turn on logging during the install?

Error message when you try to upgrade 2007 Office programs, Expression Web or Windows SharePoint Services 3.0 to the Service Pack 1 level if the Windows system drive has insufficient free disk space: "The installation of this package failed"

kkelley · 07-07-2008, 03:08 PM

thx Z I found that search but the drive has 27gb available, only needs 2gb.

kkelley · 07-29-2008, 01:04 PM

Well I did as suggested and made sure the share folder on the server and the local computer both had same security ID. In both cases I used a local user.

So the script actually starts on local PC but then just stops. Office 2007 install window comes up saying checking for files, then quits. DS gives error 30066 during script execution. Can't find much info on that error.

I have been at this for weeks.

1. I have copied Office 2007 to DS share.
2. In the updates folder I have created an msp file
3. Then run the command \\servername\msoffice2007\setup.exe /adminfile \\servername\msoffice2007\updates\office2007.msp

I would be so grateful if someone could sove this for me.

jenifer.arnold · 07-29-2008, 01:09 PM

At the end of the command, include /log c:\office2007.log.

Run the job on a test machine. Post the resulting log file here, please. The log file will be on the test machine.

kkelley · 07-29-2008, 01:17 PM

Wonder if it thinks that is a bad command.

When I add /log c:\office2007log

A setup control window comes up with all the switches you can use for install

jenifer.arnold · 07-29-2008, 01:35 PM

Was there a switch for producing a log file? Use that instead of what I typed.

kkelley · 07-29-2008, 02:08 PM

I am not sure what you mean. I did go into group Policy, Windows insttaller and turn on logging. But no log is created. Still dos window pops up with above script command, then closes.

jenifer.arnold · 07-29-2008, 03:12 PM

I looked around and you can still use that /log filename.log switch with the Office 2007 install. Make sure you typed it correctly.

snapdad · 10-09-2008, 02:14 PM

I just ran across this today. Office 2007 saves a log file by default to the %temp% directory.

This is from Microsoft TechNet:

Quote:

Typically, you do not need to customize logging options. By default, Setup creates a standard log file and saves it as a text file in the %Temp% folder on the user's computer. If an installation fails, Setup creates a verbose log file, starting with the package that caused the failure, in the same location. To change logging options, open the Config.xml file in Notepad and modify the <Logging> element.

Customize Setup before installing the 2007 Office system

mike_plichta · 12-22-2008, 02:53 PM

I find that if you create a script that is a list of "DOS" commands, the script will fail if you do not run it as a specific user. Using the system account does not work. If anyone knows how to do this using the system account, please let me know.

I posted a first attempt at doing this here, but have refined it considerably. See the following post for a good method to do this.

mike_plichta · 12-22-2008, 04:47 PM

This method not only installs office, but gives altiris a notification of when it's done and reboots the system. If you copy a .cmd file to the local machine, and then run that to do the install, the script will not "finish" until office 2007 setup is done.

First, I've assumed you have run the setup.exe /admin command to create the answer (msp) file.

Second, create a office2007.cmd file that has the following in it.

\\x.x.x.x\sharename\setup.exe /adminfile "\\x.x.x.x\sharename\mycustom.msp"

Next, create an altiris job to copy this to c:\office2007.cmd

Next, do a run script job with inline script as follows:

c:\Office2007R.cmd
del c:\tools\Office2007R.cmd
shutdown /r /t 01

This will call office2007r.cmd which installs office, but it will not run instruction 2 until 1 is finished. When office 2007 setup finishes, it will delete the cmd file and then restart the computer. Only then will altiris say the script is finished.

Be sure you run the "script" task as a specific user. It will not work if you leave it as the system account.

Pacman_1905 · 03-26-2009, 02:09 AM

Hi All

Im new to Altiris and I'm probably jumping in a little to deeply here but I would like to test a rollout of Office 2007 Professional using Software Delivery.

The problem Im running into is that all our machines on our network have Office 2003 installed. I would like to upgrade them to Office 2007. I have made a .MSP customisation file using the setup.exe /admin switch. When I try to run the setup.exe /adminfile <customisation.msp> I get a message stating that the "command-line option can be used only during the initial installation of the product"

I assume its because it has Office 2003 already installed? Right?

If so how can I simply just upgrade Office 2003 to Office 2007. Surely it cannot be this difficult!

Anyone have any ideas?

Thanks

Nick · 03-26-2009, 08:50 AM

Pacman,

Have you tried running that command line manually on a system with Office 2003 installed on it? If so did you get the same error?

jharings · 03-26-2009, 09:29 AM

The .msp (I believe) is just designed to patch an existing install. You will need either a .mst or the .xml file available in 2k7 to do the upgrade.

mike_plichta · 03-26-2009, 11:48 AM

"I get a message stating that the "command-line option can be used only during the initial installation of the product"

-This error only happens when you've already installed office 2007 on a computer. It makes me think that you did a test install of office 2007 on your computer manually, then uninstalled so you could test it using the msp method.

Inside the admin file, you can choose if you want to remove or keep the old version of office. All our office upgrades from 2003 to 2007 worked fine using the msp file and we did not recieve this error message.