How Can I Deploy Office 2013 using WDS?

How can I deploy Office 2013 Standard (32-bit) using Windows Deployment Server? We have a server available with Windows Server 2008 as its OS. We have about 130 Windows 7 machines. Some are 64-bit, some are 32-bit. Most have Office 2007 (a small number have Office 2010) which needs to be removed. Some are workstations, but most are laptops. We want to get this thing going in the next week or so. Thanks in advance for any assistance.
Bassman20122Support TechnicianAsked:
Who is Participating?
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.

Vasil Michev (MVP)Commented:
WDS is a different story, unless you have a capture image in mind.

Here's the deployment guide from MS:
Cliff GaliherCommented:
WDS is used to deploy an entire Windows operating system. You don't use it to deploy individual software packages. So unless you were planning on reformatting and installing Windows on all 130 machines, both 32 and 64 bit, with all of the various drivers, all starting in the next week, I don't think you want WDS.

Don't get me wrong. WDS is a great tool. And may be worth your time for that many machines down the road if you are a big proponent of desktop standardization. Just not the right tool for THIS job.

Unfortunately Office 2013 doesn't deploy well with GPSI either. You are really looking at deploying through a script and then having the script run via GP (a rather kludgy workaround) or using higher end deployment tools that supports BITS and similar bandwidth friendly technologies.

Tools like SpecOps Deploy, System Center Configuration Manager, or Kace all come to mind. But all come with a price-tag of varying degrees based on their feature sets. For 100+ desktops, I think there is value in System Center 2012 for a variety of reasons, so that'd be my recommendation, but that is only a suggestion after all.


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
Bassman20122Support TechnicianAuthor Commented:
Thank you vasilcho and cgaliher. It seems pretty clear that WDS is out of the question. I looked at the price of some of the solutions cgaliher suggested and, wow, they are not cheap! At the risk of going off topic, could either of you recommend a less expensive, perhaps open source, tool that could be used?

Thank you
Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

Cliff GaliherCommented:
There really aren't any open source solutions. Distributing software to multiple machines just isn't a home or home-office task, and enterprise management tools cost money. Even in the open-source world, no significant web-hosting company runs Linux without a big (and expensive) support contract like Red Hat Enterprise.

As I said, you can do this for free if you want to get your hands dirty. That means writing a script that installs at startup or logon. But too many machines starting up at once or users logging on at the same time (not uncommon for professional 9to5 businesses like legal firms) and your network gets hammered. The office deployment pages already linked to outline those options.

For 20-50 PCs, I recommend SpecOps Deploy myself. The cost per desktop is relatively small.

For 50-200ish, System Center is not a bad option. The server pricing is high, but the desktop MLs aren't bad and at that size you usually will benefit from the other non-deployment options as well.

Above 200, SC is still a good choice, but if you have specialty needs like LOB, then additional 3rd-party options also become worth considering, like Kace.

The trick is to break out the cost per desktop when looking at the solution price. You are already spending hardware, OS, antivirus (hopefully) and an Office license (since you are deploying it), so your per desktop cost is already pushing $1k+. What is reasonable to manage that. 10%? 15%? When you start doing ROI calculations from that perspective, these solutions aren't as expensive as that initial pricetag may seem.

James HaywoodCommented:
Look at MDT (Microsoft Deployment Toolkit). This is designed to allow full deployment of OS, Apps, Drivers etc but can be used just for a single application.

This article shows how to do what you want but using Office 2010. There may be some slight differences for 2013 but the basics are included.

MDT is also free!
Bassman20122Support TechnicianAuthor Commented:
Thanks cgaliher. You provided food for thought. I'll present these options to the client to see what they say. If history is a guide, however, they'll probably want us to investigate the solution suggested by hhaywood000 (thanks BTW). I'll let you know how things end up.

Peace everyone,
Bassman20122Support TechnicianAuthor Commented:
Just wanted to update people on what's happening so you don't think I've dropped the issue... As is typical, we're waiting for a response from the client. The non-official feedback is that they're leaning towards MDT.

Thanks for your patience.
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
Microsoft Office

From novice to tech pro — start learning today.