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.
LVL 5
xperttechAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

NJDEV1Commented:
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
0
xperttechAuthor Commented:
So, there is not such a thing as open software to inventory and push Office 2007 in a controlled way?
0
matrixnzCommented:
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
0
The Five Tenets of the Most Secure Backup

Data loss can hit a business in any number of ways. In reality, companies should expect to lose data at some point. The challenge is having a plan to recover from such an event.

xperttechAuthor Commented:
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?
0
matrixnzCommented:
Hi xperttech

Understand, personally I've always found WSUS best for patches updates etc...

Cheers
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
NJDEV1Commented:
Matrixnz's solution makes sense. You could implement WSUS, which is free to manage updates but for initial deployment use the setup.exe /admin to create an MSP. Also you can extract MSP's from Office hot fixes and put them in the Updates folder of Office 2007. They will get installed along with Office.
0
xperttechAuthor Commented:
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.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Software

From novice to tech pro — start learning today.