asked on

How to deploy Office 2007 over the network without buying SMS or similar software

It's been answered over and over that GPO is not the right solution for Office 2007 deployment. And if you get to make it work, this works with some limitations and quirks. BDD 2007 deploys Vista + Office but not Office by itself. Does Mircorsoft expect you to buy SMS or similar to network deploy Office 2007???

I'm upgrading computers that received Office 2003 via GPO, so I can uninstall them the same way.

I have found lots of TechNet doc about this subject but haven't come accross one that shows a step by step process to achieve this.

NJDEV1

You could try using PSExec, but you'd probably have to use a text file with machine names in it. then run a command that uses an Office MSP file for the install configuration.

http://technet.microsoft.com/en-us/sysinternals/bb897553.aspx

xperttech

ASKER

So, there is not such a thing as open software to inventory and push Office 2007 in a controlled way?

matrixnz

Why not use a Computer Startup Script in Group Policy, basically create your custom MSP file using:
setup.exe /admin

Than in the Startup Script have something like

If Exist "%ProgramFiles%\Microsoft Office\Office12\Outlook.exe" Goto End
Goto Install

:Install
\\SERVER\SHARE\Setup.exe /adminfile YourMSPFile.MSP

:End

Cheers

xperttech

ASKER

Matrixnz: Why not? Because we want to be able to "manage" the install later on as new updates/patches appear, which you know are a lot.
We are considerin ALTIRIS (Now Symantec) CLIENT MANAGEMENT SUITE if we have to purchase the software. Any thoughts, suggestions?

ASKER CERTIFIED SOLUTION

matrixnz

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

SOLUTION

NJDEV1

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

xperttech

ASKER

My issue with the script install (after the GPO remove of Office 2003) is that there is no way to track the installs and know if all succeeded. When you have 50+ workstations to handle this becomes an issue.