Now with deployment I did make a little fib. There is a sixth Scenario. That ‘s when you Deploying a Microsoft Office application. It’s not that it’s hard but it’s far better in a special way. Since it is probably one of the most common applications you may deploy, MDT 2010 has special attention paid to it for specifically Microsoft Office to allow for as seamless and as CUSTOMIZABLE install as possible.
Office 2007 / Office 2010
With Office 2007 / 2010 this is done by way of the “Office Customization Toolkit” . Typical VL (Volume License) Media will have this preinstalled into it as will Enterprise editions.
You can confirm if your version of Office has the kit built in (On 2007 / 2010) by checking the Root of the media for a folder called “Admin”
If it does you’re good to go. If however it does NOT you’re still not out of the game. It just means you have to download it via way of the “2007 Office system Administrative Template files (ADM, ADMX, ADML) and Office Customization Tool version 2.0“ for Office 2007 or the “Office 2010 Administrative Template files (ADM, ADMX/ADML) and Office Customization Tool”.
Simply download the appropriate version for your version of Office, and in the case of the Office 2010 the 32bit or 64bit to match your particular media. Double click and extract the contents to a folder. Within these extracted contents you will find a small group of folders (Your Group Policy Templates for that particular version of Office) and the much needed Admin folder.
Simply copy the Admin folder to the root folder structure of your media. If of course you are using DVD media, you’ll want to copy it to a folder on the hard drive FIRST and of course copy the Admin folder to THAT root folder structure. (See Example Visio 2010 Media without and with folder added)
Once your Media is prepared, import it into MDT 2010 into an appropriate folder destination in MDT 2010 as you would any other application with Source Files. Once it has been added in, you can right click on the properties of your Office install in MDT 2010 and see a new tab called “Office Products”
This is unique to Office 2010 / 2007 and is your one stop shop when getting that Office deployment automated. Clicking on the tab will present us with a screen with some new options of course and a few extra buttons. We’ll go over the screen options after. Right now we’re interested in that big beautiful button in the lower right hand corner called “Office Customization Tool” . Clicking on that will launch the “Office Customization Toolkit” for that particular version of Office.
Unlike most of MDT, the OCT will require local Administrative rights to run. If you run WITHOUT the Administrative rights you’ll get a weird MMC snapin error possibly and after it pukes out, it will indicate WHY it puked out. (It’s my blog, I’m allowed to say “puked”, so nyeah nyeah) The actual OCT interface is identical to both versions. When you click on it you will be prompted with a message indicating where you need to save the .MSP file. This will be within the folder structure of your Deployment Point like so….
As the OCT interface appear you will be prompted to create a new configuration file or open an existing one. If you have already customized your Office install prior to this you can open up an existing MSP file for it. Right now we’re creating a new one.
The Actual interface for OCT is pretty simple. A list of options on the left and things to fill in on the right.
There are typically a few that most of us will be interested in.
Install location and organization name
Where you do want Office to install and what Company name would you like prepopulated in the Organization field?
Licensing and User Interface (KMS and MAK license keys ONLY)
What product key do you want in this product automatically upon install? Do you want to PRE accept the End User License Agreement so the user ISN’T prompted on install? What display level for the application? Full (everything under the sun) Basic (A simple progress bar) or None (Voodoo magic happens in the background and nobody sees anything!)
Three additional options are.
on notice (Yes I do want to see a little ‘I’m done everything’ displayed on the screen) If you want a truly silent install, don’t check this off. The user will have to click on something to continue
Suppress Modal (Don’t show me any errors, if it fails, it fails)
No Cancel (Nobody is allowed to cancel (except Administrators that are trigger happy on the Task Manager and MSIEXEC)
Remove previous installations
By default it will remove all prior versions of that particular Office product. But you CAN customize things so that say you have Access 2003 left behind instead of behind overwritten with Access 2010. Here is where you at least say “Don’t erase the old one or ONLY erase the following ones
Set feature installation states
Expand this and you have our old familiar “What options am I installing” Office interface upon setup. This is EXACTLY what you think it is. Choose what you want or don’t want (Including which Applications you don’t want)
Administrators will love this. I swear I don’t know how many times I’ve encountered somebody complaining that “Because there is no Shortcut to Word on their desktop it was never installed”. If you encounter that situation, this is your chance to put that INTO the actual installation.
There are a pile of other options in the OCT but there are other articles that dedicate better time to it (or perhaps I’ll write one later). For now, we have our “Quick and Dirty” explanation of OCT. Now click on “File / Exit”, the “X” in the upper right hand order or even “ALT-F4” if you feeling like a Keyboard Guru. It will ask you where to save the MSP file. Just remember the box that popped up BEFORE you started all of this. The OCT will NOT default to the folder containing your Install media in the Deployment point (I personally think it should). Save the file with any name you choose in the office folder called “updates” for your version of Office.
Keep in mind that if you want MULTIPLE versions of the MSP file in the Updates folder you will have to specify them in your SETUP.EXE when calling Office up. By default, SETUP.EXE will apply whatever MSP file it finds in the Office Updates folder.
When you click on the “Office Products” tab you’ll notice several fields I had you ignore last time. This is because the OCT eliminates the need for them with it’s more secure MSP file format. But as I mentioned before, copies of Office using MAK or KMS keys (Typically Enterprise / Volume License) are the only ones that can have their Product key in the MSP file. This is a FEATURE of getting the better version (enhanced security).
But you CAN still use this tool in a Small to Medium size business setup. Just click on the pull down menu beside “Office product to install” and change it from “<Let Office Setup decide> . Our new options are available under CONFIG.XML settings.
If your media supports more than one language, which one? Check off the box or boxes that apply
Your 25 digit product key. If you are running an MAK or KMS version, DO NOT ENTER THIS HERE, use OCT to store it INSTEAD.
The default Company name Office should contain
Just like in OCT. None, Basic or Full. Works the exact same way
Pre accept the End User License Agreement for the user so they don’t get pestered with it upon install
An interesting option. This allows you to store the INSTALL MEDIA on the workstation without installing Office. Handy (I guess) if you want to spend the time dumping files on a local computer.
Always suppress reboot
Don’t let the computer reboot on Office install. This is an important option in case something decides to make the computer reboot. This ENSURES Office installs 100% and a reboot only happens AFTER it’s done installing
Click Ok and you’re done. That particular Office product should now just launch if you run SETUP.EXE (No additional parameters needed by default)
Here’s a small piece I ran into as well. If you want to leverage features of the OCT with a Retail or OEM product it will work, but just make sure you DON’T fill in anything under “Licensing and user interface”. Also if you go to edit an existing MSP file and click on the license key field, you WILL have to rekey in that field. That is INTENTIONAL so that people don’t try to pull out the license key if they get their hands on the .MSP file.
Now if you have an OEM or RETAIL install you have a few things to remember. You MUST remove the license key AFTER install. Having said that we can make this happen. Within Office 2010 it’s incredibly easy as Microsoft has supplied a vbScript application called OSPP.VBS (By default under your Microsoft OfficeOffice 14 Directory)
Double click on this file to launch the instructions on how to use it (Built in). Executing a
CSCRIPT.EXE OSPP.VBS /unpkey:AAAAABBBBBCCCCCDDDDDEEEEE
(Assuming of course that THAT is your 25 digit product key) will remove it from the Registry so the next time Office is installed it will prompt for the key. But there’s also TWO cooler options
CSCRIPT.EXE OSPP.VBS /inpkey:ZZZZZYYYYYXXXXXWWWWWVVVVV
will replace an EXISTING Office Product key with a new one and better yet
CSCRIPT.EXE OSPP.VBS /act
Will activate your Office products with whichever predetermined activation server you have (Default internet)
With Office 2007 you have to remove the subkeys under a Registry key (HKLMSoftwareMicrosoftOffice12.0Registration) which removes ALL your License keys for Office 2007. I’m not certain this is a supported solution either but it’s good to know if you do HAVE to change the Office 2007 Product key. Upon the first launch of Office you will be prompted for the new Product key.
Microsoft Office 2003
If you need to deploy Office 2003 it’s a similar process but you need to download the “Office 2003 Editions Resource Kit Tools” – It provides a similar interface to customizing ANY Office 2003 install.
Once installed you’ll find it under your “Microsoft Office Tools” there will be an entry called “Microsoft Office 2003 Resource Kit”. Just select the option “Custom Installation Wizard”.
This is a simple step by step wizard. Click Next, Browse to the .MSI file from your Office install (typically off the root of your Office 2003 install media). You will be asked to created a NEW MST (Windows Installer Transform) file or open an existing one. Let’s create a new one to start. Just give it a name you’ll remember. At this point it’s very similar to the OCT except it’s a Step by Step prompting Wizard as opposed to a navigable menu system. Even the options.
The biggest part will be that running setup.exe does
NOT default to a silent install. For this you must supply a command line Parameter. When you’re done with the “Custom Installation Wizard” it will supply you a sample one based upon your present location.
setup.exe TRANSFORMS=".CustomOfficeInstall2003.mst" /qb-
Drop this into the entry for “Quiet Install Command” and you’re on way to a silent install of Office 2003 to boot
Next time we’ll look at getting those Service Packs and Additional Packages into the MDT 2010 environment