Hi Hodkinsons,

At first glance, just issuing a "setup.exe" will not deploy your scripted install.  The command line should look something like:

setup.exe /adminfile file.msp

Ideally, you will use a full path to the MSP file.

As for using a package to remove previous versions of Office 2003, this shouldn't be needed if you chose to uninstall from the scripted install.  Of course, there may be instances where this doesn't work, but usually if that is the case it will require a hand uninstall.

In our environment, we had Office 2003 virtualized in XP, so removal was a snap, we only needed to Deactivate and Delete the layer.

Hope this helps.

The setup file does run from this location manually, but not if I use setup.exe /adminfile.msp from a run command, as mentioned before I thought it would automatically call the MSP file from the update folder but it doesn't seem to.

I think my first problem here is that it is not finishing downloading the package to the machine and so it's not getting as far as the install part, are there any restrictions which might be causing it to stop the download?

Thanks

It should match.  From the agent, find the GUID of the download package, then browse to it at C:\Program Files\Altiris\Altiris Agent\SoftwareManagement\Software Delivery\{GUID}\cache

The files here should match what's on the package server, which should match what the server has, which should match what you uploaded.

If the download hasn't finished, it should not have started the install task on the workstation.  The install only starts if you've downloaded all the files.  Can you compare the files you see in this local cache to what you should have?  When you do this, from the local \cache\ folder, you could double-click setup.exe (which does reference the .MSP automatically) or run the command locally (setup.exe /adminfile Updates) to see if this provides additional feedback.

If you suspect the local download is bad, you can always try the source files on the same system.

Below is the command line used to run this successfully, it was a matter of calling the config.XML file for the version fo Office we wanted to install, in this case standard. See below

\\servername\software\Microsoft Office 2007\setup.exe /config "\\servername\software\Microsoft Office 2007\Standard.ww\config.xml" 

Thanks for your help guys as always discussing helps to work through these things

After discussing how we are going to do this it has become apparent that some of our client machines have Office 2003 Pro and some have standard.

We are going to deploy Office 2007 Standard and want to remove any components of 2003 pro in the process. Will this happen automatically during the upgrade? Or can\will we need to then run a seperate uninstall command for the 2003 pro version?

I'm installing with a distribute software job that just runs setup.exe. If you created the msp to be silent and remove previous versions and you put the Updates folder that will work just fine. The one thing you might be missing is to set the task to run directly from the file source. This will eliminate the need to download the entire Office install before launching the install.

It's a task type in DS 6.x.  What version of DS are you using?

In v7 you'd create a software resource, add all the Office files to the package, set setup.exe as the Installation file, create install command lines that run setup.exe, then create a Quick Delivery Task (does not pay attention to detection rules, applicability, etc) or a Managed Software Delivery policy (a policy that checks these rules and makes sure the software stays installed on a schedule you specify).  DS doesn't really factor in here.

Does this help?