Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1313
  • Last Modified:

how to roll out office 2k3 and auto configure exchange boxes

hey everyone
i have about 130 pcs mixed with office 2000 and 2003.  they are all configured for email on our exhcange server here on the lan.
Windows 2000 Domain controller and 4 windows 2003 servers.

I need help with a couple of things

1. some of my machines on the network run office 2000. i need to upgrade these to 2003.
how can i do this without having to go and touch each computer physically. and without loosing any exchange email settings.

2. if i have a user who is always logging into a different computer how can i configure outlook so that when the users logs into the network his outlook is automatically configured and i dont have to go over there and configure outlook to use exchange and give the servername and username. i image my machines using norton ghost so im not sure if it has something to do with the original image and how office is installed.

here is the problem, some of these machines had office installed from the cd rom drive on their computer and some of them off a network share..
thank you!
  • 4
  • 3
  • 2
1 Solution
Use the office 2003 resource kit to create an automated installation of Office 2003, download from the link:
http://thesource.ofallevil.com/downloads/details.aspx?FamilyID=4bb7cb10-a6e5-4334-8925-3bcf308cfbaf&DisplayLang=enom installation Wizard
Once you install it you must run the Custom Installation Wizard.
This will allow you to create an office install with exchange settings preset (Make sure you set %username% as the username)

The ORK will create a mst file that you can apply to an office installation. I would create a network share and either use a manual install path to install or use group policy to install as when you add a package to a group policy you have the option when you initially create it to add a transform to the installation and this will force out a customized install or you can install using the following path
<path to installation>\setup.exe TRANSFORMS=<path to mst file>\<name of Mst file> /qb+

You can run the above on individual machines to install office if you do not want to use a policy.

ORK based office installs will upgrade previous versions of office just fine but if you try to install it over the same version you may run into issues. In the past I would create clean build machines to replace machines which had been installed with a CD install of office 2003. But you may be able to fix existing versions of office 2003 by using the custom maintenance wizard but I have never tried it.
I would try creating and deploying custom installs in a test environment first if I were you. It took me a few times to customize the install just the way I wanted it.
yalemortAuthor Commented:
when i am using the custom installation wizard where to i set the %username% im at the screen where it says CHANGE OFFICE USER SETTINGS
What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

You will go a few steps past that page and to the page that says Outlook: Customize Default Profile. Make sure you select modify profile. On the next page select Configure an Exchange server connection. Under User Name put %username% and put your exchange server name under server (If you have multiple exchange servers you can put any exchange server name in the same organization).

Hope that helps.

Additional note: On the Modify Setup properties near the end make sure you set ALLUSERS value to 1. This has something to do with how the installation behavior acts. It has been a few years since I had to research why I set this property but I know in the long run it will make the automation of the installation a bit easier to deal with. I think it may have to do with being easier to deal with multiple users on the same computer.
Hi valemort

I'd recommend using a Cached Installation that way you can chain all Post Office 2003 Hotfixes + the Office 2007 Compatibility Pack into the one install.  It also benefits your users because they no longer have to rely off either an Adiminstative Installation Point or CD, for future Office Updates for e.g. future Service Packs.  Here's some instructions I wrote for the company I work for:

Create a Directory on your computer for e.g. C:\MSOffice_2003
Copy your Office 2003 Contents from the CD to this directory.

Create a Directory on your computer for e.g. C:\MSOffice_2003\Add-Ons\MSOffice.2007\
Download MSOffice 2007 Compatibility Pack http://www.microsoft.com/downloads/details.aspx?FamilyId=941b3470-3ae9-4aee-8f43-c6bb74cd1466&displaylang=en
Save to C:\MSOffice_2003\Add-Ons\MSOffice.2007\

Download Microsoft® Office 2003 Resource Kit http://download.microsoft.com/download/0/e/d/0eda9ae6-f5c9-44be-98c7-ccc3016a296a/ork.exe
ORK.exe 7.3mb
Install selecting Complete Install using the defaults.

