Office 2003 Resource Kit Woes - Please Help!

I would like to deploy Office 2003 via a batch file though GPO.  That seems to be the easy part.  The part I'm having trouble with is getting my custom package to run.  I have used the Office 2003 Resource Kit to create a MST package for a custom roll-out.  I am trying to test it locally on my Windows XP Pro machine (currently with Office XP installed) first before I try it over the network.  I have to make sure this works before I can test everything though Group Policy.

When I run my batch file, I get this error:

Windows XP Setup
Please go to the Control Panel to install and configure system components.

I have the Office 2003 CD copied to C:\O2k3 on my local hard disk.  SETUPPRO.EXE, SETUPPRO.INI, PRO11.MSI, and COMPANY.MST are in the main directory.

Here is what my batch file file looks like:

setup.exe /i C:\O2K3\Pro11.msi TRANSFORMS=C:\O2K3\COMPANY.MST /qb-

Here is what my SETUPPRO.INI file looks like:

; Microsoft Office SETUP.EXE settings file.

; The MSI section gives the name of the MSI file to install. This file must be in
; the same folder as Setup.exe, and both must be in the root of the installation
; tree.

ProductName=Microsoft Office 2003

; The MST section gives the full path to a transform that should be applied.

; The option section is used for specifying individual Installer Properties.
;COMPANYNAME=my company

; The diplay section is used for overriding the default UI
;       Value           Default         Description
;       Display         full            Option to override the default UI
;                                       [none, quiet, basic, reduced, full]
;       CompletionNotice Yes            Option to display a setup completion
;                                       notice for otherwise quiet setup

; The logging section provides settings for controlling the Setup log files.
;       Value           Default         Description
;       Type            vpiwaeo         Logging modes  
;                                       [a, c, e, i, m, o, p, r, u , v,
;                                       w, *, +]
;       Path            %TEMP%          Path to create logfiles
;       Template        SetupLog(*).txt File name for log file should end in
;                                       "(*).txt"; the * is replaced with a 4
;                                       digit number to make the file name unique
Template=Microsoft Office 2003 Setup(*).txt
;Template=Product %UserName%(*).txt

; MinOSRequirement is used for defining the minimal OS requirement for
; installing the product.

; The cache section provides settings for caching the install source locally
;       Value           Default         Description
;       CDCACHE            2             Option to specify cache level
;                                       [auto, 0, 1, 2]
;       LOCALCACHEDRIVE <predefined>    Option to specify a drive to cache
;                                       the install source to
;       DELETABLECACHE  1                Option to display UI to remove the
;                                       cache at the end of setup [0,1]
;       PURGE           0               Option to always remove cache at end of
;                                       setup [0,1]


Any idea why I'm getting the error message?  It has to be someting simple that I am overlooking, at least I hope so.   Thanks in advance.
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.

XP pro really isn't set up to test a deployment like this. There are some things that it's much better to test outside of your live environment if you can, but unless you've got a separate server or vmware for example it's not always practical. This you can test on your live network relatively safely so long as you use a completely separate OU for the testing.

First you need an administrative installation point - so follow link 1 on how to do that as you may as well slipstream sp1 into the office deployment whilst you're at it. The instructions are pretty good. Once you have your shared folder on a server containing the admin install, ensure it's shared and that either domain computers or a test pc you are going to use has access to it in relation to the permissions set on that shared folder.

Next use the office custom install wizard to create a new office transform file that you're happy with and save it in the same folder as your office install. You'll need the resource kit and custom installation wizard to do that as in link no. 3.

Than create a new and separate OU. In the computer configuration, go to the software installation section and choose new. Assign the package rather than publish it, and make sure the paths to the installation point and transfrom .mst file are in the form


You can set this by simply navigating through My network places rather than through the drives.

Make sure that you use advanced options and assign to use the custom transform as a modification in software installation settings, and also ensure that either domain computers or a specific test pc that you're using has read and apply group policy permissions on the gpo, and move your test pc into that OU. If you're running xp pro as a test pc, also make sure that the policy "wait for network at startup and logon" is also enabled in group policy for that OU.

Then try running gpupdate /enforce from a command prompt on the workstation to test it.
Some useful links:

Office System (2003) SP1 Slipstreaming
Pushing out Office Via group Policy
Office 2003 Editions Resource Kit + Other Tools
VMware Workstation 4.5 - One month full evaluation free

Let us know how you get on

Deb :))
One more - This stops XP pro starting up prior to applying all the group policy features etc. as in "wait for network at startup and logon"
Description of the Windows XP Professional Fast Logon Optimization Feature
mb2010Author Commented:
Yes.  I know how to setup a group policy and I know how to set an installation point on a server.  That is the easy part.  At this point, I am concearned with getting Office 2003 to install with the custom MST package.  I want to run the batch file locally on my computer before I bother running with a GP on a test OU.  Any idea where I am going wrong there?  Why does it spit out that error when I run the batch file?  Thanks.
Cloud Class® Course: Certified Penetration Testing

