Posts Tagged rebuild
The Build Disc – Part 5b (Extras – Office 2003)
Posted by David in Build Disc, Unattended Installs on April 8th, 2009
A fully standardised install only takes us so far. At some point you have to cater to the stuff that doesn’t fit in with the standardised stuff. This article is about the extra bits that help Office 2003.
What do I install? Pretty much just the file format converters to allow Office 2003 to read files created with Office 2007.
(As an aside, the Office viewers normally only open Office 2003 files but if you install them and then install the converter, they will also read Office 2007 files.)
I’ve worked out an unattended install but for only one install it’s not really all that relevant.
For what it’s worth, this is the unattended install command:
Office2003-FileFormatConverters.exe /quiet /passive /norestart
This article is part of a series dealing with my standard system build. It starts with this article and the post you’re reading now is directly related to this one.
The Build Disc – Part 5a (Extras)
Posted by David in Build Disc on April 7th, 2009
A standard install is all very well but you reach a point, at least at the home user/small business level, where standardization falls down. Not every computer is going to have the same version of MS Office installed (or even have Office), some computers will not already have Acrobat Reader (or have an older version pre-installed).
Having already dealt with service packs, Windows/Microsoft Updates and standard utilities, now it’s time to come up with a good way of handling these extra items. I’ve set this up with our typical customers in mind and it handles the stuff we usually need. Obviously once you get to this level there is almost infinite scope for how you might handle things.
The Build Disc – Part 4b (wrap-up)
Posted by David in Build Disc, Unattended Installs on April 6th, 2009
Over the past week or so I’ve posted separate articles on each of the standard utilities that comprise the unattended installs portion of my standard build disc. Now I’m going to build on the starting point of unattended installs and talk about how to implement these installs as a component of the overall standard build.
The benefit of using unattended installs is that all of these tools get installed with no interaction required on my part. Just set it going and come back when its done. How did I do this? Largely be combining each silent install into a single batch file that does the whole install process.
Unfortunately, it’s not just a matter of doing a cut and paste on each item. In order to do this properly I need to work out which operating system I’m dealing with. For example, there’s no point trying to install Sidebar Gadgets under Windows XP.
The Build Disc – Part 4 (Standard Utilities)
Posted by David in Build Disc, Unattended Installs on March 29th, 2009
Standard Utilities:
A standard build needs to be able to be standardised. This means installing the same programs every time. With a standard install, you have to hit the “Next” button regularly and make other selections to get the software installed. This can become long and involved, it takes time. When you get busy, things get missed.
The goal for getting this installation standardised was to have all of these tools work as a silent/unattended install. The combination of this, and a scripted install, means that you can get through the complete install with minimum interaction.
The Build Disc – Part 3b (Heise)
Posted by David in Build Disc on March 29th, 2009
Using Offline Update:
(This article is written in reference to Offline Update v5.1 – it should remain relevant for other versions.)
It’s a two step process. First, you need to run the Offline Update tool, tell it what updates you’re interested in, and tell it to go and download them from Microsoft.
This process can take quite a bit of time, but you only need to do it once (or, at least, once for each new version of the Offline Update tool – about every 3-5 months or so).
At the end of this first step, Offline Update produces .iso image files (you’ll find them in the “ctupdateiso” directory) that you can burn to disc. Because I’m extending this I usually extract the created .iso images to combine with the other things I use on my build disc.