MST not applying all custom settings

Similar Threads:

1.New Exchange Server Setting Not Being Applied from MST Using C

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!

2.New Exchange Server Setting Not Being Applied from MST Using CIW

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!

3.Settings in MST File not Applied

Office 2003

I have created an MST file for Office 2003 using the Custom Installation
Wizard from the Office 2003 Resource Kit.  When I install Office 2003 using
the MST file, none of the custom settings in the MST file get applied.  For
example, the spell-checking options, grammar-checking options, and file
locations that I configured for Word in the MST file are not being applied
to the installed application.  In other words, what I am getting is the
default settings for each of the Office applications.

Also, I want to copy a custom Normal.dot file into the Templates folder, and
that's not happening either.

The MST file is in the same folder as the MSI file.  I am running the
installation using the MST file and the /qb command-line switch.  I do not
get any errors during the installation (although, I have not yet tried it
with the /qr command-line option).

Any ideas as to why the custom settings in the MST file are not getting
applied during installation?

Thanks for any help that you can offer.

--Tom

4.Custom view error - "Some view settings could not be applied"

I cannot determine why I get this error when I try to 
switch to a view I just created. There's nothing special 
going on in the worksheet. It's just a list which I have 
applied an Advanced Filter to, but which hides all non-
matching data. Is the Advanced Filter not compatible with 
Custom Views?

Thanks for any help you can offer.

Kimberly

5.e-mail security settings via custom form not being applied

I have two domains and two networks that are trusted and for all intents and 
purposes allow for seemless traffic flow.  I can logon to domain 1 when on 
domain 2's network/subnet and vica-versa, etc.  The one caveat presently 
being experienced is the ability to send email from a problem ticket tracking 
system when connected to domain 2, logged onto domain 2, but using an 
exchange account on domain 1.  I get prompted to authenticate to access the 
mailbox which is expected and can send messages, but the Outlook Security 
Settings public form settings are not being applied - I get the two prompts 
to permit the email action.  With the exact same scenario, but only changing 
that I'm connected on domain 1's network (still logged onto domain 2) I can 
send without prompt - the form is being applied.

Any thoughts on how this could be resolved would be much appreciated.

Cheers!

6. Office 2003: Custom Installation Wizard Settings Will Not Apply

7. Outlook 2003 MST not applying correctly

8. MST file does not apply correctly