U
User
I'm brand new to Outlook and have an installation question. My
organization has a need to install about 150 new copies of Outlook
2003. I started with a manual install from the CD media and had no
problems, so I began work on scripting the installation on a clean
machine.
First, I ran "setupolk.exe /a" from the Office 2003 CD and created an
administrative installation point on a network drive with development
space, L:\Develop\Outlook. I then loaded the Office 2003 Resource Kit
and used the Custom Installation Wizard to create an .mst transform.
I essentially made no changes to the defaults on any of the 24 steps.
I ensured that all of the components selected to install by default
were what should be a Typical install and saved Outlook.mst.
After running "L:\Develop\Outlook\setupolk.exe
TRANSFORMS=L:\Develop\Outlook\Outlook.mst /qb-" I was surprised by the
fact that although the installation reported a success, Outlook had
not been installed. I thoroughly checked the command-line and then
finally just ran the setup.exe in the foreground. As I stepped
through the installation options, I found that somehow in a "Typical
installation" that the Outlook component shows a red X and says "(Not
Available)." However, if I go back and select a Custom install, all
components are available and Outlook installs successfully.
Does anyone have any relevant experience that might shed some light on
where I've gone wrong? Why in the world in an Outlook installation
would a Typical install not include Outlook??? I have to think I'm
missing something somewhere in either creating the admin installation
point or within the CIW.
Thanks in advance for any help this forum can provide. Thanks!
Tim
organization has a need to install about 150 new copies of Outlook
2003. I started with a manual install from the CD media and had no
problems, so I began work on scripting the installation on a clean
machine.
First, I ran "setupolk.exe /a" from the Office 2003 CD and created an
administrative installation point on a network drive with development
space, L:\Develop\Outlook. I then loaded the Office 2003 Resource Kit
and used the Custom Installation Wizard to create an .mst transform.
I essentially made no changes to the defaults on any of the 24 steps.
I ensured that all of the components selected to install by default
were what should be a Typical install and saved Outlook.mst.
After running "L:\Develop\Outlook\setupolk.exe
TRANSFORMS=L:\Develop\Outlook\Outlook.mst /qb-" I was surprised by the
fact that although the installation reported a success, Outlook had
not been installed. I thoroughly checked the command-line and then
finally just ran the setup.exe in the foreground. As I stepped
through the installation options, I found that somehow in a "Typical
installation" that the Outlook component shows a red X and says "(Not
Available)." However, if I go back and select a Custom install, all
components are available and Outlook installs successfully.
Does anyone have any relevant experience that might shed some light on
where I've gone wrong? Why in the world in an Outlook installation
would a Typical install not include Outlook??? I have to think I'm
missing something somewhere in either creating the admin installation
point or within the CIW.
Thanks in advance for any help this forum can provide. Thanks!
Tim