Solved

Application Deployment - Simple

Posted on 2013-05-10
7
662 Views
Last Modified: 2013-12-12
Need assistance with how to deploy various versions of MS Office in network.  
Using Active Directory on Server 2000!  

Where I am Stuck:
How do I apply updates to Office before deployment?
How do I set-up group policy so that every instance of MS Office I assign to an employee will load on their machine?

Scenario:
Virtual Machine Windows 7 environment
Will make all applications part of base image except 3 versions of Office.
Want to be able to easily deploy any of our already purchased versions of MS Office with updates applied (XP Standard, 2003 Standard, 2003 professional, 2010 Professional, 2013 Standard, 2013 Professional) to the appropriate user.
Will be using Persona Management on these machines.
0
Comment
Question by:Robert Mohr
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
7 Comments
 
LVL 76

Expert Comment

by:GrahamSkan
ID: 39205347
Hi,
I have no experience as an administrator, but in maintaining my own system, I have learnt that merging updates into an installation package is called slipstreaming. I did it with
Windows 2000 when a hardware problem necessitated frequent rebuilds.

Googling  'slipstream office 2003 sp3' produces several how-to hits. I guess that would apply to the other versions.
0
 
LVL 40

Accepted Solution

by:
Vadim Rapp earned 400 total points
ID: 39205358
Office XP and 2003 you can deploy by group policy. In a nutshell, the way it works is: you run Office Customization Wizard, and specify installation options, such as product key, which products to install, which not, whether you want to install things like Office Assistant and smart tags, etc. This creates a transform. You create administrative image of the installation; you patch it with service packs; then you deploy  by the group policy the MSI from that image plus the transform. Up to you whether to do it per-machine or per-user, assign or publish. I personally publish per-user, plus install-on-demand will auto-install what's needed whenever someone tries to open .doc, .xls etc. More info at http://technet.microsoft.com/en-us/library/cc180015.aspx

Microsoft also gives you group policy templates where you can specify your preferences for the applciations already at runtime, for the users. Such as, you can specify workgroup templates directory on the network, where everybody will find company-wide templates, so your employees will have something like this:start new document . Plus many other things for various Office applications.
group policyIn Office 2007 and later the deployment has changed, and group policy deployment became discouraged (in 2007) and then impossible (2010). Now the wizard creates an XML file with all customizations, and that xml file is used by setup.exe. Accordingly Technet has novel-size articles like "Deploy Office 2010".
0
 
LVL 40

Assisted Solution

by:Vadim Rapp
Vadim Rapp earned 400 total points
ID: 39205406
For the users of Office 2003 and XP, you'll probably also want to install Compatibility Pack, so they should be able to open .docx and .xlsx files sent to them by others.
0
 
LVL 28

Assisted Solution

by:Ryan McCauley
Ryan McCauley earned 100 total points
ID: 39205821
You can set up your base image without Office, and then fully patch the base image so it's ready to go. You'd then take the image and get it ready to deploy.

You can then extract each version of office to its own network folder and then slipstream updates into each version. This is the common way to apply patches to an installation before you actually install it - that way, the newly installed version is already current, and you can apply new service packs to your slipstream folder as they're released. Here are some basic instructions:

http://www.onecomputerguy.com/install/office_slipstream.htm

I've never used Persona Management to deploy user-specific images, but you could set up an unattended install script for each version of office, and then pick the correct version based on what they need and apply it to your recently built-from-image workstation.
0
 

Author Comment

by:Robert Mohr
ID: 39209268
Awesome!  Thank-you all.  This is a huge help!
0

Featured Post

Create Professional Looking Email Signatures

Create "Professional HTML Email Signatures" with ease.
7 Day Money Back Guarantee if not 100% Satisfied.
Affordable - Try it out for 7 Days Totally Risk Free.
Installers provided for over 45 Email clients.
Both Windows & MAC Supported.
Highly Recommended!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Recently, Microsoft released a best-practice guide for securing Active Directory. It's a whopping 300+ pages long. Those of us tasked with securing our company’s databases and systems would, ideally, have time to devote to learning the ins and outs…
Auditing domain password hashes is a commonly overlooked but critical requirement to ensuring secure passwords practices are followed. Methods exist to extract hashes directly for a live domain however this article describes a process to extract u…
This Micro Tutorial hows how you can integrate  Mac OSX to a Windows Active Directory Domain. Apple has made it easy to allow users to bind their macs to a windows domain with relative ease. The following video show how to bind OSX Mavericks to …
With the advent of Windows 10, Microsoft is pushing a Get Windows 10 icon into the notification area (system tray) of qualifying computers. There are many reasons for wanting to remove this icon. This two-part Experts Exchange video Micro Tutorial s…

739 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question