I use the Custom Installation Wizard to edit the install options for our
Office 2003 installation. I am installing from an administrative share that
has been slipstreamed with Office 2003 SP2.

Our Exchange servers recently changed names, and I have a clean machine that
I am using to install Office 2003 with the new Exchange server name
configured (using the %username% variable). I have used the CIW to update
the .MST transform file to reflect the new Exchange server name (on page 18
of 24), however, when I install Office 2003 using the new .MST file, Outlook
still looks for the old Exchange server and errors out.

I've used MST files to set this setting in the past with no problems, but
when I try a new Office 2003 installation using the updated MST files, the
setting doesn't stick.

When I examine C:\Program Files\Microsoft Office\custom11.prf, I still see
the old Exchange server in there. So somehow, the original Office source
files are still holding on to that old setting. I even created a new, clean
MST file, only changing the Exchange server (on page 18 of 24) and it still
goes to the old server. I am using the following command-line to apply the
MST file:

\\server\office2003\setuppro.exe NOUSERNAME=True
TRANSFORMS="\\server\office2003\Custom.MST" /qb!

Creating and importing a custom PRF didn't work, either. I'm not concerned
about existing Office 2003 installations, just new installs. If anyone has
any info, please help!

Thanks in advance!

Just out of curiosity, I manually reinstalled Office 2003 straight from the
SETUPPRO.EXE without using a transform file and the old Exchange server
setting was still there. Where is Outlook getting this old server from?

When I search the registry for the old Exchange server, it shows up. But
when I uninstall Office 2003, and try searching the registry again for the
old Exchange server, it does not show up.

There's something about our administrative install source files that seems
to be perpetuating this old Exchange server name, whether or not you use a
transform (MST) file. Very strange.

-bhall

"bhall" wrote:

I use the Custom Installation Wizard to edit the install options for our
Office 2003 installation. I am installing from an administrative share that
has been slipstreamed with Office 2003 SP2.

Our Exchange servers recently changed names, and I have a clean machine that
I am using to install Office 2003 with the new Exchange server name
configured (using the %username% variable). I have used the CIW to update
the .MST transform file to reflect the new Exchange server name (on page 18
of 24), however, when I install Office 2003 using the new .MST file, Outlook
still looks for the old Exchange server and errors out.

I've used MST files to set this setting in the past with no problems, but
when I try a new Office 2003 installation using the updated MST files, the
setting doesn't stick.

When I examine C:\Program Files\Microsoft Office\custom11.prf, I still see
the old Exchange server in there. So somehow, the original Office source
files are still holding on to that old setting. I even created a new, clean
MST file, only changing the Exchange server (on page 18 of 24) and it still
goes to the old server. I am using the following command-line to apply the
MST file:

\\server\office2003\setuppro.exe NOUSERNAME=True
TRANSFORMS="\\server\office2003\Custom.MST" /qb!

Creating and importing a custom PRF didn't work, either. I'm not concerned
about existing Office 2003 installations, just new installs. If anyone has
any info, please help!

Thanks in advance!

I deleted C:\Program Files\Microsoft Office\custom11.prf and it didn't try to
pull the old Exchange server.

However, I still can't get it to auto configure the Exchange e-mail in
Outlook on first-run like I had previously setup. It simply starts the new
Outlook Profile wizard.

Anyone?


"bhall" wrote:


Just out of curiosity, I manually reinstalled Office 2003 straight from the
SETUPPRO.EXE without using a transform file and the old Exchange server
setting was still there. Where is Outlook getting this old server from?

When I search the registry for the old Exchange server, it shows up. But
when I uninstall Office 2003, and try searching the registry again for the
old Exchange server, it does not show up.

There's something about our administrative install source files that seems
to be perpetuating this old Exchange server name, whether or not you use a
transform (MST) file. Very strange.

-bhall

"bhall" wrote:

I use the Custom Installation Wizard to edit the install options for our
Office 2003 installation. I am installing from an administrative share that
has been slipstreamed with Office 2003 SP2.

Our Exchange servers recently changed names, and I have a clean machine that
I am using to install Office 2003 with the new Exchange server name
configured (using the %username% variable). I have used the CIW to update
the .MST transform file to reflect the new Exchange server name (on page 18
of 24), however, when I install Office 2003 using the new .MST file, Outlook
still looks for the old Exchange server and errors out.

I've used MST files to set this setting in the past with no problems, but
when I try a new Office 2003 installation using the updated MST files, the
setting doesn't stick.

When I examine C:\Program Files\Microsoft Office\custom11.prf, I still see
the old Exchange server in there. So somehow, the original Office source
files are still holding on to that old setting. I even created a new, clean
MST file, only changing the Exchange server (on page 18 of 24) and it still
goes to the old server. I am using the following command-line to apply the
MST file:

\\server\office2003\setuppro.exe NOUSERNAME=True
TRANSFORMS="\\server\office2003\Custom.MST" /qb!

Creating and importing a custom PRF didn't work, either. I'm not concerned
about existing Office 2003 installations, just new installs. If anyone has
any info, please help!

Thanks in advance!