This CPTE Certified Penetration Testing Engineer course covers everything you need to know about becoming a Certified Penetration Testing Engineer. Career Path: Professional roles include Ethical Hackers, Security Consultants, System Administrators, and Chief Security Officers.

Looks like I missed the point slightly - it was a long day yesterday: Did you setup an admin installation point on your pc at C:\O2k3 ? It won't run against a cd copy and it's not clear if you did that or not.
mb2010Author Commented:
When you say "admin installation point", do you mean "Path=C:\O2K3\PRO11.MSI" in the .ini file?  Just so you know, I am not running it from the CD.  I have all of the CD copied to "C:\O2k3".  Thanks.
Did you create an admin install of office in the folder you're testing your script against ie C:\02k3 - If you just copy the content from the Office CD this script setup.exe /i C:\O2K3\Pro11.msi TRANSFORMS=C:\O2K3\COMPANY.MST /qb- apparently doesn't work - The error message you're getting is effectively saying if you want to install this you'll need to do it from the control panel, which obviously isn't what you want to do.

From my link:
Step 1: Perform an administrative installation

Instead, use the following steps:

Insert the Office System (2003) CD into your drive, from the "Start" button select "Run" and type
x:\setup.exe /a

Note: X: is the physical drive your CD drive is assigned. Notice there is a space between the "setup.exe" and the "/".

This is going to start the install process of Office 2003. You'll be presented with the option of where you want the files to go (I chose "C:\Office2003"), and you'll be asked to enter your CD key.....

Just trying to figure out if you did this..


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
mb2010Author Commented:
I am doing that now.  We are making progress.  :-)  I did not realize I could not copy directly from the CD.  I am checking out your first link above and will try the slipstream too.  I will get back to you.
Ok - good luck!
mb2010Author Commented:
It looks like everything is set.  I have a test OU with a test policy.  I have forced a GP update on the client computer that is in the test OU.  I have rebooted teh client machine, logged in as the end user, and do not notice any changes yet.  How will I know the software is installing?
You need to make sure that this is set in XP Pro:
Description of the Windows XP Professional Fast Logon Optimization Feature

and that the test pc is in the OU that the policy's attached to. Domain computers need read and apply group policy rights on the gpo, and rights of access to the folder containing the install. You may need to reboot again - or run a gpupdate /force - you'll know because it tells you on the pc that the managed software is being installed
mb2010Author Commented:
Okay.  Everything is setup and running with the MST package through a test OU.  All Office 2003 applications run fine except for Outlook.  

When you try to launch Outlook it gives the following error.
Microsoft Office Outlook
The operation failed due to an installation problem.  Restart Outlook and try again.  If the problem persists, please reinstall.
I have tried it on both a Windows XP and a Windows 2000 box with Office XP already installed.
I may have to play with the Outlook settings in that MST package some more.  What do you think?

Sounds like a problem with the Outlook setup settings in the MST - I'd try one with all defaults left as they are to make sure it goes in ok - are you setting anything unusual with Outlook - like changing the location of pst's or Outlook address books or using cached mode?
mb2010Author Commented:
There were thoughts that the problem below might involve a profile issue.  I tried to create a new profile and received the following error when the profile wizard tries to detect the user account on the specified Exchange server:
Control Panel
An error occurred while Windows was working with the Control Panel file
I am thinking it could be either the MST like you mentioned OR that one of the Slipstream service pack installs did not go well.  Thanks for all the help.  Debsyl99: I'm thinking about upping the points for you since you've been with me from the start on this.  I'll do some more testing and get back to you.
Hmm - Glad to help - mine went in pretty well (still only in a test environment with it as yet though) - but I did have some problems with Outlook, although not this specific one. Mine were related to profiles needing to be local (app data won't roam when it comes to Outlook 2k3). I tried googling for this and couldn't find anything of much relevance. Anything in the application event logs on the client after you get the error message?

If it's any use I can post the configuration I used in my test .mst - wasn't too massive so it won't swamp the boards, but it does work so let me know. Also check that you don't have any other group policies applied to your test OU as it can interfere,
P.S I stuck with it because I know first-hand what a little **** of a deployment it can be! ;-))
mb2010Author Commented:
The problem had everything to do with the post SP1  patches I tried installing via slipstream package.  When I started over and went with only the SP1 slipstream it worked great.  I think, next, I will try to figure a way to install the addtional patches after the initial software is installed.
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
Windows Networking

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.