Download Microsoft Office ENTSetup.exe Advanced Setup.exe for Compressed Installation Images
Save this file and extract the Setup.exe to C:\MSOffice_2003 rename Setup.exe to MSOFFICE.exe

Create a Directory on your computer and download the latest updates for Office to this folder for e.g. C:\MSOffice_Updates

Extract the files using Winzip or 7zip to C:\MSOffice_2003\Files\Patches or use a commandline for e.g.
C:\MSOffice_Updates\Office2003-kb885828-client-enu.exe /c /t: C:\MSOffice_2003\Files\Patches

Rename the extracted Filename.MSP file to KBxxxxxx-Filename.MSP
For eg the Office2003-kb885828-client-enu.exe above has a MSP file MSOop.MSP
Rename the MSOop.MSP to KB885828-MSOop.MSP
You will notice updates will be in sequence starting from the Microsoft Office 2003 SP1 or SP2 depending on which version you wish to use for e.g. Office 2003 SP1 is Office2003SP1-kb842532-client-enu.exe
Why do this, because when we apply the hotfixes the OHotFix tool will apply all the MSP files in the C:\MSOffice_2003\Files\Patches folder in alphabetical order.  An problem will occur if a MSP file tries to run before another dependant update has been run, for eg, the Service Pack 1 Patch.

After all Updates have been extracted and renamed, navigate to C:\MSOffice_2003\Files\Patches\ and open the OHotFix.ini with Notepad
Note: Edit the OHotFix.ini with the following settings; Do not display the success dialog and Do not automatically reboot the computer if a reboot is required in quiet mode. (see below)

------ Start Here ------

; A final dialog can be displayed to indicate that the update was applied
; successfully.  This dialog will only be displayed if ShowSuccessDialog is
; set to 1 and OHotfixUILevel is set to n.
; 1 = Display the success dialog.
; 0 = Do not display the success dialog.

; If OhotfixUILevel is set to q and IsNormalUpdate is set to 1,
; Ohotfix can automatically reboot the computer if a reboot is required
; to complete the installation.
; 1 = Automatically reboot the computer if a reboot is required in quiet mode.
; 0 = Do not automatically reboot the computer if a reboot is required
;     in quiet mode.

------ End Here ------

Create yourself a MST file with the Custom Installation Wizard found in Start - Programs - Microsoft Office 2003 Resource Kit
At Step 23 of 24
Select NOFEATURESTATEMIGRATION - Do not match feature states during the installation

Once completed

Open C:\MSOffice_2003\Files\Setup\
Create a copy of PRO11.XML and rename to MSOFFICE.XML
Create a copy of SETUPPRO.INI and rename to MSOFFICE.INI
Edit the MSOFFICE.INI similar to the following

------ Start Here ------

; 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.
;MST1=\\server\share\some transform.mst
;MST1=D:\transforms\my transform.mst

; 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]


; Note if you wish to install the MSOffice 2007 Compatibility Pack than you can do it within the install itself just uncomment the following 4 lines


------ End Here ------

Now save the C:\MSOffice_2003\ folder to \\SERVER\SHARE\, now all you need to do is run MSOFFICE.EXE no switches, because this is handled from the MSOFFICE.INI file.

In addition to the information above for your Exchange Information please use the following:

Step 17 of 24  Customize Default Profile
Select New Profile
Type Profile Name: CustomPRF

Click Next to continue

Step 18 of 24  Specify Exchange Settings
Select Configure an Exchange Server connection
Type User Name: %UserName%
Type Exchange Server: \\Exchange\Domain.com

Click More Settings

Step 18 of 24  Specify Exchange Settings
Leave Blank

Click OK and Next to Continue

Step 19 of 24  Outlook Add Accounts
Select Do not customize Outlook profile and account information

Click Next to continue

Step 20 of 24  Remove Accounts and Export Settings
Click Export Profile Settings& button

Step 20 of 24  Remove Accounts and Export Settings
Type File name: CustomPRF.PRF to C:\Program Files\Microsoft Office\ Directory
Click Save


Open Windows Explorer
Navigate to C:\Program Files\Microsoft Office\ and open the CustomPRF.PRF with Notepad

In order to avoid creation of duplicate profile entries, the following is required in Section 1 of the PRF file

Note: Edit the CustomPRF.PRF with the following settings:

;Automatically generated PRF file from the Microsoft Office Customization and Installation Wizard

; **************************************************************
; Section 1 - Profile Defaults
; **************************************************************



Click Back x 9 to Step 11 of 24 to continue

Step 11 of 24  Add/Remove Files
Click Add&

Navigate to and select CustomPRF.PRF from C:\Program Files\Microsoft Office\ Directory
Click Add

Select <ProgramFiles\Microsoft Office> from Destination path on the users computer: drop down list.

Click OK
Click Next x 6 to Step 17 of 24 to continue

Step 17 of 24  Customize Default Profile
Select Apply PRF:
Type Apply the following profile (PRF file): C:\Program Files\Microsoft Office\CustomPRF.PRF

Click Next to continue

Step 21 of 24  Customize Default Settings
Tick Customize Outlook e-mail defaults
Select Default e-mail editor: Outlook
Select Default e-mail format: html

Click Next to continue

Step 22 of 24  Outlook: Specify Send/Receive Group Settings (Exchange Only)
Select Do not configure Send/Receive Settings

Click Next to continue

Now you can push this out to all your clients via login script or a shortcut with the following command.

Outlook.exe /importPRF \\Server\Share\CustomPRF.PRF

All Done.  Cheers

Hope that helps

yalemortAuthor Commented:
matrixnz thank you so much for your help, its very detailed but it seems a little too complex.
im just trying to deploy an office installation to computers that do not have office at all or are using office 2003.  in that deployment i want to be able port over there exchange settings.
i also want to setup oulook so that when any new user logs into a computer outlook is automatically configured for them. i dont have to setup outlook to use exchange.
i am trying what chuck suggested on my virtual pc, what i was able to do is with a custom.mst is apply teh service pack 3 to office, and also when i ran the following line:
setup.exe TRANSFORMS=E:\office\install\yale-custom.MST /qb-
on the vpc that already had office 2003 with sp2 installed(outlook was not configured at all), all it did was install sp3, it did not configure outlook to automatically configure the exchange mailbox.
so when i removed office from teh vpc, and created a shortcut to a .bat file with that commmand line, it installed office with service pack 3 adn configured it properly for outlook to automatically configure exchange.
Here are my questions,
how come it didnt configure the outlook settings when i ran the line on the vpc with office already installed? (which is the case in all my computers here)
also is this going to reinstall office everytime a user logs in? how would i deploy that line, do i need to use the active directory software deployment?
im going to install office 2000 now and see if it upgrades it and ports over the exchange settings.
Setting Exchange settings in the CIW (Custom Installation Wizard) will not work on installs that already have the same version. It will work on installs that have previous versions of office on it. So a custom install will work on your upgrades from office 2000.

For existing installs of office 2003 try the custom maintenance wizard. It will allow you to recustomize existing installs. I have only used it to change my exchange server and automatically create a pst file. So if you have many computers with different installs of office 2003 I do not know what your outcome will be.But you can test it out.
Hi yalemort

There are two things from my instructions that you need:

1. The NoFeatureStateMigration bit, basically what happens in a normal install is Office uses the last Office installation to install features so for example if you had Office 2000 and only installed word, excel, outlook, but the new install you wished to install word, outlook, the Office 2003 will still install word, excel and outlook if you haven't set NoFeatureStateMigration.

2. My Second post regarding the PRF creation, this is where you setup your Exchange information, if you don't want to use this within your install then just create the PRF and use a logon script to deploy i.e. Outlook.exe /importPRF \\Server\Share\CustomPRF.PRF

I'd also recommend attempting some of the instructions above, it may look daunting but most of it is fairly straight forward.  If you get stuck I'm happy to help.


Featured Post

Upgrade your Question Security!

Your question, your audience. Choose who sees your identity—and your question—with question security.

  • 4
  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now